Your message dated Tue, 4 May 2010 12:42:13 -0700
with message-id <[email protected]>
and subject line upgrade fails if zoneminder is already running
has caused the Debian Bug report #567740,
regarding upgrade fails if zoneminder is already running
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 [email protected]
immediately.)
--
567740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567740
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zoneminder
Version: 1.24.2-2+b1
Severity: important
when upgrading zoneminder, it fails to upgrade:
sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up zoneminder (1.24.2-2+b1) ...
Starting ZoneMinder: failure
invoke-rc.d: initscript zoneminder, action "start" failed.
dpkg: error processing zoneminder (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
zoneminder
E: Sub-process /usr/bin/dpkg returned an error code (1)
i believe it is because zoneminder is already running, and
/etc/init.d/zoneminder returns an error if called with the "start" argument
when zoneminder is already running:
sudo invoke-rc.d zoneminder start
Starting ZoneMinder: failure
invoke-rc.d: initscript zoneminder, action "start" failed.
if i manually stop zoneminder with "invoke-rc.d zoneminder stop" and then run
"apt-get -f install", it sucessfully completes the upgrade without problem.
it seems that dh_installinit added the postinst and prerm hooks that *should*
handle this properly, but maybe the "stop" argument in prerm isn't working
properly?
maybe /etc/init.d/zoneminder shouldn't treat additional "start" calls as an
error if it's already running?
i'm fairly certain this problem exists with older versions as well, but i
noticed it when upgrading this version on several machines today.
live well,
vagrant
--- End Message ---
--- Begin Message ---
Version: 1.24.2-3
this round of upgrades worked without problems, so i'm closing this bug.
live well,
vagrant
--- End Message ---
