RE: Anyone have problems with shutdown not working properly?

Keith Mastin [mailto:[email protected]]wrote:
. . .
>Stewart already made a comment about shutting down a linux srver, so I
>won't go there, but what the hell are you doing running a server in
>runlevel 5? Looking for a reason to need to shutdown?
>

I inherited it - I haven't gone there yet.  Reason for shutdown - see
previous message.

>That said, signal 15 is SIGTERM,

Uh, yeah I know.  I was just trying to show that my last message is it
killing things and no messages from Continuus are displayed.  I probably
should have listed everything but didn't.  So here they are:

Mar 11 19:00:03 tcontinuus rhnsd[1130]: Exiting
Mar 11 19:00:03 tcontinuus rhnsd: rhnsd shutdown succeeded
Mar 11 19:00:04 tcontinuus atd: atd shutdown succeeded
Mar 11 19:00:04 tcontinuus Font Server[1042]: terminating 
Mar 11 19:00:05 tcontinuus xfs: xfs shutdown succeeded
Mar 11 19:00:06 tcontinuus gpm: gpm shutdown succeeded
Mar 11 19:00:10 tcontinuus httpd: httpd shutdown succeeded
Mar 11 19:00:11 tcontinuus rpc.mountd: Caught signal 15, un-registering and
exit
ing. 
Mar 11 19:00:11 tcontinuus nfs: rpc.mountd shutdown succeeded
Mar 11 19:00:15 tcontinuus kernel: nfsd: terminating on signal 9
Mar 11 19:00:15 tcontinuus last message repeated 7 times
Mar 11 19:00:15 tcontinuus nfs: nfsd shutdown succeeded
Mar 11 19:00:16 tcontinuus nfs: Shutting down NFS services:  succeeded
Mar 11 19:00:17 tcontinuus nfs: rpc.rquotad shutdown failed
Mar 11 19:00:17 tcontinuus sshd: sshd -TERM succeeded
Mar 11 19:00:18 tcontinuus sendmail: sendmail shutdown succeeded
Mar 11 19:00:18 tcontinuus smb: smbd shutdown succeeded
Mar 11 19:00:19 tcontinuus kernel: x.x.x.x sent an invalid ICMP error to 
a broadcast.
Mar 11 19:00:19 tcontinuus smb: nmbd shutdown succeeded
Mar 11 19:00:19 tcontinuus ucd-snmp[782]: Received TERM or STOP signal...
shutting down... 
Mar 11 19:00:23 tcontinuus snmpd: snmpd shutdown succeeded
Mar 11 19:00:24 tcontinuus xinetd[900]: Exiting...
Mar 11 19:00:24 tcontinuus xinetd: xinetd shutdown succeeded
Mar 11 19:00:24 tcontinuus crond: crond shutdown succeeded
Mar 11 19:00:24 tcontinuus dd: 1+0 records in
Mar 11 19:00:24 tcontinuus dd: 1+0 records out
Mar 11 19:00:24 tcontinuus random: Saving random seed:  succeeded
Mar 11 19:00:25 tcontinuus rpc.statd[615]: Caught signal 15, un-registering
and 
exiting.
Mar 11 19:00:25 tcontinuus nfslock: rpc.statd shutdown succeeded
Mar 11 19:00:26 tcontinuus portmap: portmap shutdown succeeded
Mar 11 19:00:26 tcontinuus kernel: Kernel logging (proc) stopped.
Mar 11 19:00:26 tcontinuus kernel: Kernel log daemon terminating.
Mar 11 19:00:27 tcontinuus syslog: klogd shutdown succeeded
Mar 11 19:00:27 tcontinuus exiting on signal 15
Mar 11 19:06:07 tcontinuus syslogd 1.4.1: restart.

All this time no output to the screen.  Upon startup you see Continuus
startup messages:

Mar 11 19:06:55 tcontinuus continuus: Database server 'tcontinuus' is
On-Line
Mar 11 19:06:55 tcontinuus continuus: 
Mar 11 19:06:55 tcontinuus continuus: VDE is all ready running
Mar 11 19:06:55 tcontinuus su(pam_unix)[1363]: session closed for user
ccm_root
Mar 11 19:06:55 tcontinuus su(pam_unix)[1384]: session opened for user
ccm_root 
by (uid=0)

And it goes on from there saying it starts other Continuus stuff.  My only
thought on the "no messages to the screen" is that it was hooked up to a RCI
Master Console switch and we just replaced this with a OmniView KVM switch.
But I won't get to see a reboot until next week.

Regards,

Mike