Re: TUX: error -98 binding sock...

Hi Juan,

I have the very same problem and I've been trying to help Ingo Molnar to
solve this problem for a very long time, please check the following bug
report:
[] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D125091

I just posted a new comment on the bug and attached a new backtrace that
looks pretty much like yours.  Please, post your problem in that bug and
give a detailed description of your hardware.

I had a very good experience with tux on the 2.4 kernel back in the
RedHat 9 days.

I'm glad to see that I'm not alone with this problem.

Ingo? I hope you can give this another look.

Thanx.


-William


El dom, 13-11-2005 a las 09:42 +0100, [email protected] escribi=C3=B3=
:
> Hello all. I have more information on this issue.
>=20
> My TUX version:
> [root@neuron ~]# rpm -qa | grep tux
> tux-3.2.18-2
>=20
> I had to return to Apache handling all requests after more than four pa=
nics exactly the same:
>=20
> from /var/log/messages:
>=20
> Nov 12 04:32:16 neuron kernel: Unable to handle kernel NULL pointer der=
eference at virtual address 00000024
> Nov 12 04:32:16 neuron kernel:  printing eip:
> Nov 12 04:32:16 neuron kernel: f8a2de4b
> Nov 12 04:32:16 neuron kernel: *pde =3D 37066001
> Nov 12 04:32:16 neuron kernel: Oops: 0002 [#1]
> Nov 12 04:32:16 neuron kernel: SMP
> Nov 12 04:32:16 neuron kernel: Modules linked in: ipt_TOS iptable_mangl=
e ip_conntrack_ftp ip_conntrack_irc ipt_REJECT ipt_LOG ipt_limit ipt_mult=
iport ipt_state ip_conntrack iptable_filter ip_tables md5 ipv6 parport_pc=
 lp parport tux zlib$
> Nov 12 04:32:16 neuron kernel: CPU:    2
> Nov 12 04:32:16 neuron kernel: EIP:    0060:[<f8a2de4b>]    Not tainted=
 VLI
> Nov 12 04:32:16 neuron kernel: EFLAGS: 00010246   (2.6.9-22.0.1.ELsmp)
> Nov 12 04:32:16 neuron kernel: EIP is at do_send_abuf+0xa1/0x17c [tux]
> Nov 12 04:32:16 neuron kernel: eax: 00000000   ebx: f563d000   ecx: 000=
04040   edx: 00000000
> Nov 12 04:32:16 neuron kernel: esi: 00000000   edi: f563d134   ebp: f56=
3d000   esp: f68bbf10
> Nov 12 04:32:16 neuron kernel: ds: 007b   es: 007b   ss: 0068
> Nov 12 04:32:16 neuron kernel: Process tux (pid: 19632, threadinfo=3Df6=
8bb000 task=3Df6a2e8b0)
> Nov 12 04:32:16 neuron kernel: Stack: 00000000 f563d000 00000000 f8a3d4=
38 00000004 f8a2102e f563d000 f563d028
> Nov 12 04:32:16 neuron kernel:        f8a21cf3 f68bbf4c f8a3d438 000000=
00 00000000 f68bb000 f8a2b744 00000000
> Nov 12 04:32:16 neuron kernel:        00000005 00000005 f8a2d1d6 c0164f=
bc 00000000 c0158c58 f74992ac f8a3d438
> Nov 12 04:32:16 neuron kernel: Call Trace:
> Nov 12 04:32:16 neuron kernel:  [<f8a2102e>] tux_schedule_atom+0x2a/0x4=
2 [tux]
> Nov 12 04:32:16 neuron kernel:  [<f8a21cf3>] process_requests+0x91/0xa6=
 [tux]
> Nov 12 04:32:17 neuron kernel:  [<f8a2b744>] event_loop+0x75/0x178 [tux=
]
> Nov 12 04:32:17 neuron kernel:  [<f8a2d1d6>] __sys_tux+0x366/0x88f [tux=
]
> Nov 12 04:32:17 neuron kernel:  [<c0164fbc>] path_release+0xa/0x2d
> Nov 12 04:32:17 neuron kernel:  [<c0158c58>] sys_chdir+0x57/0x5f
> Nov 12 04:32:17 neuron kernel:  [<c012e12b>] sys_setuid+0xfc/0x108
> Nov 12 04:32:17 neuron kernel:  [<c02d0fb7>] syscall_call+0x7/0xb
> Nov 12 04:32:17 neuron kernel: Code: ff ff 5f 89 c2 58 89 73 18 85 d2 7=
9 79 83 fa f5 74 4a c6 85 e8 03 00 00 03 8b 45 6c 31 d2 c7 45 04 00 00 00=
 00 8d bd 34 01 00 00 <c7> 40 24 00 00 00 00 c7 40 28 00 00 00 00 8b 85 3=
4 01 00 00 e8
> Nov 12 04:32:17 neuron kernel:  <0>Fatal exception: panic in 5 seconds
>=20
>=20
> The server details:
>=20
> CentOS release 4.2 (Final)
> Linux version 2.6.9-22.0.1.ELsmp (buildcentos@x8664-build)
> (gcc version 3.4.4 20050721 (Red Hat 3.4.4-2))
> #1 SMP Thu Oct 27 13:14:25 CDT 2005
>=20
> This server performed well with TUX using kernel 2.4 and CentOS 3.6. No=
 hardware changes were made.
>=20
> Thank you for any point out on this.
>=20
> Regards,
>=20
> Juan
>=20
>=20
> [email protected] wrote:
> > Hello all,
> >
> > I had to reboot a TUX enabled server that threw a:
> >
> > Kernel panic - no syncing: Fatal exception
> >
> > After a reboot, all went well and it keeps going for now.
> >
> > The daily Logwatch showed:
> >
> > WARNING:  Kernel Errors Present
> >    TUX: error -98 binding sock...:  4 Time(s)
> >
> >
> > The linux server:
> >
> > CentOS release 4.2 (Final)
> > Linux version 2.6.9-22.0.1.ELsmp (buildcentos@x8664-build)
> > (gcc version 3.4.4 20050721 (Red Hat 3.4.4-2))
> > #1 SMP Thu Oct 27 13:14:25 CDT 2005
> >
> > I had been installing / configuring TUX using "mount --bind" before t=
he crash,
> > nothing special. Since I have very good experience from TUX and didn'=
t find
> > anything about this error, I just wanted to share this to see if anyb=
ody can
> > enlighten this up a bit?
> >
> > Thank you.
> >
> > Juan
> >
> > http://www.prisonserver.com
> >
> > _______________________________________________
> > tux-list mailing list
> > [email protected]
> > https://www.redhat.com/mailman/listinfo/tux-list
> >
> >
> >
> >  =20
>=20
> _______________________________________________
> tux-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/tux-list