Topic: Kernel Panic alle 2-3 Tage, samba-panic...

[PatchPanel]

Mein SME-Server 7.4 stürzt neuerdings alle 2-3 Tage komplett ab.

Kann jemand aus den messages etwas ersehen ?

Code: [Select]

Jun 19 07:53:45 server02 kernel: ------------[ cut here ]------------
Jun 19 07:53:45 server02 kernel: kernel BUG at arch/i386/mm/highmem.c:42!
Jun 19 07:53:45 server02 kernel: invalid operand: 0000 [#2]
Jun 19 07:53:45 server02 kernel: Modules linked in: appletalk(U) tg3 ipt_ULOG ipt_REJECT ppdev ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables vmnet(U) parport_pc parport vsock(U) vmci(U) vmmon(U) loop button battery ac ohci_hcd ehci_hcd k8_edac edac_mc bonding(U) floppy dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod sata_nv libata sd_mod scsi_mod
Jun 19 07:53:45 server02 kernel: CPU:    0
Jun 19 07:53:45 server02 kernel: EIP:    0060:[kmap_atomic+63/122]    Tainted: GF     VLI
Jun 19 07:53:45 server02 kernel: EIP:    0060:[<c011f13e>]    Tainted: GF     VLI
Jun 19 07:53:45 server02 kernel: EFLAGS: 00013206   (2.6.9-78.0.22.EL)
Jun 19 07:53:45 server02 kernel: EIP is at kmap_atomic+0x3f/0x7a
Jun 19 07:53:45 server02 kernel: eax: 00000068   ebx: c0002f44   ecx: c1b4f9c0   edx: 0000001a
Jun 19 07:53:45 server02 kernel: esi: fffd1000   edi: f71fc040   ebp: 00000000   esp: f670671c
Jun 19 07:53:45 server02 kernel: ds: 007b   es: 007b   ss: 0068
Jun 19 07:53:45 server02 kernel: Process vmware-vmx-stat (pid: 3880, threadinfo=f6706000 task=f6729830)
Jun 19 07:53:45 server02 kernel: Stack: f6fa5a5c 00000968 c015bfc4 f71fc040 00000000 00000000 f5a58bf4 c015c46b
Jun 19 07:53:45 server02 kernel:        00000001 f6729830 a5e5a000 f71fc040 f6706000 f71fc070 f6706794 f88dfdfe
Jun 19 07:53:45 server02 kernel:        00000001 00000000 00000000 f67067a4 00000000 c032629c f6706794 f88dfdd8
Jun 19 07:53:45 server02 kernel: Call Trace:
Jun 19 07:53:45 server02 kernel:  [follow_page+125/228] follow_page+0x7d/0xe4
Jun 19 07:53:45 server02 kernel:  [<c015bfc4>] follow_page+0x7d/0xe4
Jun 19 07:53:45 server02 kernel:  [get_user_pages+827/1161] get_user_pages+0x33b/0x489
Jun 19 07:53:45 server02 kernel:  [<c015c46b>] get_user_pages+0x33b/0x489
Jun 19 07:53:45 server02 kernel:  [<f88dfdfe>] HostIFGetUserPage+0x5a/0x88 [vmmon]
Jun 19 07:53:45 server02 kernel:  [__cond_resched+20/59] __cond_resched+0x14/0x3b
Jun 19 07:53:45 server02 kernel:  [<c032629c>] __cond_resched+0x14/0x3b
Jun 19 07:53:45 server02 kernel:  [<f88dfdd8>] HostIFGetUserPage+0x34/0x88 [vmmon]
Jun 19 07:53:45 server02 kernel:  [<f88dfe8c>] HostIF_LockPage+0x48/0x128 [vmmon]
Jun 19 07:53:45 server02 kernel:  [<f88e3e58>] Vmx86_LockPage+0x3c/0x68 [vmmon]
Jun 19 07:53:45 server02 kernel:  [<f88e2f4a>] LinuxDriver_Ioctl+0xc22/0xe04 [vmmon]
Jun 19 07:53:45 server02 kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<c012188b>] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [mempool_alloc+123/505] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [<c014f3ae>] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<c012188b>] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<f882abbb>] nv_adma_fill_sg+0x65/0xb8 [sata_nv]
Jun 19 07:53:45 server02 kernel:  [<f8846e1d>] scsi_done+0x0/0x16 [scsi_mod]
Jun 19 07:53:45 server02 kernel:  [<f882accb>] nv_adma_qc_issue+0x3e/0x4e [sata_nv]
Jun 19 07:53:45 server02 kernel:  [<f888bede>] ata_qc_issue+0x12c/0x157 [libata]
Jun 19 07:53:45 server02 kernel:  [<f888f331>] ata_scsi_translate+0x94/0xd2 [libata]
Jun 19 07:53:45 server02 kernel:  [<f8846e1d>] scsi_done+0x0/0x16 [scsi_mod]
Jun 19 07:53:45 server02 kernel:  [<f889023a>] ata_scsi_queuecmd+0x1cf/0x2ba [libata]
Jun 19 07:53:45 server02 kernel:  [<f888f059>] ata_scsi_rw_xlat+0x0/0x140 [libata]
Jun 19 07:53:45 server02 kernel:  [cfq_next_request+46/53] cfq_next_request+0x2e/0x35
Jun 19 07:53:45 server02 kernel:  [<c0265eb1>] cfq_next_request+0x2e/0x35
Jun 19 07:53:45 server02 kernel:  [elv_next_request+190/206] elv_next_request+0xbe/0xce
Jun 19 07:53:45 server02 kernel:  [<c025c234>] elv_next_request+0xbe/0xce
Jun 19 07:53:45 server02 kernel:  [mempool_alloc+123/505] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [<c014f3ae>] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<c012188b>] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [mempool_alloc+123/505] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [<c014f3ae>] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<c012188b>] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<c012188b>] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [cfq_set_request+51/107] cfq_set_request+0x33/0x6b
Jun 19 07:53:45 server02 kernel:  [<c026649e>] cfq_set_request+0x33/0x6b
Jun 19 07:53:45 server02 kernel:  [cfq_set_request+0/107] cfq_set_request+0x0/0x6b
Jun 19 07:53:45 server02 kernel:  [<c026646b>] cfq_set_request+0x0/0x6b
Jun 19 07:53:45 server02 kernel:  [elv_set_request+10/23] elv_set_request+0xa/0x17
Jun 19 07:53:45 server02 kernel:  [<c025c2de>] elv_set_request+0xa/0x17
Jun 19 07:53:45 server02 kernel:  [mempool_alloc+123/505] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [<c014f3ae>] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<c012188b>] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [mempool_alloc+123/505] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [<c014f3ae>] mempool_alloc+0x7b/0x1f9
Jun 19 07:53:45 server02 kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<c012188b>] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [<c012188b>] autoremove_wake_function+0x0/0x2d
Jun 19 07:53:45 server02 kernel:  [cfq_set_request+51/107] cfq_set_request+0x33/0x6b
Jun 19 07:53:45 server02 kernel:  [<c026649e>] cfq_set_request+0x33/0x6b
Jun 19 07:53:45 server02 kernel:  [cfq_set_request+0/107] cfq_set_request+0x0/0x6b
Jun 19 07:53:45 server02 kernel:  [<c026646b>] cfq_set_request+0x0/0x6b
Jun 19 07:53:45 server02 kernel:  [elv_set_request+10/23] elv_set_request+0xa/0x17
Jun 19 07:53:45 server02 kernel:  [<c025c2de>] elv_set_request+0xa/0x17
Jun 19 07:53:45 server02 kernel:  [get_request+917/927] get_request+0x395/0x39f
Jun 19 07:53:45 server02 kernel:  [<c025defb>] get_request+0x395/0x39f
Jun 19 07:53:45 server02 kernel:  [cfq_add_crq_rb+59/77] cfq_add_crq_rb+0x3b/0x4d
Jun 19 07:53:45 server02 kernel:  [<c0265b24>] cfq_add_crq_rb+0x3b/0x4d
Jun 19 07:53:45 server02 kernel:  [cfq_enqueue+51/100] cfq_enqueue+0x33/0x64
Jun 19 07:53:45 server02 kernel:  [<c026623f>] cfq_enqueue+0x33/0x64
Jun 19 07:53:45 server02 kernel:  [cfq_insert_request+109/223] cfq_insert_request+0x6d/0xdf
Jun 19 07:53:45 server02 kernel:  [<c02662dd>] cfq_insert_request+0x6d/0xdf
Jun 19 07:53:45 server02 kernel:  [__elv_add_request+79/135] __elv_add_request+0x4f/0x87
Jun 19 07:53:45 server02 kernel:  [<c025c04e>] __elv_add_request+0x4f/0x87
Jun 19 07:53:45 server02 kernel:  [__make_request+1237/1400] __make_request+0x4d5/0x578
Jun 19 07:53:45 server02 kernel:  [<c025f0c2>] __make_request+0x4d5/0x578
Jun 19 07:53:45 server02 kernel:  [<f88be354>] __journal_file_buffer+0x10f/0x1e8 [jbd]
Jun 19 07:53:45 server02 kernel:  [<f88bc480>] do_get_write_access+0x531/0x54d [jbd]
Jun 19 07:53:45 server02 kernel:  [__getblk+43/73] __getblk+0x2b/0x49
Jun 19 07:53:45 server02 kernel:  [<c0171586>] __getblk+0x2b/0x49
Jun 19 07:53:45 server02 kernel:  [<f88be354>] __journal_file_buffer+0x10f/0x1e8 [jbd]
Jun 19 07:53:45 server02 kernel:  [<f88bc480>] do_get_write_access+0x531/0x54d [jbd]
Jun 19 07:53:45 server02 kernel:  [<f88bc480>] do_get_write_access+0x531/0x54d [jbd]
Jun 19 07:53:45 server02 kernel:  [__cond_resched+20/59] __cond_resched+0x14/0x3b
Jun 19 07:53:45 server02 kernel:  [<c032629c>] __cond_resched+0x14/0x3b
Jun 19 07:53:45 server02 kernel:  [__getblk+43/73] __getblk+0x2b/0x49
Jun 19 07:53:45 server02 kernel:  [<c0171586>] __getblk+0x2b/0x49
Jun 19 07:53:45 server02 kernel:  [<f88f793c>] ext3_get_inode_loc+0x4f/0x223 [ext3]
Jun 19 07:53:45 server02 kernel:  [<f88f8166>] ext3_do_update_inode+0x2f7/0x31e [ext3]
Jun 19 07:53:45 server02 kernel:  [<f88bc4c1>] journal_get_write_access+0x25/0x2c [jbd]
Jun 19 07:53:45 server02 kernel:  [<f88be354>] __journal_file_buffer+0x10f/0x1e8 [jbd]
Jun 19 07:53:45 server02 kernel:  [<f88bcd9d>] journal_dirty_metadata+0x1f3/0x289 [jbd]
Jun 19 07:53:45 server02 kernel:  [<f88bc480>] do_get_write_access+0x531/0x54d [jbd]
Jun 19 07:53:45 server02 kernel:  [__cond_resched+20/59] __cond_resched+0x14/0x3b
Jun 19 07:53:45 server02 kernel:  [<c032629c>] __cond_resched+0x14/0x3b
Jun 19 07:53:45 server02 kernel:  [__getblk+43/73] __getblk+0x2b/0x49
Jun 19 07:53:45 server02 kernel:  [<c0171586>] __getblk+0x2b/0x49
Jun 19 07:53:45 server02 kernel:  [<f88f793c>] ext3_get_inode_loc+0x4f/0x223 [ext3]
Jun 19 07:53:45 server02 kernel:  [do_IRQ+691/703] do_IRQ+0x2b3/0x2bf
Jun 19 07:53:45 server02 kernel:  [<c01089ff>] do_IRQ+0x2b3/0x2bf
Jun 19 07:53:45 server02 kernel:  [common_interrupt+24/32] common_interrupt+0x18/0x20
Jun 19 07:53:45 server02 kernel:  [memcpy+35/43] memcpy+0x23/0x2b
Jun 19 07:53:45 server02 kernel:  [<c01ef4b3>] memcpy+0x23/0x2b
Jun 19 07:53:45 server02 kernel:  [avc_has_perm_noaudit+141/218] avc_has_perm_noaudit+0x8d/0xda
Jun 19 07:53:45 server02 kernel:  [<c01d4d70>] avc_has_perm_noaudit+0x8d/0xda
Jun 19 07:53:45 server02 kernel:  [avc_has_perm+59/71] avc_has_perm+0x3b/0x47
Jun 19 07:53:45 server02 kernel:  [<c01d4df8>] avc_has_perm+0x3b/0x47
Jun 19 07:53:45 server02 kernel:  [inode_has_perm+76/84] inode_has_perm+0x4c/0x54
Jun 19 07:53:45 server02 kernel:  [<c01d6336>] inode_has_perm+0x4c/0x54
Jun 19 07:53:45 server02 kernel:  [selinux_file_ioctl+662/674] selinux_file_ioctl+0x296/0x2a2
Jun 19 07:53:45 server02 kernel:  [<c01d8728>] selinux_file_ioctl+0x296/0x2a2
Jun 19 07:53:45 server02 kernel:  [do_IRQ+691/703] do_IRQ+0x2b3/0x2bf
Jun 19 07:53:45 server02 kernel:  [<c01089ff>] do_IRQ+0x2b3/0x2bf
Jun 19 07:53:45 server02 kernel:  [common_interrupt+24/32] common_interrupt+0x18/0x20
Jun 19 07:53:45 server02 kernel:  [<c03285b4>] common_interrupt+0x18/0x20
Jun 19 07:53:45 server02 kernel:  [schedule+1101/1542] schedule+0x44d/0x606
Jun 19 07:53:45 server02 kernel:  [<c0325289>] schedule+0x44d/0x606
Jun 19 07:53:45 server02 kernel:  [get_offset_pmtmr+19/1643] get_offset_pmtmr+0x13/0x66b
Jun 19 07:53:45 server02 kernel:  [<c01149a8>] get_offset_pmtmr+0x13/0x66b
Jun 19 07:53:45 server02 kernel:  [sys_ioctl+663/822] sys_ioctl+0x297/0x336
Jun 19 07:53:45 server02 kernel:  [<c0182c59>] sys_ioctl+0x297/0x336
Jun 19 07:53:45 server02 kernel:  [sys_gettimeofday+83/172] sys_gettimeofday+0x53/0xac
Jun 19 07:53:45 server02 kernel:  [<c0129995>] sys_gettimeofday+0x53/0xac
Jun 19 07:53:45 server02 kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Jun 19 07:53:45 server02 kernel:  [<c0327bdb>] syscall_call+0x7/0xb
Jun 19 07:53:45 server02 kernel: Code: 44 c0 73 09 5b 89 c8 5e e9 65 b8 03 00 89 de 8d 42 14 8b 1d 68 00 42 c0 c1 e0 0c 29 c6 8d 04 95 00 00 00 00 29 c3 83 3b 00 74 08 <0f> 0b 2a 00 e0 91 33 c0 8b 01 8b 15 10 d4 44 c0 f6 c4 08 a1 38
Jun 19 07:53:45 server02 kernel:  <0>Fatal exception: panic in 5 seconds
Jun 19 07:53:45 server02 kernel: bad: scheduling while atomic! ...[Rest aus Platzgründen weggelassen]
Beim letzten Mal habe ich dann neu gebootet, das RAID synct und alles wurde wieder gut...

