CentOS - Apr 2010 - mysterious weekly shutdown

I have a Centos 5.4 machine that has, for the past two weeks, apparently
been shut off over the weekend.  It's just sitting there turned off on
Monday morning and when someone hits the power switch it comes right
back on and everything works again.

This happened last weekend, and again over this past weekend.

Here is /var/log/messages from shortly before it apparently shut down
this weekend.  Can anyone tell me what is or might be going on?

Apr 10 11:01:27 answeringmachine vgetty[6012]: message keep,
length=00:00:20, name='', caller=none, dev=ttyACM0, pid=6012
Apr 10 11:19:10 answeringmachine vgetty[6095]: message keep,
length=00:00:24, name='', caller=none, dev=ttyACM0, pid=6095
Apr 10 11:43:56 answeringmachine vgetty[6134]: message keep,
length=00:00:11, name='', caller=none, dev=ttyACM0, pid=6134
Apr 10 12:22:34 answeringmachine mgetty[6029]: fax dev=ttyS1, pid=6029,
caller='none', name='', id='', +FHNG=074, pages=0/0,
time=00:00:51
Apr 10 12:43:49 answeringmachine gconfd (freeads-3524): Exiting
Apr 10 12:43:49 answeringmachine gdm[2872]: Master halting...
Apr 10 12:43:49 answeringmachine pcscd: winscard.c:304:SCardConnect()
Reader E-Gate 0 0 Not Found
Apr 10 12:43:50 answeringmachine shutdown[2872]: shutting down for
system halt
Apr 10 12:43:50 answeringmachine mgetty[6262]: failed dev=ttyS1,
pid=6262, got signal 15, exiting
Apr 10 12:43:50 answeringmachine mgetty[2874]: failed dev=ttyS2,
pid=2874, got signal 15, exiting
Apr 10 12:43:50 answeringmachine vgetty[2877]: failed dev=ttyACM1,
pid=2877, got signal 15, exiting
Apr 10 12:43:50 answeringmachine vgetty[6183]: failed dev=ttyACM0,
pid=6183, got signal 15, exiting
Apr 10 12:43:51 answeringmachine smartd[2854]: smartd received signal
15: Terminated 
Apr 10 12:43:51 answeringmachine smartd[2854]: smartd is exiting (exit
status 0) 
Apr 10 12:43:52 answeringmachine avahi-daemon[2769]: Got SIGTERM,
quitting.
Apr 10 12:43:52 answeringmachine avahi-daemon[2769]: Leaving mDNS
multicast group on interface eth0.IPv6 with address
fe80::21c:c0ff:fee3:f1b1.
Apr 10 12:43:52 answeringmachine avahi-daemon[2769]: Leaving mDNS
multicast group on interface eth0.IPv4 with address 192.168.0.6.
Apr 10 12:43:52 answeringmachine mountd[2588]: Caught signal 15,
un-registering and exiting.
Apr 10 12:43:52 answeringmachine kernel: nfsd: last server has exited
Apr 10 12:43:52 answeringmachine kernel: nfsd: unexporting all
filesystems
Apr 10 12:43:57 answeringmachine ntpd[2532]: ntpd exiting on signal 15
Apr 10 12:43:57 answeringmachine nm-system-settings: disconnected from
the system bus, exiting.
Apr 10 12:43:57 answeringmachine kernel: nm-system-setti[3083]: segfault
at 0000000000000000 rip 0000000000000000 rsp 00007fffb3916778 error 14
Apr 10 12:43:57 answeringmachine rpc.statd[2349]: Caught signal 15,
un-registering and exiting.
Apr 10 12:43:57 answeringmachine auditd[2264]: The audit daemon is
exiting.
Apr 10 12:43:57 answeringmachine kernel: audit(1270925037.732:154):
audit_pid=0 old=2264 by auid=4294967295
Apr 10 12:43:57 answeringmachine pcscd: pcscdaemon.c:572:signal_trap()
Preparing for suicide
Apr 10 12:43:58 answeringmachine pcscd:
hotplug_libusb.c:376:HPRescanUsbBus() Hotplug stopped
Apr 10 12:43:58 answeringmachine pcscd:
readerfactory.c:1379:RFCleanupReaders() entering cleaning function
Apr 10 12:43:58 answeringmachine pcscd: pcscdaemon.c:532:at_exit()
cleaning /var/run
Apr 10 12:43:59 answeringmachine kernel: Kernel logging (proc) stopped.
Apr 10 12:43:59 answeringmachine kernel: Kernel log daemon terminating.
Apr 10 12:44:00 answeringmachine exiting on signal 15
-- 
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com

