boinccmd - can't connect

Message boards : Number crunching : boinccmd - can't connect
Message board moderation

To post messages, you must log in.

AuthorMessage
W3Perl Project Donor
Volunteer tester

Send message
Joined: 29 Apr 99
Posts: 189
Credit: 1,474,477,358
RAC: 1,946,389
France
Message 1904763 - Posted: 4 Dec 2017, 11:50:07 UTC

I would like to know if I'm the only one to have such problem trying to use boinc 7.8
with linux. I'm managing boinc start/stop from a shell script, launching command using
boinccmd but they all failed with "can't connect to <host>"
(eg : boinccmd --host <host>:<port> --passwd <passwd> --read_global_prefs_override)

Works fine with 7.2.47. Using boincmgr works fine also with 7.8
I suspect boinc rpc failure....
ID: 1904763 · Report as offensive
Profile tullio Project Donor
Volunteer moderator
Volunteer tester

Send message
Joined: 9 Apr 04
Posts: 6749
Credit: 1,983,484
RAC: 479
Italy
Message 1904764 - Posted: 4 Dec 2017, 12:17:54 UTC - in response to Message 1904763.  

I am using BOINC 7.8.3 on two Linux boxes. I start BOINC with the command ./boincmgr.
Tullio
ID: 1904764 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 12036
Credit: 120,054,040
RAC: 54,639
United Kingdom
Message 1904766 - Posted: 4 Dec 2017, 12:52:27 UTC - in response to Message 1904763.  

What steps have you taken to ensure that:

a) the BOINC client is actually running at the time you issue the boinccmd directives?
b) the user account launching the scripts/boinccmd directives is authorised to manage BOINC?
c) the host domain name is in a format suitable for BOINC?
ID: 1904766 · Report as offensive
W3Perl Project Donor
Volunteer tester

Send message
Joined: 29 Apr 99
Posts: 189
Credit: 1,474,477,358
RAC: 1,946,389
France
Message 1904768 - Posted: 4 Dec 2017, 14:08:37 UTC - in response to Message 1904766.  

What steps have you taken to ensure that:

a) the BOINC client is actually running at the time you issue the boinccmd directives?



both boinc/boinccmd/boincmgr/boincscr/switcher extracted from the same package.
So boinccmd and boinc always the same version number.
Works with 7.2.42/7.2.47 but fail using 7.8... so 'something' have changed.


b) the user account launching the scripts/boinccmd directives is authorised to manage BOINC?



boinc and boinccmd launched from the same userid on the same host.


c) the host domain name is in a format suitable for BOINC?


I don't use FQDN but hostname as required.
ID: 1904768 · Report as offensive
W3Perl Project Donor
Volunteer tester

Send message
Joined: 29 Apr 99
Posts: 189
Credit: 1,474,477,358
RAC: 1,946,389
France
Message 1904769 - Posted: 4 Dec 2017, 14:10:31 UTC - in response to Message 1904764.  

I am using BOINC 7.8.3 on two Linux boxes. I start BOINC with the command ./boincmgr.
Tullio


could you try to run the following command :
boinccmd --read_global_prefs_override
thanks
ID: 1904769 · Report as offensive
W3Perl Project Donor
Volunteer tester

Send message
Joined: 29 Apr 99
Posts: 189
Credit: 1,474,477,358
RAC: 1,946,389
France
Message 1904776 - Posted: 4 Dec 2017, 14:26:48 UTC - in response to Message 1904768.  

Adding BOINC/cc_config.xml
<cc_config>
<options>
<use_all_gpus>1</use_all_gpus>
<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
</options>
</cc_config>

solve the problem !
You need to allow access to the gui rpc even if you don't use it !
ID: 1904776 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 12036
Credit: 120,054,040
RAC: 54,639
United Kingdom
Message 1904802 - Posted: 4 Dec 2017, 16:31:44 UTC - in response to Message 1904776.  

You need to allow access to the gui rpc even if you don't use it !
Yes, all communications with the client are done by RPC - Manager, boinccmd, BoincTasks all use the same protocol.

It's conventionally known as GUI RPC, because that's the commonest usage (the Manager being the GUI in question). That also helps to distinguish the command RPC from the other set of RPC calls, to communicate with projects.
ID: 1904802 · Report as offensive

Message boards : Number crunching : boinccmd - can't connect


 
©2018 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.