From johann at johannburkard.de Thu Jan 19 20:31:56 2006 From: johann at johannburkard.de (Johann Burkard) Date: Thu, 19 Jan 2006 21:31:56 +0100 Subject: Virtual hosts not working References: Message-ID: <8895E70AA1E84833B6E2E65649B25514@granularr> Hello, Johann Burkard wrote: > thanks, that sounded like a good idea. I was trying out setting > strip_host_tail to both 1 and 0, but Tux still became unresponsive > instantly when I set virtual hosting to 1. I upgraded to 2.6.14r2 and I still have this problem. I do # echo 1 > virtual_server and Tux stops answering requests. To repeat my question: Is someone using Tux with virtual hosts? What are the settings used? What version? Thanks, Johann From SoNNy at PrisonServer.com Thu Jan 19 20:36:03 2006 From: SoNNy at PrisonServer.com (SoNNy at PrisonServer.com) Date: Thu, 19 Jan 2006 21:36:03 +0100 Subject: Virtual hosts not working In-Reply-To: <8895E70AA1E84833B6E2E65649B25514@granularr> References: <8895E70AA1E84833B6E2E65649B25514@granularr> Message-ID: <43CFF833.9000704@PrisonServer.com> > > To repeat my question: Is someone using Tux with virtual hosts? What are the > settings used? What version? > Never got this problem, but this little how-to I wrote can give you the data you're asking for (version, settings, etc). http://www.interworx.com/forums/showthread.php?t=429 Please note that it's a howto on Installing and configuring TUX for a certain server control panel that works under Redhat Linux. Regards, Juan From johann at johannburkard.de Thu Jan 19 20:41:03 2006 From: johann at johannburkard.de (Johann Burkard) Date: Thu, 19 Jan 2006 21:41:03 +0100 Subject: Virtual hosts not working References: <8895E70AA1E84833B6E2E65649B25514@granularr> Message-ID: Hello, Johann Burkard wrote: > I upgraded to 2.6.14r2 and I still have this problem. looks like the problem is solved. It seems you cannot change documentroot while Tux is running or problems will happen. What I did: * stop Tux * edit /etc/conf.d/tux to set the documentroot * start Tux * set virtual_host and strip_host_tail It seems to be working now. Johann From anmar at gmx.net Thu Jan 19 22:11:41 2006 From: anmar at gmx.net (Angel Marin) Date: Thu, 19 Jan 2006 23:11:41 +0100 Subject: Virtual hosts not working In-Reply-To: <8895E70AA1E84833B6E2E65649B25514@granularr> References: <8895E70AA1E84833B6E2E65649B25514@granularr> Message-ID: <43D00E9D.3020509@gmx.net> Hi, Johann Burkard escribi?: > Hello, > > Johann Burkard wrote: > >>thanks, that sounded like a good idea. I was trying out setting >>strip_host_tail to both 1 and 0, but Tux still became unresponsive >>instantly when I set virtual hosting to 1. > > I upgraded to 2.6.14r2 and I still have this problem. I do > > # echo 1 > virtual_server > > and Tux stops answering requests. > > To repeat my question: Is someone using Tux with virtual hosts? What are the > settings used? What version? I have seen this sort of behavior when tux tries to chroot to a location that does not exist. Setting default_vhost to something that exists (inside the configured DOCROOT) solves that issue. Regards, -- Angel Marin http://anmar.eu.org/ From mcd at daviesinc.com Sat Jan 21 22:15:49 2006 From: mcd at daviesinc.com (Chris Davies) Date: Sat, 21 Jan 2006 17:15:49 -0500 Subject: kernel fault -- 2.6.15 with tux patch applied Message-ID: <43D2B295.9060208@daviesinc.com> I had this problem on another machine, but, thought it was a one-off issue. I issued the command reboot which caused this fault. After tux has served data, it appears to get this error. Configuration of both machines with the issue are SMP machines (not SMT or Uniprocessor). I'll try again on a uniprocessor machine to see if the problem persists. Any pointers for diagnosing? Jan 19 22:06:45 machine3 kernel: TUX: thread 1 stopping ... Jan 19 22:06:45 machine3 kernel: TUX: thread 0 stopping ... Jan 19 22:06:45 machine3 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000020 Jan 19 22:06:45 machine3 kernel: printing eip: Jan 19 22:06:45 machine3 kernel: c02d5541 Jan 19 22:06:45 machine3 kernel: *pde = 00000000 Jan 19 22:06:45 machine3 kernel: Oops: 0002 [#1] Jan 19 22:06:45 machine3 kernel: SMP Jan 19 22:06:45 machine3 kernel: Modules linked in: Jan 19 22:06:45 machine3 kernel: CPU: 0 Jan 19 22:06:45 machine3 kernel: EIP: 0060:[tux_flush_workqueue+81/185] Not tainted VLI Jan 19 22:06:45 machine3 kernel: EFLAGS: 00010206 (2.6.15-tux3) Jan 19 22:06:45 machine3 kernel: EIP is at tux_flush_workqueue+0x51/0xb9 Jan 19 22:06:45 machine3 kernel: eax: 00000000 ebx: f7bc0000 ecx: f7bc0028 edx: f7bc8028 Jan 19 22:06:45 machine3 kernel: esi: c03ded20 edi: 00000000 ebp: 00000140 esp: f7343f10 Jan 19 22:06:45 machine3 kernel: ds: 007b es: 007b ss: 0068 Jan 19 22:06:45 machine3 kernel: Process tux (pid: 2234, threadinfo=f7342000 task=f72fea30) Jan 19 22:06:45 machine3 kernel: Stack: 00000003 c03ded20 c03ded20 c02df38c c03ded20 c03ded20 c03ded20 c03dede0 Jan 19 22:06:45 machine3 kernel: c03dee70 c02df467 c03ded20 c03ded20 f7342000 00000004 c03ded20 00000000 Jan 19 22:06:45 machine3 kernel: c02dff39 c03ded20 c0119b9e f7a3ea64 f72fea30 00000001 c0119d27 00000282 Jan 19 22:06:45 machine3 kernel: Call Trace: Jan 19 22:06:45 machine3 kernel: [flush_all_requests+28/85] flush_all_requests+0x1c/0x55 Jan 19 22:06:45 machine3 kernel: [user_req_stop_thread+117/223] user_req_stop_thread+0x75/0xdf Jan 19 22:06:45 machine3 kernel: [__sys_tux+349/1736] __sys_tux+0x15d/0x6c8 Jan 19 22:06:45 machine3 kernel: [lock_timer_base+25/51] lock_timer_base+0x19/0x33 Jan 19 22:06:45 machine3 kernel: [try_to_del_timer_sync+16/77] try_to_del_timer_sync+0x10/0x4d Jan 19 22:06:45 machine3 kernel: [try_to_del_timer_sync+71/77] try_to_del_timer_sync+0x47/0x4d Jan 19 22:06:45 machine3 kernel: [tux_exit+9/12] tux_exit+0x9/0xc Jan 19 22:06:45 machine3 kernel: [do_exit+370/733] do_exit+0x172/0x2dd Jan 19 22:06:45 machine3 kernel: [sys_exit_group+0/17] sys_exit_group+0x0/0x11 Jan 19 22:06:45 machine3 kernel: [syscall_call+7/11] syscall_call+0x7/0xb Jan 19 22:06:45 machine3 kernel: Code: 00 00 8d 59 d8 f0 0f ba 71 20 00 f0 0f ba 71 24 00 8b 11 8b 41 04 89 42 04 89 10 89 49 04 89 09 c6 86 8c 01 00 00 01 fb 8b 43 6c 40 20 00 00 00 00 c7 40 24 00 00 00 00 80 bb ec 00 00 00 00 Jan 19 22:06:45 machine3 kernel: <1>Fixing recursive fault but reboot is needed! Jan 19 22:06:45 machine3 kernel: TUX: thread 1 stopped. From mcd at daviesinc.com Sat Jan 21 23:08:49 2006 From: mcd at daviesinc.com (Chris Davies) Date: Sat, 21 Jan 2006 18:08:49 -0500 Subject: kernel fault -- 2.6.15 with tux patch applied In-Reply-To: <43D2B295.9060208@daviesinc.com> References: <43D2B295.9060208@daviesinc.com> Message-ID: <43D2BF01.8070506@daviesinc.com> problem does not seem to occur on a Uniprocessor machine. Will try SMT later. Chris Davies wrote: > I had this problem on another machine, but, thought it was a one-off > issue. I issued the command reboot which caused this fault. > > After tux has served data, it appears to get this error. Configuration > of both machines with the issue are SMP machines (not SMT or > Uniprocessor). I'll try again on a uniprocessor machine to see if the > problem persists. > > Any pointers for diagnosing? > > Jan 19 22:06:45 machine3 kernel: TUX: thread 1 stopping ... > Jan 19 22:06:45 machine3 kernel: TUX: thread 0 stopping ... > Jan 19 22:06:45 machine3 kernel: Unable to handle kernel NULL pointer > dereference at virtual address 00000020 > Jan 19 22:06:45 machine3 kernel: printing eip: > Jan 19 22:06:45 machine3 kernel: c02d5541 > Jan 19 22:06:45 machine3 kernel: *pde = 00000000 > Jan 19 22:06:45 machine3 kernel: Oops: 0002 [#1] > Jan 19 22:06:45 machine3 kernel: SMP > Jan 19 22:06:45 machine3 kernel: Modules linked in: > Jan 19 22:06:45 machine3 kernel: CPU: 0 > Jan 19 22:06:45 machine3 kernel: EIP: > 0060:[tux_flush_workqueue+81/185] Not tainted VLI > Jan 19 22:06:45 machine3 kernel: EFLAGS: 00010206 (2.6.15-tux3) > Jan 19 22:06:45 machine3 kernel: EIP is at tux_flush_workqueue+0x51/0xb9 > Jan 19 22:06:45 machine3 kernel: eax: 00000000 ebx: f7bc0000 ecx: > f7bc0028 edx: f7bc8028 > Jan 19 22:06:45 machine3 kernel: esi: c03ded20 edi: 00000000 ebp: > 00000140 esp: f7343f10 > Jan 19 22:06:45 machine3 kernel: ds: 007b es: 007b ss: 0068 > Jan 19 22:06:45 machine3 kernel: Process tux (pid: 2234, > threadinfo=f7342000 task=f72fea30) > Jan 19 22:06:45 machine3 kernel: Stack: 00000003 c03ded20 c03ded20 > c02df38c c03ded20 c03ded20 c03ded20 c03dede0 > Jan 19 22:06:45 machine3 kernel: c03dee70 c02df467 c03ded20 > c03ded20 f7342000 00000004 c03ded20 00000000 > Jan 19 22:06:45 machine3 kernel: c02dff39 c03ded20 c0119b9e > f7a3ea64 f72fea30 00000001 c0119d27 00000282 > Jan 19 22:06:45 machine3 kernel: Call Trace: > Jan 19 22:06:45 machine3 kernel: [flush_all_requests+28/85] > flush_all_requests+0x1c/0x55 > Jan 19 22:06:45 machine3 kernel: [user_req_stop_thread+117/223] > user_req_stop_thread+0x75/0xdf > Jan 19 22:06:45 machine3 kernel: [__sys_tux+349/1736] > __sys_tux+0x15d/0x6c8 > Jan 19 22:06:45 machine3 kernel: [lock_timer_base+25/51] > lock_timer_base+0x19/0x33 > Jan 19 22:06:45 machine3 kernel: [try_to_del_timer_sync+16/77] > try_to_del_timer_sync+0x10/0x4d > Jan 19 22:06:45 machine3 kernel: [try_to_del_timer_sync+71/77] > try_to_del_timer_sync+0x47/0x4d > Jan 19 22:06:45 machine3 kernel: [tux_exit+9/12] tux_exit+0x9/0xc > Jan 19 22:06:45 machine3 kernel: [do_exit+370/733] do_exit+0x172/0x2dd > Jan 19 22:06:45 machine3 kernel: [sys_exit_group+0/17] > sys_exit_group+0x0/0x11 > Jan 19 22:06:45 machine3 kernel: [syscall_call+7/11] syscall_call+0x7/0xb > Jan 19 22:06:45 machine3 kernel: Code: 00 00 8d 59 d8 f0 0f ba 71 20 00 > f0 0f ba 71 24 00 8b 11 8b 41 04 89 42 04 89 10 89 49 04 89 09 c6 86 8c > 01 00 00 01 fb 8b 43 6c 40 20 00 00 00 00 c7 40 24 00 00 00 00 80 > bb ec 00 00 00 00 > Jan 19 22:06:45 machine3 kernel: <1>Fixing recursive fault but reboot > is needed! > Jan 19 22:06:45 machine3 kernel: TUX: thread 1 stopped. > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > > !DSPAM:43d2b2a9217224391266219! > From mike at mommabears.com Tue Jan 31 01:31:59 2006 From: mike at mommabears.com (MJang) Date: Mon, 30 Jan 2006 17:31:59 -0800 Subject: Documentation Message-ID: <1138671119.4027.9.camel@localhost> Just wondering what's the latest docs available for Tux. I see we're at version 3.2 for FC5, and the latest I can find is for version 2.2 http://www.redhat.com/docs/manuals/tux/TUX-2.2-Manual/, also as reflected in /usr/share/doc/tux-3.2.18/ Is there a home page or project associated with the Tux Webserver (Content Accelerator)? Thanks, Mike