Hi,
I'm in the process of upgrading our FAI installation from Lenny to Squeeze and
have run into a bit of a bug. I suspect that it is more of a Squeeze bug than a
FAI bug, but I thought that I'd check here first as the help that I have
received here is top notch :)
With some help from Michael
> On Sun, 12 Dec 2010 16:38:23 -0800, David Dreezer
> said:
> In working through the upgrade to Squeeze however, this script is
failing. The problem is that with Squeeze $netdevices_up returns all devices
except LO, up or not.
> 3: eth1: mtu 1500 qdisc pfifo_fast
state DO
> On Sun, 12 Dec 2010 16:38:23 -0800, David Dreezer
> said:
> get-boot-info determines $netdevices_up like so:
> netdevices_up=$(ip link show up | grep "^[1-9$]" | cut -d : -f 2 |
cut -d ' ' -f 2 | grep -v "^lo" | sort | uniq)
I think will will fix it even with lenny.
Ind
On Mon, 13 Dec 2010, Thomas Lange wrote:
> > On Sun, 12 Dec 2010 16:38:23 -0800, David Dreezer
> > said:
>
> > get-boot-info determines $netdevices_up like so:
>
> > netdevices_up=$(ip link show up | grep "^[1-9$]" | cut -d : -f 2 |
> cut -d ' ' -f 2 | grep -v "^lo" | sort |
> On Mon, 13 Dec 2010 16:12:05 +0100 (CET), Cristian Ionescu-Idbohrn
> said:
> My 'ip utility, iproute2-ss080725':
> does not support an "up" argument.
Below is the output on Debian lenny with iproute 20080725-2.
malzmuehle[~]> ip link show help
Usage: ip link set DEVICE { up
On Mon, 13 Dec 2010, Thomas Lange wrote:
>
> Below is the output on Debian lenny with iproute 20080725-2.
>
> malzmuehle[~]> ip link show help
> Usage: ip link set DEVICE { up | down |
> arp { on | off } |
> dynamic { on | off } |
>
Hi Thomas,
I left out an important piece of information. That is, we're using the latest
experimental. Don't know fi this makes a difference, I did not look at the 3.x
script.
David Dreezer
Customer Advocate, Social Strata, Inc.
Online Community HQ Since 1996
Hoop.la · LiveCloud · Eve Communi
Hi Thomas,
This did not work, unfortunately. I patched the get-boot-info script yet FAI
still thinks eth1 is up. If I ssh to the client machine and run that line
manually then echo $netdevices_up I see only eth0, however boot.log shows this:
netdevices_all="eth0
eth1"
netdevices_up="eth0
eth1"
On Mon, 13 Dec 2010, David Dreezer wrote:
>
> This did not work, unfortunately. I patched the get-boot-info script yet
> FAI still thinks eth1 is up. If I ssh to the client machine and run that
> line manually then echo $netdevices_up I see only eth0, however boot.log
> shows this:
>
> netdevices_a
> On Mon, 13 Dec 2010 20:50:58 -0800, David Dreezer
> said:
> This did not work, unfortunately. I patched the get-boot-info
> script
Did you patched it inside the nfsroot?
--
regards Thomas
I patched it on the fai server, than ran fai-setup -v immediately after.
David Dreezer
Customer Advocate, Social Strata, Inc.
On Dec 14, 2010, at 1:36 AM, Thomas Lange wrote:
>> On Mon, 13 Dec 2010 20:50:58 -0800, David Dreezer
>> said:
>
>> This did not work, unfortunately. I pat
Hi Cristian,
I can get that information for you tonight (us pacific) but I will
unfortunately not have access to that box until that time as it is not web
accessible and I am not physically at the facility at the moment. When last I
looked it was
r...@db099:~# ip link show up
1: lo: mtu 1643
On Tue, 14 Dec 2010, David Dreezer wrote:
>
> I can get that information for you tonight (us pacific) but I will
> unfortunately not have access to that box until that time as it is not web
> accessible and I am not physically at the facility at the moment. When last
> I looked it was
>
> r...@
You are right. As I had said in a previous email I had edited the file on the
fai server then ran fai-setup again. This did nothing because the file is
written by a deb package. I went back and manually edited it in the nfsroot
and that took care of the problem.
David Dreezer
Customer Advocat
14 matches
Mail list logo
