Message boards :
Number crunching :
boinccmd - can't connect
Message board moderation
Author | Message |
---|---|
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
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.... |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
I am using BOINC 7.8.3 on two Linux boxes. I start BOINC with the command ./boincmgr. Tullio |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
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? |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
What steps have you taken to ensure that: 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.
boinc and boinccmd launched from the same userid on the same host.
I don't use FQDN but hostname as required. |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
I am using BOINC 7.8.3 on two Linux boxes. I start BOINC with the command ./boincmgr. could you try to run the following command : boinccmd --read_global_prefs_override thanks |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
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 ! |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
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. |
©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.