Ubuntu 14.04 LTS server: configure virtual network devices [fail]











up vote
1
down vote

favorite
1












Since a few hours I have a problem with the networkdevice at my server. When I (re)boot the server I get the following fail-message:



configure virtual network devices [fail]



A few moments later it waits for network respons. And then it says that it had wait longer then 60 seconds and it will continue with booting.



When I login and when and enter: ifconfig, I only get only the lo.



When I reboot the system again I choose in grub-modus for (recovery) and in the menu I choose to start the network, and then choosing in that same menu to reboot the server.



After login again and when I enter ifconfig I get the lo and the config and I see that it got the ipaddress, netmask and other stuff.



But when I enter that ip-address in the browser then the browser can't get connection with server. Same when I try to login via SSH.



Same thing when I give the server's mac-address a static-ip-address. It get that static-ip-address, but i can't connect to the server.



Untill a few hours ago it al worked fine. I'm not sure, but maybe the problem started when I renamed the hostname in Webmin -> 'network'.



EDIT When I enter: sudo ifup --no-act eth0
I get the message: /etc/network/interface:15: option with empty value
| ifup: coulnd't read interfaces file "/etc/network/interface"



I'll hope someone can help me with this problem



Thanks,
KevinX










share|improve this question
























  • In my case the "ifup --no-act br0" allowed me to see all the commands that would be executed and one of them was a duplication of adding a default route :) thx a lot. one more command worth mentioning is "ifquery --state". if one of your interfaces which you configured (only configured ones) is missing on the output list then you did something wrong and need to investigate this interface with the previous command
    – Pawel Barcik
    Mar 5 '16 at 19:00












  • one more thing worth noting is that you can run manually the output of "ifup --no-act br0" line by line and you will see exactly which line causes problems (pro tip: look for command duplication)
    – Pawel Barcik
    Mar 5 '16 at 19:17















up vote
1
down vote

favorite
1












Since a few hours I have a problem with the networkdevice at my server. When I (re)boot the server I get the following fail-message:



configure virtual network devices [fail]



A few moments later it waits for network respons. And then it says that it had wait longer then 60 seconds and it will continue with booting.



When I login and when and enter: ifconfig, I only get only the lo.



When I reboot the system again I choose in grub-modus for (recovery) and in the menu I choose to start the network, and then choosing in that same menu to reboot the server.



After login again and when I enter ifconfig I get the lo and the config and I see that it got the ipaddress, netmask and other stuff.



But when I enter that ip-address in the browser then the browser can't get connection with server. Same when I try to login via SSH.



Same thing when I give the server's mac-address a static-ip-address. It get that static-ip-address, but i can't connect to the server.



Untill a few hours ago it al worked fine. I'm not sure, but maybe the problem started when I renamed the hostname in Webmin -> 'network'.



EDIT When I enter: sudo ifup --no-act eth0
I get the message: /etc/network/interface:15: option with empty value
| ifup: coulnd't read interfaces file "/etc/network/interface"



I'll hope someone can help me with this problem



Thanks,
KevinX










share|improve this question
























  • In my case the "ifup --no-act br0" allowed me to see all the commands that would be executed and one of them was a duplication of adding a default route :) thx a lot. one more command worth mentioning is "ifquery --state". if one of your interfaces which you configured (only configured ones) is missing on the output list then you did something wrong and need to investigate this interface with the previous command
    – Pawel Barcik
    Mar 5 '16 at 19:00












  • one more thing worth noting is that you can run manually the output of "ifup --no-act br0" line by line and you will see exactly which line causes problems (pro tip: look for command duplication)
    – Pawel Barcik
    Mar 5 '16 at 19:17













up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





Since a few hours I have a problem with the networkdevice at my server. When I (re)boot the server I get the following fail-message:



configure virtual network devices [fail]



A few moments later it waits for network respons. And then it says that it had wait longer then 60 seconds and it will continue with booting.



When I login and when and enter: ifconfig, I only get only the lo.



When I reboot the system again I choose in grub-modus for (recovery) and in the menu I choose to start the network, and then choosing in that same menu to reboot the server.



After login again and when I enter ifconfig I get the lo and the config and I see that it got the ipaddress, netmask and other stuff.



But when I enter that ip-address in the browser then the browser can't get connection with server. Same when I try to login via SSH.



Same thing when I give the server's mac-address a static-ip-address. It get that static-ip-address, but i can't connect to the server.



Untill a few hours ago it al worked fine. I'm not sure, but maybe the problem started when I renamed the hostname in Webmin -> 'network'.



EDIT When I enter: sudo ifup --no-act eth0
I get the message: /etc/network/interface:15: option with empty value
| ifup: coulnd't read interfaces file "/etc/network/interface"



I'll hope someone can help me with this problem



Thanks,
KevinX










share|improve this question















Since a few hours I have a problem with the networkdevice at my server. When I (re)boot the server I get the following fail-message:



configure virtual network devices [fail]



A few moments later it waits for network respons. And then it says that it had wait longer then 60 seconds and it will continue with booting.



When I login and when and enter: ifconfig, I only get only the lo.



When I reboot the system again I choose in grub-modus for (recovery) and in the menu I choose to start the network, and then choosing in that same menu to reboot the server.



