Package: insserv Version: 1.14.0-2 Severity: important Hi,
In our squeeze-based cluster enabling dependency-based booting causes certain daemons to have different SigIgn masks -- more to the point, they start ignoring SIGINT. As you can imagine that has all kinds of implications (for the daemons and the processes they start). Here is the symptom (ran on one of our compute nodes): root@snake1:~# cat /proc/*/status | grep "\(SigIgn\|Name\)" |egrep -B1 "[0-9a-f][0-9a-f]+2$" Name: ypbind SigIgn: 0000000000000002 -- Name: condor_master SigIgn: 0000000000001002 -- Name: condor_startd SigIgn: 0000000000001002 -- Name: exim4 SigIgn: 0000000000001002 -- Name: cron SigIgn: 0000000000000002 -- Name: sshd SigIgn: 0000000000001002 root@snake1:~# grep CONCURRENCY /etc/init.d/rc |head -n1 CONCURRENCY=makefile As soon as I set CONCURRENCY to 'none' there is not a single process ignoring SIGINT running on the fully booted system. The SigIgn mask can be fixed by simply restarting the daemons after the system is fully booted -- for each and every single one: root@snake1:~# invoke-rc.d condor restart Shutting down Condor (fast-shutdown mode)... done. Starting up Condor... done. root@snake1:~# cat /proc/*/status | grep "\(SigIgn\|Name\)" |egrep -B1 "[0-9a-f][0-9a-f]+2$" Name: ypbind SigIgn: 0000000000000002 -- Name: exim4 SigIgn: 0000000000001002 -- Name: cron SigIgn: 0000000000000002 -- Name: sshd SigIgn: 0000000000001002 root@snake1:~# invoke-rc.d exim4 restart Stopping MTA for restart: exim4_listener. Restarting MTA: exim4. root@snake1:~# cat /proc/*/status | grep "\(SigIgn\|Name\)" |egrep -B1 "[0-9a-f][0-9a-f]+2$" Name: ypbind SigIgn: 0000000000000002 -- Name: cron SigIgn: 0000000000000002 -- Name: sshd SigIgn: 0000000000001002 root@snake1:~# invoke-rc.d crom restart invoke-rc.d: unknown initscript, /etc/init.d/crom not found. root@snake1:~# invoke-rc.d cron restart Restarting periodic command scheduler: cron. root@snake1:~# cat /proc/*/status | grep "\(SigIgn\|Name\)" |egrep -B1 "[0-9a-f][0-9a-f]+2$" Name: ypbind SigIgn: 0000000000000002 -- Name: sshd SigIgn: 0000000000001002 root@snake1:~# invoke-rc.d ypbind restart invoke-rc.d: unknown initscript, /etc/init.d/ypbind not found. root@snake1:~# invoke-rc.d nis restart Stopping NIS services: ypbind ypserv ypppasswdd ypxfrd. Starting NIS services: ypbind. root@snake1:~# cat /proc/*/status | grep "\(SigIgn\|Name\)" |egrep -B1 "[0-9a-f][0-9a-f]+2$" Name: sshd SigIgn: 0000000000001002 We have some indication that not only our cluster is affected (several condor user report SIGINT-ignore related problems on Debian squeeze). However there are also clusters that are not affected -- even with dependency-based booting enabled. Therefore there a chance that this is caused by something other than insserv. However, given the number of daemons affected, I decided to report this here. In any case, I can reliably change the SigIgn masks for all these daemons by enabled/disabling dependency-based booting -- and this should probably not be happening. Thanks, Michael -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/24 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages insserv depends on: ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib insserv recommends no packages. Versions of packages insserv suggests: pn bootchart <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