Nach dem Absturz von heute kommt dann noch:

Code: [Select]

Jun 19 18:21:23 server02 smbd[5077]: [2009/06/19 18:21:23, 0] smbd/server.c:main(990)
Jun 19 18:21:23 server02 smbd[5077]:   standard input is not a socket, assuming -D option
Jun 19 18:21:23 server02 smbd[5077]: [2009/06/19 18:21:23, 0] lib/fault.c:fault_report(41)
Jun 19 18:21:23 server02 smbd[5077]:   ===============================================================
Jun 19 18:21:23 server02 smbd[5077]: [2009/06/19 18:21:23, 0] lib/fault.c:fault_report(42)
Jun 19 18:21:23 server02 smbd[5077]:   INTERNAL ERROR: Signal 11 in pid 5077 (3.0.28-0.el4.9)
Jun 19 18:21:23 server02 smbd[5077]:   Please read the Trouble-Shooting section of the Samba3-HOWTO
Jun 19 18:21:23 server02 smbd[5077]: [2009/06/19 18:21:23, 0] lib/fault.c:fault_report(44)
Jun 19 18:21:23 server02 smbd[5077]:   
Jun 19 18:21:23 server02 smbd[5077]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Jun 19 18:21:23 server02 smbd[5077]: [2009/06/19 18:21:23, 0] lib/fault.c:fault_report(45)
Jun 19 18:21:23 server02 smbd[5077]:   ===============================================================
Jun 19 18:21:23 server02 smbd[5077]: [2009/06/19 18:21:23, 0] lib/util.c:smb_panic(1655)
Jun 19 18:21:23 server02 smbd[5077]:   PANIC (pid 5077): internal error
Jun 19 18:21:23 server02 smbd[5077]: [2009/06/19 18:21:23, 0] lib/util.c:log_stack_trace(1759)
Jun 19 18:21:23 server02 smbd[5077]:   BACKTRACE: 10 stack frames:
Jun 19 18:21:23 server02 smbd[5077]:    #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x4d8b00]
Jun 19 18:21:23 server02 smbd[5077]:    #1 /usr/sbin/smbd(smb_panic+0x56) [0x4d8c07]
Jun 19 18:21:23 server02 smbd[5077]:    #2 /usr/sbin/smbd [0x4c50f5]
Jun 19 18:21:23 server02 smbd[5077]:    #3 /lib/tls/libc.so.6 [0x814918]
Jun 19 18:21:23 server02 smbd[5077]:    #4 /usr/sbin/smbd(regdb_fetch_keys+0x174) [0x5936ee]
Jun 19 18:21:23 server02 smbd[5077]:    #5 /usr/sbin/smbd(regdb_init+0x2a7) [0x5945d0]
Jun 19 18:21:23 server02 smbd[5077]:    #6 /usr/sbin/smbd(init_registry+0x19) [0x58f2b9]
Jun 19 18:21:23 server02 smbd[5077]:    #7 /usr/sbin/smbd(main+0x3d3) [0x5a2f55]
Jun 19 18:21:23 server02 smbd[5077]:    #8 /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x801df3]
Jun 19 18:21:23 server02 smbd[5077]:    #9 /usr/sbin/smbd [0x2fb9f1]
Jun 19 18:21:23 server02 smbd[5077]: [2009/06/19 18:21:23, 0] lib/fault.c:dump_core(181)
Jun 19 18:21:23 server02 smbd[5077]:   dumping core in /var/log/samba/cores/smbd
Jun 19 18:21:23 server02 smbd[5077]:
und ich komme nicht auf die Netzlaufwerke drauf...