After login again and when I enter ifconfig I get the lo and the config and I see that it got the ipaddress, netmask and other stuff.



But when I enter that ip-address in the browser then the browser can't get connection with server. Same when I try to login via SSH.



Same thing when I give the server's mac-address a static-ip-address. It get that static-ip-address, but i can't connect to the server.



Untill a few hours ago it al worked fine. I'm not sure, but maybe the problem started when I renamed the hostname in Webmin -> 'network'.



EDIT When I enter: sudo ifup --no-act eth0
I get the message: /etc/network/interface:15: option with empty value
| ifup: coulnd't read interfaces file "/etc/network/interface"



I'll hope someone can help me with this problem



Thanks,
KevinX







14.04 networking server interface virtual






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 7 '15 at 8:25

























asked May 7 '15 at 6:55









kevinx

652311




652311












  • In my case the "ifup --no-act br0" allowed me to see all the commands that would be executed and one of them was a duplication of adding a default route :) thx a lot. one more command worth mentioning is "ifquery --state". if one of your interfaces which you configured (only configured ones) is missing on the output list then you did something wrong and need to investigate this interface with the previous command
    – Pawel Barcik
    Mar 5 '16 at 19:00












  • one more thing worth noting is that you can run manually the output of "ifup --no-act br0" line by line and you will see exactly which line causes problems (pro tip: look for command duplication)
    – Pawel Barcik
    Mar 5 '16 at 19:17


















  • In my case the "ifup --no-act br0" allowed me to see all the commands that would be executed and one of them was a duplication of adding a default route :) thx a lot. one more command worth mentioning is "ifquery --state". if one of your interfaces which you configured (only configured ones) is missing on the output list then you did something wrong and need to investigate this interface with the previous command
    – Pawel Barcik
    Mar 5 '16 at 19:00












  • one more thing worth noting is that you can run manually the output of "ifup --no-act br0" line by line and you will see exactly which line causes problems (pro tip: look for command duplication)
    – Pawel Barcik
    Mar 5 '16 at 19:17
















In my case the "ifup --no-act br0" allowed me to see all the commands that would be executed and one of them was a duplication of adding a default route :) thx a lot. one more command worth mentioning is "ifquery --state". if one of your interfaces which you configured (only configured ones) is missing on the output list then you did something wrong and need to investigate this interface with the previous command
– Pawel Barcik
Mar 5 '16 at 19:00






In my case the "ifup --no-act br0" allowed me to see all the commands that would be executed and one of them was a duplication of adding a default route :) thx a lot. one more command worth mentioning is "ifquery --state". if one of your interfaces which you configured (only configured ones) is missing on the output list then you did something wrong and need to investigate this interface with the previous command
– Pawel Barcik
Mar 5 '16 at 19:00














one more thing worth noting is that you can run manually the output of "ifup --no-act br0" line by line and you will see exactly which line causes problems (pro tip: look for command duplication)
– Pawel Barcik
Mar 5 '16 at 19:17




one more thing worth noting is that you can run manually the output of "ifup --no-act br0" line by line and you will see exactly which line causes problems (pro tip: look for command duplication)
– Pawel Barcik
Mar 5 '16 at 19:17










1 Answer
1






active

oldest

votes

















up vote
0
down vote













I had this situation once.



In my case,



ifup eth0


will show the message




can not find /etc/network/interfaces




But actually the file is exist.



So I tried to copy the interfaces file, delete the original interfaces file, the mv the new file back (still no luck).



So I create the interfaces file from scratch again. This time it works.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














     

    draft saved


    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f620431%2fubuntu-14-04-lts-server-configure-virtual-network-devices-fail%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    I had this situation once.



    In my case,



    ifup eth0


    will show the message




    can not find /etc/network/interfaces




    But actually the file is exist.



    So I tried to copy the interfaces file, delete the original interfaces file, the mv the new file back (still no luck).



    So I create the interfaces file from scratch again. This time it works.






    share|improve this answer



























      up vote
      0
      down vote













      I had this situation once.



      In my case,



      ifup eth0


      will show the message




      can not find /etc/network/interfaces




      But actually the file is exist.



      So I tried to copy the interfaces file, delete the original interfaces file, the mv the new file back (still no luck).



      So I create the interfaces file from scratch again. This time it works.






      share|improve this answer

























        up vote
        0
        down vote










        up vote
        0
        down vote









        I had this situation once.



        In my case,



        ifup eth0


        will show the message




        can not find /etc/network/interfaces




        But actually the file is exist.



        So I tried to copy the interfaces file, delete the original interfaces file, the mv the new file back (still no luck).



        So I create the interfaces file from scratch again. This time it works.






        share|improve this answer














        I had this situation once.



        In my case,



        ifup eth0


        will show the message




        can not find /etc/network/interfaces




        But actually the file is exist.



        So I tried to copy the interfaces file, delete the original interfaces file, the mv the new file back (still no luck).



        So I create the interfaces file from scratch again. This time it works.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 11 '16 at 13:16









        wittich

        785716




        785716










        answered Mar 11 '16 at 9:24









        Jiang Junyu

        1




        1






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f620431%2fubuntu-14-04-lts-server-configure-virtual-network-devices-fail%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Ellipse (mathématiques)

            Quarter-circle Tiles

            Mont Emei