RE: Anyone have problems with shutdown not working properly?

Rick Warner [mailto:[email protected]]wrote:

>> Unfortunately this Linux server runs Continuus(Telelogic's CM/CS) and
their
>> fix for us when too many application processes get running and thus lock
out
>> 'doze users is to restart xinetd(doesn't work) or reboot.  This happens
at
>> least twice a week!  Granted this is dumb, but hey I just started here a
>> couple of months ago and so I have to live with what they tossed me.
BTW,
>> Telelogic hasn't been very helpful in this matter other than saying
upgrade
>> your JRE - no effect - So, we don't have the problem in the new version
>> coming out in April that is supported under RH8!  I love it!  Makes me
feel
>> like I'm running an NT server and dealing with M$.
>
>Continuus?  Blechhhh.   Informix backend I take it is the shutdown issue.
>A couple of questions come to mind.  But first, could you post the 
>shutdown command you are using?
>

Yep, Informix backend.  Unfortunately I have no experience with either until
now.

I have use either:

shutdown -r now

or

/sbin/shutdown -r now

>There are at least two possibilities here: shutdown is not working right, 
>or, alternatively, shutdown is working correctly but you do not think that 
>is true.  In your original post the only evidence you provided that it is 
>not working correctly is that during shutdown you see the beginning of the 
>shutdown messages but then nothing until you see the hardware/BIOS stuff.
>An alternative reason that you would not see this info on shutdown is that 
>there is an alternative console to which the messages are displayed.  
>E.g., if you have a serial console as the primary console then shutdown 
>messages will be displayed there rather than on the tty[1-6] or whatever
>virtual consoles you have defined.  Is there an alternative console 
>defined in lilo.conf/grub.conf (depends on your boot loader).
>

I tried switching vc's when the shutdown was happening but no luck.  Next
time I was going to try the shutdown using our KVM switch and then unhook it
and attach a regular monitor and keyboard and see what happens.  I'm
trhinking like you say I'm just not looking at the "right" console when the
shutdown happens.  BTW, my grub.conf is:
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/ida/c0d0p6
#          initrd /initrd-version.img
#boot=/dev/ida/c0d0
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.7-10enterprise)
        root (hd0,0)
        kernel /vmlinuz-2.4.7-10enterprise ro root=/dev/ida/c0d0p6
        initrd /initrd-2.4.7-10enterprise.img
title Red Hat Linux (2.4.7-10smp)
        root (hd0,0)
        kernel /vmlinuz-2.4.7-10smp ro root=/dev/ida/c0d0p6
        initrd /initrd-2.4.7-10smp.img
title Red Hat Linux-up (2.4.7-10)
        root (hd0,0)
        kernel /vmlinuz-2.4.7-10 ro root=/dev/ida/c0d0p6
        initrd /initrd-2.4.7-10.img

>Let's say it is an improper shutdown; have you tried the appropriate 
>'init' commands as an alternative?  Two strategies:
>
>1)  init 6
>
Not yet but will do.

>OR
>
>1) init 1
>   manually shutdown continuus
>   init x 
> 
We have done:
manually shutdown continuus
shutdown -r now

this of course will shutdown continuus properly although its redundant if
things are working right.  BTW, does it matter if the script is linked as
S99/K99 instead of maybe S89/K89 or S90/K90?  I wouldn't think so, but I
have never had anything linked at x99.

Regards,

Mike
---
Mike Shaw            VOICE: +1 (317)306-3084
Raytheon Technical Services  
UNIX Administrator     FAX:  +1 (317)306-4253  
INET: [email protected]