Bug#398817: marked as done (apache2/2.2.3-3.1 Segmentation faults (11))
Your message dated Sat, 15 Nov 2008 21:31:37 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line segfault does not occur anymore has caused the Debian Bug report #398817, regarding apache2/2.2.3-3.1 Segmentation faults (11) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 398817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398817 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2.2-common Version: 2.2.3-3.1 Severity: grave Hi, on a Debian Testing system with some packages from Unstable (php5) I'm getting in apache2/2.2.3-3.1 many Segmentation faults (11) after the apache server is running for some hours. It's a frequently high visited webserver. The apache error logfile gives this: [Wed Nov 15 20:04:08 2006] [notice] child pid 32443 exit signal Segmentation fault (11) [Wed Nov 15 20:04:08 2006] [notice] child pid 2567 exit signal Segmentation fault (11) [Wed Nov 15 20:04:11 2006] [notice] child pid 435 exit signal Segmentation fault (11) [Wed Nov 15 20:04:11 2006] [notice] child pid 451 exit signal Segmentation fault (11) [Wed Nov 15 20:04:11 2006] [notice] child pid 2320 exit signal Segmentation fault (11) [Wed Nov 15 20:04:13 2006] [notice] child pid 2074 exit signal Segmentation fault (11) and so on... After restarting the apache server it's running fine again for some hours. Following related packages are installed: apache2-mpm-prefork 2.2.3-3.1 apache2-prefork-dev 2.2.3-3.1 apache2-utils 2.2.3-3.1 apache2.2-common 2.2.3-3.1 libapache2-mod-auth-plain 2.0.48-4-2.2 libapache2-mod-perl2 2.0.2-2.2 libapache2-mod-php5 5.2.0-3 libapache2-mod-python 3.2.10-2 libapache2-svn 1.4.0-5 libapr1 1.2.7-7 libapr1-dev 1.2.7-7 libaprutil1 1.2.7+dfsg-2 libaprutil1-dev 1.2.7+dfsg-2 libmysqlclient15-dev 5.0.26-3 libmysqlclient15off 5.0.26-3 linux-image-2.6.17-2-amd64 2.6.17-9 mysql-client-5.0 5.0.26-3 mysql-common 5.0.26-3 mysql-server 5.0.26-3 mysql-server-5.0 5.0.26-3 php5 5.2.0-3 php5-cgi 5.2.0-3 php5-cli 5.2.0-3 php5-common 5.2.0-3 php5-curl 5.2.0-3 php5-dev 5.2.0-3 php5-gd 5.2.0-3 php5-mcrypt 5.1.2-1-tomek1 (original sid source built against php5-5.2.0-3) php5-mhash 5.2.0-3 php5-mysql 5.2.0-3 php5-recode 5.2.0-3 php5-xmlrpc 5.2.0-3 php5-xsl 5.2.0-3 The following apache2 modules are enabled: actions alias auth_basic authn_file auth_plain authz_default authz_groupfile authz_host authz_user autoindex cgi dav_fs dav dav_svn dir env expires headers include info mime mime_magic negotiation perl php5 rewrite setenvif status I can provide more informations if needed. Personally I don't think it has to do something with one of the following bug reports: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392189 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397904 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392373 And because I don't know which package is causing the problem, I have created a new bug report instead of replying to another one. Thanks. -- Best regards, Thomas Babut E-Mail: [EMAIL PROTECTED] PGP ID: 9EA93CB2 Jabber: [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ---End Message--- ---BeginMessage--- The original reporter of this bug said the segfault did not appear again. The other segfaults in the report are obviously about php or some of its plugins. Closing the report. ---End Message---
Bug#429320: marked as done (sid - apache2 segmentation fault (negotiation.load))
Your message dated Sat, 15 Nov 2008 21:40:45 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line sid - apache2 segmentation fault(negotiation.load) has caused the Debian Bug report #429319, regarding sid - apache2 segmentation fault (negotiation.load) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 429319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429319 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2.2-common Version: 2.2.3-5 Severity: Important The module negotiation.load is causing segmentation fault in apache2. child pid 4660 exit signal Segmentation fault (11) ---End Message--- ---BeginMessage--- There has been no response to the request for more information for a long time. Closing the bug report. If the bug is still relevant and you have more information, feel free to reopen the report. ---End Message---
Bug#429319: marked as done (sid - apache2 segmentation fault(negotiation.load))
Your message dated Sat, 15 Nov 2008 21:40:45 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line sid - apache2 segmentation fault(negotiation.load) has caused the Debian Bug report #429319, regarding sid - apache2 segmentation fault(negotiation.load) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 429319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429319 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2.2-common Version: 2.2.3-5 Severity: Important The module negotiation.load is causing segmentation fault in apache2. child pid 4660 exit signal Segmentation fault (11) ---End Message--- ---BeginMessage--- There has been no response to the request for more information for a long time. Closing the bug report. If the bug is still relevant and you have more information, feel free to reopen the report. ---End Message---
Bug#466369: marked as done (apache2: apr_sock_info_get() failed for domain.)
Your message dated Sat, 15 Nov 2008 21:45:38 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line apache2: apr_sock_info_get() failed for domain has caused the Debian Bug report #466369, regarding apache2: apr_sock_info_get() failed for domain. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 466369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466369 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2 Version: 2.2.8-1 Severity: important Hi when i am installing apache2 from sources it gives this error. Please find the log. __start__ deepak:/etc/apache2# apt-get install apache2 libapache2-mod-php5 apache2-mpm-prefork Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: db4.4-util apache-common libbtutil0 libbttracker0 Use 'apt-get autoremove' to remove them. The following NEW packages will be installed: apache2 apache2-mpm-prefork libapache2-mod-php5 0 upgraded, 3 newly installed, 0 to remove and 4 not upgraded. Need to get 0B/2824kB of archives. After this operation, 6222kB of additional disk space will be used. Selecting previously deselected package apache2-mpm-prefork. (Reading database ... 83630 files and directories currently installed.) Unpacking apache2-mpm-prefork (from .../apache2-mpm-prefork_2.2.8-1_i386.deb) ... Selecting previously deselected package apache2. Unpacking apache2 (from .../apache2_2.2.8-1_all.deb) ... Selecting previously deselected package libapache2-mod-php5. Unpacking libapache2-mod-php5 (from .../libapache2-mod-php5_5.2.5-2_i386.deb) ... Setting up apache2-mpm-prefork (2.2.8-1) ... Starting web server: apache2apache2: apr_sockaddr_info_get() failed for deepak apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName . Setting up apache2 (2.2.8-1) ... Setting up libapache2-mod-php5 (5.2.5-2) ... Creating config file /etc/php5/apache2/php.ini with new version Reloading web server config: apache2apache2: apr_sockaddr_info_get() failed for deepak apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName __End__ my /etc/apt/sources.list has following mirror. deb http://ftp.iitm.ac.in/debian stable main deb http://ftp.iitm.ac.in/debian unstable main contrib non-free deb http://ftp.iitm.ac.in/debian testing main contrib non-free -- Deepak Tripathi E3 71V3 8Y C063 (We Live By Code) http://deepkatripathi.blogspot.com ---End Message--- ---BeginMessage--- According to the submitter, the bug does not appear anymore. Closing the report. ---End Message---
Bug#434562: marked as done (apache2.2-common: Segfaulting when using mod_authn_dbd with DBDriver pgsql)
Your message dated Sat, 15 Nov 2008 22:01:52 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line Re: Bug#434562: Inability to reproduce has caused the Debian Bug report #434562, regarding apache2.2-common: Segfaulting when using mod_authn_dbd with DBDriver pgsql to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 434562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434562 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2.2-common Version: 2.2.3-5 Severity: normal Seemingly, apache2.2-common does not bundle any file apr_dbd_pgsql.so (which I gather [0] is needed when specifying DBDriver pgsql). The above is guesswork on my part why my apache2.2 server segfaults upon configuration file reading (and `strace apache2 -t` yields no useful information except that apache seemingly gets past loading my virtualhosts). It seems it cannot run something needed in that file. As a consequence, I cannot proceed with upgrading the setup in [1] to a DBD-and-authn-using-setup. However, I gather [2] that the deprecated auth_pgsql module could still be used. I haven't tried that yet. Also refer to [3], which seems to be a similar problem. Regards, skrewz. [0] http://httpd.apache.org/docs/2.2/mod/mod_dbd.html#dbdriver [1] http://www.debian-administration.org/articles/208 [2] http://httpd.apache.org/docs/2.2/mod/mod_auth_basic.html#authbasicauthoritative [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405773 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apache2.2-common depends on: ii apache2-utils 2.2.3-5utility programs for webservers ii libmagic1 4.21-1 File type determination library us ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii mime-support 3.39-1 MIME files 'mime.types' 'mailcap ii net-tools 1.60-17The NET-3 networking toolkit ii procps1:3.2.7-3 /proc file system utilities apache2.2-common recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- version: 2.2.6-1 On Sat, 29 Mar 2008, Anders Breindahl wrote: For all I care, the bug may be closed -- but technically, I can't say it's been resolved. I am closing this as fixed in 2.2.6. ---End Message---
Bug#476415: marked as done (apache2 (SSL?) x64 segfault)
Your message dated Sat, 15 Nov 2008 22:08:34 +0100 (CET)
with message-id [EMAIL PROTECTED]
and subject line not reproducible
has caused the Debian Bug report #476415,
regarding apache2 (SSL?) x64 segfault
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
476415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476415
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: apache2
Version: 2.2.8-3
Apache2 and apache2ctl both segfault. I believe it's related to SSL,
since apache.org's issues system appears to have a number of similar
bugs, and also because apache actually runs, but the SSL vhost I had
set up before doesn't run now.
# apache2ctl restart
/usr/sbin/apache2ctl: line 83: 14250 Segmentation fault $HTTPD
${APACHE_ARGUMENTS} -t 2/dev/null
Syntax OK
/usr/sbin/apache2ctl: line 83: 14251 Segmentation fault $HTTPD
${APACHE_ARGUMENTS} -t
# apache2 -v
Server version: Apache/2.2.8 (Debian)
Server built: Mar 14 2008 10:46:22
Segmentation fault
I'm running gcc 4.2.3 (and before, with the same problem, 4.1.3), and
everything's 64bit.
I originally posted this to the already established bug at
https://issues.apache.org/bugzilla/show_bug.cgi?id=43317 and they told
me to report it to you guys.
Please feel free to contact me regarding this bug and I'll provide any
debugging information that I can.
--
Jonathan
---End Message---
---BeginMessage---
Since this bug is not reproducible and cannot be fixed without a stack
trace, I am closing the report.
---End Message---
Bug#480210: marked as done (apache2-mpm-prefork: Stale child threads not serving requests or timing out)
Your message dated Sat, 15 Nov 2008 21:55:07 +0100 (CET)
with message-id [EMAIL PROTECTED]
and subject line bug 480210: apache problems with libmysqlclient
has caused the Debian Bug report #480210,
regarding apache2-mpm-prefork: Stale child threads not serving requests or
timing out
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
480210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480210
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: apache2-mpm-prefork
Version: 2.2.8-3
Severity: normal
I've been coming across issues lately with Apache child threads hanging in a
wait
state (and not serving connections) indefinitely with no recovery. Now, it may
be
php related or something, I'm not ruling that out. But at present I'm unable
to
debug it to the degree of finding the source (after much searching and doing
things
like stracing bad threads).
What happens is the server is running fine in general, but certain clients seem
to
be able to cause a thread to lock up while serving a request. The majority of
the
offenders seem to be while serving jpg thumbnail images out of a gallery,
although
I have found other examples as well where threads do not recover. The bad cases
are the same few files requested by one client, typically very rapidly in
succession
and usually from country TLDs like .pl or .ar (which makes me believe it's an
intentional DoS, although I can't find a description of the attack anywhere).
The following is an strace when the server was recieving these requests on a
thread
being accessed by the IP causing the lock ups:
http://underhanded.org/13098.out
The requests in that thread referencing URLs with thumbnail in them are the
ones
in question. I was unable to derive anything useful from that particular
trace,
but it's there if you should need it.
Outside of the apparently deliberate attempts to lock up (or maybe just crawl)
the server,
each of these threads shares the common attribute of being flagged as (W)ait
status
in apache itself, lasting until the thread is killed (20 hours + on some).
Here's an example of a grep of long wait status threads and what they were
doing:
[EMAIL PROTECTED]:/etc# /usr/sbin/apache2ctl fullstatus | /bin/grep -A 1 -E
'[0-9]+/[0-9]+/[0-9]+[[:space:]]+W[[:space:]]+[0-9]+\.[0-9]+[[:space:]]+[0-9]{2,}'
77-0 6850 0/130/30864 W 1.19 24970 0 0.0 0.84 205.13 195.114.160.136
blond.website.com GET / HTTP/1.1
--
111-0 12167 0/13/601 W 0.00 73426 0 0.0 0.04 3.51 91.106.219.88
blond.website.com GET
--
136-0 6870 0/146/26295 W 1.14 24810 0 0.0 1.06 175.10 195.114.160.136
blond.website.com GET / HTTP/1.1
--
141-0 9486 0/0/24479 W 0.20 24970 0 0.0 0.00 156.45 195.114.160.136
blond.website.com GET /articles/category HTTP/1.1
--
164-0 9496 0/26/21884 W 0.22 24804 0 0.0 0.07 141.98 195.114.160.136
blond.website.com GET / HTTP/1.1
--
332-0 9607 0/19/5332 W 0.33 24809 0 0.0 0.19 30.86 195.114.160.136
blond.website.com GET /articles/category HTTP/1.1
--
376-0 13058 0/186/655 W 0.75 72737 0 0.0 1.22 3.95 128.180.192.139
blond.website.com GET / HTTP/1.1
--
405-0 7313 0/169/831 W 0.85 25003 0 0.0 0.69 4.55 195.114.160.136
blond.website.com GET /articles/category HTTP/1.1
--
424-0 8346 0/78/1624 W 0.28 24939 0 0.0 0.30 10.43 195.114.160.136
blond.website.com GET / HTTP/1.1
--
480-0 7355 1/134/175 W 0.75 24933 0 41.7 1.24 1.49 195.114.160.136
blond.website.com GET /articles/category HTTP/1.1
Any suggestions as to rectifying this would be GREATLY appreciated, as I am at
my wits' end trying to track down what exactly is going on. Currently I am
writing
a script to take teh results frmo the above grep and kill off the processes.
If you need any additional information or need me to test anything to help
resolve
this or reproduce, please do not hesitate to let me know.
Here some relevant parts of the apache config (this happens with KeepAlives off
as well):
--
HostnameLookups Off
Timeout 5
KeepAlive On
MaxKeepAliveRequests 1000
KeepAliveTimeout 4
IfModule mpm_prefork_module
ServerLimit 700
StartServers100
MinSpareServers 5
MaxSpareServers 10
MaxClients 700
MaxRequestsPerChild 1
GracefulShutdownTimeout 15
/IfModule
-
-- Package-specific info:
List of enabled modules from 'apache2 -M':
actions* alias auth_basic auth_mysql authn_alias authn_file
authnz_ldap authz_default authz_groupfile
Processed: tagging 485413
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 485413 moreinfo Bug#485413: apache2: Apache crashes system due to exessive memory allocation Tags were: moreinfo Tags added: moreinfo End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438528: marked as done (SSL: Init: Multiple RSA server certificates not allowed)
Your message dated Sat, 15 Nov 2008 22:32:26 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line Bug#438528: SSL: Init: Multiple RSA server certificates not allowed has caused the Debian Bug report #438528, regarding SSL: Init: Multiple RSA server certificates not allowed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 438528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438528 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2-mpm-worker Version: 2.2.3-4+etch1 Severity: important I did try to set up IP Basel SSL on a machine with multiple IP Addresse. Each has it's own SSL Certificate. Still I seam to permanently get the Error: Init: Multiple RSA server certificates not allowed If I have more that one Virtualhost which uses certificates. After some research with Google, this seams to happen to all debian users wich have upgraded from apache2.0 to apache2.2. No solution could be found. Is there a fix to that problem? Regards -Benoit- -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=de_CH, LC_CTYPE=de_CH (charmap=ISO-8859-1) Versions of packages apache2-mpm-worker depends on: ii apache2. 2.2.3-4+etch1 Next generation, scalable, extenda ii libapr1 1.2.7-8.2 The Apache Portable Runtime Librar ii libaprut 1.2.7+dfsg-2The Apache Portable Runtime Utilit ii libc62.3.6.ds1-13etch2 GNU C Library: Shared libraries ii libdb4.4 4.4.20-8Berkeley v4.4 Database Libraries [ ii libexpat 1.95.8-3.4 XML parsing C library - runtime li ii libldap2 2.1.30-13.3 OpenLDAP libraries ii libpcre3 6.7-1 Perl 5 Compatible Regular Expressi ii libpq4 8.1.9-0etch1PostgreSQL C client library ii libsqlit 3.3.8-1.1 SQLite 3 shared library ii libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-2 universally unique id library apache2-mpm-worker recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- There has been no response to the request for more information for a long time. Closing the bug report. If the bug is still relevant and you have more information, feel free to reopen the report. ---End Message---
Bug#360437: marked as done (apache2-mpm-prefork: add -F from 1.3 to 2.0)
Your message dated Sat, 15 Nov 2008 22:18:25 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line apache2-mpm-prefork: add -F from 1.3 to 2.0 has caused the Debian Bug report #360437, regarding apache2-mpm-prefork: add -F from 1.3 to 2.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 360437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360437 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2-mpm-prefork Version: 2.0.54-5 Severity: wishlist Hello, Apache 1.3 had an option -F to run under process supervisors (eg. runit), but Apache 2.0 doesn't seem to have it anymore. It would be nice if you could add this feature to Apache 2.0. I don't understand why it was stripped in the first place... Best, --Toni++ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) ---End Message--- ---BeginMessage--- There has been no response to the request for more information for a long time. Closing the bug report. If the bug is still relevant and you have more information, feel free to reopen the report. ---End Message---
Bug#308788: marked as done (apache2-common: userdir doesn't work for ldap based entries ?)
Your message dated Sat, 15 Nov 2008 21:58:20 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line apache2-common: userdir doesn't work for ldap based entries ? has caused the Debian Bug report #308788, regarding apache2-common: userdir doesn't work for ldap based entries ? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 308788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308788 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2-common Version: 2.0.54-2 Severity: normal I used LDAP server to provide user info(getent all works through libnss-ldap) but it seems that userdir module in apache2 doesn't honour it. From the log, it seems that not even the translation of ~ldapuser to /home/ldapuser/public_html occurred at all as I only see a /~ldapuser access denied. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.11.8-xbox-chimpanzee Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages apache2-common depends on: ii apache2-utils 2.0.54-2 utility programs for webservers ii debconf 1.4.30.13Debian configuration management sy ii debianutils 2.8.4Miscellaneous utilities specific t ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libdb4.24.2.52-18Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libgcc1 1:3.4.3-12 GCC support library ii libmagic1 4.12-1 File type determination library us ii mime-support3.28-1 MIME files 'mime.types' 'mailcap ii net-tools 1.60-10 The NET-3 networking toolkit ii openssl 0.9.7e-3 Secure Socket Layer (SSL) binary a ii ssl-cert1.0-11 Simple debconf wrapper for openssl -- no debconf information ---End Message--- ---BeginMessage--- version: 2.2.3-4 There has been no response to the request for more information for a long time and the bug was likely fixed in 2.2.x. Closing the bug report. If the bug is still relevant and you have more information, feel free to reopen the report. ---End Message---
Bug#345260: marked as done (Apache2-mpm-worker 2.0.55-3 crashing box, memory leak?)
Your message dated Sat, 15 Nov 2008 22:38:01 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line Apache2-mpm-worker 2.0.55-3 crashing box, memory leak? has caused the Debian Bug report #345260, regarding Apache2-mpm-worker 2.0.55-3 crashing box, memory leak? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 345260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345260 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2-mpm-worker Version: 2.0.55-3 We're running Apache 2.0.55 (distro testing package ver 2.0.55-3) on Linux 2.6.14.3. We use worker MPM, mod_actions, mod_rewrite, mod_layout and fastcgi running php. Box serves about 40-50 requests per second in durning day. Once in a while one of apache2 processes rapidly starts to consume lot of memory, freezing the system and crashing it, without any chance to stop it or trace it. We wasn't able to find out what is causing this, error.log doesn't say anything useful and because of sudden apache2 process behaviour tracing is also very hard. Below is attached 'top' screen right before the actual crash, as well as some syslog output before another server reboot. -- top - 21:15:21 up 1:29, 2 users, load average: 17.18, 9.77, 6.55 Tasks: 116 total,2 running, 114 sleeping,0 stopped,0 zombie Cpu(s): 1.3% us, 5.3% sy, 0.0% ni, 0.0% id, 90.7% wa, 1.3% hi, 1.3% si Mem:905776k total,898128k used,7648k free,404k buffers Swap:0k total,0k used,0k free,18236k cached PID USERPR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 130 root15 S 3.0 0.00:00.13 pdflush 6485 www-data 210 881m 600m 1100 S 1.3 67.90:04.83 apache2 9959 www-data 160 284m 8404 1124 S 1.0 0.90:00.57 apache2 1483 root170 2620 544 412 D 0.3 0.10:01.05 syslogd 4789 www-data 250 293m 16m 1136 S 0.3 1.90:06.94 apache2 7270 root160 2196 1100 820 R 0.3 0.10:01.30 top 9790 www-data 170 17500 5552 1272 D 0.3 0.60:00.43 php 10015 www-data 160 284m 8448 1096 S 0.3 0.90:00.59 apache2 -- Dec 28 03:13:35 werewolf kernel: Out of Memory: Killed process 1080 (apache2). Dec 28 03:13:35 werewolf kernel: Out of Memory: Killed process 25021 (apache2 ). Dec 28 03:13:55 werewolf kernel: Out of Memory: Killed process 25084 (apache2). Dec 28 03:13:55 werewolf kernel: Out of Memory: Killed process 25116 (apache2). Dec 28 03:14:28 werewolf kernel: Out of Memory: Killed process 25087 (apache2). Dec 28 03:14:29 werewolf kernel: Out of Memory: Killed process 25164 (apache2). -- apache2.conf (parts): ServerLimit 12 IfModule worker.c StartServers 3 MaxClients 384 MinSpareThreads 20 MaxSpareThreads 50 ThreadsPerChild 32 MaxRequestsPerChild 1 /IfModule AddOutputFilterByType LAYOUT text/html application/x-httpd-php LayoutEndTag /BODY LayoutFooter /some_document.html FastCgiServer /usr/lib/cgi-bin/php4 FastCgiConfig -idle-timeout 15 AddHandler php-fastcgi .php .php3 .php4 Location /cgi-bin/php SetHandler fastcgi-script /Location Action php-fastcgi /cgi-bin/php AddType application/x-httpd-php .php .php3 .php4 I've added this two lines: ulimit -S -m 25600 ulimit -H -m 25600 on top of apache2ctl script (which actually only calls /usr/sbin/apache2 -k start), without any result. Top still shows apache2 processes with resident size = 30Mb. It already crashed our server two times, here's top output in last 4 seconds: top - 22:03:16 up 1 day, 1:33, 2 users, load average: 8.26, 6.90, 4.71 PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 23439 www-data 19 0 372m 94m 1820 S 28.3 10.7 0:08.90 apache2 top - 22:03:18 up 1 day, 1:33, 2 users, load average: 9.76, 7.23, 4.83 PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 23439 www-data 19 0 551m 273m 1820 S 53.1 30.9 0:09.97 apache2 132 root 15 0 000 D 9.9 0.0 0:27.16 kswapd0 This apache process was spawned after 22:03:14, then it consumed 273Mb of memory in about 4 seconds, and finally frozen our box (probably taking rest of memory). In this situation you understand it's hard to deliver any debug information. I'm suprised that ulimit doesn't work with apache, maybe we use it the wrong way? We have some info that may be useful though. From time to time appear apache processes consuming a lot of memory. They grow in time, mostly exiting normally, so I'm not sure they're related to this bug. But I guess that's better than nothing. Below is a trace of one of this kind of processes. # ls /proc/9200/task 9200 9211
Bug#427580: marked as done (apache2: new install failed to start)
Your message dated Sat, 15 Nov 2008 22:51:16 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line apache2: new install failed to start has caused the Debian Bug report #427580, regarding apache2: new install failed to start to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 427580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427580 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2 Version: 2.2.3-4 Severity: normal I did a complete purge of apache/apache2 removed all directories and reinstalled apache2 on start (/etc/init.d/apache2 start) I received. apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName (98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs failed! -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (900, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages apache2 depends on: ii apache2-mpm-worker2.2.3-4High speed threaded model for Apac apache2 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- There is nothing we can do about this problem. The same occurs when some other process occupies port 80. Closing the report. ---End Message---
Bug#497735: marked as done (/etc/init.d/apache2 stop failed)
Your message dated Sat, 15 Nov 2008 22:45:59 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line Re: Bug#497735: /etc/init.d/apache2 stop failed has caused the Debian Bug report #497735, regarding /etc/init.d/apache2 stop failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 497735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497735 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2 Severity: normal On a system with apache2, and only apache2, the stop command to the init script failed. After some poking around, I found that the stop subroutine was calling apache2 -k to stop, not apache2ctl. Apache2ctl sets some environment vars (by sourcing /etc/apache2/envvars), one of which is necessary for the call to apache2 -k to succeed. Changing the call (s, IIRC, there were 2) in the init script fixed the problem. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Version: 2.2.6-1 On Wed, 3 Sep 2008, Glenn English wrote: On a system with apache2, and only apache2, the stop command to the init script failed. After some poking around, I found that the stop subroutine was calling apache2 -k to stop, not apache2ctl. APT policy: (500, 'stable') This has been fixed in testing/unstable already. It is not a severe enough bug to warrant a backport to stable. ---End Message---
Processed: tagging 495110
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 495110 - pending Bug#495110: apache2.2-common: /DocumentRoot/ s,/* *$,, Tags were: pending patch Tags removed: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 441404
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 441404 - moreinfo Bug#441404: apache2.2-common: SSLCertificateChainFile in virtual host context Tags were: moreinfo Tags removed: moreinfo End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 493142
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 493142 wontfix Bug#493142: apache2.2-common: init.d stop does not wait for Apache to stop Tags were: etch patch Tags added: wontfix End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 503537 to libaprutil1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 reassign 503537 libaprutil1 Bug#503537: apache2-mpm-worker: Segmentation fault on apache 2.2.9, libaprutil1 related Bug reassigned from package `apache2-mpm-worker' to `libaprutil1'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503537: marked as done (apache2-mpm-worker: Segmentation fault on apache 2.2.9, libaprutil1 related)
Your message dated Sat, 15 Nov 2008 23:20:39 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line bug #503537: Segmentation fault on apache 2.2.9, libaprutil1 related has caused the Debian Bug report #503537, regarding apache2-mpm-worker: Segmentation fault on apache 2.2.9, libaprutil1 related to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 503537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503537 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2-mpm-worker Version: 2.2.9-10 Severity: important Starting apache2 with /etc/init.d/apache2 got a segmentation fault in apache2ctl. Then trying the apache2 executable with any option directly did also seg-fault. # apache2 -v Server version: Apache/2.2.9 (Debian) Server built: Oct 1 2008 14:34:07 Segmentation fault Interestingly is that the process stays alive even when is printing and reporting a seg-fault. The seg-fault happens always, but apache still works! I solved the seg-fault by updating libaprutil1 from 1.2.7+dfsg-2+b1 to 1_1.2.12+dfsg-8. Now I don't have any seg-faults. Currently, there is no such version dependency of libaprutil1 from apache2-mpm-worker. All the best, Federico Ruiz. -- Package-specific info: List of enabled modules from 'apache2 -M': alias auth_basic authn_file authz_default authz_groupfile authz_host authz_user autoindex cgid deflate dir env mime negotiation setenvif status -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24 (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apache2-mpm-worker depends on: ii apache2.2-common 2.2.9-10 Apache HTTP Server common files ii libapr11.2.11-1 The Apache Portable Runtime Librar ii libaprutil11.2.12+dfsg-8 The Apache Portable Runtime Utilit ii libc6 2.7-6 GNU C Library: Shared libraries ii libpcre3 7.6-2 Perl 5 Compatible Regular Expressi apache2-mpm-worker recommends no packages. apache2-mpm-worker suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 1.2.12+dfsg-1 This is probably this issue which was fixed in apr-util 1.2.8: *) Fix to ensure that deprecated LDAP interfaces are still exposed if using OpenLDAP 2.3. [Joe Orton] svn commit log: * include/apr_ldap.h.in: For OpenLDAP, before including ldap.h, define LDAP_DEPRECATED to 1 if it is not already defined. Fixes use of OpenLDAP 2.3, which by default hides the ldap_init() etc prototypes, which can have rather catastrophic effects at runtime. (since the compiler presumes ldap_init() returns int and discards the top half of the LDAP * pointer value on 64-bit platforms) In other words: Version 1.2.7+dfsg-2+b1 which was linked against the new openldap was broken. ---End Message---
You have 1 unrread message
DDo it noow! http://blogs.cjb.net/arteangf/162152/ Of officers of the british navy. However, you're 'at this moment the second officer, who had run mastiff qualities won so upon lord byron as even now because a murder has touched you personally. To say to my brother, mr. Smith, but and you wish.
Bug#464342: marked as done (apache2-mpm-prefork: Segmentation faults after upgrading)
Your message dated Sun, 16 Nov 2008 08:45:08 +0100 (CET) with message-id [EMAIL PROTECTED] and subject line apache2-mpm-prefork: Segmentation faults after upgrading has caused the Debian Bug report #464342, regarding apache2-mpm-prefork: Segmentation faults after upgrading to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 464342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464342 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2-mpm-prefork Version: 2.2.6-3 Severity: normal After upgrading system libraries, not apache2, I have a segmentation fault when starting apache2. See below: /usr/sbin/apache2ctl: line 80: 10691 Segmentation fault $HTTPD -k $ARGV When stopping I have the following message: Stopping web server: apache2* We failed to correctly shutdown apache, so we're now killing all running apache processes. This is almost certainly suboptimal, so please make sure your system is working as you'd expect now! -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apache2-mpm-prefork depends on: ii apache2.2-common2.2.6-3 Next generation, scalable, extenda ii libapr1 1.2.11-1 The Apache Portable Runtime Librar ii libaprutil1 1.2.12+dfsg-2+b1 The Apache Portable Runtime Utilit ii libc6 2.7-6GNU C Library: Shared libraries ii libdb4.44.4.20-11Berkeley v4.4 Database Libraries [ ii libexpat1 1.95.8-4 XML parsing C library - runtime li ii libldap22.1.30.dfsg-13.5 OpenLDAP libraries ii libpcre37.4-1Perl 5 Compatible Regular Expressi ii libpq5 8.3~rc2-1+b1 PostgreSQL C client library ii libsqlite3-03.4.2-2 SQLite 3 shared library ii libuuid11.40.3-1 universally unique id library apache2-mpm-prefork recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- There has been no response to the request for more information for a long time. Closing the bug report. If the bug is still relevant and you have more information, feel free to reopen the report. ---End Message---
