Re: [Testbed-admins] Error on creating nodes

["Espinola, Derek" <despinola@ll.mit.edu>]

Title: Re: [Testbed-admins] Error on creating nodes

Yup looks like it is booting into newnode MFS

Sep 22 13:47:06 boss-nlet bootinfo[912]: 172.19.5.254: REQUEST (vers 1)
Sep 22 13:47:06 boss-nlet bootinfo[912]: iptonodeid: No such nodeid: 172.19.5.254
Sep 22 13:47:06 boss-nlet bootinfo[912]: Unable to convert IP to nodeid for 172.19.5.254!
Sep 22 13:47:06 boss-nlet bootinfo[912]: 172.19.5.254: nonexistent IP, booting 'emulab-ops,NEWNODE-MFS'
Sep 22 13:47:06 boss-nlet bootinfo[912]: iptonodeid: No such nodeid: 172.19.5.254
Sep 22 13:47:06 boss-nlet bootinfo[912]: Unable to convert IP to nodeid for 172.19.5.254!
Sep 22 13:47:06 boss-nlet bootinfo[912]: 172.19.5.254: REPLY: boot from mfs /tftpboot/freebsd.newnode

The 172.19.5.254 is the temporary ip assigned when installing as a newnode.  Any ideas?

On 9/22/09 1:41 PM, "Leigh Stoller" <stoller@flux.utah.edu> wrote:

> > The machines are rebooting but, when they come up they read “Node is
> > already a real node, named pc1” ....And they continue to show “PCs
> > reloading on the mgmt site.
>
> So that sorta sounds like they are still booting into the newnode MFS?
> What does /usr/testbed/log/bootinfo.log show for the same time period.
>
> Lbs