[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#243536: marked as done (apache: Fails to restart on SIGUSR1)



Your message dated Wed, 14 Apr 2004 20:12:52 +0200 (CEST)
with message-id <[🔎] Pine.LNX.4.58.0404142011060.12019@trider-g7.ext.fabbione.net>
and subject line Bug#243536: apache: Fails to restart on SIGUSR1
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; 13 Apr 2004 16:56:49 +0000
>From root@hupp.org Tue Apr 13 09:56:49 2004
Return-path: <root@hupp.org>
Received: from (hupp) [66.45.227.173] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BDRDN-0005zc-00; Tue, 13 Apr 2004 09:56:49 -0700
Received: by hupp (Postfix, from userid 0)
	id 8D30583D6; Tue, 13 Apr 2004 17:50:37 +0100 (BST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Adam Hupp <hupp@cs.wisc.edu>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: apache: Fails to restart on SIGUSR1
X-Mailer: reportbug 2.56
Date: Tue, 13 Apr 2004 17:50:37 +0100
Message-Id: <[🔎] 20040413165037.8D30583D6@hupp>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 1

Package: apache
Version: 1.3.29.0.2-4
Severity: normal

After upgrading to testing I noticed (after a few days) that my apache
process was not running.  The last thing in the error logs is:

[notice] SIGUSR1 received.  Doing graceful restart

If I start apache and then do a 

apachectl graceful 

or 

killall -SIGUSR1 apache

Apache will no longer be running, with that entry in the log file.  It
may be useful to know that this server is a user-mode-linux
virtual host.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (650, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.25-5um
Locale: LANG=C, LC_CTYPE=C

Versions of packages apache depends on:
ii  apache-common               1.3.29.0.2-4 Support files for all Apache webse
ii  debconf                     1.4.16       Debian configuration management sy
ii  dpkg                        1.10.20      Package maintenance system for Deb
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libdb4.2                    4.2.52-15    Berkeley v4.2 Database Libraries [
ii  libexpat1                   1.95.6-8     XML parsing C library - runtime li
ii  libmagic1                   4.07-2       File type determination library us
ii  libpam0g                    0.76-15      Pluggable Authentication Modules l
ii  logrotate                   3.6.5-2      Log rotation utility
ii  mime-support                3.26-1       MIME files 'mime.types' & 'mailcap
ii  perl                        5.8.3-2      Larry Wall's Practical Extraction 

-- debconf information:
  apache/server-name: www.erinspottery.com
  apache/document-root: /var/www
  apache/server-port: 80
* apache/enable-suexec: false
  apache/init: true
  apache/server-admin: webmaster@erinspottery.com

---------------------------------------
Received: (at 243536-done) by bugs.debian.org; 14 Apr 2004 18:12:59 +0000
>From fabbione@fabbione.net Wed Apr 14 11:12:59 2004
Return-path: <fabbione@fabbione.net>
Received: from port5.ds1-sby.adsl.cybercity.dk (trider-g7.fabbione.net) [212.242.169.198] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BDosc-00057Y-00; Wed, 14 Apr 2004 11:12:58 -0700
Received: from trider-g7.ext.fabbione.net (port5.ds1-sby.adsl.cybercity.dk [212.242.169.198])
	by trider-g7.fabbione.net (Postfix) with ESMTP
	id F412116; Wed, 14 Apr 2004 20:12:52 +0200 (CEST)
Date: Wed, 14 Apr 2004 20:12:52 +0200 (CEST)
From: Fabio Massimo Di Nitto <fabbione@fabbione.net>
Sender: fabbione@fabbione.net
To: Adam Hupp <hupp@cs.wisc.edu>, 243536-done@bugs.debian.org
Cc: Debian Apache Maintainers <debian-apache@lists.debian.org>
Subject: Re: Bug#243536: apache: Fails to restart on SIGUSR1
In-Reply-To: <[🔎] 20040414134913.GA28183@upl.cs.wisc.edu>
Message-ID: <[🔎] Pine.LNX.4.58.0404142011060.12019@trider-g7.ext.fabbione.net>
References: <[🔎] 20040413165037.8D30583D6@hupp>   
 <[🔎] Pine.LNX.4.58.0404132011100.26391@trider-g7.ext.fabbione.net>
 <[🔎] 20040414134913.GA28183@upl.cs.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: 243536-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 1


Hi Adam,
	I am closing this bug since it is a very well known problem in
php4 <-> libcrypto <-> libc6 problem and there are several (hundreds now?)
duplicates in the BTS. A possible workaround is to load libapache-mod-ssl
without even configuring it and it would solve the problem. In any case it
is not an apache error.

Thanks
Fabio

On Wed, 14 Apr 2004, Adam Hupp wrote:

> On Tue, Apr 13, 2004 at 08:12:22PM +0200, Fabio Massimo Di Nitto wrote:
> >
> > Hi Adam,
> > 	can you atleast include the configuration files? It works here and
> > for most of us. I assume that one external module has been upgraded and
> > apache not reloaded immediatly after. That could have lead to a crash
> > (possibly php4/perl related) at logrotate time.
>
> This is a persistant problem, not a one time thing.  I've found
> through some trial and error that the cause is php4 4.3.3-4.  The
> httpd.conf is attached.
>
> -Adam
>

-- 
<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.



Reply to: