Boinc Manager -> Boinc Client: "connection failed" (4.30/4.32)

Questions and Answers : Unix/Linux : Boinc Manager -> Boinc Client: "connection failed" (4.30/4.32)
Message board moderation

To post messages, you must log in.

AuthorMessage
NimdaCinatas
Volunteer tester

Send message
Joined: 26 Oct 99
Posts: 4
Credit: 14,281
RAC: 0
Germany
Message 99050 - Posted: 15 Apr 2005, 7:51:06 UTC

Hi Folks,

I'm crunching for several projects since January with different client versions (downloaded or self compiled).

Few days ago I downloaded dev client 4.30 for windows for testing - and love the statistics tab!

Trying to run same version (download version) on Linux raised an error when starting boincmgr: connection to client running on localhost failed.

Same problem comes with cvs version (4.32, 2005-04-14).

OK, these are dev versions and are not said to be stable but maybe I'm only lacking of some config changes which should be made in client_state.xml or somewhere else...

If you've an advise what could be the problem I#d be pleased to here from you.

For the moment I reverted to custom build 4.23 which runs fine. But unfortunately without statistics tab :-(

Thanx in advance,
Marcel


BTW: I'm running boinc client first and boincmgr second so it should work!?
ID: 99050 · Report as offensive
Profile Tigher
Volunteer tester

Send message
Joined: 18 Mar 04
Posts: 1547
Credit: 760,577
RAC: 0
United Kingdom
Message 99249 - Posted: 15 Apr 2005, 17:49:26 UTC

Hi. This might help....really not sure. Have you set up the remote_hosts.cfg file?


ID: 99249 · Report as offensive
NimdaCinatas
Volunteer tester

Send message
Joined: 26 Oct 99
Posts: 4
Credit: 14,281
RAC: 0
Germany
Message 100706 - Posted: 18 Apr 2005, 5:16:48 UTC - in response to Message 99249.  

Hi Ian.

Thanks for your advice.

I already used the client option "allow_remote_gui_rpc" so this should not change anything but I tried it anyway.

Creating the file "remote_hosts.cfg" with following content did not give the wanted:

#------------------------
127.0.0.1
localhost
localhost.localdomain
#------------------------

Reading through checkin_notes (cvs of 04-14) gave another file "remote_hosts" (w/o cfg-ending) so I tried to symlink the cfg-file but again no error change.

I'll try another - newer - cvs version (or maybe the new 4.32 download file) and post my experience here.

So long,
Marcel
ID: 100706 · Report as offensive
NimdaCinatas
Volunteer tester

Send message
Joined: 26 Oct 99
Posts: 4
Credit: 14,281
RAC: 0
Germany
Message 100710 - Posted: 18 Apr 2005, 5:23:54 UTC - in response to Message 100706.  

To Ian and all others:

I downloaded the new 4.32 Client/Manager package and this one works fine for me.
ID: 100710 · Report as offensive
Profile HotblackDesiato
Avatar

Send message
Joined: 7 May 05
Posts: 4
Credit: 16,748
RAC: 0
Germany
Message 110366 - Posted: 12 May 2005, 5:44:41 UTC - in response to Message 99249.  

<blockquote>Hi. This might help....really not sure. Have you set up the remote_hosts.cfg file?
</blockquote>

Here the same problem (Debian GNU/Linux sid). I have created the remote_hosts.cfg, but to no avail. "Connection failed" (version 4.32).

Stefan
ID: 110366 · Report as offensive
NimdaCinatas
Volunteer tester

Send message
Joined: 26 Oct 99
Posts: 4
Credit: 14,281
RAC: 0
Germany
Message 110381 - Posted: 12 May 2005, 6:06:26 UTC - in response to Message 110366.  

<blockquote>Here the same problem (Debian GNU/Linux sid). I have created the remote_hosts.cfg, but to no avail. "Connection failed" (version 4.32).</blockquote>

Hi Stefan,

are you sure you've started boinc client app before trying to start boingmgr? As you see I had the same problem with 4.30 and it's solved for me since 4.32.

Another possible chance is using console parameter "-allow_remote_gui_rpc" when starting boinc client (not manager).

I'm using a mix of Debian sarge + sid.

Marcel
ID: 110381 · Report as offensive
Profile HotblackDesiato
Avatar

Send message
Joined: 7 May 05
Posts: 4
Credit: 16,748
RAC: 0
Germany
Message 111712 - Posted: 16 May 2005, 15:25:29 UTC - in response to Message 110381.  

<blockquote>Here the same problem (Debian GNU/Linux sid). I have created the remote_hosts.cfg, but to no avail. "Connection failed" (version 4.32).</blockquote>

Hi Stefan,

are you sure you've started boinc client app before trying to start boingmgr? As you see I had the same problem with 4.30 and it's solved for me since 4.32.

Another possible chance is using console parameter "-allow_remote_gui_rpc" when starting boinc client (not manager).

I'm using a mix of Debian sarge + sid.

Marcel


Hi Marcel,

I start my boing client with the following cron job at startup, so it is always running when I try boincmgr:

# use /bin/sh to run commands, no matter what /etc/passwd says
SHELL=/bin/sh
# setiathome
@reboot cd /home/stefan/setiathome; ./boinc >/dev/null 2>/dev/null


I also tried the option "-allow_remote_gui_rpc" but I still get the "connection failed" error.

Any further ideas ?

Stefan
ID: 111712 · Report as offensive
Profile HotblackDesiato
Avatar

Send message
Joined: 7 May 05
Posts: 4
Credit: 16,748
RAC: 0
Germany
Message 111804 - Posted: 16 May 2005, 20:41:59 UTC

Hi Marcel,

version 4.41 works !

But it was a long and stony way... It needs the WxWidgets version >=2.6.0 to compile the GUI and the latest Debian packages are 2.4.x ... So first I compiled and installed the WxWindows libraries and then compiled Boinc 4.41.

The resulting boinc_gui (boincmgr) is a 29MB executable !!! But it instantly connected to the boinc client. Unfortunately it is not very stable...


Stefan
ID: 111804 · Report as offensive
Profile HotblackDesiato
Avatar

Send message
Joined: 7 May 05
Posts: 4
Credit: 16,748
RAC: 0
Germany
Message 111831 - Posted: 16 May 2005, 21:55:25 UTC

Hi Marcel,

I just compiled the current development version 4.68. boinc_gui'sm file size is 7 MB. Both client and GUI seem to work well.

Stefan
ID: 111831 · Report as offensive

Questions and Answers : Unix/Linux : Boinc Manager -> Boinc Client: "connection failed" (4.30/4.32)


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.