/proc and /sys are guaranteed to be mounted by either the initramfs or
by init.
I'm going to mark this bug invalid as it's not caused by anything in
ifenslave-2.6 itself and probably not by Ubuntu.
** Changed in: ifenslave-2.6 (Ubuntu)
Status: New => Invalid
--
You received this bug noti
I have added an exit 0 at the top of the script, and it boots correctly.
The strange thing is that this is happening on other machines built with
12.04, even where there is no separate /var partition. Do you have any
further ideas why this would be happening now in 12.04, but didn't use
to occur i
Right, so /var may be mounted after your script is triggered, as your
script depends on /var, that may explain the failure.
Can you maybe make the script "exit 0" right at the beginning to confirm
that calling the script isn't the problem and that's indeed something
done within the script that's m
I'm very grateful for your help.
Interesting idea that - my fstab is attached.
** Attachment added: "fstab"
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/1056792/+attachment/3398771/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Can you also attach your /etc/fstab?
I'm wondering if perhaps the network is coming up early enough that some
devices aren't mounted yet causing the script to fail.
A failure of a post-up script on bond0 will likely hold eth0 and eth1 causing
the delay. ifupdown only considers an interface as fu
As requested, complete tar of /etc/network attached to this bug.
** Attachment added: "Full /etc/network tarbal"
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/1056792/+attachment/3398696/+files/network.tar.gz
** Changed in: ifenslave-2.6 (Ubuntu)
Status: Incomplete => Ne
Attached is my post-up file. It is simply a bash script that monitors
the status of the bonded device in /proc - so should, of course, in no
way influence the actual process of bring up the device (it's a post-up
command after all).
That said, you go me thinking - so I tried commenting out the lin
Based on the errors in /var/log/upstart, it looks like your interface is
already getting configured by something prior to ifupdown making it fail
to bring up the interface and causing the hang.
Can you please attach a tarball containing all of /etc/network/ and your
/usr/local/sbin/check-bond.sh s
Has anyone taken a look at the logs or had any thoughts on this? Can it
be assigned to the maintainer of the ifenslave-2.6 package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056792
Title:
Bonde
As requested, an attached tarball file of the upstart logs.
** Attachment added: "Tarball og upstart logs."
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/1056792/+attachment/3351331/+files/upstart_logs_pm1.tar
** Changed in: ifenslave-2.6 (Ubuntu)
Status: Incomplete => N
Please attach a tarball of /var/log/upstart/
** Changed in: ifenslave-2.6 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056792
Title:
Bonded network devic
ifenslave-2.6 information:
russell@pm1 ~ $ aptitude show ifenslave-2.6
Package: ifenslave-2.6
State: installed
Automatically installed: no
Version: 1.1.0-19ubuntu5
Priority: optional
Section: net
Maintainer: Ubuntu Developers
Architecture: amd64
Uncompressed Size: 103 k
Depends:
** Attachment added: "Screenshot of errors during boot and the "waiting..."
lines."
https://bugs.launchpad.net/bugs/1056792/+attachment/3344912/+files/Screenshot-JViewer%5B10.0.2.158%5D%20-%201%20fps.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
13 matches
Mail list logo
