This matches my experience. I (very stupidly) deleted the original
controller database, so I can't re-create your scenario exactly.
Unfortunately, however, restoring the entire /var/xgrid/* tree from
our daily backup of the day before our power-outage (after stopping
the Xgrid service) does not seem to fix the Offline agent problem
after restarting the Xgrid service.
That would seem to rule out my hypothesis. Something more subtle may
be happening.
One thing, though: the agents are likely to all have the wrong cookie
from the old controller (not sure if Kerberos generates one) and
would probably be considered Offline. Did you try to remove an agent
and restart it? You probably did in this case too, but just making sure.
I have, however, confirmed your
test results on a non-server OS X box.
OK, glad that was not just me wanting the result that made it happen
(as is often the case when you do science...). I should file a formal
bug report when I have some time.
Thanks for clarifying the situation so well in your description.
Do you think it's possible that there was an upgrade of the database
libraries that Xgrid uses (Berkeley DB, right?) that's incompatible
with the Xgrid binaries in OS X 10.4.4?
Of course, I have no idea what would cause the problem
(unfortunately, I don't have the source code for Xgrid!), but it is
quite weird. Usually, you have backward-compatibility or forward-
compatibility problems, not self-compatibility problems. OS X.4.4 can
manipulate the database created by X.4.0 but not the one created by X.
4.4!!?? Curious to see what happens on an Intel machine ;-)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xgrid-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xgrid-users/email@hidden
