isns fails to config with dpkg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
isns (Debian) |
Fix Released
|
Unknown
|
|||
isns (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: isns
Hello, Bug Trackers, Developers, etc.
Attached is a screenshot from Synaptic, showing ldconfig with dpkg failing with isns. This is probably repetitive, and you've seen it before, but it's been a consistent failure through several updates, and at least one kernel:
uname -a:
Linux ubu864Serv2R 2.6.24-19-server #1 SMP Wed Jun 18 14:44:47 UTC 2008 x86_64 GNU/Linux
Thanks,
Gordon
(My email is the rest of the screen name after my name, just add the at and the dot if you need to send a message)
ProblemType: Package
Architecture: amd64
Date: Fri Jul 4 20:34:32 2008
Dependencies:
libgcc1 1:4.2.3-2ubuntu7
gcc-4.2-base 4.2.3-2ubuntu7
libgdbm3 1.8.3-3
libc6 2.7-10ubuntu3
DistroRelease: Ubuntu 8.04
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: isns 2.1-01+dfsg-2.1
PackageArchitec
SourcePackage: isns
Title: package isns 2.1-01+dfsg-2.1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.24-19-server x86_64
Related branches
Changed in isns: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in isns: | |
status: | Unknown → New |
Changed in isns: | |
assignee: | nobody → pschorf |
status: | Triaged → In Progress |
Changed in isns: | |
assignee: | pschorf → nobody |
status: | In Progress → Confirmed |
Changed in isns (Debian): | |
status: | New → Fix Released |
Thank you for your bug report. I can confirm that this is still an issue. The reason for the error is that the init script does not pass "--oknodo" to start-stop-daemon. This means that the "stop" and "restart" actions always give an error if the isnsd service is not already running, and the "start" action always gives an error if the isnsd service is already running.
The isns postinst script calls the "restart" action when then package is configured on install, and this will always fail for a new installation of the package (not an upgrade)