Bug 959793 - isdn.service failed to start on boot
Summary: isdn.service failed to start on boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 914871 (view as bug list)
Depends On:
Blocks: F19Blocker, F19FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2013-05-05 19:02 UTC by Robert Lightfoot
Modified: 2014-01-17 20:42 UTC (History)
15 users (show)

Fixed In Version: systemd-201-2.fc18.7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-15 08:34:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Lightfoot 2013-05-05 19:02:03 UTC
Description of problem:
isdn.service fails to start on boot

Version-Release number of selected component (if applicable):
3.2-90.fc19

How reproducible:
100%

Steps to Reproduce:
1. Install F19 from DVD {Beta-TC3 in this case}
2. Finish install and reboot
3. Get Service Failed Message
  
Actual results:
Service fails to start

Expected results:
service should not start unless needed and should succeed if needed

Additional info:
Output of systemctl status isdn.service follows:
isdn.service - ISDN Services
   Loaded: loaded (/usr/lib/systemd/system/isdn.service; enabled)
   Active: failed (Result: exit-code) since Sun 2013-05-05 14:53:39 EDT; 3min 58s ago
  Process: 415 ExecStart=/usr/libexec/isdn start (code=exited, status=6)

Comment 1 Than Ngo 2013-05-06 12:31:59 UTC
systemd enables isdn by default, reassign to correct component

Comment 2 Lukáš Nykrýn 2013-05-06 13:42:40 UTC
(In reply to comment #1)
> systemd enables isdn by default, reassign to correct component

So systemd should not enable isdn by default? It is in this (outdated) list https://fedoraproject.org/wiki/Starting_services_by_default

Comment 3 Bill Nottingham 2013-05-06 15:29:12 UTC
Should it have some condition where it doesn't even try to start unless it's configured?

Comment 4 Lennart Poettering 2013-05-06 15:42:45 UTC
Not sure what the bug is about.

If it is about isdn enabling itself by default after installation, then this should be fixed in the isdn package (and it should mirgate to the recommended macro-based spec file snippets).

If it is about isdn failing to start, then this also needs to be fixed in the isdn package.

Hence, reassigning.

Comment 5 Michal Schmidt 2013-05-06 15:49:07 UTC
(In reply to comment #3)
> Should it have some condition where it doesn't even try to start unless it's
> configured?

From looking at /usr/libexec/isdn, this should work:
ConditionPathExists=/etc/sysconfig/isdncard

(In reply to comment #4)
> If it is about isdn enabling itself by default after installation, then this
> should be fixed in the isdn package (and it should mirgate to the
> recommended macro-based spec file snippets).

isdn4k-utils.spec already uses the macros.
So I guess comment #1 is a request to delete this line from 90-default.preset:
enable isdn.service

Comment 6 Lennart Poettering 2013-05-06 16:00:32 UTC
AH, sorry, I missed that, isdn.service is indeed listed.

Hmm, should we remove it? ISDN maintainers, what's your take on this?

I'd be happy to remove it from the preset file.

Comment 7 Than Ngo 2013-05-07 07:49:38 UTC
Lennart, ISDN card is not configured during the installation, imo it doesn't make sense to enable it by default.

isdn.service is enable in 90-default.preset, so it should be fixed in systemd package, please remove isdn.service from preset file.

reassign to correct component

thanks

Comment 8 Lennart Poettering 2013-05-07 11:25:38 UTC
OK, I disabled isdn.service in the preset fiels for F18 and F19. This will be included in the next rebuild.

Comment 9 Igor Gnatenko 2013-05-15 07:46:11 UTC
Clean install FC19 Beta TC4.
Bug present.

Comment 10 Michal Schmidt 2013-05-15 08:34:13 UTC
(In reply to comment #9)
> Clean install FC19 Beta TC4.
> Bug present.

This is expected. F19 Beta TC4 has systemd-203. This bug is fixed in systemd-204-2.fc19.
https://admin.fedoraproject.org/updates/FEDORA-2013-7859/systemd-204-2.fc19

Comment 11 Fedora Update System 2013-05-17 12:35:11 UTC
systemd-201-2.fc18.7 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/systemd-201-2.fc18.7

Comment 12 Fedora Update System 2013-05-23 12:22:28 UTC
systemd-201-2.fc18.7 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Than Ngo 2013-05-27 08:13:29 UTC
*** Bug 914871 has been marked as a duplicate of this bug. ***

Comment 14 Burnie West 2014-01-17 20:42:48 UTC
Is this a regression? I am running FC20-3.12.6-300.

I noticed the message FAILED TO START ISDN SERVICES after having troubles updating nfs-utils and firefox - both of which occurred during a yum update today that failed to remove firefox and nfs-utils. I got past that by using the command setenforce permissive, then successfully rebooted after removing the downrev firefox version. It was after that reboot that I noticed the above message.


Note You need to log in before you can comment on or make changes to this bug.