Re: Bug#237763: apache-ssl: SIGSEGV on connect
Le Sat, Mar 13, 2004 at 18:24:10 +0100, Fabio Massimo Di Nitto a crit: On Sat, 13 Mar 2004, simon raven wrote: yes, with and without php4 enabled it SEGVs. mod-perl is: ii libapache-mod-perl 1.29.0.2-4 php is currently enabled in the conf. attaching gzipped httpd.conf from /etc/apache-ssl. Unfortunatly this is not enough for me and i see that your config is pretty complex. Please stop apache-ssl and do: strace apache-ssl -X -F and send me the full output after the first client connects at that point apache-ssl should crash in the same way you see in the error logs. alright. my next reply will have the strace log Thanks Fabio -- user fajita: step one fajita Whatever the problem, step one is always to look in the error log. user fajita: step two fajita 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
Processed: Re: Bug#237763: apache-ssl: SIGSEGV on connect
Processing commands for [EMAIL PROTECTED]: tags 237763 + moreinfo Bug#237763: apache-ssl: SIGSEGV on connect Tags were: sid Tags added: moreinfo tags 237763 + unreproducible Bug#237763: apache-ssl: SIGSEGV on connect Tags were: moreinfo sid Tags added: unreproducible stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Bug#237763: apache-ssl: SIGSEGV on connect
On Sat, 13 Mar 2004, simon raven wrote: yes, with and without php4 enabled it SEGVs. mod-perl is: ii libapache-mod-perl 1.29.0.2-4 php is currently enabled in the conf. attaching gzipped httpd.conf from /etc/apache-ssl. Unfortunatly this is not enough for me and i see that your config is pretty complex. Please stop apache-ssl and do: strace apache-ssl -X -F and send me the full output after the first client connects at that point apache-ssl should crash in the same way you see in the error logs. Thanks Fabio -- user fajita: step one fajita Whatever the problem, step one is always to look in the error log. user fajita: step two fajita When in danger or in doubt, step two is to scream and shout.
