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. I have, however, confirmed your
test results on a non-server OS X box. ...<snip>...
OK, problem solved, with a big help from Ernie and Xgrid developers.
The trick was to make sure there was also a '/var/xgrid/controller/
blobs' directory, and that it is owned by 'xgridcontroller'.
So here would be the right way of restarting your controller with a
fresh database, and keep a backup. I checked the script below works.
and run the above script using sudo, e.g.:
sudo /path/reset_controller.sh
(the sleep seems to be needed to give launchd a chance to realize the
controller is stopped)
So nothing to do with 10.4.0 or 10.4.4. Retrospectively, it seems
obvious I should have tried to at least create a blobs directory. I
thought the database engine would create it as necessary when the
database grows bigger.
_______________________________________________
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
