Why I'm giving message `A start job is running for raise network interfaces` at boot after disabling predictable network interfaces names?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I disabled predictable network interfaces names by changing GRUB_CMDLINE_LINUX line in /etc/default/grub from:



GRUB_CMDLINE_LINUX="pci=nomsi"


to:



GRUB_CMDLINE_LINUX="pci=nomsi net.ifnames=0"


on a fresh installation of Debian GNU/Linux testing system with installed proprietary NVIDIA drivers. I did it because my external USB Wi-Fi card didn't work with systemd interfaces names.



After disabling predictable network interfaces names I'm giving following message at boot:




A start job is running for raise network interfaces (2 minutes of 5
mins 1 sec)




and system boots long.



My /etc/network/intefaces file:



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback


Why am I giving this message at boot? How can I avoid long booting of my system?










share|improve this question























  • A background question on the jargon: unix.stackexchange.com/questions/310737
    – JdeBP
    Aug 11 '17 at 5:29














up vote
1
down vote

favorite












I disabled predictable network interfaces names by changing GRUB_CMDLINE_LINUX line in /etc/default/grub from:



GRUB_CMDLINE_LINUX="pci=nomsi"


to:



GRUB_CMDLINE_LINUX="pci=nomsi net.ifnames=0"


on a fresh installation of Debian GNU/Linux testing system with installed proprietary NVIDIA drivers. I did it because my external USB Wi-Fi card didn't work with systemd interfaces names.



After disabling predictable network interfaces names I'm giving following message at boot:




A start job is running for raise network interfaces (2 minutes of 5
mins 1 sec)




and system boots long.



My /etc/network/intefaces file:



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback


Why am I giving this message at boot? How can I avoid long booting of my system?










share|improve this question























  • A background question on the jargon: unix.stackexchange.com/questions/310737
    – JdeBP
    Aug 11 '17 at 5:29












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I disabled predictable network interfaces names by changing GRUB_CMDLINE_LINUX line in /etc/default/grub from:



GRUB_CMDLINE_LINUX="pci=nomsi"


to:



GRUB_CMDLINE_LINUX="pci=nomsi net.ifnames=0"


on a fresh installation of Debian GNU/Linux testing system with installed proprietary NVIDIA drivers. I did it because my external USB Wi-Fi card didn't work with systemd interfaces names.



After disabling predictable network interfaces names I'm giving following message at boot:




A start job is running for raise network interfaces (2 minutes of 5
mins 1 sec)




and system boots long.



My /etc/network/intefaces file:



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback


Why am I giving this message at boot? How can I avoid long booting of my system?










share|improve this question















I disabled predictable network interfaces names by changing GRUB_CMDLINE_LINUX line in /etc/default/grub from:



GRUB_CMDLINE_LINUX="pci=nomsi"


to:



GRUB_CMDLINE_LINUX="pci=nomsi net.ifnames=0"


on a fresh installation of Debian GNU/Linux testing system with installed proprietary NVIDIA drivers. I did it because my external USB Wi-Fi card didn't work with systemd interfaces names.



After disabling predictable network interfaces names I'm giving following message at boot:




A start job is running for raise network interfaces (2 minutes of 5
mins 1 sec)




and system boots long.



My /etc/network/intefaces file:



# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback


Why am I giving this message at boot? How can I avoid long booting of my system?







debian systemd network-interface






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 10 '17 at 16:59

























asked Aug 10 '17 at 16:39









java-devel

255215




255215











  • A background question on the jargon: unix.stackexchange.com/questions/310737
    – JdeBP
    Aug 11 '17 at 5:29
















  • A background question on the jargon: unix.stackexchange.com/questions/310737
    – JdeBP
    Aug 11 '17 at 5:29















A background question on the jargon: unix.stackexchange.com/questions/310737
– JdeBP
Aug 11 '17 at 5:29




A background question on the jargon: unix.stackexchange.com/questions/310737
– JdeBP
Aug 11 '17 at 5:29










2 Answers
2






active

oldest

votes

















up vote
3
down vote



accepted










Solved by changing file /etc/network/interfaces.d/setup from:



auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp


to:



auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp





share|improve this answer




















  • This worked for me in Debian 9.1
    – Ajeeb.K.P
    Aug 14 '17 at 8:33

















up vote
1
down vote













Disable the service that waits to start the network interfaces.



systemctl disable NetworkManager-wait-online.service


And to enable:



