Strona 1 z 1

Co jakiś czas przestaje działać poprawnie routing?

: 21 czerwca 2009, 19:37
autor: prot
Witam.
Mam problem tego typu iż pada mi routing co jakiś czas.
Log błędu wygląda tak.:

Kod: Zaznacz cały

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@host-xxx-xxx-xxx-xxx :~#
Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: Oops: 0000 [#1]

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: CPU:    0

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: EIP:    0060:[<c065147d>]    Not tainted VLI

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: EFLAGS: 00010286   (2.6.22.12-net_system #1)

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: EIP is at __ip_route_output_key+0x20d/0x890

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: eax: 80000000   ebx: 00000000   ecx: 00000000   edx:                                              000000e0

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: esi: f7049e5c   edi: a0b317ec   ebp: f7049d64   esp:                                              f7049d44

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: ds: 007b   es: 007b   fs: 0000  gs: 0033  ss: 0068

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: Process squid (pid: 4741, ti=f7048000 task=f7d32a70 t                                             ask.ti=f7048000)

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: Stack: fffef6ad f7049e98 00000000 00650dee 00000001 0                                             000a728 f7926000 00000000

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:        00000000 00000001 00000000 a0b317ec 2a9fc35b 0                                             0000000 00000000 00000000

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:        00000000 00000000 00000000 00000000 00000000 0                                             0000000 00000000 2a05c35b

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: Call Trace:

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c0651b1e>] ip_route_output_flow+0x1e/0x250

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c0670230>] tcp_v4_connect+0x150/0x640

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c0125200>] autoremove_wake_function+0x0/0x50

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c067d608>] inet_stream_connect+0x1e8/0x270

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c062d735>] sys_recvfrom+0x125/0x180

Message from syslogd@host-v at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c062c1e5>] sys_connect+0xd5/0xf0

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c0125200>] autoremove_wake_function+0x0/0x50

Message from syslogd@host-xxx-xxx-xxx-xxx 2 at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c062dc28>] sys_socketcall+0x98/0x280

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  [<c01027c2>] sysenter_past_esp+0x5f/0x85

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel:  =======================

Message from syslogd@host-xxx-xxx-xxx-xxx at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: Code: 00 00 81 fa e0 00 00 00 0f 84 03 04 00 00 81 fa                                              f0 00 00 00 0f 84 57 02 00 00 84 c0 0f 84 4f 02 00 00 8b 44 24 08 0d 00 00 00 8                                             0 <f6> 83 b8 00 00 00 08 0f 44 44 24 08 89 44 24 08 8b ab 08 01 00

Message from syslogd@host-xxx-xxx-xxx-xxx  at Sun Jun 21 17:43:25 2009 ...
host-xxx-xxx-xxx-xxx  kernel: EIP: [<c065147d>] __ip_route_output_key+0x20d/0x890 S                                             S:ESP 0068:f7049d44
Ktoś wie jaka możne być przyczyna takiego stanu rzeczy?
Dodam jeszcze iż wszystkie aplikacje działają prócz www wydaje mi się ze błąd jest spowodowany błędem powodowanym przez squida.

: 21 czerwca 2009, 22:20
autor: killanonimx
To chyba są błędy z kernela, a dokładniej modułu odpowiedzialnego za tcp/ip.
Jakiś pakiet się trafia, no i siada.

[ Dodano: 2009-06-21, 22:21 ]
A może to jednak squid