Den Server habe ich vor ca. 1,5 Wochen direkt mit 7.4 neu aufgesetzt.
Gegenüber meinem alten der mit der Zeit über mehrere Versionen aktualisiert wurde, fällt mir noch eine erhöhte Festplattenaktivität auf (rein subjektiv anhand der LED, obwohl keine Maschinen verbunden sind), sowie eine nahezu dauernde CPU-Aktivität von 100% (sme7admin).



Bin für jede Hilfe dankbar !



Gruß
PatchPanel

[PatchPanel]

Das RAID musste diesmal nicht synchronisiert werden und Samba läuft nach einem Reboot auch wieder... 


In der STATUS emails vom sme7admin steht folgendes:

Code: [Select]

#>tail /var/log/messages :
Jun 19 19:15:36 server02 esmith::event[4739]: Running event handler: /etc/e-smith/events/actions/generic_template_expand
Jun 19 19:15:37 server02 esmith::event[4739]: expanding /etc/sysconfig/kernel 
Jun 19 19:15:37 server02 esmith::event[4739]: expanding /boot/grub/grub.conf 
Jun 19 19:15:37 server02 esmith::event[4739]: generic_template_expand=action|Event|local|Action|generic_template_expand|Start|1245431736 890982|End|1245431737 919404|Elapsed|1.028422
Jun 19 19:15:37 server02 esmith::event[4739]: Running event handler: /etc/e-smith/events/local/S50clear-pptp-interfaces
Jun 19 19:15:38 server02 esmith::event[4739]: S50clear-pptp-interfaces=action|Event|local|Action|S50clear-pptp-interfaces|Start|1245431737 919666|End|1245431738 3522|Elapsed|0.083856
Jun 19 19:15:38 server02 esmith::event[4739]: Running event handler: /etc/e-smith/events/actions/adjust-services
Jun 19 19:15:38 server02 esmith::event[4739]: adjusting supervised yum (once) 
Jun 19 19:15:38 server02 esmith::event[4739]: adjust-services=action|Event|local|Action|adjust-services|Start|1245431738 3867|End|1245431738 167959|Elapsed|0.164092
Jun 19 19:15:40 server02 fstab-sync[4823]: added mount point /media/cdrom for /dev/hda
und

