From nicolas at incrowd.be Tue Nov 8 01:08:01 2005 From: nicolas at incrowd.be (Nicolas Van Eenaeme) Date: Tue, 8 Nov 2005 02:08:01 +0100 Subject: Crashing TUX In-Reply-To: <1129897758.13105.14.camel@nalwalovaton.coomeva.nal> Message-ID: <20051108010759.0BCFA3800D@astra.telenet-ops.be> Hi William, Last week I had a crash again and I managed to do the ps aux | grep ' [DRZ]'. This is the output: poison at static:~$ ps aux | grep ' [DRZ]' USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 5 0.0 0.0 0 0 ? Z Nov02 1:23 [kswapd] web 412 0.0 0.0 2260 816 ? D Nov02 0:08 [TUX worker 0] web 413 3.5 0.0 2260 816 ? R Nov02 101:00 [TUX worker 1] web 414 0.0 0.0 2260 816 ? D Nov02 0:00 [TUX worker 0] web 417 0.1 0.0 2260 816 ? D Nov02 3:24 [TUX worker 1] web 418 0.0 0.0 2260 816 ? D Nov02 0:02 [TUX worker 1] nobody 18631 0.6 0.0 1532 736 ? D 06:25 1:13 /usr/bin/find / ( -fstype NFS -o -fstype nfs -o -fstype afs -o -fstype proc -o -fstype smbfs -o -fstype autofs -o -fstype iso9660 -o -fstype ncpfs -o -fstype coda -o -fstype devpts -o -fstype ftpfs -o -fstype devfs -o -fstype mfs -o -fstype shfs -o -fstype sysfs -o -fstype cifs -o -fstype lustre_lite -o -type d -regex \(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex $\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\) ) -prune -o -print poison 18919 1.0 0.0 2488 872 pts/0 R+ 09:22 0:00 ps aux poison 18920 0.0 0.0 1544 476 pts/0 R+ 09:22 0:00 grep [DRZ] I don't know what that find process is but I think it shouldn't be there. Maybe the TUX worker 1 (PID 413) is the problem. Do you have any ideas what could be causing these crashes? Thanks in advance, Nicolas Van Eenaeme -----Oorspronkelijk bericht----- Van: tux-list-bounces at redhat.com [mailto:tux-list-bounces at redhat.com] Namens William Lovaton Verzonden: vrijdag 21 oktober 2005 14:29 Aan: TUX discussion list Onderwerp: Re: Crashing TUX Hi Nicolas, Are you sure your load problems are about tux? Did you checked your cron jobs? may be it's logrotate or something like that. When the load is that high you can log into the system and execute this command: ps aux | grep ' [DRZ]' All of the processes with state D or R are the ones generating the high load, with this information you can identify the offending processes. BTW, what distro and version are you using? Right now I have a lot of experience with Fedora Core 3. -William El vie, 21-10-2005 a las 10:02 +0200, Nicolas Van Eenaeme escribi?: > Hi all, > > > > I?m running TUX on a popular website here in Belgium (>2.000.000 > pageviews / day) and I use it to serve all my static content (images, > css, ). > > This works great. The average load on my server stays below 1. But > after each period of 5 days (average) the load suddenly goes to 6 or > above (I can see this on my MRTG stats) and it takes ages to serve a > simple image. If this happens the only way to fix it is to reboot my > server. It?s strange because this happens early in the morning > (usually between 5 ? 7 am.) when there are almost no users on the > site. > > > > Is there somebody who can help me or do you have some suggestions for > me how I can fix this? I?m running the 2.4 kernel. > > > > Thanks in advance, > > Nicolas Van Eenaeme > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list _______________________________________________ tux-list mailing list tux-list at redhat.com https://www.redhat.com/mailman/listinfo/tux-list From mcd at daviesinc.com Tue Nov 8 01:59:22 2005 From: mcd at daviesinc.com (Chris Davies) Date: Mon, 07 Nov 2005 20:59:22 -0500 Subject: Crashing TUX In-Reply-To: <20051108010759.0BCFA3800D@astra.telenet-ops.be> References: <20051108010759.0BCFA3800D@astra.telenet-ops.be> Message-ID: <4370067A.5000007@daviesinc.com> that find process is part of updatedb -- has nothing to do with tux. Nicolas Van Eenaeme wrote: > > Last week I had a crash again and I managed to do the ps aux | grep ' > [DRZ]'. This is the output: > > poison at static:~$ ps aux | grep ' [DRZ]' > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > root 5 0.0 0.0 0 0 ? Z Nov02 1:23 [kswapd] > ^^^^ this looks rather suspect > nobody 18631 0.6 0.0 1532 736 ? D 06:25 1:13 /usr/bin/find > / ( -fstype NFS -o -fstype nfs -o -fstype afs -o -fstype proc -o -fstype > smbfs -o -fstype autofs -o -fstype iso9660 -o -fstype ncpfs -o -fstype coda > -o -fstype devpts -o -fstype ftpfs -o -fstype devfs -o -fstype mfs -o > -fstype shfs -o -fstype sysfs -o -fstype cifs -o -fstype lustre_lite -o > -type d -regex > \(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex > $\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\) ) -prune -o -print ^^^^ from updatedb From williama_lovaton at coomeva.com.co Tue Nov 8 13:05:52 2005 From: williama_lovaton at coomeva.com.co (William Lovaton) Date: Tue, 08 Nov 2005 08:05:52 -0500 Subject: Crashing TUX In-Reply-To: <20051108010759.0BCFA3800D@astra.telenet-ops.be> References: <20051108010759.0BCFA3800D@astra.telenet-ops.be> Message-ID: <1131455152.3841.10.camel@nalwalovaton.coomeva.nal> Hi Nicolas, Like Chris says, that find process seems to be from a cron job. But contrary to what he says I think it might be affecting tux because it is using the disk heavily (at least performance wise). I'm not really sure that tux crashed, I skimmed through this thread and I don't see that you posted any crash report, can you check /var/log/messages to see if there is any sign of problems with tux? if there is a crash it might be useful to get the backtrace in that file posted on this list. Another thing, what distro do you have? right now I'm using Fedora Core 3 (2.6 kernel) on my desktop and on my production server and the system's crontab says something like this: # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly It means it will execute every script in those directories (/etc/cron.*) and may be the 'find' process is executed from one of them. Try to adjust the hours to start in a "quiet" hour according to your server usage. As a blind guess I think the script might be in /etc/cron.weekly since you said the problem happens every 5 days or so. Besides, you also said that it happens between 5 and 7 AM and looking at the ps output, it started and 6:25 AM and is running with the 'nobody' user. The other strange thing I see is that kswapd is in a zombie state (Z), may be there is nothing bad about it but I can't recall seeing that on my systems. How is your ram coming along? are you sure you have enough? next time try to check you RAM when this problems happens again. Good luck, -William El mar, 08-11-2005 a las 02:08 +0100, Nicolas Van Eenaeme escribi?: > Hi William, > > Last week I had a crash again and I managed to do the ps aux | grep ' > [DRZ]'. This is the output: > > poison at static:~$ ps aux | grep ' [DRZ]' > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > root 5 0.0 0.0 0 0 ? Z Nov02 1:23 [kswapd] > > web 412 0.0 0.0 2260 816 ? D Nov02 0:08 [TUX worker > 0] > web 413 3.5 0.0 2260 816 ? R Nov02 101:00 [TUX worker > 1] > web 414 0.0 0.0 2260 816 ? D Nov02 0:00 [TUX worker > 0] > web 417 0.1 0.0 2260 816 ? D Nov02 3:24 [TUX worker > 1] > web 418 0.0 0.0 2260 816 ? D Nov02 0:02 [TUX worker > 1] > nobody 18631 0.6 0.0 1532 736 ? D 06:25 1:13 /usr/bin/find > / ( -fstype NFS -o -fstype nfs -o -fstype afs -o -fstype proc -o -fstype > smbfs -o -fstype autofs -o -fstype iso9660 -o -fstype ncpfs -o -fstype coda > -o -fstype devpts -o -fstype ftpfs -o -fstype devfs -o -fstype mfs -o > -fstype shfs -o -fstype sysfs -o -fstype cifs -o -fstype lustre_lite -o > -type d -regex > \(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/afs$\)\|\(^/amd$\)\|\(^/alex > $\)\|\(^/var/spool$\)\|\(^/sfs$\)\|\(^/media$\) ) -prune -o -print > poison 18919 1.0 0.0 2488 872 pts/0 R+ 09:22 0:00 ps aux > poison 18920 0.0 0.0 1544 476 pts/0 R+ 09:22 0:00 grep [DRZ] > > I don't know what that find process is but I think it shouldn't be there. > Maybe the TUX worker 1 (PID 413) is the problem. > > Do you have any ideas what could be causing these crashes? > > Thanks in advance, > Nicolas Van Eenaeme > > -----Oorspronkelijk bericht----- > Van: tux-list-bounces at redhat.com [mailto:tux-list-bounces at redhat.com] Namens > William Lovaton > Verzonden: vrijdag 21 oktober 2005 14:29 > Aan: TUX discussion list > Onderwerp: Re: Crashing TUX > > Hi Nicolas, > > Are you sure your load problems are about tux? Did you checked your cron > jobs? may be it's logrotate or something like that. When the load is > that high you can log into the system and execute this command: > ps aux | grep ' [DRZ]' > > All of the processes with state D or R are the ones generating the high > load, with this information you can identify the offending processes. > > BTW, what distro and version are you using? Right now I have a lot of > experience with Fedora Core 3. > > -William > > > El vie, 21-10-2005 a las 10:02 +0200, Nicolas Van Eenaeme escribi?: > > Hi all, > > > > > > > > I?m running TUX on a popular website here in Belgium (>2.000.000 > > pageviews / day) and I use it to serve all my static content (images, > > css, ?). > > > > This works great. The average load on my server stays below 1. But > > after each period of 5 days (average) the load suddenly goes to 6 or > > above (I can see this on my MRTG stats) and it takes ages to serve a > > simple image. If this happens the only way to fix it is to reboot my > > server. It?s strange because this happens early in the morning > > (usually between 5 ? 7 am.) when there are almost no users on the > > site. > > > > > > > > Is there somebody who can help me or do you have some suggestions for > > me how I can fix this? I?m running the 2.4 kernel. > > > > > > > > Thanks in advance, > > > > Nicolas Van Eenaeme > > > > > > _______________________________________________ > > tux-list mailing list > > tux-list at redhat.com > > https://www.redhat.com/mailman/listinfo/tux-list > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list From sonny at prisonserver.com Wed Nov 9 14:03:20 2005 From: sonny at prisonserver.com (sonny at prisonserver.com) Date: Wed, 9 Nov 2005 08:03:20 -600 GMT Subject: TUX: error -98 binding sock... Message-ID: <437201a8.2757.0@prisonserver.com> 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 at 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 the 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 anybody can enlighten this up a bit? Thank you. Juan http://www.prisonserver.com From jblakeley at gmail.com Wed Nov 9 19:05:40 2005 From: jblakeley at gmail.com (Jeff Blakeley) Date: Wed, 9 Nov 2005 11:05:40 -0800 Subject: Optimizing TUX Message-ID: <5535e0aa0511091105w469748dbhbff81b62b7e39bd5@mail.gmail.com> Can anyone refer me to an Optimization Guide? I'm looking to get the best possible performance out of TUX running on a 1p kernel with 4 NIC's. I've already divied the worker threads between the NIC's and have changed a few other settings, of which I can share out if needed. Thanks in advance! From bakirov at transfer.kg Thu Nov 10 04:48:43 2005 From: bakirov at transfer.kg (Meder Bakirov) Date: Thu, 10 Nov 2005 10:48:43 +0600 Subject: Optimizing TUX In-Reply-To: <5535e0aa0511091105w469748dbhbff81b62b7e39bd5@mail.gmail.com> References: <5535e0aa0511091105w469748dbhbff81b62b7e39bd5@mail.gmail.com> Message-ID: <200511101048.43352.bakirov@transfer.kg> Here is an article "Installing and Configuring the TUX Web Server for Optimal Performance", maybe it will be useful for you: http://www1.us.dell.com/content/topics/global.aspx/power/en/ps1q02_morse?c=us&l=en&s=corp On Thursday 10 November 2005 01:05, Jeff Blakeley wrote: > Can anyone refer me to an Optimization Guide? I'm looking to get the > best possible performance out of TUX running on a 1p kernel with 4 > NIC's. I've already divied the worker threads between the NIC's and > have changed a few other settings, of which I can share out if needed. > > Thanks in advance! > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list -- Best rgrds, .coder My Intellect is The Power! (c) The Prodigy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From SoNNy at PrisonServer.com Sun Nov 13 08:42:10 2005 From: SoNNy at PrisonServer.com (SoNNy at PrisonServer.com) Date: Sun, 13 Nov 2005 09:42:10 +0100 Subject: TUX: error -98 binding sock... In-Reply-To: <437201a8.2757.0@prisonserver.com> References: <437201a8.2757.0@prisonserver.com> Message-ID: <4376FC62.9080707@PrisonServer.com> Hello all. I have more information on this issue. My TUX version: [root at neuron ~]# rpm -qa | grep tux tux-3.2.18-2 I had to return to Apache handling all requests after more than four panics exactly the same: from /var/log/messages: Nov 12 04:32:16 neuron kernel: Unable to handle kernel NULL pointer dereference 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 = 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_mangle ip_conntrack_ftp ip_conntrack_irc ipt_REJECT ipt_LOG ipt_limit ipt_multiport 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:[] 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: 00004040 edx: 00000000 Nov 12 04:32:16 neuron kernel: esi: 00000000 edi: f563d134 ebp: f563d000 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=f68bb000 task=f6a2e8b0) Nov 12 04:32:16 neuron kernel: Stack: 00000000 f563d000 00000000 f8a3d438 00000004 f8a2102e f563d000 f563d028 Nov 12 04:32:16 neuron kernel: f8a21cf3 f68bbf4c f8a3d438 00000000 00000000 f68bb000 f8a2b744 00000000 Nov 12 04:32:16 neuron kernel: 00000005 00000005 f8a2d1d6 c0164fbc 00000000 c0158c58 f74992ac f8a3d438 Nov 12 04:32:16 neuron kernel: Call Trace: Nov 12 04:32:16 neuron kernel: [] tux_schedule_atom+0x2a/0x42 [tux] Nov 12 04:32:16 neuron kernel: [] process_requests+0x91/0xa6 [tux] Nov 12 04:32:17 neuron kernel: [] event_loop+0x75/0x178 [tux] Nov 12 04:32:17 neuron kernel: [] __sys_tux+0x366/0x88f [tux] Nov 12 04:32:17 neuron kernel: [] path_release+0xa/0x2d Nov 12 04:32:17 neuron kernel: [] sys_chdir+0x57/0x5f Nov 12 04:32:17 neuron kernel: [] sys_setuid+0xfc/0x108 Nov 12 04:32:17 neuron kernel: [] syscall_call+0x7/0xb Nov 12 04:32:17 neuron kernel: Code: ff ff 5f 89 c2 58 89 73 18 85 d2 79 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 40 24 00 00 00 00 c7 40 28 00 00 00 00 8b 85 34 01 00 00 e8 Nov 12 04:32:17 neuron kernel: <0>Fatal exception: panic in 5 seconds The server details: CentOS release 4.2 (Final) Linux version 2.6.9-22.0.1.ELsmp (buildcentos at x8664-build) (gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)) #1 SMP Thu Oct 27 13:14:25 CDT 2005 This server performed well with TUX using kernel 2.4 and CentOS 3.6. No hardware changes were made. Thank you for any point out on this. Regards, Juan sonny at prisonserver.com 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 at 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 the 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 anybody can > enlighten this up a bit? > > Thank you. > > Juan > > http://www.prisonserver.com > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > > > > From williama_lovaton at coomeva.com.co Tue Nov 15 23:37:48 2005 From: williama_lovaton at coomeva.com.co (William Lovaton) Date: Tue, 15 Nov 2005 18:37:48 -0500 Subject: TUX: error -98 binding sock... In-Reply-To: <4376FC62.9080707@PrisonServer.com> References: <437201a8.2757.0@prisonserver.com> <4376FC62.9080707@PrisonServer.com> Message-ID: <1132097868.3803.11.camel@nalwalovaton.coomeva.nal> 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=125091 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, SoNNy at PrisonServer.com escribi?: > Hello all. I have more information on this issue. > > My TUX version: > [root at neuron ~]# rpm -qa | grep tux > tux-3.2.18-2 > > I had to return to Apache handling all requests after more than four panics exactly the same: > > from /var/log/messages: > > Nov 12 04:32:16 neuron kernel: Unable to handle kernel NULL pointer dereference 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 = 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_mangle ip_conntrack_ftp ip_conntrack_irc ipt_REJECT ipt_LOG ipt_limit ipt_multiport 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:[] 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: 00004040 edx: 00000000 > Nov 12 04:32:16 neuron kernel: esi: 00000000 edi: f563d134 ebp: f563d000 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=f68bb000 task=f6a2e8b0) > Nov 12 04:32:16 neuron kernel: Stack: 00000000 f563d000 00000000 f8a3d438 00000004 f8a2102e f563d000 f563d028 > Nov 12 04:32:16 neuron kernel: f8a21cf3 f68bbf4c f8a3d438 00000000 00000000 f68bb000 f8a2b744 00000000 > Nov 12 04:32:16 neuron kernel: 00000005 00000005 f8a2d1d6 c0164fbc 00000000 c0158c58 f74992ac f8a3d438 > Nov 12 04:32:16 neuron kernel: Call Trace: > Nov 12 04:32:16 neuron kernel: [] tux_schedule_atom+0x2a/0x42 [tux] > Nov 12 04:32:16 neuron kernel: [] process_requests+0x91/0xa6 [tux] > Nov 12 04:32:17 neuron kernel: [] event_loop+0x75/0x178 [tux] > Nov 12 04:32:17 neuron kernel: [] __sys_tux+0x366/0x88f [tux] > Nov 12 04:32:17 neuron kernel: [] path_release+0xa/0x2d > Nov 12 04:32:17 neuron kernel: [] sys_chdir+0x57/0x5f > Nov 12 04:32:17 neuron kernel: [] sys_setuid+0xfc/0x108 > Nov 12 04:32:17 neuron kernel: [] syscall_call+0x7/0xb > Nov 12 04:32:17 neuron kernel: Code: ff ff 5f 89 c2 58 89 73 18 85 d2 79 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 40 24 00 00 00 00 c7 40 28 00 00 00 00 8b 85 34 01 00 00 e8 > Nov 12 04:32:17 neuron kernel: <0>Fatal exception: panic in 5 seconds > > > The server details: > > CentOS release 4.2 (Final) > Linux version 2.6.9-22.0.1.ELsmp (buildcentos at x8664-build) > (gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)) > #1 SMP Thu Oct 27 13:14:25 CDT 2005 > > This server performed well with TUX using kernel 2.4 and CentOS 3.6. No hardware changes were made. > > Thank you for any point out on this. > > Regards, > > Juan > > > sonny at prisonserver.com 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 at 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 the 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 anybody can > > enlighten this up a bit? > > > > Thank you. > > > > Juan > > > > http://www.prisonserver.com > > > > _______________________________________________ > > tux-list mailing list > > tux-list at redhat.com > > https://www.redhat.com/mailman/listinfo/tux-list > > > > > > > > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list