logcheck sniffed these out of my system logs lately -- does it indicate anything serious?
Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:44:38 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:44:38 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:46:53 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:46:53 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:46:53 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:46:53 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) Feb 23 20:46:53 server kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) Feb 23 20:46:53 server kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) -- I use Debian/GNU Linux version 3.0; Linux server 2.4.20-k6 #1 Mon Jan 13 23:49:14 EST 2003 i586 unknown DEBIAN NEWBIE TIP #25 from Will Trillich <[EMAIL PROTECTED]> : Did you know you have MORE THAN ONE CONSOLE to use? There's six, by default: try Control-Alt-F6 to see console six, Ctl-Alt-F3 for console 3, and so forth. (If you don't use the X window display system, you don't need to include the control key. If you do have X running, you can return to it from any console via Alt-F7, unless you've changed the defaults.) Each console can have its own login, running its own jobs. Very handy! Also see http://newbieDoc.sourceForge.net/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