Code: [Select]

#>tail /var/log/messages :
Jun 17 18:38:32 server02 last message repeated 61 times
Jun 17 18:39:33 server02 last message repeated 61 times
Jun 17 18:40:01 server02 su(pam_unix)[11870]: session opened for user qmailr by (uid=0)
Jun 17 18:40:34 server02 last message repeated 61 times
Jun 17 18:40:44 server02 su(pam_unix)[11870]: session closed for user qmailr
Jun 17 18:41:35 server02 last message repeated 61 times
Jun 17 18:42:36 server02 last message repeated 61 times
Jun 17 18:43:37 server02 last message repeated 61 times
Jun 17 18:44:38 server02 last message repeated 61 times
Jun 17 18:45:01 server02 su(pam_unix)[12175]: session opened for user qmailr by (uid=0)

Erfordert das noch ein Eingreifen ?
Wie kann man das bereinigen ?



Danke und
Gruß
PatchPanel

[Igi2003]

Das sieht mir nach nem Speicherdefekt aus. Check mal dein RAM mit memtest, austauschen, dann dürfte gut sein. Du hast nämlich nen Error in HighMEM. Dummerweise scheint sich da samba eingenistet zu haben, deswegen der fehler.

Mfg

[PatchPanel]

Krass, hätte ich nicht gedacht - der zweite von 4 DIMM's ist defekt...
Danke für den Hinweis !


Kannst Du noch was zu den anderen messages sagen ?

Gruß
PatchPanel

[Igi2003]

Im Moment nicht. Aber dein qmail is kräftig am schaffen, deswegen die wiederholten Zeilen.
Check mal was dein Qmail macht oder nicht schafft, evtl. ne Mail die nach außen soll, aber geblockt wird da private IP.

Mfg