[Bug 1895157] Re: Boinc cannot enable RPC access to start client or manager

ikesterhaney 1895157 at bugs.launchpad.net
Fri Sep 11 23:44:58 BST 2020


Some research unearthed a reason and possible solution -

This error happens when the user has no permission to use the RPC port number, or forgotten to allow it through the firewall.
Happens in combination with Gstate.init() failed, error code: -180

To set BOINC to use a specific port number, one different from the default 31316, do:
boinc --gui_rpc_port N, example given boinc --gui_rpc_port 37777, this starts the BOINC client with TCP port 37777.

If you don't want to use any GUI to check on this BOINC from a remote location, you can also start BOINC without any GUI RPC:
boinc --no_gui_rpc

Source -
https://boinc.mundayweb.com/wiki/index.php?title=GUI_RPC_bind_to_port_31416_failed:_98

-- 
You received this bug notification because you are a member of Debian
BOINC Maintainers, which is subscribed to boinc in Ubuntu.
https://bugs.launchpad.net/bugs/1895157

Title:
  Boinc cannot enable RPC access to start client or manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1895157/+subscriptions



More information about the pkg-boinc-devel mailing list