[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
Redirecting to ifupdown package. upstart really isn't involved here, as the script that responds to udev events, /etc/init/network- interface.conf, is part of ifupdown. The way these would normally be brought up is by /etc/init/networking.conf which will bring up any interfaces not already up after udev has done all it can. ** Package changed: upstart (Ubuntu) = ifupdown (Ubuntu) ** Changed in: ifupdown (Ubuntu) Importance: Undecided = Medium ** Changed in: ifupdown (Ubuntu) Status: New = Confirmed ** Summary changed: - virtual network interfaces sometimes dont start on startup + alias network interfaces sometimes dont start on boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: alias network interfaces sometimes dont start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/678425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ifupdown (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: alias network interfaces sometimes dont start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/678425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
Unfortunatelly not. This is the only workaround I have found so far. Did you encounter a similar issue? RS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: virtual network interfaces sometimes dont start on startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
Have you find another workaround ? Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: virtual network interfaces sometimes dont start on startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
Another update: This morning my ubuntu servers automatically restarted after auto updates, and I realised that on one server the primary network interface eth0 was left down. But interfaces eth0:0 and eth0:1 were up and working correctly! Thats really weird I think. I use a workaround now - I put ifup eth0 ifup eth0:0 ifup eth0:1 in my /etc/rc.local file, thus ensuring that every interface will wake up at the end of the boot sequence. But this is just a dirty workaroundI would like to see a better solution. Regards Roman Smid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: virtual network interfaces sometimes dont start on startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
@gollum53: you are using lucid or later and you should have the following exmaple as bonding config in your /etc/network/interfaces auto bond0 iface bond0 inet static address 192.168.1.10 netmask 255.255.255.0 gateway 192.168.1.1 bond-slaves none bond-mode 1 # active-passive bond-miimon 100 auto eth0 iface eth0 inet manual bond-primary bond0 bond-slaves eth0 eth1 auto eth1 iface eth1 inet manual bond-primary bond0 bond-slaves eth0 eth1 Why is that? Upstart brings most of the time first the bond0 interface up. But in most cases at this time, the hardware interfaces are not ready (udev didn't signal that to upstart) So, the bonding of the hardware interfaces to the bond interface needs to be done on hardware nic level. Can you come back and try that, pls? It works here on several hundreds of servers of HP without any problem. REgards, \sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: virtual network interfaces sometimes dont start on startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
@Stephan Adig: Thank you for your comment. I'm using lucid 64 bit, and I don't use bonding at all. My /etc/network/interfaces file looks similar to this: auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address xxx.xxx.xxx.89 netmask 255.255.255.224 network xxx.xxx.xxx.xxx broadcast xxx.xxx.xxx.xxx gateway xxx.xxx.xxx.xxx dns-nameservers xxx.xxx.xxx.xxx dns-search foobar.com #first virtual interface auto eth0:0 iface eth0:0 inet static address xxx.xxx.xxx.73 netmask 255.255.255.224 gateway xxx.xxx.xxx.xxx #second virtual interface auto eth0:1 iface eth0:1 inet static address xxx.xxx.xxx.74 netmask 255.255.255.224 gateway xxx.xxx.xxx.xxx ---end of file Is there something bad in this configuration? Thanx Roman Smid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: virtual network interfaces sometimes dont start on startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
** Also affects: ifupdown Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: virtual network interfaces sometimes dont start on startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 678425] Re: virtual network interfaces sometimes dont start on startup
One more comment - the affected hardware is HP ProLiant DL 380 G5 server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: virtual network interfaces sometimes dont start on startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
