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

Bug#497735: marked as done (/etc/init.d/apache2 stop failed)



Your message dated Sat, 15 Nov 2008 22:45:59 +0100 (CET)
with message-id <Pine.LNX.4.64.0811152244151.32586@eru.sfritsch.de>
and subject line Re: Bug#497735: /etc/init.d/apache2 stop failed
has caused the Debian Bug report #497735,
regarding /etc/init.d/apache2 stop failed
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.)


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


On a system with apache2, and only apache2, the stop command to the init
script failed. After some poking around, I found that the stop
subroutine was calling apache2 -k to stop, not apache2ctl.

Apache2ctl sets some environment vars (by sourcing /etc/apache2/envvars), one of which is necessary for the
call to apache2 -k to succeed. Changing the call (s, IIRC, there were 2)
in the init script fixed the problem.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)



--- End Message ---
--- Begin Message ---
Version: 2.2.6-1

On Wed, 3 Sep 2008, Glenn English wrote:
On a system with apache2, and only apache2, the stop command to the init
script failed. After some poking around, I found that the stop
subroutine was calling apache2 -k to stop, not apache2ctl.

 APT policy: (500, 'stable')

This has been fixed in testing/unstable already. It is not a severe enough bug to warrant a backport to stable.


--- End Message ---

Reply to: