Topic: SME Server 7.0 ne répond plus

[ohaldi]

Bonjour à tous,
J'ai installé SME Server 7.0 sur un petit Asus Pundit. La tâche principal de SME Server est de récupérer me e-mails dans les divers comptes pop.
Malheureusement de temps en temps, je dois redémarrer la machine parce-qu'elle ne répond plus. Je ne peux que le redémarrer pour y avoir à nouveau accès.
Comment puis-je tracer les causes de ces arrêts?
Merci d'avances pour tous renseignements.
Otto

[baud]

Bonjour,
je suis dans le même cas que Ohaldi    avec cette même option de récupération de courrier pop.

Ma question recoupe également celle posée: Comment peut-on tracer les causes de ces arrêts?

Par avance merci
Baud

[baud]

Code: [Select]

May  5 09:45:01 sme su(pam_unix)[32283]: session opened for user qmailr by (uid=0)
May  5 09:45:09 sme su(pam_unix)[32283]: session closed for user qmailr
May  5 09:45:09 sme crond(pam_unix)[32281]: session closed for user root
May  5 10:00:01 sme crond(pam_unix)[32407]: session opened for user root by (uid=0)
May  5 10:00:02 sme su(pam_unix)[32409]: session opened for user qmailr by (uid=0)
May  5 10:00:10 sme su(pam_unix)[32409]: session closed for user qmailr
May  5 10:00:10 sme crond(pam_unix)[32407]: session closed for user root
May  5 10:01:01 sme crond(pam_unix)[32448]: session opened for user root by (uid=0)
May  5 10:01:06 sme crond(pam_unix)[32448]: session closed for user root
May  5 10:13:02 sme crond(pam_unix)[32526]: session opened for user root by (uid=0)
May  5 10:13:09 sme crond(pam_unix)[32526]: session closed for user root
May  5 10:15:01 sme crond(pam_unix)[32532]: session opened for user root by (uid=0)
May  5 10:15:01 sme su(pam_unix)[32534]: session opened for user qmailr by (uid=0)
May  5 10:15:09 sme su(pam_unix)[32534]: session closed for user qmailr
May  5 10:15:09 sme crond(pam_unix)[32532]: session closed for user root
May  5 10:20:00 sme kernel: divide error: 0000 [#1]
May  5 10:20:00 sme kernel: Modules linked in: via686a eeprom lm80 i2c_sensor i2c_isa i2c_viapro i2c_core appletalk(U) 8139too bonding(U) ipt_ULOG ipt_MASQUERADE ipt_state ipt_TOS ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables button battery ac uhci_hcd parport_pc parport snd_via82xx snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore mii dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod
May  5 10:20:00 sme kernel: CPU:    0
May  5 10:20:00 sme kernel: EIP:    0060:[__tcp_select_window+249/265]    Not tainted VLI
May  5 10:20:00 sme kernel: EIP:    0060:[<c02e0389>]    Not tainted VLI
May  5 10:20:00 sme kernel: EFLAGS: 00010202   (2.6.9-34.EL)
May  5 10:20:00 sme kernel: EIP is at __tcp_select_window+0xf9/0x109
May  5 10:20:00 sme kernel: eax: 00000000   ebx: 00000000   ecx: 2b7ffffe   edx: 00000000
May  5 10:20:00 sme kernel: esi: caa2f868   edi: 00001d50   ebp: 00000000   esp: c96ffd24
May  5 10:20:00 sme kernel: ds: 007b   es: 007b   ss: 0068
May  5 10:20:00 sme kernel: Process httpd (pid: 3318, threadinfo=c96ff000 task=c0516270)
May  5 10:20:00 sme kernel: Stack: 00000000 0000fa4b 00001b69 caa2f868 caa2f868 c1ff40cc c02df2ec cf1025f8
May  5 10:20:00 sme kernel:        00100000 c01cbc2d 00000000 00000003 00000001 00000000 00000014 cb621a18
May  5 10:20:00 sme kernel:        cb6219e0 caa2f600 caa2f868 cb621b60 caa2f600 00000006 c02e0098 00000000
May  5 10:20:01 sme kernel: Call Trace:
May  5 10:20:01 sme kernel:  [tcp_transmit_skb+574/2006] tcp_transmit_skb+0x23e/0x7d6
May  5 10:20:01 sme kernel:  [<c02df2ec>] tcp_transmit_skb+0x23e/0x7d6
May  5 10:20:01 sme kernel:  [avc_has_perm_noaudit+140/217] avc_has_perm_noaudit+0x8c/0xd9
May  5 10:20:01 sme kernel:  [<c01cbc2d>] avc_has_perm_noaudit+0x8c/0xd9
May  5 10:20:01 sme kernel:  [tcp_write_xmit+118/622] tcp_write_xmit+0x76/0x26e
May  5 10:20:01 sme kernel:  [<c02e0098>] tcp_write_xmit+0x76/0x26e
May  5 10:20:01 sme kernel:  [tcp_sendmsg+2644/3004] tcp_sendmsg+0xa54/0xbbc
May  5 10:20:01 sme kernel:  [<c02d6355>] tcp_sendmsg+0xa54/0xbbc
May  5 10:20:01 sme kernel:  [inet_sendmsg+56/66] inet_sendmsg+0x38/0x42
May  5 10:20:01 sme kernel:  [<c02f27f5>] inet_sendmsg+0x38/0x42
May  5 10:20:01 sme kernel:  [sock_sendmsg+219/247] sock_sendmsg+0xdb/0xf7
May  5 10:20:01 sme kernel:  [<c02aafa0>] sock_sendmsg+0xdb/0xf7
May  5 10:20:01 sme kernel:  [tcp_recvmsg+1495/1554] tcp_recvmsg+0x5d7/0x612
May  5 10:20:01 sme kernel:  [<c02d720a>] tcp_recvmsg+0x5d7/0x612
May  5 10:20:01 sme kernel:  [sock_common_recvmsg+48/70] sock_common_recvmsg+0x30/0x46
May  5 10:20:01 sme kernel:  [<c02ae8d9>] sock_common_recvmsg+0x30/0x46
May  5 10:20:01 sme kernel:  [sock_aio_read+269/283] sock_aio_read+0x10d/0x11b
May  5 10:20:01 sme kernel:  [<c02ab23a>] sock_aio_read+0x10d/0x11b
May  5 10:20:01 sme kernel:  [autoremove_wake_function+0/45] autoremove_wake_function+0x0/0x2d
May  5 10:20:01 sme kernel:  [<c011e887>] autoremove_wake_function+0x0/0x2d
May  5 10:20:01 sme kernel:  [inode_has_perm+76/84] inode_has_perm+0x4c/0x54
May  5 10:20:02 sme kernel:  [<c01cd1eb>] inode_has_perm+0x4c/0x54
May  5 10:20:02 sme kernel:  [sock_readv_writev+124/129] sock_readv_writev+0x7c/0x81
May  5 10:20:02 sme kernel:  [<c02ab416>] sock_readv_writev+0x7c/0x81
May  5 10:20:02 sme kernel:  [sock_writev+42/49] sock_writev+0x2a/0x31
May  5 10:20:02 sme kernel:  [<c02ab479>] sock_writev+0x2a/0x31
May  5 10:20:02 sme kernel:  [sock_writev+0/49] sock_writev+0x0/0x31
May  5 10:20:02 sme kernel:  [<c02ab44f>] sock_writev+0x0/0x31
May  5 10:20:02 sme kernel:  [do_readv_writev+412/541] do_readv_writev+0x19c/0x21d
May  5 10:20:02 sme kernel:  [<c0168ee3>] do_readv_writev+0x19c/0x21d
May  5 10:20:02 sme kernel:  [sock_common_setsockopt+21/25] sock_common_setsockopt+0x15/0x19
May  5 10:20:02 sme kernel:  [<c02ae904>] sock_common_setsockopt+0x15/0x19
May  5 10:20:02 sme kernel:  [sys_setsockopt+114/137] sys_setsockopt+0x72/0x89
May  5 10:20:02 sme kernel:  [<c02ac467>] sys_setsockopt+0x72/0x89
May  5 10:20:02 sme kernel:  [sys_setsockopt+128/137] sys_setsockopt+0x80/0x89
May  5 10:20:02 sme kernel:  [<c02ac475>] sys_setsockopt+0x80/0x89
May  5 10:20:02 sme kernel:  [sys_socketcall+441/506] sys_socketcall+0x1b9/0x1fa
May  5 10:20:02 sme kernel:  [<c02acb11>] sys_socketcall+0x1b9/0x1fa
May  5 10:20:02 sme kernel:  [vfs_writev+62/67] vfs_writev+0x3e/0x43
May  5 10:20:02 sme kernel:  [<c0168fe2>] vfs_writev+0x3e/0x43
May  5 10:20:02 sme kernel:  [sys_writev+60/98] sys_writev+0x3c/0x62
May  5 10:20:02 sme kernel:  [<c0169085>] sys_writev+0x3c/0x62
May  5 10:20:02 sme kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
May  5 10:20:02 sme kernel:  [<c030fe57>] syscall_call+0x7/0xb
May  5 10:20:02 sme kernel: Code: d1 89 df d3 fb 89 d8 d3 e0 39 f8 74 25 8d 7b 01 d3 e7 eb 1e 89 d8 29 e8 39 c7 0f 9e c2 39 df 0f 9f c0 09 d0 a8 01 74 0a 89 d8 99 <f7> fd 89 c7 0f af fd 89 f8 59 5b 5b 5e 5f 5d c3 55 57 56 53 83
May  5 10:20:02 sme kernel:  <0>Fatal exception: panic in 5 seconds
May  5 12:51:20 sme syslogd 1.4.1: restart.
May  5 12:51:20 sme syslog: Démarrage de syslogd succeeded


J'ai du mal à comprendre ce qui se passe avant le kernel panic??
 

Baud
--------
http://baud.homelinux.net