OK - after 5 years running SETI on various platforms, I decided to install it on my linux machine. I could no longer find a SETI client - just this BOINC thing. I have followed the instructions and checked all the documentation I can find, but cannot find anything that answers this issue. When I run the BOINC manager it tries to connect to localhost then pops up a connection failed dialogue.

When I try to attach to a project it tells me I have no Internet connection (obviously untrue as I am on this web page posting this). I am running Novell Linux Desktop (based on SuSe).

Anyone got any ideas please?

---

It depends a little bit on the realease you are using. Basicly SETI@home with BOINC is splitted in several single programs, no longer one program as with the Classic release. This makes some differences and may create problems.

The BOINC Daemon "boinc" is managing all communication sheduling the work and must be startet. If it is not running BOINC Manager (the graphical userinterface) get a "Connect" error.

The communication between BOINC Daemon and BOINC Manager is done on port 1043 on localhost. If a firewall rule block it, BOINC Manager get a "Connect error".

The last releases of BOINC client software use a password to protect the communication between BOINC Daemon and BOINC Manager. This password is placed in file "gui_rpc_auth.cfg" in the BOINC install folder and if BOINC (what is the default) has created it for you, it looks like a long string of chars and numbers.

The programs search for this password file in the current directory when they start. If you change this gui password, you have to start all programms (Daemon, Manager or CLI) again. If you start one of the programs from a different directory, or don't restart one program this may give different used passwords and BOINC Manager get a "Connect" error.

---

Greetings from Bremen/Germany
Jens Seidler (TheBigJens)

I had the same experience with 5.2.6 version. Never with earlier versions (4.43).
With 5.2.7 boinc manager was first able to access the network.
But you need to start it from a root console (SU).
However, I reverted back to version 4.43 for the client stopped working for unknown reason after one day.
I also signaled a problem in COMMAND submenus. It is not possible to independently select working option and network option. There must be a problem there. Is it the only a cosmetic problem ?

Best regards,

Bernard,
f6bvp

Merci Bernard and Danke Jens

It was a rights issue - as soon as I ran the BOINC client as root it worked properly and created the password file as described by Jens and from then on the manager connected with no problems.

Now all I have to do is get BOINC installed instead of the classic seti client on all my other machines ;)

Cheers, DagBoy.

---