Bug#219378: Doh.
Ok, it looks like rotatelogs (which is what I meant in my previous email) no longer comes with apache-common? In that case, it was apache attempting to open a pipe to a nonexistant program to log which hangs. Still think this is a bug :-)
Bug#219378: Doh.
On Sun, 29 Feb 2004, Matthew Wilcox wrote: On Sun, Feb 29, 2004 at 05:37:08AM -0600, Dave O wrote: Ok, it looks like rotatelogs (which is what I meant in my previous email) no longer comes with apache-common? In that case, it was apache attempting to open a pipe to a nonexistant program to log which hangs. Still think this is a bug :-) Apache in woody doesn't use rotatelogs, it uses logrotate. What on earth are you doing? not woody, sid. CustomLog |/usr/sbin/rotatelogs /path/to/access.log 86400 combined /usr/sbin/rotatelogs was in apache-common before, but no longer seems to be. The 1.3.29 apache tarball still has it, though :/ The real problem here, however, is that apache simply hangs when you log to a pipe and the program you are logging to is not found. No error could be found anywhere and the end result is that all apache children end up hung and once you reach MaxClients the server is unusuable.
Bug#154447: Is this problem still reproducible?
Are you still able to reproduce this problem with current kernels and apache? We are currently triaging bugs to prepare for a release of Debian, and would like to prune our bugs list of old bugs that can no longer be reproduced. Cheers -Thom
Bug#111687: marked as done (404 pages should use UTF-8 or % encoding)
Your message dated Sun, 29 Feb 2004 18:28:36 + with message-id [EMAIL PROTECTED] and subject line Agreed, closing has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 8 Sep 2001 17:24:21 + From [EMAIL PROTECTED] Sat Sep 08 12:24:21 2001 Return-path: [EMAIL PROTECTED] Received: from itaipu.nitnet.com.br [200.255.111.241] by master.debian.org with smtp (Exim 3.12 1 (Debian)) id 15flq7-0005Tc-00; Sat, 08 Sep 2001 12:24:20 -0500 Received: (qmail 305 invoked from network); 8 Sep 2001 17:37:28 - Received: from salzburg.nitnet.com.br (HELO flower.cesarb) (200.198.84.62) by itaipu.nitnet.com.br with SMTP; 8 Sep 2001 17:37:28 - Received: from cesarb by flower.cesarb with local (Exim 3.31 #1 (Debian)) id 15flpm-Zl-00; Sat, 08 Sep 2001 14:23:58 -0300 From: Cesar Eduardo Barros [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: 404 pages should use UTF-8 or % encoding X-Reportbug-Version: 1.23 X-Mailer: reportbug 1.23 Date: Sat, 08 Sep 2001 14:23:58 -0300 Message-Id: [EMAIL PROTECTED] Sender: Cesar Eduardo Barros [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Package: apache Version: 1.3.19-1 Severity: normal The 404 page for http://localhost/á; is: Not Found The requested URL /á was not found on this server. It should have shown the non-ASCII characters as % escapes, as mozilla does in the URL bar and before sending: http://localhost/%C3%A1 It might also use UTF8 to convert it back to the intended code (see http://lists.w3.org/Archives/Public/uri/1997Apr/0115.html http://www.w3.org/International/O-URL-and-ident http://www.w3.org/TR/REC-html40/appendix/notes.html#h-B.2.1 for background), but since some people use local encodings like latin-1 this is not as good as the escapes. By the way, http://localhost/á is an invalid URL (that's why mozilla converted it to http://localhost/%C3%A1 before sending to the server), and /á is also invalid as the local part for a URL (at least before UTF-8 is standardized as the canonical encoding for URLs). -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux flower 2.4.7 #1 Sat Jul 21 20:57:24 BRT 2001 i686 Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 Versions of packages apache depends on: ii apache-common1.3.19-1Support files for all Apache webse ii libc62.2.4-1 GNU C Library: Shared libraries an ii libdb2 2:2.7.7.0-1 The Berkeley database routines (ru ii mime-support 3.12-1 MIME files 'mime.types' 'mailcap ii perl 5.6.1-5 Larry Wall's Practical Extraction ii perl [perl5] 5.6.1-5 Larry Wall's Practical Extraction --- Received: (at 111687-done) by bugs.debian.org; 29 Feb 2004 18:28:37 + From [EMAIL PROTECTED] Sun Feb 29 10:28:37 2004 Return-path: [EMAIL PROTECTED] Received: from mirror.positive-internet.com [80.87.128.67] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AxVg5-0006kZ-00; Sun, 29 Feb 2004 10:28:37 -0800 Received: by mirror.positive-internet.com (Postfix, from userid 1002) id A324A432FA; Sun, 29 Feb 2004 18:28:36 + (GMT) Date: Sun, 29 Feb 2004 18:28:36 + From: Thom May [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Agreed, closing Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Operating-System: Linux/2.6.2-1-686 (i686) User-Agent: Mutt/1.5.5.1+cvs20040105i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_27 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no version=2.60-bugs.debian.org_2004_02_27 X-Spam-Level: Note that 404 pages are informational for users. they're not standardised, and they're not supposed to be machine readable. Were it providing a hyperlinked URL also, then that should be escaped. I'm closing this bug. -Thom
Processed: pending
Processing commands for [EMAIL PROTECTED]: tags 165155 pending Bug#165155: Security Problems in apache = 1.3.27 There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#45904: marked as done (mod_roaming seems not to work with Communicator 4.61)
Your message dated Sun, 29 Feb 2004 20:09:33 + with message-id [EMAIL PROTECTED] and subject line I think this might be somewhat out of date. has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 24 Sep 1999 14:26:52 + Received: (qmail 23857 invoked from network); 24 Sep 1999 14:26:51 - Received: from unknown (HELO shaslam.london.excite.com) (194.129.119.130) by master.debian.org with SMTP; 24 Sep 1999 14:26:51 - Received: from shaslam by shaslam.london.excite.com with local (Exim 3.03 #1 (Debian)) id 11UWIl-0004eC-00; Fri, 24 Sep 1999 15:26:19 +0100 From: Steve Haslam [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: mod_roaming seems not to work with Communicator 4.61 X-Reportbug-Version: 0.29 X-Mailer: reportbug 0.29 Date: Fri, 24 Sep 1999 15:26:18 +0100 Message-Id: [EMAIL PROTECTED] Package: apache-common Version: 1.3.9-8 Severity: normal When Communicator 4.61 tries to check the roaming server, it performs PUT and DELETE ops on /roaming/WRITETEST. However, mod_roaming disallows all these because it doesn't fit the /roaming/userid/file scheme: access.log: 127.0.0.1 - - [24/Sep/1999:15:05:04 +0100] \ DELETE /roaming/WRITETEST HTTP/1.0 403 215 error.log: [Fri Sep 24 15:05:04 1999] [error] [client 127.0.0.1] \ Roaming uri must contain a userid [Fri Sep 24 15:05:04 1999] [warn] [client 127.0.0.1] \ Is the URL of the form http://host/roamingalias/userid/file? SRH -- System Information Debian Release: potato Architecture: i386 Kernel: Linux shaslam 2.2.12 #1 Wed Sep 22 13:41:51 BST 1999 i686 Versions of packages apache-common depends on: ii libc6 2.1.2-3GNU C Library: Shared libraries an ii libgdbmg1 1.7.3-26.2 GNU dbm database routines (runtime ii perl-5.005 [perl5]5.005.03-4 Larry Wall's Practical Extracting --- Received: (at 45904-done) by bugs.debian.org; 29 Feb 2004 20:09:34 + From [EMAIL PROTECTED] Sun Feb 29 12:09:34 2004 Return-path: [EMAIL PROTECTED] Received: from mirror.positive-internet.com [80.87.128.67] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AxXFm-0002yg-00; Sun, 29 Feb 2004 12:09:34 -0800 Received: by mirror.positive-internet.com (Postfix, from userid 1002) id A6A8C432FA; Sun, 29 Feb 2004 20:09:33 + (GMT) Date: Sun, 29 Feb 2004 20:09:33 + From: Thom May [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: I think this might be somewhat out of date. Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Operating-System: Linux/2.6.2-1-686 (i686) User-Agent: Mutt/1.5.5.1+cvs20040105i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_27 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no version=2.60-bugs.debian.org_2004_02_27 X-Spam-Level: Uh, communicator 4.6.1 you say? I think, unless the roaming problem is still ongoing with a reasonably recent mozilla/apache combo, this bug is better off closed. -Thom
中药灭蚊蝇 一夏仅一瓶
! 36 0635-866186813061524676mailto:[EMAIL PROTECTED] http://lxly.yeah.net 98 EBT
Bug#235566: apache: Apache does not load; no errors given
On Sun, Feb 29, 2004 at 11:29:28PM -0500, Bill Denney wrote: My system does not load apache and it does not write an error to the error log (/var/log/apache/error.log or to /var/log/messages). Upon restart, I get this in /var/log/apache/error/log: Processing config directory: /etc/apache/conf.d [Sun Feb 29 23:10:47 2004] [warn] pid file /var/run/apache.pid overwritten -- Unclean shutdown of previous Apache run? I'm having severe difficulty localizing the problem since I don't have any errors to go from. When I run apache in single server mode (apache -X -F), it gives a segmentation fault (this behavior just started--previously it would work in this mode). I've still not localized the problems from this. What modules do you have enabled? (PHP often causes problems of this type.) Try disabling modules and see if the problem goes away. -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain
Bug#235566: apache: Apache does not load; no errors given
On Mon, 1 Mar 2004, Matthew Wilcox wrote: On Sun, Feb 29, 2004 at 11:29:28PM -0500, Bill Denney wrote: My system does not load apache and it does not write an error to the error log (/var/log/apache/error.log or to /var/log/messages). Upon restart, I get this in /var/log/apache/error/log: Processing config directory: /etc/apache/conf.d [Sun Feb 29 23:10:47 2004] [warn] pid file /var/run/apache.pid overwritten -- Unclean shutdown of previous Apache run? I'm having severe difficulty localizing the problem since I don't have any errors to go from. When I run apache in single server mode (apache -X -F), it gives a segmentation fault (this behavior just started--previously it would work in this mode). I've still not localized the problems from this. What modules do you have enabled? (PHP often causes problems of this type.) Try disabling modules and see if the problem goes away. Reading through the php bugs informed me that I need to remove php-imap (which was no longer necessary for my setup). That fixed my problem. Bill -- ..that would require that my computer have enough processor speed and memory to be able to rub its tummy and pat its head. -- Kelly Klega
Bug#235566: apache: Apache does not load; no errors given
On Mon, 1 Mar 2004, Matthew Wilcox wrote: On Sun, Feb 29, 2004 at 11:29:28PM -0500, Bill Denney wrote: My system does not load apache and it does not write an error to the error log (/var/log/apache/error.log or to /var/log/messages). Upon restart, I get this in /var/log/apache/error/log: Processing config directory: /etc/apache/conf.d [Sun Feb 29 23:10:47 2004] [warn] pid file /var/run/apache.pid overwritten -- Unclean shutdown of previous Apache run? I'm having severe difficulty localizing the problem since I don't have any errors to go from. When I run apache in single server mode (apache -X -F), it gives a segmentation fault (this behavior just started--previously it would work in this mode). I've still not localized the problems from this. What modules do you have enabled? (PHP often causes problems of this type.) Try disabling modules and see if the problem goes away. Disabling PHP solved the problem. Do you know of a way to fix the problem with the PHP module? Bill -- Linus ran his automatic release-scripts on a bad tree because he is a booger-head. -- Linus Torvalds
