Your message dated Sat, 24 Nov 2007 10:14:11 +0100
with message-id <[EMAIL PROTECTED]>
and subject line #385741 sysv-rc: invoke-rc.d detects false running processes
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: sysv-rc
Version: 2.86.ds1-15
Followup-For: Bug #378280
When trying to remove apache2, I got this error and dpkg won't continue:
* Stopping web server (apache2)...
... failed!
You may still have some apache2 processes running. There are
processes named 'apache2' which do not match your pid file,
and in the name of safety, we've left them alone. Please review
the situation by hand.
[fail]
invoke-rc.d: initscript apache2, action "stop" failed.
If I check what is going on:
$ ps aux|grep apache2
root 4888 12.8 12.2 131936 126684 pts/2 T+ 18:56 0:03
/usr/bin/dpkg --status-fd 41 --force-depends --force-remove-essential
--purge apache2-mpm-prefork
leiota 4941 0.0 0.0 4040 744 pts/1 R+ 18:56 0:00 grep
apache2
Well I just imagine that invoke-rc.d believes that dpkg process is
actually apache2
and breaks on that.
I haven't found a workaround so that I cannot uninstall any daemon program.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
-- no debconf information
--- End Message ---
--- Begin Message ---
This was very likely a bug in the apache2 packages current at the time
and has been fixed long ago (in 2.2.3-2 I think). Therefore, I am
closing the bug.
--- End Message ---
