Kernel panic after approx 12 hours of up time.

[finalbillybong]

So I'm having a problem with my server kernel panicking after about 12 hours (or more) up time. As I'm using my server for DHCP this is causing me a few problems as I have to manually reset the server (power off then on) each time it happens so my iPhone etc can obtain an IP. I don't have the skills to diagnose the problem so I'm reaching out to you lot for help. Does Amahi record logs that I could post here to see if they have any clues? If yes, where are they stored?

Any more info I can give, just ask?

Can anyone guide a noob?

Thanks fellas!

[bigfoot65]

Have you checked that you have Fedora updates installed? Usually when there is a kernel problem, it often indicates a hardware compatibility issue or could be there is a more current kernel that works better.

Is this 32 or 64 bit Fedora 14?

[finalbillybong]

It's 64bit. How can I check the status of my updates? If they are not up today's how do I update?

[bigfoot65]

Best thing to do is open a terminal window from the HDA or use Putty to SSH into the HDA. Then become root user and enter:
yum update

http://wiki.amahi.org/index.php/Root

Hope this helps.

[finalbillybong]

OK I've done that. It installed two updates one for dosfstools and one for logrotate.

Total size was 132KB I think.

[radioz]

Many important log files are located in /var/log.

Take a look at /var/log/messages. It will hopefully show where your system crashed.
Search for 'panic' in the file. If you find it, post the 20 lines just before (and including the panic) it happens.

[finalbillybong]

Right I checked out the messages log.

Hope this can help.

