[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Testbed-admins] Can not bring up the first node for a new Emulab site

Follow your instruction, I logged into the 4.7 freebsd.newnode and I found that the script is '/etc/network/newclient'.(I think this is the right one) Then I ran it, got the following message on screen,

----------------------------------------
Looking for a BPF device for XXX
Opened /dev/bpf15
Looking for BPF device for XXX
Opened /dev/bpf16

Sending out packets
URL is http://boss.bbn.com/newnodecheckin.php?cpuspeed=0&diskdev=ad0&disksize=76319&ifacename0=de0&ifacemac0=XXXXXX&ifacename1=xl0&ifacemac1=XXXXXX&messages=

URL size is XXX
fetch: -: Bad Request
-----------------------------------------
BTW, I downloaded the MFSs from http://www.emulab.net/downloads/tftpboot-latest.tar.gz.  And also I mounted the 6.2 freebsd.newnode and looked at the stuff inside. I found there is code related to 'role' in newclient script, but that script in 4.7 newnode do not have. Am I looked at the right place?

Any suggestion?
Thanks a lot,
Evan Zhang




On Fri, Jul 31, 2009 at 9:41 AM, Leigh Stoller <stoller@flux.utah.edu> wrote:
and 'messages' and this GET request get a error code '400' which is
bad request. Then I looked at newnodecheckin.php and there is a
required parameter 'role' defined in this file.

So based on what I observed , could I say the old 4.X
MFS(freebsd47.newnode) is not supported anymore by the current
emulab software or you want to fix this, or I miss something
here?

Hmm, the 4.7 newnode code is the same as the 6.2 code; they both
pass the role argument.

The thing to do is set the root password on the MFS, reboot the
node, then log in on the console and run the script by hand.

In the freebsd.newnode/boot directory:

boss> sudo mdconfig -a -t vnode -u 1 -f mfsroot
boss> sudo mount /dev/md1 /mnt
boss> sudo chroot /mnt passwd root
boss> sudo umount /mnt
boss> sudo mdconfig -d -u 1
boss> sudo ./prepare


PS: The reason why I am using this old MFS because I even can not
boot the new MFS(freebsd62.newnode) from both of my P3 processor
machine and Core 2 Duo processor machine.

Sounds like a driver problem. I suspect you will have the same problem
when you to boot the disk images.

Lbs