The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Server Crash, need help with diagnosis

Discussion in 'General Discussion' started by Man0warr, Apr 25, 2007.

  1. Man0warr

    Man0warr Well-Known Member

    Joined:
    Jun 5, 2006
    Messages:
    59
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Dallas, TX
    Saturday morning one of our server crashed, I can't figure out why it crashed, we got it rebooted pretty quick. This is from the messages log from that day, theres nothing for a few hours before this in the log, around 4am there was some pure-ftpd loopbacks, thats about it.

    Where else can I check for logs on what could have happened?


    Apr 21 06:46:09 proton syslogd 1.4.1: restart.
    Apr 21 06:46:09 proton syslog: syslogd startup succeeded
    Apr 21 06:46:09 proton kernel: klogd 1.4.1, log source = /proc/kmsg started.
    Apr 21 06:46:09 proton kernel: Linux version 2.4.21-32.EL (bhcompile@tweety.build.redhat.com) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-52)) #1 Fri A$
    Apr 21 06:46:09 proton kernel: BIOS-provided physical RAM map:
    Apr 21 06:46:09 proton kernel: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 0000000000100000 - 000000007ff74000 (usable)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 000000007ff74000 - 000000007ff76000 (ACPI NVS)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 000000007ff76000 - 000000007ff97000 (ACPI data)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 000000007ff97000 - 0000000080000000 (reserved)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 00000000fecf0000 - 00000000fecf1000 (reserved)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
    Apr 21 06:46:09 proton syslog: klogd startup succeeded
    Apr 21 06:46:09 proton kernel: BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
    Apr 21 06:46:09 proton kernel: BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
    Apr 21 06:46:09 proton kernel: 1151MB HIGHMEM available.
    Apr 21 06:46:09 proton kernel: 896MB LOWMEM available.
    Apr 21 06:46:09 proton rpc.statd[874]: Version 1.0.6 Starting
    Apr 21 06:46:09 proton kernel: NX protection not present; using segment protection
    Apr 21 06:46:09 proton kernel: On node 0 totalpages: 524148
    Apr 21 06:46:09 proton kernel: zone(0): 4096 pages.
    Apr 21 06:46:09 proton kernel: zone(1): 225280 pages.
    Apr 21 06:46:09 proton nfslock: rpc.statd startup succeeded
    Apr 21 06:46:09 proton kernel: zone(2): 294772 pages.
    Apr 21 06:46:09 proton rpc.statd[874]: unable to register (statd, 1, udp).
    Apr 21 06:46:09 proton kernel: Kernel command line: ro root=LABEL=/
    Apr 21 06:46:09 proton kernel: Initializing CPU#0
    Apr 21 06:46:09 proton kernel: Detected 2394.051 MHz processor.
    Apr 21 06:46:09 proton kernel: Console: colour VGA+ 80x25
    Apr 21 06:46:09 proton kernel: Calibrating delay loop... 4771.02 BogoMIPS
    Apr 21 06:46:09 proton kernel: Page-cache hash table entries: 524288 (order: 9, 2048 KB)
    Apr 21 06:46:09 proton kernel: Page-pin hash table entries: 131072 (order: 7, 512 KB)
    Apr 21 06:46:09 proton kernel: Dentry cache hash table entries: 262144 (order: 9, 2048 KB)
    Apr 21 06:46:09 proton kernel: Inode cache hash table entries: 131072 (order: 8, 1024 KB)
    Apr 21 06:46:09 proton kernel: Buffer cache hash table entries: 131072 (order: 7, 512 KB)
    Apr 21 06:46:09 proton kernel: Memory: 2053432k/2096592k available (1543k kernel code, 38552k reserved, 1071k data, 164k init, 1179088k highmem)
    Apr 21 06:46:09 proton kernel: zapping low mappings.
    Apr 21 06:46:09 proton kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
    Apr 21 06:46:09 proton kernel: CPU: Trace cache: 12K uops, L1 D cache: 8K
    Apr 21 06:46:09 proton kernel: CPU: L2 cache: 128K
    Apr 21 06:46:09 proton kernel: Intel machine check architecture supported.
    Apr 21 06:46:09 proton kernel: Intel machine check reporting enabled on CPU#0.
    Apr 21 06:46:09 proton kernel: CPU: Intel(R) Celeron(R) CPU 2.40GHz stepping 09
    Apr 21 06:46:09 proton kernel: Enabling fast FPU save and restore... done.
    Apr 21 06:46:09 proton random: Initializing random number generator: succeeded
    Apr 21 06:46:09 proton kernel: Enabling unmasked SIMD FPU exception support... done.
    Apr 21 06:46:09 proton kernel: Checking 'hlt' instruction... OK.
    Apr 21 06:46:09 proton kernel: POSIX conformance testing by UNIFIX
    Apr 21 06:46:09 proton kernel: Process timing init...done.
    Apr 21 06:46:09 proton kernel: mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
    Apr 21 06:46:09 proton kernel: mtrr: detected mtrr type: Intel
    Apr 21 06:46:10 proton kernel: PCI: PCI BIOS revision 2.10 entry at 0xfba64, last bus=2
    Apr 21 06:46:10 proton kernel: PCI: Using configuration type 1

    etc etc more startup stuff
     
  2. mohakevin

    mohakevin Well-Known Member

    Joined:
    Jan 19, 2005
    Messages:
    84
    Likes Received:
    0
    Trophy Points:
    6
    If you server have crashed you´ll have to find what´s wrong with your server.

    it can be memory, I/O, CPU...

    You need to analyse.

    Regards.
     
  3. ceobryan

    ceobryan Registered

    Joined:
    Apr 26, 2007
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Check the /var/log/messages and messages.X files. You need the lines before the "restart". I work on solaris boxes, but for the most part the errors are the same.
     
  4. Man0warr

    Man0warr Well-Known Member

    Joined:
    Jun 5, 2006
    Messages:
    59
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Dallas, TX
    The problem is that there is nothing suspicious before the restart, just normal day to day stuff.
     
  5. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    You may well only get useful information from the console serial port if it simply crashes as the OS may not be able to write to disk when it fails and the Oops will be directly to the console instead. Other than that, make sure you're running an up to date kernel and possible have the datacenter/yourself runs some burn-in tests on the hardware. Sudden, unexplained crashes can often be an indication of a fault memory stick or a disk on its way out, which a burn-in test might well detect.
     
Loading...

Share This Page