X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7FBB4.977B0A69@onstor-exch02.onstor.net>; Thu, 20 Sep 2007 10:32:25 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: question on bringup error
Date: Thu, 20 Sep 2007 10:32:25 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E030E37F2@onstor-exch02.onstor.net>
In-Reply-To: <20070920042638.3df5eacb@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: question on bringup error
Thread-Index: Acf7eRz/OP6LxPllSyKPgtgTlnSUwAAOwUyw
From: "Mike Lee" <mike.lee@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "dl-Cougar" <dl-Cougar@onstor.com>

Dude,=20
I think you got something...

mikel@linux-compile.onstor.net:/var/nfsroot/eng155/etc/network 23 % cat =
interfaces=20
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
  address 10.2.1.23
  netmask 255.255.0.0
  gateway 10.2.0.1

# The secondary network interface
#auto eth1
iface eth1 inet static
  address 10.2.1.25
  netmask 255.255.0.0
  gateway 10.2.0.1
mikel@linux-compile.onstor.net:/var/nfsroot/eng155/etc/network 24 %=20

So, I guess these settings over-ride the DHCP assignments?

I will update the IP address and try again.

Thanks.

-Mike
-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, September 20, 2007 4:27 AM
To: Mike Lee
Cc: dl-Cougar
Subject: Re: question on bringup error


post the contents of /etc/network/interfaces.  it looks like you are
getting a new IP address after you start booting, and that doesn't work
with the dhclient program we are using, sadly enough.

On Wed, 19 Sep 2007 18:38:26 -0700 "Mike Lee" <mike.lee@onstor.com>
wrote:

> Team:
>=20
> I'm seeing the following error while trying to bring up the current
> bobcat linux filer I'm using:
>=20
> Sending DHCP requests ., OK
> IP-Config: Got DHCP answer from 10.0.0.143, my address is 10.2.2.3
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: remaining active for wake-on-lan
> IP-Config: Complete:
>       device=3Deth0, addr=3D10.2.2.3, mask=3D255.255.0.0, =
gw=3D10.2.0.1,
>      host=3Deng155, domain=3D, nis-domain=3Donstorlab,
>      bootserver=3D10.0.0.143, rootserver=3D10.0.0.143,
> rootpath=3D/var/nfsroot/eng155 hdc: CF 512MB, CFA DISK drive
> ide1 at 0x020-0x027,0x02e on irq 11
> hdc: max request size: 128KiB
> hdc: 1028160 sectors (526 MB) w/0KiB Cache, CHS=3D1020/16/63
>  hdc: hdc1
> ide-cs: hdc: Vpp =3D 0.0
> Looking up port of RPC 100003/2 on 10.0.0.143
> Looking up port of RPC 100005/1 on 10.0.0.143
> VFS: Mounted root (nfs filesystem) readonly.
> Freeing unused kernel memory: 112k freed
> INIT: version 2.86 booting
> Starting the hotplug events dispatcher: udevd.
> Synthesizing the initial hotplug events...done.
> udevd-event[715]: rename_netif: error changing netif name eth0 to
> eth3: Device or resource busy Waiting for /dev to be fully
> populated...done. :
> :
> Setting up networking....
> Configuring network interfaces...nfs: server 10.0.0.143 not
> responding, still trying fp0: FP0:1 > warning:
> rmc_pm_handle_failure(): sess {unknown_app:pm.0.0} down nfs: server
> 10.0.0.143 not responding, still trying tx1: TXRX1:1 > warning:
> rmc_pm_handle_failure(): sess {unknown_app:pm.0.0} down fp0: warning:
> rmc_pm_handle_failure(): sess {unknown_app:pm.0.0} down tx1: warning:
> rmc_pm_handle_failure(): sess {unknown_app:pm.0.0} down fp0: warning:
> rmc_pm_handle_failure(): sess {unknown_app:pm.0.0} down tx1: warning:
> rmc_pm_handle_failure(): sess {unknown_app:pm.0.0} down fp0: warning:
> rmc_pm_handle_failure(): sess {unknown_app:pm.0.0} down tx1: warning:
> rmc_pm_handle_failure(): sess {unknown_app:pm.0.0} down
>=20
>=20
> Would anyone know what might be wrong?
> I've checked my dhcpd.conf setting and my fstab contents and do not
> see anything wrong (yet). The messages at the ned pertains to pm not
> running, but I cannot get a prompt to investigate, which is another
> problem.
>=20
> Thanks.
>=20
> -Mike
