Network Service is not getting started even if interface is present
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 5 of 5
  1. #1
    Join Date
    Jan 2019
    Location
    India
    Posts
    3
    Windows NT 10.0 Chrome 71.0.3578.98

    Network Service is not getting started even if interface is present

    Hello Everyone!

    I am getting an error while starting the network service at Fedora 23 server. ENS3 is the interface but not sure why ENS5 is coming into the picture.

    Please find the below details for reference:

    -- Subject: Unit network.service has begun start-up
    -- Unit network.service has begun starting up.
    Jan 29 05:38:40 labr network[6071]: Default interface: ens3
    Jan 29 05:38:40 labr network[6071]: Bringing up loopback interface: [ OK ]
    Jan 29 05:38:40 labr network[6071]: Bringing up interface fw0: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device ens5 does not seem to be present, delaying initialization.
    Jan 29 05:38:40 labr /etc/sysconfig/network-scripts/ifup-eth[6213]: Device ens5 does not seem to be present, delaying initialization.
    Jan 29 05:38:40 labr network[6071]: [FAILED]
    Jan 29 05:38:40 labr network[6071]: Bringing up interface mgmt0: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: [ OK ]
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr network[6071]: RTNETLINK answers: File exists
    Jan 29 05:38:42 labr systemd[1]: network.service: Control process exited, code=exited status=1
    Jan 29 05:38:42 labr systemd[1]: Failed to start LSB: Bring up/down networking.
    -- Subject: Unit network.service has failed
    -- Unit network.service has failed.
    Jan 29 05:38:42 labr audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
    Jan 29 05:38:42 labr systemd[1]: network.service: Unit entered failed state.
    Jan 29 05:38:42 labr systemd[1]: network.service: Failed with result 'exit-code'.
    Jan 29 05:39:18 labr systemd[1]: Starting LSB: Bring up/down networking...

    --------------------------------------

    bash-4.3# ls /sys/class/net/
    ens3 lo

    ---------------------------------------

    bash-4.3# systemctl status network
    ● network.service - LSB: Bring up/down networking
    Loaded: loaded (/etc/rc.d/init.d/network)
    Active: failed (Result: exit-code) since Tue 2019-01-29 05:39:20 PST; 2min 38s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 6360 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

    Jan 29 05:39:20 labr network[6360]: RTNETLINK answers: File exists
    Jan 29 05:39:20 labr network[6360]: RTNETLINK answers: File exists
    Jan 29 05:39:20 labr network[6360]: RTNETLINK answers: File exists
    Jan 29 05:39:20 labr network[6360]: RTNETLINK answers: File exists
    Jan 29 05:39:20 labr network[6360]: RTNETLINK answers: File exists
    Jan 29 05:39:20 labr network[6360]: RTNETLINK answers: File exists
    Jan 29 05:39:20 labr systemd[1]: network.service: Control proces...1
    Jan 29 05:39:20 labr systemd[1]: Failed to start LSB: Bring up/d....
    Jan 29 05:39:20 labr systemd[1]: network.service: Unit entered f....
    Jan 29 05:39:20 labr systemd[1]: network.service: Failed with re....
    Hint: Some lines were ellipsized, use -l to show in full.
    Last edited by yash1; 29th January 2019 at 02:49 PM.

  2. #2
    Join Date
    Jan 2019
    Location
    India
    Posts
    3
    Windows NT 10.0 Chrome 71.0.3578.98

    Re: Network Service is not getting started even if interface is present

    to add, there are no files in /etc/udev/rules.d

  3. #3
    Join Date
    Dec 2013
    Location
    United Kingdom
    Posts
    6,799
    Linux Firefox 64.0

    Re: Network Service is not getting started even if interface is present

    moved to EOL, please upgrade your server as Fedora 23 is no longer supported. This leaves your server vulnerable to far too many un-patched security risks.

  4. #4
    Join Date
    Jan 2019
    Location
    India
    Posts
    3
    Windows NT 10.0 Chrome 71.0.3578.98

    Re: Network Service is not getting started even if interface is present

    It is an appliance (Orchestrator) which willl be upgraded to 27 version which is also EOL. But is there any solution to this issue?

  5. #5
    Join Date
    Apr 2014
    Location
    Brooklyn
    Posts
    60
    Windows NT 10.0 Firefox 64.0

    Re: Network Service is not getting started even if interface is present

    Go to /etc/sysconfig/network-scripts and rename your ifcfg-ens5 to ifcfg-ens3
    then use a text editor and change any values inside of /etc/sysconfig/network-scripts/ifcfg-ens3 from ens5 to ens3
    Look for NAME=ens5 and DEVICE=ens5

    Once that is complete restart networking or reboot.

Similar Threads

  1. [SOLVED]
    lvmetad service not started - is this intentional?
    By SteveT in forum Using Fedora
    Replies: 7
    Last Post: 17th March 2017, 08:42 AM
  2. daemons started with service command blocked by network
    By arnonm in forum Servers & Networking
    Replies: 2
    Last Post: 13th October 2011, 12:59 AM
  3. Replies: 8
    Last Post: 6th September 2009, 04:08 AM
  4. Replies: 5
    Last Post: 19th November 2007, 11:05 PM
  5. Replies: 3
    Last Post: 3rd May 2007, 06:15 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •