Re: [Testbed-admins] Frisbee Linux

[Mike Hibler <mike@flux.utah.edu>]

On your boss node, look in /usr/testbed/log/tmcd.log and see if the server
ever saw the loadinfo request.  If not, look on the client to see who it
is trying to contact by running "tmcc bossinfo".

If it is talking to boss but just not getting back any info, then the DB
state may be wrong.  The easiest way to "fix" that is to put the node in
an experiment (if it isn't already) and then "nfree" it so that it goes
through the full reload cycle.

E.g., if the node is currently in "hwdown" or "reloading" then just do:

      nfree emulab-ops hwdown pcXXX, or
      nfree emulab-ops reloading pcXXX

If the node is currently free, first do:

      wap sched_reserve emulab-ops hwdown pcXXX

and then nfree it.

On Wed, Jul 07, 2010 at 08:21:16AM -0400, ANKIT PATEL wrote:
> I am trying to use the Linux MFS and currently cannot get Frisbee Linux to
> boot correctly. It encounters a problem during startup where it cannot get
> the loadinfo:
> "*** Failed to get loadinfo data"
> 
> If I enable debug mode in the /usr/bin/tmcc I can see it loops for 30
> seconds and tries to get the loadinfo. Any suggestions on how to fix this or
> where to start looking?
> 
> Thanks,
> Ankit Patel

> _______________________________________________
> Testbed-admins mailing list
> Testbed-admins@flux.utah.edu
> http://www.flux.utah.edu/mailman/listinfo/testbed-admins