• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Is there a multi-computer tracking for WCG like HFM.net is to F@H ??

Markfw

Markfw

Moderator Emeritus, Elite Member
Title says it all. Tired of logging into every box to make sure its still running.
 
Markfw said:
Title says it all. Tired of logging into every box to make sure its still running.
Click to expand...
Use BOINCTasks

Insert this into cc_config.xml

<allow_remote_gui_rpc>1</allow_remote_gui_rpc>

You get the password from gui_rpc_auth.cfg, insert that into password field in BoincTasks
 
Last edited:
well, that looks great, but it can't find the other computers, and I can't even specify the IP.
 
Markfw said:
well, that looks great, but it can't find the other computers, and I can't even specify the IP.
Click to expand...

That functionality is..... broken.
You'll need to hit, computer tab, so that it shows this:
gZ6bWKf.png


Then you'll go upto the menu and hit computer, and select add computer.
It'll do something like this, where you can now input its IP, and the password. The "computers" column is to input its name, it can be anything:
7Xezsts.png
 
Last edited:
Some additions to what Kiska said:

Kiska said:
Use BOINCTasks
Click to expand...

Though plain boincmgr can access remote nodes in the same way.

Kiska said:
Insert this into cc_config.xml

<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
Click to expand...

On Windows, the file path is C:\ProgramData\BOINC\cc_config.xml.

The allow...rpc tag goes into an options tag which goes into an cc_config tag:
Code: 
<cc_config>
    <options>
        <allow_remote_gui_rpc>1</allow_remote_gui_rpc>
    </options>
</cc_config>

Some more documentation on this file is available at https://boinc.berkeley.edu/wiki/client_configuration and https://boinc.mundayweb.com/wiki/index.php?title=Client_configuration.

Depending on what kind of changes were made to this file, it is either sufficient to use boincmgr's menu item "Options/ Read config files" to get the changes recognized, or you need to restart boinc. I guess enabling remote access belongs to the latter kind of changes. If in doubt, just restart boinc.

I suppose, an alternative to adding the allow...rpc tag to cc_config.xml is simply to start boinc with the option "--allow_remote_gui_rpc". This way looks to be common on Linux. On an openSUSE box, I have this option added to the ExecStart line in the boinc-client.service systemd file. On Gentoo boxes which I have not yet migrated to systemd, I set ALLOW_REMOTE_RPC="yes" in /etc/conf.d/boinc.

Kiska said:
You get the password from gui_rpc_auth.cfg, insert that into password field in BoincTasks
Click to expand...

Normally there is an autogenerated password in there. You can replace it with a password of your own choice.
 
Last edited:
OK, the directory does not exist. there is no xml file anywhere on the computer name cc_config.xml, and when I added a computer with a computer name, IP address and password, it just says "not connected" for status.

crashtech, teamviewer is not the answer I need, I need it on one screen, and I am not even running bionc on the computer I use to monitor the rest.

Not making much progress. BTW, using Windows 10
 
Hmm, https://boinc.berkeley.edu/wiki/BOINC_Data_directory does not tell where the BOINC data are located on Windows 10. I would assume it is the same as Windows 8 or 7. (I have 7.)

On my Windows PCs, C:\ProgramData is hidden. So one either needs to switch on the listing of hidden files in explorer, or type C:\ProgramData into explorer's location bar.

cc_config.xml does not exist by default, it needs to be created manually, e.g. by saving it from notepad into the BOINC data directory.

Oh, and the cc_config.xml file which you need to create, and the gui_rpc_auth.cfg file which contains the password, reside on the computer with the BOINC worker which is meant to be controlled. (As opposed to the computer which is going to run the GUI.)
 
ok, I created the cc_config.xml, and found the directory, and put it there. There is what appears to be an encoded password in the gui_rpc_auth.cfg file, so I did not mess with it, but I put the boinc password in the screen. Then I played around, and it said connecting, but then "not connected" was the result after about 10 seconds. Any ideas ??
 
Last edited:
That image came from the monitoring computer, but the file cc_config was done in the target computer that is running boinc.
 
Click out of the tab to force a restart of the internal client(as in, click another tab like tasks, and switch back), that should make it connected, also tick those checkboxes
 
I did that, and it says connecting, but after 10 seconds, it comes back with that I showed.
 
Markfw said:
There is what appears to be an encoded password in the gui_rpc_auth.cfg file, so I did not mess with it, but I put the boinc password in the screen.
Click to expand...

By default there should be a long hexadecimal string there - but this very string is the password in plaintext, not salted/ scrambled/ encrypted. If you want to keep this autogenerated password, make a copy of the file for viewing on the monitoring computer, then copy-and-paste it into the monitoring UI's password requester.

