Re: Bug#243536: apache: Fails to restart on SIGUSR1
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 ## ## httpd.conf -- Apache HTTP server configuration file ## # # Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See URL:http://www.apache.org/docs/ for detailed information about # the directives. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # After this file is processed, the server will look for and process # /etc/apache/srm.conf and then /etc/apache/access.conf # unless you have overridden these with ResourceConfig and/or # AccessConfig directives here. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with / (or drive:/ for Win32), the # server will use that explicit path. If the filenames do *not* begin # with /, the value of ServerRoot is prepended -- so logs/foo.log # with ServerRoot set to /usr/local/apache will be interpreted by the # server as /usr/local/apache/logs/foo.log. # ### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # # # ServerType is either inetd, or standalone. Inetd mode is only supported on # Unix platforms. # ServerType standalone # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept, unless they are specified # with an absolute path. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation # (available at URL:http://www.apache.org/docs/mod/core.html#lockfile); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # ServerRoot /etc/apache # # The LockFile directive sets the path to the lockfile used when Apache # is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or # USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at # its default value. The main reason for changing it is if the logs # directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL # DISK. The PID of the main server process is automatically appended to # the filename. # LockFile /var/lock/apache.lock # # PidFile: The file in which the server should record its process # identification number when it starts. # PidFile /var/run/apache.pid # # ScoreBoardFile: File used to store internal server process information. # Not all architectures require this. But if yours does (you'll know because # this file will be created when you run Apache) then you *must* ensure that # no two invocations of Apache share the same scoreboard file. # ScoreBoardFile /var/run/apache.scoreboard # # In the standard configuration, the server will process this file, # srm.conf, and access.conf in that order. The latter two files are # now distributed empty, as it is recommended that all directives # be kept in a single file for simplicity. The commented-out values # below are the built-in defaults. You can have the server ignore # these files altogether by using /dev/null (for Unix) or # nul (for Win32) for the arguments to the directives. # #ResourceConfig /etc/apache/srm.conf #AccessConfig /etc/apache/access.conf # # Timeout: The number of seconds before receives and sends time out. # Timeout 300 # # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to Off to deactivate. # KeepAlive On # # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an
Re: Bug#243536: apache: Fails to restart on SIGUSR1
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.
Re: Bug#243536: apache: Fails to restart on SIGUSR1
On Apr 14, 8:12pm, Fabio Massimo Di Nitto wrote: 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. Perhaps it would be best to put some info about it in apache's README.Debian until it's fixed in PHP. It could prevent at least some useless bug reports... Pawel -- (___) | Pawel Wiecek - Coven / Svart - | o o | http://www.coven.vmh.net/[EMAIL PROTECTED]GSM: +48603240006 | \ ^ / | GPG/PGP info in message headers * [ Debian GNU/Linux developer ] | () |Never underestimate the power of human stupidity. -- Heinlein |
Bug#243536: apache: Fails to restart on SIGUSR1
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 dpkg1.10.20 Package maintenance system for Deb ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdb4.24.2.52-15Berkeley 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 libpam0g0.76-15 Pluggable Authentication Modules l ii logrotate 3.6.5-2 Log rotation utility ii mime-support3.26-1 MIME files 'mime.types' 'mailcap ii perl5.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: [EMAIL PROTECTED]
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. Fabio On Tue, 13 Apr 2004, Adam Hupp wrote: 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 dpkg1.10.20 Package maintenance system for Deb ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libdb4.24.2.52-15Berkeley 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 libpam0g0.76-15 Pluggable Authentication Modules l ii logrotate 3.6.5-2 Log rotation utility ii mime-support3.26-1 MIME files 'mime.types' 'mailcap ii perl5.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: [EMAIL PROTECTED] -- 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.
