I've just done a software upgrade from Fedora 14 to Fedora 16 and have finally managed to get BOINC working again, but I have just one last niggle.

When I used to start the BOINC_Manager on Fedora 14 it would automatically connect to my client and show my tasks etc.

Now I have to log in as root, dump that password out of /var/lib/boinc/g* and paste it into the "Select Computer" dialogue.

There was some way of connecting automagically, I can't believe this feature has been written out, so what is the secret again please ?

BTW This is BOINC 6.12.35, and I preferred the old manager where it was possible to see the log in the GUI

Nothing been written out. Could be the properties and permission of the gui_rpc_auth.cfg file.

One fix is the remove the password or edit it to something you remember, then restart the core client. All my clients have the same pw, so there's little to remember for local or remote connection.

--//--

Thanks for the reply. I have a symbolic link to /var/lib/boinc/gui_rpc_auth.cfg in my home directory, seems to make no difference

But things are going from bad to worse here. I cannot get the gui to connect to the client at all now. Sometimes it says "connecting to local host" quickly followed by Disconnected, and other times it just stays stuck on Disconnected.

I'm wondering if I should just cut my losses, delete the whole package and data directories and start again,

The client is ticking away doing work, just seems a shame to loose it all.

If the core client is ticking, I'd just run the installer again from the repository [right click to select reinstall or similar]. In Ubuntu that sure would set all the permissions straight.

It's interesting how different Linux versions put files in different places. On Ubuntu all the datadir files go to /var/lib/boinc-client/ and the gui_rpc_auth.cfg + 3 more go to /etc/boinc-client/ and are the once you can edit. These are symlinked in /var/lib/boinc-client

According this wiki page http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Fedora , the firewall is by default on in Fedora. Maybe port 31416 over localhost gets blocked for the RPC calls.

--//--

Thanks for the reply, but it seems that the Fedora distribution is buggy.

See https://bugzilla.redhat.com/show_bug.cgi?id=768402

I tried downloading 6.12.34 off http://boinc.berkeley.edu/download.php, but that doesn't run because it's built against lots of libraries not in RedHat Fedora 16

I think I'll just leave the client ticking away, and talk to it via the command line interface if I need to.

you could also install wine and then boinctasks and use that as your boinc manager.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

Thanks for the reply.

I can read /home/mike/gui_rpc_auth.cfg which is a symbolic link to the real one.
I can control boinc-client with boinccmd.

No messages are appearing in /var/log/boincerr.log
I'm getting a full log in /var/log/boinc.log

So, OK I thought I'll just start the boinc-manager up one last time to see if there is some way of getting debugging messages out of it, and guess what ? It started OK !!

I have no idea what is going on there. The only thing I can think off is that while I've been controlling it with boinccmd I've downloaded some more work-units, and boinccmd may have tweaked something, privs or Selinux stuff

The only thing I used boinccmd for was to allowmorework on Seti, and to resume a task on climateprediction.

I'm leaving well alone now it's working.

The only thing I can think off is that while I've been controlling it with boinccmd I've downloaded some more work-units, and boinccmd may have tweaked something, privs or Selinux stuff

Boinccmd uses the same port (TCP 31416) as both the Boinc an Boinc Manager binaries do. I'm not totally sure you can use Boinc Manager and Boinccmd at the same time, since usually only one program can use the port. Anyone want to test?

---

Anyone want to test?

I often use boinccmd while the manager is running. So, at least with 5.10.45, there should be no concurrency problem.

Gruß,
Gundolf

I just tested and it works without a problem. However, I also have just about everything BOINC wise enabled through my Windows firewall. So it could be tainted.

---