From mayuran.yogarajah at casalemedia.com Wed Aug 17 17:31:02 2005 From: mayuran.yogarajah at casalemedia.com (Mayuran Yogarajah) Date: Wed, 17 Aug 2005 13:31:02 -0400 Subject: Apache mod_dir Message-ID: <43037456.3030302@casalemedia.com> Is there something equivalent to Apache's mod_dir module for TUX ? thanks, M From max at expires-2004.workforce.de Mon Aug 22 08:53:51 2005 From: max at expires-2004.workforce.de (Max Helmet) Date: Mon, 22 Aug 2005 10:53:51 +0200 Subject: AW: Apache mod_dir Message-ID: > Is there something equivalent to Apache's mod_dir module for TUX ? TUX acts just like Apache with DirectoryIndex index.html DirectorySlash On Unlike Apache, you can only have one type of index file with TUX. If you aren't comfortable with "index.html", you'll have to alter the kernel sources and rebuild your kernel. Just locate #define INDEX "/index.html" in /[path to kernel sources]/net/tux/proto_http.c and change it to "/index.htm", "/index.txt", "/default.htm" or whatever you prefer. Regards, Max From mayuran.yogarajah at casalemedia.com Mon Aug 22 15:39:03 2005 From: mayuran.yogarajah at casalemedia.com (Mayuran Yogarajah) Date: Mon, 22 Aug 2005 11:39:03 -0400 Subject: debugging TUX Message-ID: <4309F197.2040603@casalemedia.com> There isn't much documentation on this so I was hoping to get some information from here. We're seeing some strange and inconsistant behaviour with the files TUX serves. Our setup is normal; TUX on port 80, apache on 8080. With TUX logging on we see that some static pages that TUX should be serving are in fact passed to apache. The status code is -1 in the TUX logs, and we can see the request in apache's common log. Is there some way to find out why TUX is passing the request to apache ? thanks, M From williama_lovaton at coomeva.com.co Mon Aug 22 16:13:40 2005 From: williama_lovaton at coomeva.com.co (William Lovaton) Date: Mon, 22 Aug 2005 11:13:40 -0500 Subject: debugging TUX In-Reply-To: <4309F197.2040603@casalemedia.com> References: <4309F197.2040603@casalemedia.com> Message-ID: <1124727220.26833.6.camel@nalwalovaton.coomeva.nal> Hi, Could you post the mentioned log record to the list? remember that tux follows several rules to decide whether to hand the the request over to apache or not. -William El lun, 22-08-2005 a las 11:39 -0400, Mayuran Yogarajah escribi?: > There isn't much documentation on this so I was hoping to get some > information from here. We're seeing some strange and inconsistant > behaviour with the files TUX serves. Our setup is normal; TUX on > port 80, apache on 8080. With TUX logging on we see that some > static pages that TUX should be serving are in fact passed to apache. > The status code is -1 in the TUX logs, and we can see the request in > apache's common log. Is there some way to find out why TUX is > passing the request to apache ? > > thanks, > M > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list From max at expires-2004.workforce.de Tue Aug 23 07:39:09 2005 From: max at expires-2004.workforce.de (Max Helmet) Date: Tue, 23 Aug 2005 09:39:09 +0200 Subject: AW: debugging TUX In-Reply-To: <4309F197.2040603@casalemedia.com> Message-ID: > There isn't much documentation on this so I was hoping to get some > information from here. We're seeing some strange and inconsistant > behaviour with the files TUX serves. Our setup is normal; TUX on > port 80, apache on 8080. With TUX logging on we see that some > static pages that TUX should be serving are in fact passed to apache. > The status code is -1 in the TUX logs, and we can see the request in > apache's common log. Is there some way to find out why TUX is > passing the request to apache ? You can follow TUX's request processing on syslog by enabling TUX debugging: 1) If your kernel wasn't built with CONFIG_TUX_DEBUG=y, then rebuild your kernel with this option turned on. 2) Enter the following comands: echo 1 > /proc/sys/net/tux/Dprintk echo 1 > /proc/sys/net/tux/TDprintk 3) Follow kernel messages: cat /proc/kmsg 4) Open a second terminal session and request the page in question: wget -S --spider http://localhost/page.html 5) Tux should have printed verbose messages to your first terminal. Regards, Max From mayuran.yogarajah at casalemedia.com Tue Aug 23 17:50:45 2005 From: mayuran.yogarajah at casalemedia.com (Mayuran Yogarajah) Date: Tue, 23 Aug 2005 13:50:45 -0400 Subject: AW: debugging TUX In-Reply-To: References: Message-ID: <430B61F5.6040606@casalemedia.com> >You can follow TUX's request processing on syslog by enabling TUX debugging: >1) If your kernel wasn't built with CONFIG_TUX_DEBUG=y, then > rebuild your kernel with this option turned on. >2) Enter the following comands: > echo 1 > /proc/sys/net/tux/Dprintk > echo 1 > /proc/sys/net/tux/TDprintk >3) Follow kernel messages: > cat /proc/kmsg >4) Open a second terminal session and request the page in question: > wget -S --spider http://localhost/page.html >5) Tux should have printed verbose messages to your first terminal. > >Regards, >Max > > Ok I've done this and am now seeing messages through /proc/kmsg. Unfortunately I have no idea how to interpret any of this :/ I am looking to find the reason why TUX decides to pass the request to apache. I know TUX has 7 rules that must hold for TUXto serve the request. If I could somehow see which rule is violated that would help. The main issue is that TUX is not serving the request when it should be and I am trying to find out why. thanks, M From williama_lovaton at coomeva.com.co Tue Aug 23 19:25:52 2005 From: williama_lovaton at coomeva.com.co (William Lovaton) Date: Tue, 23 Aug 2005 14:25:52 -0500 Subject: AW: debugging TUX In-Reply-To: <430B61F5.6040606@casalemedia.com> References: <430B61F5.6040606@casalemedia.com> Message-ID: <1124825152.30435.13.camel@nalwalovaton.coomeva.nal> Mayuran, We may be able to help you identify which rule is not met, please post that single request that is being ignored by tux. For instance it could be that the request is for the user module of apache. Eg: http://server/~mayuran/somefile.html Cheers, -William El mar, 23-08-2005 a las 13:50 -0400, Mayuran Yogarajah escribi?: > Ok I've done this and am now seeing messages through /proc/kmsg. > Unfortunately > I have no idea how to interpret any of this :/ I am looking to find the > reason why > TUX decides to pass the request to apache. I know TUX has 7 rules that > must hold > for TUXto serve the request. If I could somehow see which rule is > violated that > would help. The main issue is that TUX is not serving the request when > it should be > and I am trying to find out why. > > thanks, > M > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list From max at expires-2004.workforce.de Wed Aug 24 08:34:49 2005 From: max at expires-2004.workforce.de (Max Helmet) Date: Wed, 24 Aug 2005 10:34:49 +0200 Subject: AW: AW: debugging TUX In-Reply-To: <1124825152.30435.13.camel@nalwalovaton.coomeva.nal> Message-ID: > Mayuran Yogarajah: > > Ok I've done this and am now seeing messages through /proc/kmsg. > > Unfortunately > > I have no idea how to interpret any of this William Lovaton: > We may be able to help you identify which rule is not met, please post > that single request that is being ignored by tux. For instance it could > be that the request is for the user module of apache. Eg: > http://server/~mayuran/somefile.html Besides this, you could provide us with the kernel messages that are printed out by tux: ... 3) Save kernel messages: cat /proc/kmsg > tux_debug_log.txt 4) Open a second terminal session and request the page in question: wget -S --spider http://localhost/page.html 5) Press CTRL-C in your first terminal 6) Paste contents of tux_debug_log.txt into your mail. Regards, Max