Bug 752562

Summary: Upgrading from FC15 to FC16 has buggered my system. Way to go.
Product: [Fedora] Fedora Reporter: Tim Greening-Jackson <tim>
Component: sipwitchAssignee: David Sugar <dyfet>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: alekcejk, dyfet, mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: sipwitch-1.2.0-1.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-22 01:58:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Boot log
none
Output of sysctl status sipwitch.service none

Description Tim Greening-Jackson 2011-11-09 20:58:31 UTC 
I have just tried upgrading an FC15 installation to FC6 using the 64-bit DVD image downloaded from the net. Now when I try to boot the boot hangs and I suddently get a screen full of messages which indicate the reason that it's fallen over is that sipwitch can't be started and I am then directed to sysctl status sipwitch.service or some such (sorry to be vague but I have no means of capturing the message and have had to boot to Windows to send this bug report).

Have to say this is less than impressive. Although I don't particularly wnat to mess my system up (although I'll do pretty much anything to get away from the GUI with FC15) unless this can be solved simply I think Debian calls.
Comment 1 nucleo 2011-11-09 21:11:23 UTC 
I confirm that sipw process takes very much CPU time.
There is sipwitch-1.1.2-1.fc16 in Fedora 16.
Comment 2 Tim Greening-Jackson 2011-11-09 21:34:44 UTC 
Created attachment 532679 [details]
Boot log

Log recovered from /var/log
Comment 3 Tim Greening-Jackson 2011-11-09 21:35:46 UTC 
Created attachment 532680 [details]
Output of sysctl status sipwitch.service

Captured from command line
Comment 4 Tim Greening-Jackson 2011-11-09 21:36:27 UTC 
I am somewhat confused as I have never ever used sipwitch (and wasn't even aware of its existence until this evening).
Comment 5 Tim Greening-Jackson 2011-11-09 21:38:27 UTC 
(In reply to comment #1)
> I confirm that sipw process takes very much CPU time.
> There is sipwitch-1.1.2-1.fc16 in Fedora 16.

Hi nucleo. It possibly does take a lot of CPU, but it never even gets started on my system: the boot falls over at the point at which sipwitch is started. But I don't know enough about the internals of FC to do anything about it.
Comment 6 nucleo 2011-11-09 22:04:01 UTC 
You can try to boot in text runlevel 3 by adding ' 3' to kernel commandline in grub.
Then you should login as root and disable sipwitch service with 'chkconfig --del sipwitch' and restart system.
Comment 7 David Sugar 2012-02-13 10:26:09 UTC 
This is verified and solved by either disabling, or otherwise not installing, the "subscriber" module (sipwitch-plugin-subscriber).  This also is fixed upstream in sipwitch 1.2.0, which I need to push back into F16.
Comment 8 Fedora Update System 2012-02-13 10:56:43 UTC 
sipwitch-1.2.0-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/sipwitch-1.2.0-1.fc16
Comment 9 Fedora Update System 2012-02-14 09:03:24 UTC 
Package sipwitch-1.2.0-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sipwitch-1.2.0-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1610/sipwitch-1.2.0-1.fc16
then log in and leave karma (feedback).
Comment 10 Fedora Update System 2012-02-22 01:58:24 UTC 
sipwitch-1.2.0-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.