Bugzilla – Bug 124869
"kill signal [missing]"
Last modified: 2006-02-01 22:36:42 UTC
During rebooting or shutting down SUSE i noticed that "kill signal" is "missing" (in red) instead of "done" (in green). But i did not notice any problems because of it. It seems to be simple status/info bug. I had this bug also in SUSE 9.3 but i thought it was not very important. Now it looks like the same error.
Hmmm .. which boot script does show this message. Please check this because I do never have seen this message. Btw: Are you using you're own or an foreign boot script?
I see this message just after default install when i reboot or shut down system. I didn't change any scripts, all settings are deafult. I saw on suse forum that some users have the same error but noone knows what does it mean http://forums.suselinuxsupport.de/index.php?showtopic=18103
Please set in the configuration file /etc/sysconfig/boot the variable RUN_PARALLEL to no and reboot. Now you should be able to see _which_ script cause this message.
Sorry i did it and there is no new information so i can't see which sript is "guilty".
But the message is visible? Please report the lines above and below the message.
It looks this way; (...) Sending all processes the Term signal ... [done] Sending all processes the Kill signal ... [done] #here are few blank lines, the first line has red info : [missing] #nothing here, just blank line [done] #nothing here, just blank line [done] Restore device permissions [done] Turning off swap [done] Set Hardware Clock to the current system time [done] (...) I can't see what are these blank lines, there is simply no message at all, just blank lines and one red [missing].
Created attachment 53625 [details] Temporary replacment for /etc/init.d/halt OK, lets try to debug this. Therefore please could you move the current script /etc/init.d/halt to the root's home: mv /etc/init.d/halt /root/ Then please copy the attachment to /etc/init.d/halt and run chmod 755 /etc/init.d/halt and reboot. Please provide the messages before and after the `missing' message. After that you should do mv /root/halt /etc/init.d/halt to get back the old halt script. Thanks
Ok, now there is a lot of output but i have no idea how to save it. This reboot/shutdown procedure takes so fast i can't even write down it. Please could you give me some advice how to save this output?
Hmmm ... I've added line like echo After ... into the halt script. Just go to the last line and add a sleep 60 after the echo. This provides you 1 minutes to read and write.
Here it is: (...) Sending all processes the Term signal ... [done] Sending all processes the Kill signal ... [done] Before /dev/tty1 After /dev/tty1 Before /etc/init.d/boot.d/K12boot.ipconfig After /etc/init.d/boot.d/K12boot.ipconfig Before /etc/init.d/boot.d/K13boot.isapnp After /etc/init.d/boot.d/K13boot.isapnp Before /etc/init.d/boot.d/K12boot.sysctl After /etc/init.d/boot.d/K12boot.sysctl Before /etc/init.d/boot.d/K14SuSEfirewall2_init #here is a blank line and at the end of this line is red word "missing" After /etc/init.d/boot.d/K14SuSEfirewall2_init Before /etc/init.d/boot.d/K14boot.ldconfig After /etc/init.d/boot.d/K14boot.ldconfig Before /etc/init.d/boot.d/K14boot.preload After /etc/init.d/boot.d/K14boot.preload Before /etc/init.d/boot.d/K15boot.idedma After /etc/init.d/boot.d/K15boot.idedma (...) Everything looks fine instead of these lines with "K14SuSEfirewall2_init"
Ah ... OK. Don't forget to move the old halt script back and many thanks for your help. IMHO the script /etc/init.d/SuSEfirewall2_init should do nothing if called for stop action.
Np, I hope it will be helpful.
fixed for 10.1
(In reply to comment #13) > fixed for 10.1 > Could this bug be fixed for 10.0 too? If it could not, please, could you post a simple way to fix it and I will fix it myself?