On Sat, Feb 6, 2010 at 3:00 PM,
<testbed-admins-request@flux.utah.edu> wrote:
Send Testbed-admins mailing list submissions to
testbed-admins@flux.utah.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://www.flux.utah.edu/mailman/listinfo/testbed-admins
or, via email, send a message with subject or body 'help' to
testbed-admins-request@flux.utah.edu
You can reach the person managing the list at
testbed-admins-owner@flux.utah.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Testbed-admins digest..."
Today's Topics:
1. Problem after creating nodes (Miguel A. Erazo)
2. Re: Problem after creating nodes (Leigh Stoller)
----------------------------------------------------------------------
Message: 1
Date: Fri, 5 Feb 2010 19:46:27 -0400
From: "Miguel A. Erazo" <miguel.erazo@gmail.com>
Subject: [Testbed-admins] Problem after creating nodes
To: testbed-admins@flux.utah.edu
Message-ID:
<1b19fbfd1002051546i49f48281y47609b467510cb36@mail.gmail.com">1b19fbfd1002051546i49f48281y47609b467510cb36@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello all,
I have successfully Created nodes but after hitting 'Create' they do not
boot to the new image. No change is observed in them. (So I guess something
is wrong with frisbee)
However, I could manually make them to boot from /tftpboot/freebsd by using
the 'Interactive mode' in the booting process by doing a:
loader:/tftpboot/freebsd
After this, the node boots successfully and now its hostname is:
pc1.reloading.emulab-ops.primessf.net (which I think is correct at
this stage)
By doing this I think I bypassed frisbee and something maybe wrong. Now my
node is in the 'Reloading' experiment under emulab-ops.
My questions are:
- what could be missing so that nodes do not boot into the Frisbee MFS to
later reboot and sit in the bootloader?
- By doing the 'loader:/tftpboot/freebsd' command in the booting process am
I bypassing something so that I will have problems in the
future?
- Is this node that booted from 'loader:/tftpboot/freebsd' ready to be used
for an experiment? what is missing?
Any help is greatly appreciated,
Miguel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /listarchives/testbed-admins/attachments/20100205/410ae6b4/attachment.html
------------------------------
Message: 2
Date: Fri, 5 Feb 2010 15:59:23 -0800
From: Leigh Stoller <stoller@flux.utah.edu>
Subject: Re: [Testbed-admins] Problem after creating nodes
To: "Miguel A. Erazo" <miguel.erazo@gmail.com>
Cc: testbed-admins@flux.utah.edu
Message-ID: <201B3499-439C-4FA8-A69B-C576B3B6737A@flux.utah.edu">201B3499-439C-4FA8-A69B-C576B3B6737A@flux.utah.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
> I have successfully Created nodes but after hitting 'Create' they do
> not boot to the new image. No change is observed in them. (So I
> guess something is wrong with frisbee)
Hmm, the best way to figure what is going on is to look on the
console. Did the node ever try to the load the frisbee MFS and if it
did, what did the console say as it tried to run frisbee. Send us
output ...
Basically, watching the console in a window that is saving the output
during the entire create node process is a very good idea, especially
when you are fist getting a testbed started up.
You can rerun the created node process by:
boss> wap deletenode pcXXX -f -b
and then pushing the power button on the node. It will go back through
the newnode path.
Lbs
------------------------------
_______________________________________________
Testbed-admins mailing list
Testbed-admins@flux.utah.edu
http://www.flux.utah.edu/mailman/listinfo/testbed-admins
End of Testbed-admins Digest, Vol 55, Issue 5
*********************************************