But as I said, it is easily possible to overwrite this initial password with your own, e.g. so that you have the same password on all of your BOINC workers. Then restart the worker, and connect from the monitoring computer using the new password.

It is even possible to make gui_rpc_auth.cfg an empty file, meaning no password needed for access.

Furthermore: If the BOINC worker has got a so-called "personal firewall" or "desktop firewall", or/ and if there are real firewalls between the monitoring PC and the worker, then all these firewalls must be configured to permit access to the worker's port 31416.

When I enabled remote access on my Windows workers and restarted BOINC on them, Windows 7 Professional popped up a requester asking whether to allow access of that application to private networks or/and public networks. I switched on access to private networks. Since this requester only came up (1.) at the very first run of BOINC right after installation and (2.) when I restarted BOINC after having added <allow_remote_gui_rpc>1</allow_remote_gui_rpc> in cc_config.xml, I figure that the requester at that (2.) occasion came up precisely because the BOINC client now began to listen at this port 31416.
 
OK, windows 10 firewall. I added a range that allows access if a private network (workgroup is private I think) 192.168.1.1 to 192.168.1.100. Then retried, and it still doesn;t work when I reconnect. Does windows have to be restarted for the rule to work ?
 
Markfw said:
OK, windows 10 firewall. I added a range that allows access if a private network (workgroup is private I think) 192.168.1.1 to 192.168.1.100. Then retried, and it still doesn;t work when I reconnect. Does windows have to be restarted for the rule to work ?
Click to expand...

Lets troubleshoot this by turning off your firewall completely, though I think its not a firewall issue.

Here is my cc_config.xml if you want to compare (ignore the log flags):
Code: 
<cc_config>
    <log_flags>
        <file_xfer>1</file_xfer>
        <sched_ops>1</sched_ops>
        <task>1</task>
        <android_debug>0</android_debug>
        <app_msg_receive>0</app_msg_receive>
        <app_msg_send>0</app_msg_send>
        <async_file_debug>0</async_file_debug>
        <benchmark_debug>0</benchmark_debug>
        <checkpoint_debug>0</checkpoint_debug>
        <coproc_debug>0</coproc_debug>
        <cpu_sched>0</cpu_sched>
        <cpu_sched_debug>0</cpu_sched_debug>
        <cpu_sched_status>0</cpu_sched_status>
        <dcf_debug>0</dcf_debug>
        <disk_usage_debug>0</disk_usage_debug>
        <file_xfer_debug>0</file_xfer_debug>
        <gui_rpc_debug>0</gui_rpc_debug>
        <heartbeat_debug>0</heartbeat_debug>
        <http_debug>0</http_debug>
        <http_xfer_debug>0</http_xfer_debug>
        <mem_usage_debug>0</mem_usage_debug>
        <network_status_debug>0</network_status_debug>
        <notice_debug>0</notice_debug>
        <poll_debug>0</poll_debug>
        <priority_debug>0</priority_debug>
        <proxy_debug>0</proxy_debug>
        <rr_simulation>0</rr_simulation>
        <rrsim_detail>0</rrsim_detail>
        <sched_op_debug>0</sched_op_debug>
        <scrsave_debug>0</scrsave_debug>
        <slot_debug>0</slot_debug>
        <state_debug>0</state_debug>
        <statefile_debug>0</statefile_debug>
        <suspend_debug>0</suspend_debug>
        <task_debug>1</task_debug>
        <time_debug>0</time_debug>
        <trickle_debug>0</trickle_debug>
        <unparsed_xml>1</unparsed_xml>
        <work_fetch_debug>0</work_fetch_debug>
    </log_flags>
    <options>
        <abort_jobs_on_exit>0</abort_jobs_on_exit>
        <allow_multiple_clients>1</allow_multiple_clients>
        <allow_remote_gui_rpc>1</allow_remote_gui_rpc>
        <client_version_check_url>http://boinc.berkeley.edu/download.php?xml=1</client_version_check_url>
        <client_new_version_text></client_new_version_text>
        <client_download_url>http://boinc.berkeley.edu/download.php</client_download_url>
        <disallow_attach>0</disallow_attach>
        <dont_check_file_sizes>0</dont_check_file_sizes>
        <dont_contact_ref_site>0</dont_contact_ref_site>
        <lower_client_priority>0</lower_client_priority>
        <dont_suspend_nci>0</dont_suspend_nci>
        <dont_use_vbox>0</dont_use_vbox>
        <exit_after_finish>0</exit_after_finish>
        <exclusive_app>factorio</exclusive_app>
        <exit_before_start>0</exit_before_start>
        <exit_when_idle>0</exit_when_idle>
        <fetch_minimal_work>0</fetch_minimal_work>
        <fetch_on_update>0</fetch_on_update>
        <force_auth>default</force_auth>
        <http_1_0>0</http_1_0>
        <http_transfer_timeout>300</http_transfer_timeout>
        <http_transfer_timeout_bps>10</http_transfer_timeout_bps>
        <max_event_log_lines>2000</max_event_log_lines>
        <max_file_xfers>8</max_file_xfers>
        <max_file_xfers_per_project>5</max_file_xfers_per_project>
        <max_stderr_file_size>0</max_stderr_file_size>
        <max_stdout_file_size>0</max_stdout_file_size>
        <max_tasks_reported>0</max_tasks_reported>
        <ncpus>-1</ncpus>
        <network_test_url>http://www.google.com/</network_test_url>
        <no_alt_platform>0</no_alt_platform>
        <no_gpus>0</no_gpus>
        <no_info_fetch>0</no_info_fetch>
        <no_priority_change>0</no_priority_change>
        <os_random_only>0</os_random_only>
        <process_priority>2</process_priority>
        <process_priority_special>2</process_priority_special>
