by clearing the file, that "fixed" the problem.
I reran named_setup and exports_setup then the nodes rebooted with and got the new OS (I could tell since I had changed the motd) but is there a way to tell on the node itself which image it booted to (if you have multiple freebsd images for example)?
The Named setup and the dhcp setup seam to work.
Ben Burnett
R&D Software Engineer: wired, wireless, ad hoc, mesh networking,
network monitoring and data visualization
ATC (Architecture Technology Corporation)
http://www.atcorp.com/ bburnett@atcorp.com (952) 829-5864 x167
--------Views expressed are mine and not those of ATC--------
Personal:
ben@burnett.ws http://www.burnett.ws/
http://ben.burnett.ws/http://www.linkedin.com/in/benburnett
On Fri, Jun 19, 2009 at 12:52 PM, Leigh Stoller
<stoller@flux.utah.edu> wrote:
Okay, so now that we got this figured out, I added testbed-admins back
on since this is an interesting failure mode.
named.root has the internet servers configured, but my testbed is
not connected to the internet, so should I clear the file (copy to
backup, then clear it) then restart named?
So I am not entirely sure why named.root was missing, which explains
why named was failing to start, but I think it is safe to clear that
file since there is no point in trying to go offsite for queries.
so, now do I run named_setup?
I added two nodes (pc1 and pc2) and I couldn't find them anywhere in
the config files.
You will want to run named_setup and exports_setup. I assume they *did*
make it into /usr/local/etc/dhcpd.conf ...
The you can reboot them:
boss> wap newnode_reboot <IP1>
boss> wap newnode_reboot <IP2>
where IP1 and IP2 are the IPs of the new nodes. Typically this happens
in the backend of the web page addnode script, but since that aborted,
you can just run the steps above by hand.
Or you can skip all of the above and do this:
boss> wap deletenode pc1
boss> wap deletenode pc2
and start over from the web interface ...
Lbs