systemctl enable NetworkManager-wait-online.service


Alternatively you can reduce the amount of time that it waits to start the job.



vim /etc/systemd/system/network-online.target.wants/networking.service 

TimeoutStartSec=5min ##Change parameter, should be at the end of the page.





share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f385281%2fwhy-im-giving-message-a-start-job-is-running-for-raise-network-interfaces-at%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    3
    down vote



    accepted










    Solved by changing file /etc/network/interfaces.d/setup from:



    auto lo
    iface lo inet loopback

    auto eth0
    iface eth0 inet dhcp


    to:



    auto lo
    iface lo inet loopback

    allow-hotplug eth0
    iface eth0 inet dhcp





    share|improve this answer




















    • This worked for me in Debian 9.1
      – Ajeeb.K.P
      Aug 14 '17 at 8:33














    up vote
    3
    down vote



    accepted










    Solved by changing file /etc/network/interfaces.d/setup from:



    auto lo
    iface lo inet loopback

    auto eth0
    iface eth0 inet dhcp


    to:



    auto lo
    iface lo inet loopback

    allow-hotplug eth0
    iface eth0 inet dhcp





    share|improve this answer




















    • This worked for me in Debian 9.1
      – Ajeeb.K.P
      Aug 14 '17 at 8:33












    up vote
    3
    down vote



    accepted







    up vote
    3
    down vote



    accepted






    Solved by changing file /etc/network/interfaces.d/setup from:



    auto lo
    iface lo inet loopback

    auto eth0
    iface eth0 inet dhcp


    to:



    auto lo
    iface lo inet loopback

    allow-hotplug eth0
    iface eth0 inet dhcp





    share|improve this answer












    Solved by changing file /etc/network/interfaces.d/setup from:



    auto lo
    iface lo inet loopback

    auto eth0
    iface eth0 inet dhcp


    to:



    auto lo
    iface lo inet loopback

    allow-hotplug eth0
    iface eth0 inet dhcp






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Aug 10 '17 at 19:01









    java-devel

    255215




    255215











    • This worked for me in Debian 9.1
      – Ajeeb.K.P
      Aug 14 '17 at 8:33
















    • This worked for me in Debian 9.1
      – Ajeeb.K.P
      Aug 14 '17 at 8:33















    This worked for me in Debian 9.1
    – Ajeeb.K.P
    Aug 14 '17 at 8:33




    This worked for me in Debian 9.1
    – Ajeeb.K.P
    Aug 14 '17 at 8:33












    up vote
    1
    down vote













    Disable the service that waits to start the network interfaces.



    systemctl disable NetworkManager-wait-online.service


    And to enable:



    systemctl enable NetworkManager-wait-online.service


    Alternatively you can reduce the amount of time that it waits to start the job.



    vim /etc/systemd/system/network-online.target.wants/networking.service 

    TimeoutStartSec=5min ##Change parameter, should be at the end of the page.





    share|improve this answer
























      up vote
      1
      down vote













      Disable the service that waits to start the network interfaces.



      systemctl disable NetworkManager-wait-online.service


      And to enable:



      systemctl enable NetworkManager-wait-online.service


      Alternatively you can reduce the amount of time that it waits to start the job.



      vim /etc/systemd/system/network-online.target.wants/networking.service 

      TimeoutStartSec=5min ##Change parameter, should be at the end of the page.





      share|improve this answer






















        up vote
        1
        down vote










        up vote
        1
        down vote









        Disable the service that waits to start the network interfaces.



        systemctl disable NetworkManager-wait-online.service


        And to enable:



        systemctl enable NetworkManager-wait-online.service


        Alternatively you can reduce the amount of time that it waits to start the job.



        vim /etc/systemd/system/network-online.target.wants/networking.service 

        TimeoutStartSec=5min ##Change parameter, should be at the end of the page.





        share|improve this answer












        Disable the service that waits to start the network interfaces.



        systemctl disable NetworkManager-wait-online.service


        And to enable:



        systemctl enable NetworkManager-wait-online.service


        Alternatively you can reduce the amount of time that it waits to start the job.



        vim /etc/systemd/system/network-online.target.wants/networking.service 

        TimeoutStartSec=5min ##Change parameter, should be at the end of the page.






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 10 '17 at 17:06









        Hunter.S.Thompson

        4,66931334




        4,66931334



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f385281%2fwhy-im-giving-message-a-start-job-is-running-for-raise-network-interfaces-at%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?