Bug 1058966 - sipwitch fails to start
Summary: sipwitch fails to start
Keywords:
Status: CLOSED DUPLICATE of bug 1057867
Alias: None
Product: Fedora
Classification: Fedora
Component: sipwitch
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: David Sugar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-28 21:22 UTC by Gareth Williams
Modified: 2014-01-28 22:10 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-28 22:10:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Gareth Williams 2014-01-28 21:22:51 UTC 
Description of problem: sipwitch fails to start with systemctl


Version-Release number of selected component (if applicable): 1.6.1.1.fc20


How reproducible: Always


Steps to Reproduce:
1. Enter 'systemctl start sipwitch' at terminal.
2.
3.

Actual results: Fails with 'Failed to issue method call: Unit sipwitch.service failed to load: No such file or directory.'


Expected results: sipwitch starts.


Additional info:
The sipwitch.service file is located in /usr/lib64/systemd/service/ directory.  There are no other files in this directory on my x86_64 machine.  Moving the file to /usr/lib/systemd/service/ resolves the 'no such file' issue but sipwitch still fails to start.  journalctl shows sipwitch complaining and printing it's help (list of command line options). Editing the sipwitch.service file and changing the ExecStart line to:
ExecStart=/usr/sbin/sipw -b $OPTIONS
allows the service to start.  Whether the options are passed correctly is another question - I've not got that far yet...
Comment 1 David Sugar 2014-01-28 22:08:58 UTC 
This is a dup of 1057867, which is currently pending fix release...
Comment 2 David Sugar 2014-01-28 22:10:23 UTC 

*** This bug has been marked as a duplicate of bug 1057867 ***
Note You need to log in before you can comment on or make changes to this bug.