Not sure, but there is a default 32 hex password in the 'gui_rpc_auth.cfg' file. Have changed that to the same password as what i use to log into the website, to make it easy on the gray cells. Then attaching should work fine.

Indeed, killing the BOINCmgr and relaunching it will re-establish the connection most of the times.

Changing that password didn't help me either... I even chose a new password on the website, but that didn't help.

After more testing, I have found where I think the problem lies, but have no idea on how to fix it.

I was running BOINC as a system service with the Make_BOINC_Services.sh script (sorry to have left this out in my original post).

When I completely eliminate this script and service everything runs fine with BOINC Manager.

There must be something in the BOINC Startup Item that is not configured correctly/fubared when the service starts at boot up??

Only thing in the Startup Items>Boinc is the Boinc executable and the Startup Parameter.plist:

{
Description = "BOINC client daemon";
Provides = ("BOINC client daemon");
Requires = ("NFS");
OrderPreference = "Last";
}

And as I said in my original post, I have to Force Quit the boinc service to stop the services, so it does seem like something is hanging with that service.

As these are public computing lab computers that I'm configuring I really want the service to run all the time, not just when a user is logged in.

Cheryl

OK, I understand that as it controls remote accesses to the BOINC service. But that wasn't her problem. For access problems between one manager and one service, that password file can't be the problem.

I resolved my issue and must admit that it was a stupid mistake on my part. When I ran the Make_BOINC_Service.sh, I left out the path to the data directory in the command itself. (I mis-read the instructions given with the script, reading steps 6 & 7 as an either/or situation, not both).

Thanks for all help and suggestions that were given.
Cheryl