Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 103971

Summary: /etc/init.d/bluetooth errors
Product: [Retired] Red Hat Raw Hide Reporter: Chris Ricker <chris.ricker>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-09-11 21:30:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 88859    
Bug Blocks: 100644    

Description Chris Ricker 2003-09-08 16:55:50 UTC
I get the following error when booting up, and also when upgrading from

bluez-utils-2.3-9

to

bluez-utils-2.3-12:

Can't open RFCOMM control socket: No such file or directory


It's coming from this part of the init script:

        if [ -x /usr/bin/rfcomm -a -f /etc/bluetooth/rfcomm.conf ]; then
                /usr/bin/rfcomm -f /etc/bluetooth/rfcomm.conf bind all
        fi

That appears to require a socket which isn't present on my system (probably b/c
I don't have bluetooth hardware)

I also see the following in dmesg once this error occurs:

request_module[bt-proto-3]: fork failed, errno 1

Comment 1 David Woodhouse 2003-09-08 23:18:54 UTC
Well for cosmetic reasons I suppose the rfcomm tool could refrain from actually
opening its socket unless it needs to, but the modprobe shouldn't fail and there
shouldn't be any errors.

Bug #88859 seems to have recurred, but that isn't the problem in this case. It
looks like the kernel isn't even managing to run modprobe. Does it manage to
autoload any other modules?

Reassigning to kernel.

Comment 2 Chris Ricker 2003-09-09 13:28:49 UTC
It autoloads other modules just fine....

Comment 3 Chris Ricker 2003-09-11 21:29:48 UTC
I don't see this any more with kernel-2.4.22-1.2040.nptl from RHN