<proxy_info>
    <socks_server_name></socks_server_name>
    <socks_server_port>80</socks_server_port>
    <http_server_name></http_server_name>
    <http_server_port>80</http_server_port>
    <socks5_user_name></socks5_user_name>
    <socks5_user_passwd></socks5_user_passwd>
    <http_user_name></http_user_name>
    <http_user_passwd></http_user_passwd>
    <no_proxy></no_proxy>
</proxy_info>
        <rec_half_life_days>10.000000</rec_half_life_days>
        <report_results_immediately>1</report_results_immediately>
        <run_apps_manually>0</run_apps_manually>
        <save_stats_days>30</save_stats_days>
        <skip_cpu_benchmarks>0</skip_cpu_benchmarks>
        <simple_gui_only>0</simple_gui_only>
        <start_delay>0.000000</start_delay>
        <stderr_head>0</stderr_head>
        <suppress_net_info>0</suppress_net_info>
        <unsigned_apps_ok>0</unsigned_apps_ok>
        <use_all_gpus>0</use_all_gpus>
        <use_certs>0</use_certs>
        <use_certs_only>0</use_certs_only>
        <vbox_window>0</vbox_window>
    </options>
</cc_config>

A step we can try with the firewall is:

Open Windows firewall with Advanced Security:
Go to inbound rules, add New Rule OR you could look for BOINC client in the list, and see if Actions is set to "Allow the connection"
In program, use this: %ProgramFiles%\BOINC\boinc.exe or wherever boinc.exe is
Actions leave as default, leave profile as default, call it whatever you want it. And the firewall should be updated
 
Last edited:
I turned off the firewall, no change. Do you have to reboot a computer for the firewall status to be effected ?
 
If remote access is the only thing you need to address at this point, then you can leave cc_config.xml as short as shown further up in this tread, i.e. just with <cc_config><options><allow_remote_gui_rpc>1</allow_remote_gui_rpc></options></cc_config> and nothing more.

If there is a syntax error in cc_config.xml, boincmgr on the worker PC should show a complaint in he "Notices" tab when starting up, and in Tools/ Event log too.

I have seen posts in other forums in which users report that they had to whitelist the BOINC data directory in their virus scanner. Otherwise strange malfunctions happened, among them inability to access a BOINC worker remotely.

Windows Firewall needs to have a permissive Inbound rule for BOINC on the worker PC (or two rules, for TCP and UDP?), whereas it looks to me like no intervention to Windows Firewall is necessary on the monitoring PC.

Not sure about the necessity of a reboot to drive home any changes to the firewall. If Windows shows that the Firewall is no longer active, then I would think it truly isn't.
 
If you have BOINC also installed on the monitoring PC (but not necessarily running there), you can try this at the command line:

"%PROGRAMFILES%\BOINC\boinccmd" --host 192.168.0.24 --passwd my-nifty-pw --get_cc_status

If BOINC is not running on the host, the command will hang until you hit Ctrl-C.
Ditto if BOINC on that host is running but configured to disallow remote access.
If you got the password wrong, the command returns "Authorization failure: -155".

If everything was set up right, you will get a response like this:

network connection status: online
CPU status
not suspended
current mode: according to prefs
perm mode: according to prefs
perm becomes current in 0 sec​
GPU status
not suspended
current mode: according to prefs
perm mode: according to prefs
perm becomes current in 0 sec​
Network status
not suspended
current mode: according to prefs
perm mode: according to prefs
perm becomes current in 0 sec​

If that went well, try
"%PROGRAMFILES%\BOINC\boinccmd" --host 192.168.0.24 --passwd my-nifty-pw --get_state

This should give a huge output about all configured projects, running tasks, and more.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top