Server Crashes

Discussion in 'Site & Server Administration' started by protocol96, Dec 17, 2010.

0
  1. #1
    Below are the logs from messages, everyday around that time my server crashes and I have to reboot it.

    
Dec 17 06:52:17 Cloud1 NetworkManager[891]: Frame 28: NetworkManager (0x400000+0x41b2c9) [0x41b2c9]
Dec 17 06:52:17 Cloud1 NetworkManager[891]: ******************* END **********************************
Dec 17 06:52:17 Cloud1 avahi-daemon[902]: Found user 'avahi' (UID 498) and group 'avahi' (GID 493).
Dec 17 06:52:17 Cloud1 avahi-daemon[902]: Successfully dropped root privileges.
Dec 17 06:52:17 Cloud1 avahi-daemon[902]: avahi-daemon 0.6.25 starting up.
Dec 17 06:52:17 Cloud1 avahi-daemon[902]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Dec 17 06:52:17 Cloud1 avahi-daemon[902]: dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Dec 17 06:52:17 Cloud1 avahi-daemon[902]: WARNING: Failed to contact D-Bus daemon.
Dec 17 06:52:17 Cloud1 rpc.statd[916]: Version 1.2.2 starting
Dec 17 06:52:17 Cloud1 sm-notify[917]: Version 1.2.2 starting
Dec 17 06:52:17 Cloud1 kernel: [   15.097408] RPC: Registered udp transport module.
Dec 17 06:52:17 Cloud1 kernel: [   15.097411] RPC: Registered tcp transport module.
Dec 17 06:52:17 Cloud1 kernel: [   15.097414] RPC: Registered tcp NFSv4.1 backchannel transport module.
Dec 17 06:52:19 Cloud1 xinetd[1159]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
Dec 17 06:52:19 Cloud1 xinetd[1159]: Started working: 0 available services
Dec 17 06:57:04 Cloud1 kernel: [  301.820066] type=1305 audit(1292569024.695:12405): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
Dec 17 10:12:32 Cloud1 yum[1566]: Installed: apachetop-0.12.6-7.fc12.x86_64
    PHP:

     
    protocol96, Dec 17, 2010 IP
  2. PsyHost

    PsyHost Well-Known Member

    Messages:
    641
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    110
    #2
    Check your disc space levels.
     
    PsyHost, Dec 17, 2010 IP
  3. protocol96

    protocol96 Peon

    Messages:
    413
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    0
    #3
    got plenty of space
     
    protocol96, Dec 17, 2010 IP
  4. PsyHost

    PsyHost Well-Known Member

    Messages:
    641
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    110
    #4
    paste syslog from same time frame.
     
    PsyHost, Dec 17, 2010 IP
  5. protocol96

    protocol96 Peon

    Messages:
    413
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    0
    #5
    dont think I have syslog installed on my server
     
    protocol96, Dec 17, 2010 IP
  6. protocol96

    protocol96 Peon

    Messages:
    413
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    0
    #6
    ohh!! sorry those messages are from syslog!
     
    protocol96, Dec 17, 2010 IP
  7. protocol96

    protocol96 Peon

    Messages:
    413
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    0
    #7
    I guess here's the problem part
    
Dec 16 03:08:08 Cloud1 autodeath: Default route disabled by autodeath cron job. See: man system-autodeath for more information.
    PHP:
    Here's when my server stops
     
    protocol96, Dec 17, 2010 IP
  8. PsyHost

    PsyHost Well-Known Member

    Messages:
    641
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    110
    #8
    it doesn't stop, it disables the default route.
    if you don't have that in their for any reason try 
    yum remove yum update system-autodeath
    Code (markup):
     
    PsyHost, Dec 17, 2010 IP