Koozali.org: home of the SME Server

Kernel panic täglich um 4 Uhr früh

Offline andras98

  • 2
  • +0/-0
Kernel panic täglich um 4 Uhr früh
« on: May 18, 2008, 08:46:13 PM »
Hi,

Hab seit kurzem folgende Meldung ... die meinen Server lahmlegt. Jemand einen Tipp?
Die Meldung kam früher nie (früher, ca. 1 Jahr). Verändert wurde bis vor ein paar Tagen nichts. Dachte zuerst ein Update könne helfen ... Leider war das ein Irrglaube. Die Maschine panikte jeden Tag ca. um 4:00 in der Früh. :-(
lg,
and

z.B.
Code: [Select]
May 11 23:30:31 atlas afpd[4455]: uam: "DHCAST128" available
May 11 23:30:31 atlas afpd[4455]: Finished parsing Config File
May 12 04:05:05 atlas kernel: Unable to handle kernel paging request at virtual address 94808b06
May 12 04:05:05 atlas kernel:  printing eip:
May 12 04:05:05 atlas kernel: c011fb4c
May 12 04:05:05 atlas kernel: *pde = 00000000
May 12 04:05:05 atlas kernel: Oops: 0002 [#1]
May 12 04:05:05 atlas kernel: Modules linked in: appletalk(U) 8139too bonding(U) ipt_ULOG ipt_REJECT ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables button battery ac ohci_hcd uhci_hcd ehci_hcd snd_cmipci snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore mii floppy dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod
May 12 04:05:05 atlas kernel: CPU:    0
May 12 04:05:05 atlas kernel: EIP:    0060:[schedule_tail+252/262]    Not tainted VLI
May 12 04:05:05 atlas kernel: EIP:    0060:[<c011fb4c>]    Not tainted VLI
May 12 04:05:05 atlas kernel: EFLAGS: 00010292   (2.6.9-67.0.7.EL)
May 12 04:05:05 atlas kernel: EIP is at schedule_tail+0xfc/0x106
May 12 04:05:05 atlas kernel: eax: b7f9a70c   ebx: b7f9a708   ecx: 00000000   edx: 00000000
May 12 04:05:05 atlas kernel: esi: c9260000   edi: 94808b06   ebp: c9260fb8   esp: c9260fb0
May 12 04:05:05 atlas kernel: ds: 007b   es: 007b   ss: 0068
May 12 04:05:05 atlas kernel: Process rkhunter (pid: 32117, threadinfo=c9260000 task=c8dc6c50)
May 12 04:05:05 atlas kernel: Stack: d180abe0 c8dc6c50 c8c38fbc c031db3e c8dc77f0 01200011 00000000 00000000
May 12 04:05:05 atlas kernel:        00000000 b7f9a708 bfe1ed78 00000000 0000007b 0000007b 00000078 00c9b7a2
May 12 04:05:05 atlas kernel:        00000073 00000282 bfe1ed04 0000007b
May 12 04:05:05 atlas kernel: Call Trace:
May 12 04:05:05 atlas kernel:  [ret_from_fork+6/20] ret_from_fork+0x6/0x14
May 12 04:05:05 atlas kernel:  [<c031db3e>] ret_from_fork+0x6/0x14
May 12 04:05:05 atlas kernel: Code: fb 05 00 00 b8 9e f0 32 c0 e8 7b 16 00 00 e8 9c c7 1f 00 89 d8 83 c0 04 19 d2 39 46 18 83 da 00 85 d2 75 0a 8b 06 8b 80 94 00 00 <00> 89 03 8d 65 f8 5b 5e 5d c3 55 a1 b8 15 41 c0 89 e5 5d c3 55
May 12 04:05:05 atlas kernel:  <0>Fatal exception: panic in 5 seconds
May 12 09:50:29 atlas syslogd 1.4.1: restart.

oder eines Tages

Code: [Select]
May 8 01:12:05 atlas kernel: Loaded 24086 symbols from /boot/System.map-2.6.9-55.0.9.EL.
May 8 01:12:05 atlas kernel: Symbols match kernel version 2.6.9.
May 8 01:12:05 atlas kernel: No module symbols loaded - kernel modules not enabled.
May 8 01:12:04 atlas syslog: Herunterfahren von syslogd succeeded
May 9 19:12:49 atlas smbd[6001]: [2008/05/09 19:12:49, 0] lib/util_sock.c:read_socket_data(384)
May 9 19:12:49 atlas smbd[6001]: read_socket_data: recv failure for 4. Error = No route to host
May 10 04:03:17 atlas kernel: ------------[ cut here ]------------
May 10 04:03:17 atlas kernel: kernel BUG at mm/slab.c:908!
May 10 04:03:17 atlas kernel: invalid operand: 0000 [#1]
May 10 04:03:17 atlas kernel: Modules linked in: appletalk(U) 8139too ipt_ULOG ipt_REJECT ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables loop button battery ac ohci_hcd uhci_hcd ehci_hcd snd_cmipci snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore mii bonding(U) floppy dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod
May 10 04:03:17 atlas kernel: CPU: 0
May 10 04:03:17 atlas kernel: EIP: 0060:[kmem_freepages+53/135] Not tainted VLI
May 10 04:03:17 atlas kernel: EIP: 0060:[<c0153086>] Not tainted VLI
May 10 04:03:17 atlas kernel: EFLAGS: 00010246 (2.6.9-55.0.9.EL)
May 10 04:03:17 atlas kernel: EIP is at kmem_freepages+0x35/0x87
May 10 04:03:17 atlas kernel: eax: 00000000 ebx: dfffba60 ecx: 00000000 edx: c1227a00
May 10 04:03:17 atlas kernel: esi: 00000001 edi: d13d0000 ebp: d13d0000 esp: dffebf38
May 10 04:03:17 atlas kernel: ds: 007b es: 007b ss: 0068
May 10 04:03:17 atlas kernel: Process events/0 (pid: 3, threadinfo=dffeb000 task=dfe10bd0)
May 10 04:03:17 atlas kernel: Stack: dfffba60 d0568f60 00000005 c0153157 dfffba60 dfffbae8 00000005 c04316a0
May 10 04:03:17 atlas kernel: c0154b0f c04316e0 c04316e0 00000283 00000000 dfead160 c0137e98 c0154988
May 10 04:03:17 atlas kernel: ffffffff ffffffff 00000001 00000000 c0120055 00010000 00000000 c0318bdb
May 10 04:03:17 atlas kernel: Call Trace:
May 10 04:03:17 atlas kernel: [slab_destroy+89/114] slab_destroy+0x59/0x72
May 10 04:03:17 atlas kernel: [<c0153157>] slab_destroy+0x59/0x72
May 10 04:03:17 atlas kernel: [cache_reap+391/627] cache_reap+0x187/0x273
May 10 04:03:17 atlas kernel: [<c0154b0f>] cache_reap+0x187/0x273
May 10 04:03:17 atlas kernel: [worker_thread+491/752] worker_thread+0x1eb/0x2f0
May 10 04:03:17 atlas kernel: [<c0137e98>] worker_thread+0x1eb/0x2f0
May 10 04:03:17 atlas kernel: [cache_reap+0/627] cache_reap+0x0/0x273
May 10 04:03:17 atlas kernel: [<c0154988>] cache_reap+0x0/0x273
May 10 04:03:17 atlas kernel: [default_wake_function+0/12] default_wake_function+0x0/0xc
May 10 04:03:17 atlas kernel: [<c0120055>] default_wake_function+0x0/0xc
May 10 04:03:17 atlas kernel: [schedule+1099/1540] schedule+0x44b/0x604
May 10 04:03:17 atlas kernel: [<c0318bdb>] schedule+0x44b/0x604
May 10 04:03:17 atlas kernel: [default_wake_function+0/12] default_wake_function+0x0/0xc
May 10 04:03:17 atlas kernel: [<c0120055>] default_wake_function+0x0/0xc
May 10 04:03:17 atlas kernel: [worker_thread+0/752] worker_thread+0x0/0x2f0
May 10 04:03:17 atlas kernel: [<c0137cad>] worker_thread+0x0/0x2f0
May 10 04:03:17 atlas kernel: [kthread+105/145] kthread+0x69/0x91
May 10 04:03:17 atlas kernel: [<c013cd0d>] kthread+0x69/0x91
May 10 04:03:17 atlas kernel: [kthread+0/145] kthread+0x0/0x91
May 10 04:03:17 atlas kernel: [<c013cca4>] kthread+0x0/0x91
May 10 04:03:17 atlas kernel: [kernel_thread_helper+5/11] kernel_thread_helper+0x5/0xb
May 10 04:03:17 atlas kernel: [<c01041dd>] kernel_thread_helper+0x5/0xb
May 10 04:03:17 atlas kernel: Code: c1 ea 0c c1 e2 05 53 be 01 00 00 00 8b 48 5c 03 15 f0 78 43 c0 89 c3 d3 e6 8d 4e ff 83 f9 ff 74 18 0f ba 32 07 19 c0 85 c0 75 08 <0f> 0b 8c 03 99 f0 32 c0 83 c2 20 49 eb e3 9c 58 fa 29 35 14 15
May 10 04:03:17 atlas kernel: <0>Fatal exception: panic in 5 seconds
May 10 20:21:11 atlas syslogd 1.4.1: restart.
May 10 20:21:11 atlas syslog: Starten von syslogd succeeded



Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: Kernel panic täglich um 4 Uhr früh
« Reply #1 on: May 18, 2008, 09:04:08 PM »
Hi,

Hab seit kurzem folgende Meldung ... die meinen Server lahmlegt. Jemand einen Tipp?
Die Meldung kam früher nie (früher, ca. 1 Jahr). Verändert wurde bis vor ein paar Tagen nichts. Dachte zuerst ein Update könne helfen ... Leider war das ein Irrglaube. Die Maschine panikte jeden Tag ca. um 4:00 in der Früh. :-(
lg,
and

z.B.
Code: [Select]
May 11 23:30:31 atlas afpd[4455]: uam: "DHCAST128" available
May 11 23:30:31 atlas afpd[4455]: Finished parsing Config File
May 12 04:05:05 atlas kernel: Unable to handle kernel paging request at virtual address 94808b06
May 12 04:05:05 atlas kernel:  printing eip:
May 12 04:05:05 atlas kernel: c011fb4c
May 12 04:05:05 atlas kernel: *pde = 00000000
May 12 04:05:05 atlas kernel: Oops: 0002 [#1]
May 12 04:05:05 atlas kernel: Modules linked in: appletalk(U) 8139too bonding(U) ipt_ULOG ipt_REJECT ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables button battery ac ohci_hcd uhci_hcd ehci_hcd snd_cmipci snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore mii floppy dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod
May 12 04:05:05 atlas kernel: CPU:    0
May 12 04:05:05 atlas kernel: EIP:    0060:[schedule_tail+252/262]    Not tainted VLI
May 12 04:05:05 atlas kernel: EIP:    0060:[<c011fb4c>]    Not tainted VLI
May 12 04:05:05 atlas kernel: EFLAGS: 00010292   (2.6.9-67.0.7.EL)
May 12 04:05:05 atlas kernel: EIP is at schedule_tail+0xfc/0x106
May 12 04:05:05 atlas kernel: eax: b7f9a70c   ebx: b7f9a708   ecx: 00000000   edx: 00000000
May 12 04:05:05 atlas kernel: esi: c9260000   edi: 94808b06   ebp: c9260fb8   esp: c9260fb0
May 12 04:05:05 atlas kernel: ds: 007b   es: 007b   ss: 0068
May 12 04:05:05 atlas kernel: Process rkhunter (pid: 32117, threadinfo=c9260000 task=c8dc6c50)
May 12 04:05:05 atlas kernel: Stack: d180abe0 c8dc6c50 c8c38fbc c031db3e c8dc77f0 01200011 00000000 00000000
May 12 04:05:05 atlas kernel:        00000000 b7f9a708 bfe1ed78 00000000 0000007b 0000007b 00000078 00c9b7a2
May 12 04:05:05 atlas kernel:        00000073 00000282 bfe1ed04 0000007b
May 12 04:05:05 atlas kernel: Call Trace:
May 12 04:05:05 atlas kernel:  [ret_from_fork+6/20] ret_from_fork+0x6/0x14
May 12 04:05:05 atlas kernel:  [<c031db3e>] ret_from_fork+0x6/0x14
May 12 04:05:05 atlas kernel: Code: fb 05 00 00 b8 9e f0 32 c0 e8 7b 16 00 00 e8 9c c7 1f 00 89 d8 83 c0 04 19 d2 39 46 18 83 da 00 85 d2 75 0a 8b 06 8b 80 94 00 00 <00> 89 03 8d 65 f8 5b 5e 5d c3 55 a1 b8 15 41 c0 89 e5 5d c3 55
May 12 04:05:05 atlas kernel:  <0>Fatal exception: panic in 5 seconds
May 12 09:50:29 atlas syslogd 1.4.1: restart.

oder eines Tages

Code: [Select]
May 8 01:12:05 atlas kernel: Loaded 24086 symbols from /boot/System.map-2.6.9-55.0.9.EL.
May 8 01:12:05 atlas kernel: Symbols match kernel version 2.6.9.
May 8 01:12:05 atlas kernel: No module symbols loaded - kernel modules not enabled.
May 8 01:12:04 atlas syslog: Herunterfahren von syslogd succeeded
May 9 19:12:49 atlas smbd[6001]: [2008/05/09 19:12:49, 0] lib/util_sock.c:read_socket_data(384)
May 9 19:12:49 atlas smbd[6001]: read_socket_data: recv failure for 4. Error = No route to host
May 10 04:03:17 atlas kernel: ------------[ cut here ]------------
May 10 04:03:17 atlas kernel: kernel BUG at mm/slab.c:908!
May 10 04:03:17 atlas kernel: invalid operand: 0000 [#1]
May 10 04:03:17 atlas kernel: Modules linked in: appletalk(U) 8139too ipt_ULOG ipt_REJECT ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables loop button battery ac ohci_hcd uhci_hcd ehci_hcd snd_cmipci snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore mii bonding(U) floppy dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod
May 10 04:03:17 atlas kernel: CPU: 0
May 10 04:03:17 atlas kernel: EIP: 0060:[kmem_freepages+53/135] Not tainted VLI
May 10 04:03:17 atlas kernel: EIP: 0060:[<c0153086>] Not tainted VLI
May 10 04:03:17 atlas kernel: EFLAGS: 00010246 (2.6.9-55.0.9.EL)
May 10 04:03:17 atlas kernel: EIP is at kmem_freepages+0x35/0x87
May 10 04:03:17 atlas kernel: eax: 00000000 ebx: dfffba60 ecx: 00000000 edx: c1227a00
May 10 04:03:17 atlas kernel: esi: 00000001 edi: d13d0000 ebp: d13d0000 esp: dffebf38
May 10 04:03:17 atlas kernel: ds: 007b es: 007b ss: 0068
May 10 04:03:17 atlas kernel: Process events/0 (pid: 3, threadinfo=dffeb000 task=dfe10bd0)
May 10 04:03:17 atlas kernel: Stack: dfffba60 d0568f60 00000005 c0153157 dfffba60 dfffbae8 00000005 c04316a0
May 10 04:03:17 atlas kernel: c0154b0f c04316e0 c04316e0 00000283 00000000 dfead160 c0137e98 c0154988
May 10 04:03:17 atlas kernel: ffffffff ffffffff 00000001 00000000 c0120055 00010000 00000000 c0318bdb
May 10 04:03:17 atlas kernel: Call Trace:
May 10 04:03:17 atlas kernel: [slab_destroy+89/114] slab_destroy+0x59/0x72
May 10 04:03:17 atlas kernel: [<c0153157>] slab_destroy+0x59/0x72
May 10 04:03:17 atlas kernel: [cache_reap+391/627] cache_reap+0x187/0x273
May 10 04:03:17 atlas kernel: [<c0154b0f>] cache_reap+0x187/0x273
May 10 04:03:17 atlas kernel: [worker_thread+491/752] worker_thread+0x1eb/0x2f0
May 10 04:03:17 atlas kernel: [<c0137e98>] worker_thread+0x1eb/0x2f0
May 10 04:03:17 atlas kernel: [cache_reap+0/627] cache_reap+0x0/0x273
May 10 04:03:17 atlas kernel: [<c0154988>] cache_reap+0x0/0x273
May 10 04:03:17 atlas kernel: [default_wake_function+0/12] default_wake_function+0x0/0xc
May 10 04:03:17 atlas kernel: [<c0120055>] default_wake_function+0x0/0xc
May 10 04:03:17 atlas kernel: [schedule+1099/1540] schedule+0x44b/0x604
May 10 04:03:17 atlas kernel: [<c0318bdb>] schedule+0x44b/0x604
May 10 04:03:17 atlas kernel: [default_wake_function+0/12] default_wake_function+0x0/0xc
May 10 04:03:17 atlas kernel: [<c0120055>] default_wake_function+0x0/0xc
May 10 04:03:17 atlas kernel: [worker_thread+0/752] worker_thread+0x0/0x2f0
May 10 04:03:17 atlas kernel: [<c0137cad>] worker_thread+0x0/0x2f0
May 10 04:03:17 atlas kernel: [kthread+105/145] kthread+0x69/0x91
May 10 04:03:17 atlas kernel: [<c013cd0d>] kthread+0x69/0x91
May 10 04:03:17 atlas kernel: [kthread+0/145] kthread+0x0/0x91
May 10 04:03:17 atlas kernel: [<c013cca4>] kthread+0x0/0x91
May 10 04:03:17 atlas kernel: [kernel_thread_helper+5/11] kernel_thread_helper+0x5/0xb
May 10 04:03:17 atlas kernel: [<c01041dd>] kernel_thread_helper+0x5/0xb
May 10 04:03:17 atlas kernel: Code: c1 ea 0c c1 e2 05 53 be 01 00 00 00 8b 48 5c 03 15 f0 78 43 c0 89 c3 d3 e6 8d 4e ff 83 f9 ff 74 18 0f ba 32 07 19 c0 85 c0 75 08 <0f> 0b 8c 03 99 f0 32 c0 83 c2 20 49 eb e3 9c 58 fa 29 35 14 15
May 10 04:03:17 atlas kernel: <0>Fatal exception: panic in 5 seconds
May 10 20:21:11 atlas syslogd 1.4.1: restart.
May 10 20:21:11 atlas syslog: Starten von syslogd succeeded
Schaut sich an ie ein cronjob Problem oder so etwas, schon geguckt welcihe cron jobs laufen etwa um 4?
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Offline andras98

  • 2
  • +0/-0
Re: Kernel panic täglich um 4 Uhr früh
« Reply #2 on: May 18, 2008, 09:17:27 PM »
Tja an die dachte ich auch aber weder root noch mein user haben welche eingetragen!

Offline capri

  • ****
  • 530
  • +0/-0
    • GAMEWARE
Re: Kernel panic täglich um 4 Uhr früh
« Reply #3 on: May 20, 2008, 02:38:34 PM »
Nur so eine Idee, aber vielleicht mal memtest86 laufen lassen, vielleicht ist ein Speicherriegel etwas 'wackelig' und bei Vollast erzeugt er dann Speicherfehler?

Was ich auch mal hatte schadhafte SATA/IDE Kabel/Stecker, die verursachen Fehler die man schwer auf die Kabel zurückführen würde, mag banal klingen, aber das erlebte ich schon selbst bei neuen Rechnern, schlechte Kabelsteckverbindungen gerade bei SATA können auch dafür sorgen, dass bei starker Beanspruchung des Busses (wenn zur Reorganisation die Haupt Cronjobs laufen) es zu Timing Problemen kommt kann.




Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: Kernel panic täglich um 4 Uhr früh
« Reply #4 on: May 20, 2008, 03:00:04 PM »
Tja an die dachte ich auch aber weder root noch mein user haben welche eingetragen!
Aber mit Annamen kommt mann nirgendwo... kontrolieren bitte, wir sollen Sachen aussliessen stat sagen das sich nichts geändert hat, darum: Gibt es cronjobs die am etwa 4Uhr gestartet werden können?
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Offline slnx0001

  • 12
  • +0/-0
    • RetterForen.de
Re: Kernel panic täglich um 4 Uhr früh
« Reply #5 on: July 09, 2008, 04:07:46 PM »
Meines Wissens erfolgt immer morgens um 4:00 Uhr der Check nach Updates, vorausgesetzt die automatischen Updates sind aktiviert.

Hattest Du schon mal Probleme mit Deiner Netzwerkkarte, wenn sie belastet wurde? Ich hatte bei unserem Server mal das Problem mit einer Karte die er nicht mochte, kam dort ein bißchen mehr Traffic an hat das auch zu ner Kernelpanic geführt.

Oder hat es sich inzwischen erledigt?