Bug 637101 - Network service startup fails
Summary: Network service startup fails
Keywords:
Status: CLOSED DUPLICATE of bug 630225
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-24 09:47 UTC by Zdenek Kabelac
Modified: 2010-09-24 16:26 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-24 16:26:25 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Failing boot log from network.service start (22.71 KB, text/plain)
2010-09-24 09:49 UTC, Zdenek Kabelac 		no flags Details
Log from systemctl restart network.service (14.23 KB, text/plain)
2010-09-24 09:50 UTC, Zdenek Kabelac 		no flags Details
View All

Description Zdenek Kabelac 2010-09-24 09:47:52 UTC 
Description of problem:

I'm unable to make my network.service 'active' on boot time - systemd reports it always as 'failed' - (attached log from systemctl restart network.service - where it makes to 'active' state.

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

systemd-sysvinit-10-4.fc15.x86_64
systemd-units-10-4.fc15.x86_64
systemd-10-4.fc15.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Zdenek Kabelac 2010-09-24 09:49:40 UTC 
Created attachment 449379 [details]
Failing boot log from network.service start

Here is cut from boot log - as the whole log seems to quite mangled - let me know if you need to know more details
Comment 2 Zdenek Kabelac 2010-09-24 09:50:50 UTC 
Created attachment 449380 [details]
Log from systemctl restart network.service

This command seems to be able to make network service active
Comment 3 Bill Nottingham 2010-09-24 16:26:25 UTC 

*** This bug has been marked as a duplicate of bug 603225 ***
Comment 4 Bill Nottingham 2010-09-24 16:26:47 UTC 

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