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

Re: Bug#243536: apache: Fails to restart on SIGUSR1

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.


On Tue, 13 Apr 2004, Adam Hupp wrote:

> Package: apache
> Version:
> 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      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

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