sfcb fails to stop, resulting in sblim-cmpi-base failing to install

Bug #344697 reported by Guillaume Bottex
2
Affects Status Importance Assigned to Milestone
sblim-cmpi-base (Ubuntu)
Invalid
Low
Unassigned
sblim-sfcb (Ubuntu)
Fix Released
Low
Thierry Carrez

Bug Description

Binary package hint: sblim-cmpi-base

sblim-cmpi-base could not be reinstalled after a the installation of sfcb.
the steps I did are the following:

After misregistering my own CIM provider to sfcb, I did in synaptic:
- Reinstallation of sfcb (did not correct my problem)
- Complete removal of scfb
- Installation of sfcb (did correct my problem, but the root/cimv2 has been emptied)
- Reinstallation of sblim-cmpi-base -> crash

ProblemType: Package
Architecture: i386
Dependencies:
 libgcc1 1:4.3.2-1ubuntu12
 libcmpiosbase-common0 1.5.6-0ubuntu1
 gcc-4.3-base 4.3.2-1ubuntu12
 findutils 4.4.0-2ubuntu3
 libc6 2.8~20080505-0ubuntu9
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: sblim-cmpi-base 1.5.6-0ubuntu1
SourcePackage: sblim-cmpi-base
Title: package sblim-cmpi-base 1.5.6-0ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.27-11-generic i686

Related branches

Revision history for this message
Guillaume Bottex (danmcgoo) wrote :
Revision history for this message
Thierry Carrez (ttx) wrote :

In the logs it appears that SFCB couldn't be stopped after sblim-cmpi-base was reinstalled. It was probably not running. It may be related to the extra providers you installed. If sfcb is running OK now, what happens if you reinstall it now ? If you run "sudo dpkg --configure -a" ?

Changed in sblim-cmpi-base:
status: New → Incomplete
Revision history for this message
Guillaume Bottex (danmcgoo) wrote :

Actually the problem disappeared the next day when I boot up my computer.
So it's maybe due to the fact that SFCB was not running, I don't remember if I shut it down before uninstalling the sblim-cmpi-base package.

Revision history for this message
Thierry Carrez (ttx) wrote :

The problem occurs when sfcbd refuses to stop on SIGTERM. provider-register.sh checks that sfcbd is really stopped and fails if it isn't, resulting in a failed install.

Solution is to have a more aggressive stop in /etc/init.d/sfcb, like --retry=TERM/10/KILL/5

When you hit the issue It can be workarounded by manually killing the sfcbd process and sudo dpkg -- configure -a to finish the install.

Changed in sblim-cmpi-base:
importance: Undecided → Low
status: Incomplete → Triaged
Thierry Carrez (ttx)
Changed in sblim-sfcb:
importance: Undecided → Low
status: New → Triaged
Changed in sblim-cmpi-base:
status: Triaged → Invalid
Revision history for this message
Guillaume Bottex (danmcgoo) wrote :

I looked to the source of the sblim-cmpi-base debian package.
SFCB is effectively stopped with the init script (/etc/init.d/sfcb).
But I noticed that SFCB usually have some problems to stop by using this script, usually when SFCB is in an unresponding state.
My method is to kill it with a "killall -9 sfcbd".

More genarally I noticed that SFCB have some responding problems.

Thierry Carrez (ttx)
Changed in sblim-sfcb:
assignee: nobody → ttx
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sblim-sfcb - 1.3.0-0ubuntu4

---------------
sblim-sfcb (1.3.0-0ubuntu4) jaunty; urgency=low

  * debian/sfcb.init: Use retry schedule in start-stop-daemon --stop to kill
    sfcbd if it doesn't stop when nicely asked (LP: #344697)

 -- Thierry Carrez <email address hidden> Mon, 23 Mar 2009 11:51:52 +0100

Changed in sblim-sfcb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.