On Mon, Apr 12, 2010 at 1:08 PM, Frank Cox <theatre at sasktel.net>
wrote:
> I have a Centos 5.4 machine that has, for the past two weeks, apparently
> been shut off over the weekend. ?It's just sitting there turned off on
> Monday morning and when someone hits the power switch it comes right
> back on and everything works again.
>
> This happened last weekend, and again over this past weekend.
>
> Here is /var/log/messages from shortly before it apparently shut down
> this weekend. ?Can anyone tell me what is or might be going on?
>
> Apr 10 12:43:59 answeringmachine kernel: Kernel logging (proc) stopped.
> Apr 10 12:43:59 answeringmachine kernel: Kernel log daemon terminating.
> Apr 10 12:44:00 answeringmachine exiting on signal 15
> --
I've seen this on some HP Blades that I administer. I ended up
disabling the pcsd daemon. It might have been related to a dynamically
attached optical device that was moved from blade to blade, but I
didn't spend much time troubleshooting.  Since disabling pcsd a few
months ago it has been solid.

Frank wrote:
> I have a Centos 5.4 machine that has, for the past two weeks, apparently
> been shut off over the weekend.  It's just sitting there turned off on
> Monday morning and when someone hits the power switch it comes right
> back on and everything works again.
>
> This happened last weekend, and again over this past weekend.
>
> Here is /var/log/messages from shortly before it apparently shut down
> this weekend.  Can anyone tell me what is or might be going on?
>
> Apr 10 11:01:27 answeringmachine vgetty[6012]: message keep,
> length=00:00:20, name='', caller=none, dev=ttyACM0, pid=6012
> Apr 10 11:19:10 answeringmachine vgetty[6095]: message keep,
> length=00:00:24, name='', caller=none, dev=ttyACM0, pid=6095
> Apr 10 11:43:56 answeringmachine vgetty[6134]: message keep,
> length=00:00:11, name='', caller=none, dev=ttyACM0, pid=6134
> Apr 10 12:22:34 answeringmachine mgetty[6029]: fax dev=ttyS1, pid=6029,
> caller='none', name='', id='', +FHNG=074,
pages=0/0, time=00:00:51
> Apr 10 12:43:49 answeringmachine gconfd (freeads-3524): Exiting
This - I wonder if someone's somehow getting in. Anything in
/var/log/secure for 12:43?
> Apr 10 12:43:49 answeringmachine gdm[2872]: Master halting...
> Apr 10 12:43:49 answeringmachine pcscd: winscard.c:304:SCardConnect()
> Reader E-Gate 0 0 Not Found
> Apr 10 12:43:50 answeringmachine shutdown[2872]: shutting down for
> system halt
Here's a thought: does it have bluetooth enabled? Is it in range to talk
to someone *else's* bluetooth keyboard? Is anyone near enough to shut down
their machine, and/or accidentally yours?
<snip>
> status 0)
> Apr 10 12:43:52 answeringmachine avahi-daemon[2769]: Got SIGTERM,
> quitting.
Is this machine hardwired? If so, you do NOT need the avahi-daemon, on by
default, which is intended for a clueless home user to set up a network.
Turn it *off*, and yank the firewall rule that allows it.
<snip>

           mark