Recent Posts

1

Questions / Re: Can't connect to BOINC client

« Last post by JStateson on March 21, 2020, 04:24:06 am »

Put the following into the cc_config.xml file at \programdata\boinc under "options"

<allow_remote_gui_rpc>1</allow_remote_gui_rpc>

suggest this:
<cc_config>
  <log_flags>
  </log_flags>
  <options>
   <use_all_gpus>1</use_all_gpus>
   <allow_remote_gui_rpc>1</allow_remote_gui_rpc>
  </options>
</cc_config>

double check your password file for white space or unprintable character.   If you delete the gui_rpc_auth.cfg file it is automatically re-created with a 32 char password when boinc starts up.  Best is to use notepad and delete the line and save an empty file.  Its length should be exactly "0" unless you want a password

2

Questions / Re: Can't connect to BOINC client

« Last post by Shin on March 19, 2020, 02:56:51 pm »

I tried the host-info command and got the IP, but even that doesn't work when trying to connect. When I do the host-info to a remote machine that doesn't output anything.
I can ping both IPs perfectly with instant responses. Both machines are Windows

And I have checked that only one BOINC client is running.

3

Questions / Re: Can't connect to BOINC client

« Last post by JStateson on March 19, 2020, 01:37:50 pm »

Windows or Linux client?

If Linux then at /etc/boinc-client you need to edit the file remote_hosts.cfg and add the name of the boinctasks system or its IP address.  This is not needed for windows.

If client is in windows make sure there is only one client running and that the manager is not running.  Use tasks manager to verify.  Make sure that each system can "ping" the other using system names else network problem.

From the system running the client, from an admin command prompt do the following:
c:\Program Files\boinc>boinccmd --get_host_info

do the same thing from system running boinctasks. I assume it is also running boinc (but not boincmgr)
c:\Program Files\boinc>boinccmd --host YOUR_REMOTE_SYSTEM --get_host_info

Installing boinctasks under windows should automatically ask to allow access through the firewall.

If each system can ping each other then try a telnet connection from the boinctasks system to the client

telnet YOUR_REMOTE_SYSTEM 31416

Pressing CTRL-C should generate an error message such as "<boinc_gui_rpc_reply>" plus other stuff.   If you do not see that message suspect firewall or network problem.  Use CTRL-] then "quit" to exit telnet.

HTH

4

Questions / Can't connect to BOINC client

« Last post by Shin on March 19, 2020, 11:50:26 am »

I can't seem to find or add my computer running BOINC using the "Find computer" or "Add computer" menus. I used the machine IP, password in gui_rpc_auth.cfg, and port 31416. But no luck, I've tried adding a TCP exception in the firewall but that doesn't seem to work either.

Any idea around this? Not sure if it's just me forgetting something. 

5

Questions / Re: Boinctasks stuck on "updating"

« Last post by hucker on March 11, 2020, 11:04:03 pm »

If the computers don't have a fixed IP set than you should use the MAC address and remove the IP address.
You should set up the remote computer in BOINC to allow a connections from any IP address.
In BoincTasks Setting, make sure the Expert tab shows Reconnect every xx seconds e.g. 120 and the Connection timeout e.g 120.

I've fixed it.  A faulty ethernet cable was causing some packets to be lost - I only spotted it by running a continuous ping between computers and swapping different cables in.  I didn't suspect a wiring problem before, since I can easily transfer terabytes of data using windows file sharing.  I assume this must be more robust than whatever method you're using.  Perhaps you should program Boinctasks to cater for the odd lost packet?

6

Questions / Re: Boinctasks stuck on "updating"

« Last post by hucker on March 09, 2020, 07:23:19 pm »

If the computers don't have a fixed IP set than you should use the MAC address and remove the IP address.
You should set up the remote computer in BOINC to allow a connections from any IP address.
In BoincTasks Setting, make sure the Expert tab shows Reconnect every xx seconds e.g. 120 and the Connection timeout e.g 120.

It's as good as fixed, they haven't changed IP since I bought them.  It's technically DHCP and COULD change, but doesn't.

If I run Efmer Boinc Toolbox on the remote computer, it has a tick against "allow remote (RPC) access for all computers" (and all the other 3 ticks) - is that good enough?  I don't have the toolbox running all the time, only when I need to create or fix a connection.  Should it run all the time?

My expert tab says reconnect every 30 seconds and timeout in 120.  Are there better numbers to use than those?

7

Questions / Re: Boinctasks stuck on "updating"

« Last post by fred on March 09, 2020, 03:29:53 pm »

If the computers don't have a fixed IP set than you should use the MAC address and remove the IP address.
You should set up the remote computer in BOINC to allow a connections from any IP address.
In BoincTasks Setting, make sure the Expert tab shows Reconnect every xx seconds e.g. 120 and the Connection timeout e.g 120.

8

Questions / Re: Boinctasks stuck on "updating"

« Last post by hucker on March 08, 2020, 06:36:42 pm »

Boinctasks seems to have a very flimsy connection, often requiring the toolbox to persuade communication to work.  Can't this be reprogrammed to function better?

BoincTasks relies on the BOINC client to communicate.
But what you are telling, something isn't right.
Do you use a fixed IP address, or a dynamic.
Doesn't the offending BOINC computer show anything in it's message log. It might be refusing the connection.

The problem seems to occur when one computer is a bit bogged down with something, either the one running Boinctasks (it did it last night when I was backing up the whole system to a slow hard disk with cloning software), or one of the ones it's monitoring.  Perhaps if it can't get a response in a certain timeframe due to the CPU being overloaded then it gets upset?  This usually results in a couple of the computers disappearing from the task list, or sometimes the whole thing stops responding.  Even right clicking on the tray icon for Boinctasks and clicking exit does nothing.

The IPs are handed out by the ISP router automatically by DHCP, but they always remain the same.  As far as I can remember, I gave Boinctasks the IP of each machine, so I don't think that's the problem.  Ipconfig on a machine shows they only have a 3 day lease, but they won't lose the IP even if switched off for longer, as the router cycles through new IPs first if more machines are connected.

Do you want me to turn on any specific debug logging?  I had a quick glance at the stdoutdae.txt on the computer that usually causes the problems because it's slowest, but I can't spot anything.  The stdoutdae.txt on this computer (the one running boinctasks) has no entries for the past few months!  I've deleted the file to see if it will start again.

9

Questions / Re: Boinctasks stuck on "updating"

« Last post by fred on March 08, 2020, 02:42:08 am »

Boinctasks seems to have a very flimsy connection, often requiring the toolbox to persuade communication to work.  Can't this be reprogrammed to function better?

BoincTasks relies on the BOINC client to communicate.
But what you are telling, something isn't right.
Do you use a fixed IP address, or a dynamic.
Doesn't the offending BOINC computer show anything in it's message log. It might be refusing the connection.

10

Questions / Re: Boinctasks stuck on "updating"

« Last post by hucker on February 26, 2020, 10:09:50 pm »

Ok, I now have the "offending" computer running perfectly.  But Boinctasks still sticks for no reason.  It's monitoring four computers: itself, and three others on a fast local network.  There is no reason for this sticking.  Why does it keep stopping responding?  There's spare CPU time on all computers, yet it just stops talking to the other machines for no reason.  Any other communication between the computers works fine, eg file transfers, remote desktop, etc.  Boinctasks seems to have a very flimsy connection, often requiring the toolbox to persuade communication to work.  Can't this be reprogrammed to function better?