Bug 439138

Summary:	sblim-sfcb (as submitted to STABLE) startup/shutdown problems
Product:	[openSUSE] openSUSE 11.1	Reporter:	Klaus Kämpf <kkaempf>
Component:	WBEM	Assignee:	E-mail List <bnc-wbem-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Factory
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Klaus Kämpf 2008-10-27 10:06:34 UTC

I just build and installed sblim-sfcb as submitted to STABLE.

Running sfcbd (non-daemon mode) _once_ and stopping it with ctrl-c works fine.

The second start fails with "bind error: Address already in use", hitting ctrl-c results in "connect error: Connection refused" followed by a SIGSEGV for InternalProvider.

Comment 1 Klaus Kämpf 2008-10-27 10:07:56 UTC

SEGV at
#0  0x00007f9ee47db9f1 in getControlChars (id=0x7f9ee0e2c9d6 "registrationDir", val=0x7f9ee0e28710) at control.c:213
213        if ((ctl = ct->ft->get(ct, id))) {

Comment 2 Klaus Kämpf 2008-10-27 10:08:52 UTC

(gdb) print ct
$1 = (UtilHashTable *) 0x0

This is probably due to the failed startup. sfcbd has to terminate on failed startup.

Comment 3 Bart Whiteley 2008-11-07 23:47:13 UTC

Description says: 
> Running sfcbd (non-daemon mode) _once_ and stopping it with ctrl-c works fine.
> 
> The second start fails with "bind error: Address already in use", hitting
> ctrl-c results in "connect error: Connection refused" 

We saw similar behavior on two boxes.  It is attempting to bind to a unix socket, and bind fails with "Address already in use".  However, the line above the call to bind() is a call to unlink() removing an old socket file, if present, so the bind error should not be happening. 

When I build sfcb locally, it doesn't have this problem.  I'm not sure if I have more recent patches in my local build, or if there is some badness in the autobuild build environment.  

Let's see if this problem goes away in rc1.

Comment 4 Bart Whiteley 2008-12-09 00:03:38 UTC


*** This bug has been marked as a duplicate of bug 445334 ***