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

Bug#330276: marked as done ('apache2ctl status' exits with 0 after 404)

Your message dated Tue, 18 Mar 2008 21:31:55 +0100
with message-id <200803182131.56174.sf@sfritsch.de>
and subject line 'apache2ctl status' exits with 0 after 404
has caused the Debian Bug report #330276,
regarding 'apache2ctl status' exits with 0 after 404
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
330276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330276
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apache2
Version: 2.0.54-4
Severity: normal


When 'apache2ctl status' is called against a server that does not have
the 'status.cgi' configured, it gets a 404 but then still exits with a 0
exit code.  While in some ways it could legitimately be said to have
verified that the server is at least running, it gives a false
impression via its exit code, one which is particularly frustrating with
automated tools.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-k7-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages apache2 depends on:
ii  apache2-mpm-prefork           2.0.54-4   traditional model for Apache2

apache2 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
version: 2.2.8-3

> Well, I'm writing a tool for automated server management
> (http://reductivelabs.com/projects/puppet), and it needs some way
> to automatically discern whether a service is currently running. 
> Normally the init script's status command would be sufficient, but
> since that is lacking, well, I was hoping I could use apache2ctl.

The status function was added to the init script in version 2.2.8-3 in 
unstable. It shows if apache2 is running. Therefore I am closing this 
bug.

To determine if apache2 is actually working, you need to do requests 
that depend on the used configuration (e.g. query a URL that causes a 
database access, etc.).

--- End Message ---
Reply to: