I've just installed boinc on Fedora 9 and attached to two projects, one of them here. Alas, whenever I try to open the manager to see how it's doing, I get told that I must open it in the same directory as the client. Even if I do that from a command line it fails. I've tried to connect to localhost, as instructed, using both my password and the root password but it still fails. I know it's running, but I just can't connect to it. (It did connect at first, mind you.) What am I doing wrong?
Copyright © 2024 Einstein@Home. All rights reserved.
Boincmgr not connecting to client
)
You are probably putting in the wrong password. The one you need is the one stored in the file gui_rpc_auth.cfg. The default is a 32 char random string but you can change it to be whatever you want with a text editor. If you change it, you need to restart BOINC.
If you have the client and the manager in the same directory (as they should be) and the client is started when the system boots (--daemon flag), you can start/stop the manager any time you need to and it will simply attach to the localhost client without you having to give a password. The manager can read and use what is in the auth file. The password is really for when you want to attach remotely to another host somewhere else on the network. You can install the same gui_rpc_auth.cfg file on all your networked hosts and manage them from a single instance of the manager. To attach to a remote host, you will need to use the password that's in the auth file.
Cheers,
Gary.
RE: I've just installed
)
Check out this page if you installed via the package manager.
Kathryn :o)
Einstein@Home Moderator
It Just Doesn't Work. No
)
It Just Doesn't Work. No matter what I do it doesn't connect. I think I'm going to uninstall/reinstall and follow those instructions correctly from the start and see if that works.
RE: It Just Doesn't
)
Have you checked ownership and permissions for the auth file? Are Boinc and Boinc Manager able to read the auth file? Have you changed the password in the auth file?
In Windows, if it doesn't work - reinstall.
In Unix, if it doesn't work - investigate why (and profit from the pain) :-).
Good luck!
Cheers,
Gary.
RE: In Windows, if it
)
LOL. That's awesome Gary! Given the pains I've gone through to get to where I am now (/me sighs thinking about setting up a cron tab), I must be extremely rich.
Kathryn :o)
Einstein@Home Moderator
RE: .... I must be
)
When I remember the first posts I ever saw from you and when I look at how skilled you are now, I think you must be very rich indeed! :-).
Cheers,
Gary.
RE: RE: .... I must be
)
I just looked at my very first post here. Wow. It's a nice reminder of just how far I've come.
Kathryn :o)
Einstein@Home Moderator
RE: RE: It Just Doesn't
)
Actually, uninstalling it and reinstalling it according to the instructions pointed to above worked fine. That is, until I rebooted and it didn't restart. Got it running again, and we'll see what happens in the future. Thanx, everybody, for all your help and the pointers you gave me.
BTW, Gary Roberts, the reason I decided to reinstall was that I figured I'd probably done it wrong the first time, and as it turns out, I was more-or-less right.
RE: Actually, uninstalling
)
This situation continued until I installed a graphics card with enough RAM to change from Metacity to Compiz. Now, It Just Works, and a few other odd start-up issues have Gone Away. Weird.