Aug 5 19:47:52 freenas kernel: [ 1.348802] Initalizing network drop monitor service
Aug 5 19:47:52 freenas kernel: [ 1.361795] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Aug 5 19:47:52 freenas kernel: [ 1.486186] ata4.00: ATAPI: HL-DT-ST DVDRAM GSA-T50N, RH03, max UDMA/133
Aug 5 19:47:52 freenas kernel: [ 1.508221] ata4.00: configured for UDMA/133
Aug 5 19:47:52 freenas kernel: [ 1.519124] ata3.00: ATA-8: WDC WD5000AAKS-007AA0, 05.01D05, max UDMA/133
Aug 5 19:47:52 freenas kernel: [ 1.519133] ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Aug 5 19:47:52 freenas kernel: [ 1.523145] ata3.00: configured for UDMA/133
Aug 5 19:47:52 freenas kernel: [ 1.523481] scsi 2:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 05.0 PQ: 0 ANSI: 5
Aug 5 19:47:52 freenas kernel: [ 1.523917] sd 2:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Aug 5 19:47:52 freenas kernel: [ 1.524089] sd 2:0:0:0: Attached scsi generic sg0 type 0
Aug 5 19:47:52 freenas kernel: [ 1.524293] sd 2:0:0:0: [sda] Write Protect is off
Aug 5 19:47:52 freenas kernel: [ 1.524624] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 5 19:47:52 freenas kernel: [ 1.525496] sda:
Aug 5 19:47:52 freenas kernel: [ 1.526528] scsi 3:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-T50N RH03 PQ: 0 ANSI: 5
Aug 5 19:47:52 freenas kernel: [ 1.538175] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Aug 5 19:47:52 freenas kernel: [ 1.538186] Uniform CD-ROM driver Revision: 3.20
Aug 5 19:47:52 freenas kernel: [ 1.538731] sr 3:0:0:0: Attached scsi generic sg1 type 5
Aug 5 19:47:52 freenas kernel: [ 1.563978] sda1 sda2
Aug 5 19:47:52 freenas kernel: [ 1.564939] sd 2:0:0:0: [sda] Attached SCSI disk
Aug 5 19:47:52 freenas kernel: [ 1.565019] Freeing unused kernel memory: 948k freed
Aug 5 19:47:52 freenas kernel: [ 1.565725] Write protecting the kernel read-only data: 10240k
Aug 5 19:47:52 freenas kernel: [ 1.566558] Freeing unused kernel memory: 1572k freed
Aug 5 19:47:52 freenas kernel: [ 1.568794] Freeing unused kernel memory: 1836k freed
Aug 5 19:47:52 freenas kernel: [ 1.618415] dracut: dracut-006-6.fc14
Aug 5 19:47:52 freenas kernel: [ 1.638293] dracut: rd_NO_LUKS: removing cryptoluks activation
Aug 5 19:47:52 freenas kernel: [ 1.641074] usb 1-2: new high speed USB device using ehci_hcd and address 2
Aug 5 19:47:52 freenas kernel: [ 1.641912] dracut: rd_NO_LVM: removing LVM activation
Aug 5 19:47:52 freenas kernel: [ 1.665369] udev[81]: starting version 161
Aug 5 19:47:52 freenas kernel: [ 1.757237] usb 1-2: New USB device found, idVendor=13fe, idProduct=3100
Aug 5 19:47:52 freenas kernel: [ 1.757249] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 5 19:47:52 freenas kernel: [ 1.757260] usb 1-2: Product: 360 Grey
Aug 5 19:47:52 freenas kernel: [ 1.757267] usb 1-2: Manufacturer: Integral
Aug 5 19:47:52 freenas kernel: [ 1.757274] usb 1-2: SerialNumber: 079C01000018DFAC
Aug 5 19:47:52 freenas kernel: [ 1.829057] Initializing USB Mass Storage driver...
Aug 5 19:47:52 freenas kernel: [ 1.829489] scsi4 : usb-storage 1-2:1.0
Aug 5 19:47:52 freenas kernel: [ 1.830185] usbcore: registered new interface driver usb-storage
Aug 5 19:47:52 freenas kernel: [ 1.830195] USB Mass Storage support registered.
Aug 5 19:47:52 freenas kernel: [ 1.876978] [drm] Initialized drm 1.1.0 20060810
Aug 5 19:47:52 freenas kernel: [ 1.942447] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Aug 5 19:47:52 freenas kernel: [ 2.019376] [drm] set up 7M of stolen space
Aug 5 19:47:52 freenas kernel: [ 2.021029] [drm] initialized overlay support
Aug 5 19:47:52 freenas kernel: [ 2.193169] fbcon: inteldrmfb (fb0) is primary device
Aug 5 19:47:52 freenas kernel: [ 2.252568] Console: switching to colour frame buffer device 180x56
Aug 5 19:47:52 freenas kernel: [ 2.266884] fb0: inteldrmfb frame buffer device
Aug 5 19:47:52 freenas kernel: [ 2.266889] drm: registered panic notifier

[radioz]

Thanks for the log. Unfortunately, although it does have the word 'panic' in there, it is just reporting that a panic handler had been installed during the boot-up sequence.

If you have never looked at a /var/log/messages log file before it is difficult to pick out the 'normal stuff' from real errors. If you look at the date/time fields of the lines in the log file, you can see that all of these messages came out very quickly during the boot-up sequence. If you have a rough idea how long after boot-up the failure occurred, you can look down the log to see if there is anything suspicious. Look for other instances of the word 'panic'.

The boot-up sequence only takes a minute or two and after that you should start to see other activities going on. On my system, most of the messages relate to networking activities (nmbd and dhcp).

Note that this log file will be 'rotated' periodically to keep it from growing too large. This means opening a new 'messages' file and saving the old one. The system keeps the last few older logfiles before deleting them. Note that the filenames are changed to add the date and time to the name. Here are mine for example:

Code: Select all

-rw-r--r-- 1 root root 555543 Jul 10 03:13 messages-20110710 -rw-r--r-- 1 root root 458411 Jul 17 03:23 messages-20110717 -rw-r--r-- 1 root root 419768 Jul 24 03:41 messages-20110724 -rw-r--r-- 1 root root 453437 Jul 31 03:11 messages-20110731 -rw-r--r-- 1 root root 433866 Aug 5 21:54 messages

If you can pin down the date and time when one of your failures occurred, you can look in the appropriate log file.

I hope this is helpful. Feel free to ask questions if you need help.