Bug#803190: apache2: systectl status apache2.service reports startup failed, even though apache2 is running

2015-10-27 Thread Adam Hupp
Package: apache2
Version: 2.4.10-10+deb8u3
Severity: normal

After upgrading to jessie the apache2 init script reports failure (via
systemctl) even though it actually starts up correctly.

adam@gaba:~$ sudo /etc/init.d/apache2 start
Starting apache2 (via systemctl): apache2.serviceJob for apache2.service 
failed. See 'systemctl status apache2.service' and 'journalctl -xn' for details.
failed!

Hoever, it does actually startup correctly:

adam@gaba:~$ ps aux | grep /usr/sbin/apache2
root  7192  0.0  4.2  98744 21472 ?Ss   12:45   0:00 
/usr/sbin/apache2 -k start
www-data  7195  0.0  2.0 100224 10196 ?S12:45   0:00 
/usr/sbin/apache2 -k start
www-data  7196  0.0  2.0 100224 10196 ?S12:45   0:00 
/usr/sbin/apache2 -k start
www-data  7197  0.0  2.0 100224 10196 ?S12:45   0:00 
/usr/sbin/apache2 -k start
www-data  7198  0.0  2.0 100224 10196 ?S12:45   0:00 
/usr/sbin/apache2 -k start
www-data  7199  0.0  2.0 100224 10196 ?S12:45   0:00 
/usr/sbin/apache2 -k start

`systemctl status` does not imply what the problem is:

adam@gaba:~$ systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
   Loaded: loaded (/etc/init.d/apache2)
  Active: failed (Result: exit-code) since Tue 2015-10-27 12:45:54 PDT; 
1min 53s ago
Process: 7178 ExecStart=/etc/init.d/apache2 start (code=exited, 
status=1/FAILURE)

Neither does `journalctl`: 

Oct 27 12:45:34 gaba systemd[1]: Starting LSB: Apache2 web server...
-- Subject: Unit apache2.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apache2.service has begun starting up.
Oct 27 12:45:34 gaba apache2[7178]: Starting web server: apache2[Tue Oct 27 
12:45:34.261012 2015] [core:warn] [pid 7191] AH00117: Ignoring deprecated use 
of DefaultType in line 1
Oct 27 12:45:54 gaba apache2[7178]: failed!
Oct 27 12:45:54 gaba apache2[7178]: The apache2 instance did not start within 
20 seconds. Please read the log files to discover problems ... (warning).
Oct 27 12:45:54 gaba systemd[1]: apache2.service: control process exited, 
code=exited status=1
Oct 27 12:45:54 gaba systemd[1]: Failed to start LSB: Apache2 web server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apache2.service has failed.
--
-- The result is failed.
Oct 27 12:45:54 gaba systemd[1]: Unit apache2.service entered failed state.

There is nothing in the apache error log either.  

-- Package-specific info:

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.1.5-x86-linode80 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apache2 depends on:
ii  apache2-bin2.4.10-10+deb8u3
ii  apache2-data   2.4.10-10+deb8u3
ii  apache2-utils  2.4.10-10+deb8u3
ii  dpkg   1.17.25
ii  lsb-base   4.1+Debian13+nmu1
ii  mime-support   3.58
ii  perl   5.20.2-3+deb8u1
ii  procps 2:3.3.9-9

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.35

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  lynx-cur [www-browser]   2.8.9dev1-2+deb8u1

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.1-3
ii  libaprutil1  1.5.4-1
ii  libaprutil1-dbd-sqlite3  1.5.4-1
ii  libaprutil1-ldap 1.5.4-1
ii  libc62.19-18+deb8u1
ii  libldap-2.4-22.4.40+dfsg-1+deb8u1
ii  liblua5.1-0  5.1.5-7.1
ii  libpcre3 2:8.35-3.3
ii  libssl1.0.0  1.0.1k-3+deb8u1
ii  libxml2  2.9.1+dfsg1-5
ii  perl 5.20.2-3+deb8u1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  lynx-cur [www-browser]   2.8.9dev1-2+deb8u1

Versions of packages apache2 is related to:
ii  apache2  2.4.10-10+deb8u3
ii  apache2-bin  2.4.10-10+deb8u3

-- Configuration Files:
/etc/apache2/apache2.conf changed:
Options -Indexes
ServerRoot "/etc/apache2"
ServerName "hupp.org"
ServerTokens Prod
PidFile /var/run/apache2.pid
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15

StartServers  5
MinSpareServers   5
MaxSpareServers  10
MaxClients  150
MaxRequestsPerChild   0


StartServers  2
MaxClients  150
MinSpareThreads  25
MaxSpareThreads  75 
ThreadsPerChild  25
MaxRequestsPerChild   0

User www-data
Group www-data
AccessFile

Bug#247229: apache2-common: -S option segfaults when NameVirtualHost specifies port

2004-05-04 Thread Adam Hupp
On Tue, May 04, 2004 at 07:04:41PM +0100, Thom May wrote:
> > 
> Just a backtrace with gdb would be a good start.

#0  0x0807e515 in ap_set_name_virtual_host ()
#1  0x0807e6d3 in ap_set_name_virtual_host ()
#2  0x0807eaff in ap_fini_vhost_config ()
#3  0x0807dbd1 in main ()

I think I have a better way to reproduce it.  If NameVirtualHost has a
port specified (e.g. *:80) and a VirtualHost does not (e.g
) then it faults.

-Adam




Bug#247229: apache2-common: -S option segfaults when NameVirtualHost specifies port

2004-05-03 Thread Adam Hupp
Package: apache2-common
Version: 2.0.49-1
Severity: normal

I had a NameVirtualHost *:80 directive in my apache2.conf.  I tried
running 'apache2 -S' to debug my vhosts and got a segfault.  Changing it
to "NameVirtualHost *" fixed the segfault.  I can provide a core file if
needed.

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

Versions of packages apache2-common depends on:
ii  debconf 1.4.22   Debian configuration management sy
ii  debianutils 2.8.1Miscellaneous utilities specific t
ii  libapr0 2.0.49-1 The Apache Portable Runtime
ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libdb4.24.2.52-16Berkeley v4.2 Database Libraries [
ii  libexpat1   1.95.6-8 XML parsing C library - runtime li
ii  libldap22.1.23-1 OpenLDAP libraries
ii  libmagic1   4.07-2   File type determination library us
ii  libssl0.9.7 0.9.7d-1 SSL shared libraries
ii  mime-support3.26-1   MIME files 'mime.types' & 'mailcap
ii  net-tools   1.60-9   The NET-3 networking toolkit
ii  openssl 0.9.7d-1 Secure Socket Layer (SSL) binary a
ii  ssl-cert1.0-7Simple debconf wrapper for openssl
ii  zlib1g  1:1.2.1-5compression library - runtime

-- no debconf information




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

2004-04-14 Thread Adam Hupp
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 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 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

Bug#243536: apache: Fails to restart on SIGUSR1

2004-04-13 Thread Adam Hupp
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]