Bug#237763: (no subject)
Le Tue, Mar 16, 2004 at 07:06:11 +0100, Fabio Massimo Di Nitto a écrit: > > Good.. well no but more or less ;) Can I see your apache-ssl.conf? As far > as i can see from the code it requires some dirs/files to be in place in > order to work correctly. ok, well i didn't have anything set up for it (the keynote mod), i thought it was a new "came with the distribution" DSO that needed to be enabled for it to work correctly. i'll look up the docs for it, config, and test to see if it works as it should. i'll let you know. > > Fabio > > -- > fajita: step one > Whatever the problem, step one is always to look in the error log. > fajita: step two > When in danger or in doubt, step two is to scream and shout. -- @@-@@ | ,''`. http://www.debian.org/ | http://www.nuit.ca/ | | : :' : Debian GNU/Linux| http://simonraven.nuit.ca/ | | `. `' | PGP key fingerprint (new one): | | `- | 7C49 FD9C 1054 7300 3B7B| | | 8BF4 6A88 7AE2 711D F097| @@-@@ signature.asc Description: Digital signature
Re: Bug#237763: (no subject)
Hi Simon, On Tue, 16 Mar 2004 [EMAIL PROTECTED] wrote: > well, i tried disabling apache-ssl-keynote, and php4, and i got a real > connection with both disabled. i know it's the keynote thing since i had > only disabled php4 before, and the same thing happened. found our > culprit i think. Good.. well no but more or less ;) Can I see your apache-ssl.conf? As far as i can see from the code it requires some dirs/files to be in place in order to work correctly. > oh, and there's a typo in the modules-config: > > Remember that in order to activate the new configuration apache-ssl has to be > restart. You noted. thanks. Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Re: Bug#237763: (no subject)
Le Mon, Mar 15, 2004 at 18:31:46 +0100, Fabio Massimo Di Nitto a écrit: > > Hi Simon, > we need a bit more help from you now. > > The first thing is to check the .htaccess in /var/www/nuit that it is > loaded immediatly before the crash. Try to remove it and see if the crash > still occours. At least that's my best guess since i can't say from the > strace if it happens with other urls. ok, when i rm'd the .htaccess, same stuff happened, > Second thing i noticed you run nscd. Can you try to disable it? needed for ldap connections (not essential, but makes things a little zippier, yeh it's one of theo weird things that's both slightly buggy, and slightly useful at the same time ;) well, i tried disabling apache-ssl-keynote, and php4, and i got a real connection with both disabled. i know it's the keynote thing since i had only disabled php4 before, and the same thing happened. found our culprit i think. i'm trying with php4 enabled, to see if it's also that causing SEGV. curl --insecure https://www.nuit.ca/ (04-03-16) http://www.w3.org/TR/REC-html40/loose.dtd";> Bienvenue au Domaine de la Nuit * Canada * Welcome to Night's Domain [...] oh, and there's a typo in the modules-config: Remember that in order to activate the new configuration apache-ssl has to be restart. You ^^^ works ok with the php4 module. curl --insecure https://www.nuit.ca/ (04-03-16) http://www.w3.org/TR/REC-html40/loose.dtd";> [...] i'm just glad i didn't have to re-edit my conf. ah :) "my precccioousss con" ;) simon > > Thanks > Fabio > > -- > fajita: step one > Whatever the problem, step one is always to look in the error log. > fajita: step two > When in danger or in doubt, step two is to scream and shout. -- @@-@@ | ,''`. http://www.debian.org/ | http://www.nuit.ca/ | | : :' : Debian GNU/Linux| http://simonraven.nuit.ca/ | | `. `' | PGP key fingerprint (new one): | | `- | 7C49 FD9C 1054 7300 3B7B| | | 8BF4 6A88 7AE2 711D F097| @@-@@ signature.asc Description: Digital signature
Re: Bug#237763: (no subject)
Hi Simon, we need a bit more help from you now. The first thing is to check the .htaccess in /var/www/nuit that it is loaded immediatly before the crash. Try to remove it and see if the crash still occours. At least that's my best guess since i can't say from the strace if it happens with other urls. Second thing i noticed you run nscd. Can you try to disable it? Third thing (if the first fails) is to hunt down the module that has the problem and we can use two different approches here. I leave up to you the one you prefer since both of them will take time. The first one would be to start from a fresh config with the minimal amount of modules and see if that problem still happens, and start adding one piece of config and relative associated module at a time, until we don't spot the one causing the problem. Otherwise we need to take out one module at a time with the running config until we don't find the guilty one. I would suggest with modules that are not shipped with the apache package and from the apache package in particular apache_ssl_keynote (since it is quite new and probably didn't receive all the tests required on all archs), mod_imap (that is pretty old and unmaintained, iirc). Another thing are the numbers of extensions you load in php4. Some of them are known to be problematic and i know you told me that you have tested without php4, but i would be glad if you can check if you are running the latest pkgs for php4 and do the test again. Excluding php4 globally would be the best. Thanks Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Re: Bug#237763: (no subject)
Hi Ralf, On Mon, 15 Mar 2004 [EMAIL PROTECTED] wrote: > ??? Do you actually _read_ Fabio's mails (as opposed to just glance at it)? It's ok don't worry.. I also did my mistake in the paste flaming at people for mistakes or misunderstandings or not completely reading their mails and Simon apologized immediatly after. And for everyone: Please guys let's not start another flamewar for nothing, ok? Let's keep the crap out of debian-apache. Thanks Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Bug#237763: (no subject)
On Mon, Mar 15, 2004 at 02:27:28PM +, [EMAIL PROTECTED] wrote: > Le Mon, Mar 15, 2004 at 14:55:57 +0100, Fabio Massimo Di Nitto a ?crit: > > On Mon, 15 Mar 2004 [EMAIL PROTECTED] wrote: > > > > > BTW, did those test cases have suexec enabled? i do here, for various > > > reasons. > > > > On yes it was enabled (at least loaded) > > > > > > > > on the strace, i did -F -x and -f -x the second for the second log. > > > > Sorry Simon but it's not -x. it's -X. This will avoid apache-ssl to fork > > and will simplify a lot the strace. Mind do send this strace too? > > > well both -X and -x were done, exact same circumstances.. oh wait, > correction: > > strace -x -f apache-ssl > and > strace -x -F apache-ssl > > were done. so same tests, and just a different switch on *-part2.log. > tests done were the curl and HEAD commands i pasted. and i didn't have a > -X switch (sid). ??? Do you actually _read_ Fabio's mails (as opposed to just glance at it)? The '-X' switch belongs to _apache_, not strace. From the manpage: -X Run in single-process mode, for internal debugging purposes only; the daemon does not detach from the terminal or fork any children. Do NOT use this mode to provide ordinary web service. Ralf Mattes
Bug#237763: (no subject)
On Mon, 15 Mar 2004 [EMAIL PROTECTED] wrote: > strace -x -f apache-ssl > and > strace -x -F apache-ssl strace apache-ssl -X -F the -X and -F are the options for apache-ssl and not for strace :) probably we misunderstood each other... Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Bug#237763: (no subject)
Le Mon, Mar 15, 2004 at 15:34:05 +0100, Fabio Massimo Di Nitto a écrit: > On Mon, 15 Mar 2004 [EMAIL PROTECTED] wrote: > > > strace -x -f apache-ssl > > and > > strace -x -F apache-ssl > > strace apache-ssl -X -F > > the -X and -F are the options for apache-ssl and not for strace :) > > probably we misunderstood each other... doh. just not my day... :D. i have a lot to do right now oh well. ok, coming right up (attached). oh boy... i did apache-ssl -X -F and it just crashed... (52:13:28:%) curl --insecure https://www.nuit.ca/ (04-03-15) curl: (52) Empty reply from server ([EMAIL PROTECTED]:pts/4)(~) (52:14:38:%) curl --insecure https://www.nuit.ca/ (04-03-15) curl: (7) Connect failed pidof apache-ssl (04-03-15) ([EMAIL PROTECTED]:pts/73)(/) (1:14:38:#) hmm > Fabio > > -- > fajita: step one > Whatever the problem, step one is always to look in the error log. > fajita: step two > When in danger or in doubt, step two is to scream and shout. -- @@-@@ | ,''`. http://www.debian.org/ | http://www.nuit.ca/ | | : :' : Debian GNU/Linux| http://simonraven.nuit.ca/ | | `. `' | PGP key fingerprint (new one): | | `- | 7C49 FD9C 1054 7300 3B7B| | | 8BF4 6A88 7AE2 711D F097| @@-@@ apache-ssl-try3.log.gz Description: Binary data signature.asc Description: Digital signature
Bug#237763: (no subject)
Le Mon, Mar 15, 2004 at 14:55:57 +0100, Fabio Massimo Di Nitto a écrit: > On Mon, 15 Mar 2004 [EMAIL PROTECTED] wrote: > > > BTW, did those test cases have suexec enabled? i do here, for various > > reasons. > > On yes it was enabled (at least loaded) > > > > > on the strace, i did -F -x and -f -x the second for the second log. > > Sorry Simon but it's not -x. it's -X. This will avoid apache-ssl to fork > and will simplify a lot the strace. Mind do send this strace too? > well both -X and -x were done, exact same circumstances.. oh wait, correction: strace -x -f apache-ssl and strace -x -F apache-ssl were done. so same tests, and just a different switch on *-part2.log. tests done were the curl and HEAD commands i pasted. and i didn't have a -X switch (sid). -x -- print non-ascii strings in hex, -xx -- print all strings in hex -f -- follow forks, -ff -- with output into separate files -F -- attempt to follow vforks, -h -- print help message partial snip from strace --help. > And that's why the bug is open :-) I added more information coming from > other tests so that also other users can see them and it is an implicit > explanation for me donwgrading the severity to important since the "core" > is working fine. yeh, the paragraph above was from my misunderstanding (stated previously) ;). > Thanks > Fabio > > -- > fajita: step one > Whatever the problem, step one is always to look in the error log. > fajita: step two > When in danger or in doubt, step two is to scream and shout. -- @@-@@ | ,''`. http://www.debian.org/ | http://www.nuit.ca/ | | : :' : Debian GNU/Linux| http://simonraven.nuit.ca/ | | `. `' | PGP key fingerprint (new one): | | `- | 7C49 FD9C 1054 7300 3B7B| | | 8BF4 6A88 7AE2 711D F097| @@-@@ signature.asc Description: Digital signature
Bug#237763: (no subject)
On Mon, 15 Mar 2004 [EMAIL PROTECTED] wrote: > BTW, did those test cases have suexec enabled? i do here, for various > reasons. On yes it was enabled (at least loaded) > > on the strace, i did -F -x and -f -x the second for the second log. Sorry Simon but it's not -x. it's -X. This will avoid apache-ssl to fork and will simplify a lot the strace. Mind do send this strace too? > i'm attaching the results. just a reminder: just because a bug > can't be reproduced immediately, doesn't mean it doesn't exist :). And that's why the bug is open :-) I added more information coming from other tests so that also other users can see them and it is an implicit explanation for me donwgrading the severity to important since the "core" is working fine. Thanks Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Bug#237763: (no subject)
Le Sun, Mar 14, 2004 at 07:22:04 +0100, Fabio Massimo Di Nitto a écrit: > severity 237763 important > stop > > After a round robin of tests on 4 different ppc installations, we still > cannot reproduce this bug that seems to be pretty specific to something > on your machine/setup. We used the default apache-ssl config with the > usual suspects installed (php4 and perl). In all cases we were able to get > pages out of it without segfaults. excuse me? you're closing this without even giving me a chance to do the strace? WTF do you think you're doing ? um, you're not the only one who's busy you know. FFS. > Thanks > Fabio > > -- > fajita: step one > Whatever the problem, step one is always to look in the error log. > fajita: step two > When in danger or in doubt, step two is to scream and shout. > -- @@-@@ | ,''`. http://www.debian.org/ | http://www.nuit.ca/ | | : :' : Debian GNU/Linux| http://simonraven.nuit.ca/ | | `. `' | PGP key fingerprint (new one): | | `- | 7C49 FD9C 1054 7300 3B7B| | | 8BF4 6A88 7AE2 711D F097| @@-@@ signature.asc Description: Digital signature
Bug#237763: (no subject)
On Mon, 15 Mar 2004 [EMAIL PROTECTED] wrote: > Le Sun, Mar 14, 2004 at 07:22:04 +0100, Fabio Massimo Di Nitto a écrit: > > severity 237763 important > > stop > > > > After a round robin of tests on 4 different ppc installations, we still > > cannot reproduce this bug that seems to be pretty specific to something > > on your machine/setup. We used the default apache-ssl config with the > > usual suspects installed (php4 and perl). In all cases we were able to get > > pages out of it without segfaults. > > excuse me? you're closing this without even giving me a chance to do the > strace? WTF do you think you're doing ? um, you're not the only one > who's busy you know. FFS. Sorry?? the bug is open. Noone has been closing it. I only downgraded the severity to important. Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
