Project

General

Profile

Bug #42737

Unblock SIGCHLD to prevent too many smartd processes

Added by Martin Herrman 8 months ago. Updated 4 months ago.

Status:
Done
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No
Tags:

Description

I first noticed this in 11.1-U5 and it remains in 11.1-U6. It could happen in previous versions as well.

The number of smartd-daemon processes after 1-2 days of uptime is around 20-30, and was around 42 after a much longer uptime.

root@freenas:~ # ps aux | grep smart
root 2825 0.0 0.0 8656 4360 - Is Wed20 0:00.30 /usr/local/sbin/smartd -n -i 1800 -c /usr/local/etc/smartd.conf -p /var/run/smartd-daemon.pid
root 7827 0.0 0.0 7096 3360 - I Wed20 0:00.06 /bin/sh /usr/sbin/service smartd-daemon status
root 7966 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 7967 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 7980 0.0 0.0 7096 3360 - I Wed20 0:00.06 /bin/sh /usr/sbin/service smartd-daemon status
root 8080 0.0 0.0 7096 3360 - I Wed20 0:00.06 /bin/sh /usr/sbin/service smartd-daemon status
root 8163 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8166 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8263 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8264 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8452 0.0 0.0 7096 3360 - I Wed20 0:00.06 /bin/sh /usr/sbin/service smartd-daemon status
root 8592 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8593 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8598 0.0 0.0 7096 3360 - I Wed20 0:00.06 /bin/sh /usr/sbin/service smartd-daemon status
root 8736 0.0 0.0 7096 3360 - I Wed20 0:00.06 /bin/sh /usr/sbin/service smartd-daemon status
root 8742 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8749 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8883 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 8884 0.0 0.0 7096 3360 - I Wed20 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 11542 0.0 0.0 7096 3360 - I 20:49 0:00.06 /bin/sh /usr/sbin/service smartd-daemon status
root 11687 0.0 0.0 7096 3360 - I 20:49 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 11688 0.0 0.0 7096 3360 - I 20:49 0:00.00 /bin/sh /usr/sbin/service smartd-daemon status
root 62454 0.0 0.0 6696 2596 0 S+ 20:43 0:00.00 grep smart
root@freenas:~ # ps aux | grep smart | wc -l
23

I have 4 disks and enabled the smartd daemon in services.

I have attached a screenshot of the disks and my smartd configuration.


Related issues

Copied to FreeNAS - Bug #50786: Unblock SIGCHLD to prevent too many smartd processesDone
Copied to FreeNAS - Bug #50797: Unblock SIGCHLD to prevent too many smartd processesDone

Associated revisions

Revision c2651164 (diff)
Added by Vladimir Vinogradenko 7 months ago

Unblock SIGCHLD before running /usr/sbin/service, in rare cases this can lead to
request hang, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231933

Ticket: #42737

History

#1 Updated by Dru Lavigne 8 months ago

  • Private changed from No to Yes
  • Reason for Blocked set to Need additional information from Author

Martin: please attach a debug (System -> Advanced -> Save debug) to this ticket.

#2 Updated by Martin Herrman 8 months ago

  • File debug-freenas-20180827205953.tgz added

Dru Lavigne wrote:

Martin: please attach a debug (System -> Advanced -> Save debug) to this ticket.

See attachment!

#3 Updated by Dru Lavigne 8 months ago

  • Category changed from Services to Middleware
  • Assignee changed from Release Council to William Grzybowski
  • Reason for Blocked deleted (Need additional information from Author)

#4 Updated by William Grzybowski 8 months ago

  • Assignee changed from William Grzybowski to Vladimir Vinogradenko

#5 Updated by Vladimir Vinogradenko 8 months ago

Martin, I was not able neither to reproduce the issue nor deduce its cause from provided debug. Can you please post output of

ps auxww -d

Also it would be very helpful if we could arrange TeamViewer session and I can inspect your FreeNAS installation directly.

#6 Updated by Dru Lavigne 8 months ago

  • Status changed from Unscreened to Blocked
  • Reason for Blocked set to Need additional information from Author

#7 Updated by Martin Herrman 7 months ago

  • File psauxwwd.txt added

Vladimir Vinogradenko wrote:

Martin, I was not able neither to reproduce the issue nor deduce its cause from provided debug. Can you please post output of

[...]

Also it would be very helpful if we could arrange TeamViewer session and I can inspect your FreeNAS installation directly.

Hi Vladimir,

thanks for trying to reproduce it. I have attached the output of ps auxww -d.

Timewise it is hard for me to schedule a teamviewer session, but I could temporarily provide you VPN access to my home network and an account on the freenas box. Would that work out for you?

#8 Updated by Bug Clerk 7 months ago

  • Status changed from Blocked to In Progress

#9 Updated by Vladimir Vinogradenko 7 months ago

Martin, thank you for your help, problem solved!

#10 Updated by Martin Herrman 7 months ago

Vladimir Vinogradenko wrote:

Martin, thank you for your help, problem solved!

Nice work!

#11 Updated by Dru Lavigne 7 months ago

  • File deleted (debug-freenas-20180827205953.tgz)

#12 Updated by Dru Lavigne 7 months ago

  • File deleted (psauxwwd.txt)

#13 Updated by Dru Lavigne 7 months ago

  • Private changed from Yes to No
  • Reason for Blocked deleted (Need additional information from Author)

#14 Updated by Dru Lavigne 7 months ago

  • Target version changed from Backlog to TrueNAS 11.1-U6.2

#15 Updated by Bug Clerk 7 months ago

  • Status changed from In Progress to Ready for Testing

#16 Updated by Bug Clerk 7 months ago

  • Copied to Bug #50786: Unblock SIGCHLD to prevent too many smartd processes added

#17 Updated by Bug Clerk 7 months ago

  • Copied to Bug #50797: Unblock SIGCHLD to prevent too many smartd processes added

#18 Updated by Dru Lavigne 6 months ago

  • Subject changed from Too many smartd-daemon processes to Unblock SIGCHLD to prevent too many smartd processes
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#19 Updated by Dru Lavigne 5 months ago

  • Target version changed from TrueNAS 11.1-U6.2 to 11.1-U7

#20 Updated by Caleb St. John 4 months ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

#22 Updated by Dru Lavigne 4 months ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF