Bug 124869

Summary: "kill signal [missing]"
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Rafał Polak <rafpolak>
Component: BasesystemAssignee: Ludwig Nussel <lnussel>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: SUSE Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Temporary replacment for /etc/init.d/halt

Description Rafał Polak 2005-10-10 23:15:24 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.
Comment 1 Dr. Werner Fink 2005-10-11 09:18:10 UTC
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?
Comment 2 Rafał Polak 2005-10-11 09:44:14 UTC
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
Comment 3 Dr. Werner Fink 2005-10-11 10:09:34 UTC
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.
Comment 4 Rafał Polak 2005-10-11 10:45:16 UTC
Sorry i did it and there is no new information so i can't see which sript is
"guilty".
Comment 5 Dr. Werner Fink 2005-10-11 11:24:07 UTC
But the message is visible?  Please report the lines above and
below the message.
Comment 6 Rafał Polak 2005-10-11 11:48:49 UTC
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].
Comment 7 Dr. Werner Fink 2005-10-11 13:12:41 UTC
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
Comment 8 Rafał Polak 2005-10-11 16:27:00 UTC
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?
Comment 9 Dr. Werner Fink 2005-10-11 16:33:49 UTC
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.
Comment 10 Rafał Polak 2005-10-11 17:50:53 UTC
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"
Comment 11 Dr. Werner Fink 2005-10-12 09:19:58 UTC
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.
Comment 12 Rafał Polak 2005-10-12 09:42:41 UTC
Np, I hope it will be helpful.
Comment 13 Ludwig Nussel 2006-01-03 10:44:27 UTC
fixed for 10.1
Comment 14 Rafał Polak 2006-02-01 22:36:42 UTC
(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?