AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070920042626.3d1754e1@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<mike.lee@onstor.com>,<dl-Cougar@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E030E37EA@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 20 Sep 2007 04:26:38 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Mike Lee" <mike.lee@onstor.com>
Cc: "dl-Cougar" <dl-Cougar@onstor.com>
Subject: Re: question on bringup error
Message-ID: <20070920042638.3df5eacb@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E030E37EA@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E030E37EA@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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:
> 
> I'm seeing the following error while trying to bring up the current
> bobcat linux filer I'm using:
> 
> 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=eth0, addr=10.2.2.3, mask=255.255.0.0, gw=10.2.0.1,
>      host=eng155, domain=, nis-domain=onstorlab,
>      bootserver=10.0.0.143, rootserver=10.0.0.143,
> rootpath=/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=1020/16/63
>  hdc: hdc1
> ide-cs: hdc: Vpp = 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
> 
> 
> 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.
> 
> Thanks.
> 
> -Mike
