| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Cannot manage remote client from BOINC Manager after upgrading remote client to 7.16.15 [Linux] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 802 Status: Offline Project Badges: 
|
Remote client: Debian 10
----------------------------------------Upgraded the boinc-client package from 7.14.2 (buster stable) to (7.16.15+dfsg.is.7.16.11+dfsg-1~bpo10+1) (buster backports) According to pull request Client: don't allow empty GUI RPC password #3709, empty passwords are no longer allowed, which is what I was doing, since at this time BOINC Manager does not save passwords for remote clients. In other words, it would be a pain in the rear to manually set strong passwords for each remote host and have to remember them. I like how the BOINC Manager auto-populates the local password, but it's unable to auto-populate remote passwords at this time. Hence why I am using a blank password on all remote Linux boxes in gui_rpc_auth.cfg I've since set both /etc/boinc-client/gui_rpc_auth.cfg and /var/lib/boinc-client/gui_rpc_auth.cfg from a blank newline to having a simple password, but I'm now no longer able to connect to these clients at all from my Windows primary machine's BOINC Manager. What am I doing wrong? Below are the contents and permissions for each directory. /etc/boinc-client/ drwxr-xr-x 2 boinc boinc 4096 Sep 27 10:56 . drwxr-xr-x 70 root root 4096 Sep 27 11:47 .. -rw-rw-r-- 1 boinc boinc 4347 Sep 27 10:26 cc_config.xml -rw-rw-r-- 1 boinc boinc 1502 Sep 27 11:20 global_prefs_override.xml -rw-r----- 1 boinc boinc 2 Sep 27 11:16 gui_rpc_auth.cfg -rw-r--r-- 1 boinc boinc 309 Jul 11 19:41 remote_hosts.cfg /var/lib/boinc-client/ drwxr-x--- 5 boinc boinc 4096 Sep 27 11:54 . drwxr-xr-x 26 root root 4096 Sep 27 10:51 .. -rw-r--r-- 1 boinc boinc 3003 Sep 27 11:54 account_www.worldcommunitygrid.org.xml -rw-r--r-- 1 boinc boinc 51891 Sep 27 10:11 all_projects_list.xml lrwxrwxrwx 1 boinc boinc 34 Oct 16 2019 ca-bundle.crt -> /etc/ssl/certs/ca-certificates.crt lrwxrwxrwx 1 boinc boinc 31 Sep 27 10:51 cc_config.xml -> /etc/boinc-client/cc_config.xml -rw-r--r-- 1 boinc boinc 584961 Sep 27 11:49 client_state_prev.xml -rw-r--r-- 1 boinc boinc 584962 Sep 27 11:54 client_state.xml -rw-r--r-- 1 boinc boinc 325 Sep 27 11:47 coproc_info.xml -rw-r--r-- 1 boinc boinc 30946 Sep 27 11:54 daily_xfer_history.xml -rw-r--r-- 1 boinc boinc 9074 Sep 1 13:40 get_current_version.xml -rw-r--r-- 1 boinc boinc 1371 Oct 16 2019 get_project_config.xml lrwxrwxrwx 1 boinc boinc 43 Sep 27 10:51 global_prefs_override.xml -> /etc/boinc-client/global_prefs_override.xml -rw-r--r-- 1 boinc boinc 1372 Mar 8 2020 global_prefs.xml lrwxrwxrwx 1 boinc boinc 34 Sep 27 10:51 gui_rpc_auth.cfg -> /etc/boinc-client/gui_rpc_auth.cfg -rw-r--r-- 1 boinc boinc 505032 Sep 27 09:59 job_log_www.worldcommunitygrid.org.txt -rw-r--r-- 1 boinc boinc 0 Sep 27 11:47 lockfile -rw-r--r-- 1 boinc boinc 142 Oct 16 2019 lookup_account.xml -rw-r--r-- 1 boinc boinc 13108 Sep 27 11:48 lookup_website.html -rw-r--r-- 1 boinc boinc 26278 Oct 16 2019 master_www.worldcommunitygrid.org.xml drwxrwx--x 2 boinc boinc 4096 Sep 27 11:47 notices drwxrwx--x 3 boinc boinc 4096 Oct 16 2019 projects lrwxrwxrwx 1 boinc boinc 34 Sep 27 10:51 remote_hosts.cfg -> /etc/boinc-client/remote_hosts.cfg -rw-r--r-- 1 boinc boinc 16648 Sep 27 11:54 sched_reply_www.worldcommunitygrid.org.xml -rw-r--r-- 1 boinc boinc 31768 Sep 27 11:54 sched_request_www.worldcommunitygrid.org.xml drwxrwx--x 4 boinc boinc 4096 Sep 27 06:00 slots -rw-r--r-- 1 boinc boinc 9036 Sep 27 11:54 statistics_www.worldcommunitygrid.org.xml -rw-r--r-- 1 boinc boinc 1260 May 10 07:50 stderrgpudetect.txt -rw-r--r-- 1 boinc boinc 1008 May 10 07:50 stdoutgpudetect.txt -rw-r--r-- 1 boinc boinc 16426 Sep 27 11:47 time_stats_log
[Edit 2 times, last edit by hchc at Sep 27, 2020 4:15:34 PM] |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3295 Status: Offline Project Badges:
|
Can't really help but 7.16.15 seems to be a development version, could there be a bug?
----------------------------------------7.16.6 is the latest stable per the BOINC download page. AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 609 Status: Offline Project Badges: 
|
I'm doing this also: blank password. Using Ubuntu 7.16.6 client and using a Windows BOINC manager.
----------------------------------------So this is nice to know about "Client: don't allow empty GUI RPC password #3709" on the newer clients. I strongly disagree with their security rationale. Yes if you are in a company or other such similar environment (like at Berkley) and production machines are just crunching when they are idle and they are open to whomever and maybe from the WAN. They fail to consider home users doing just 24/7 crunching like me. It's my house, my machines, my network and nothing is open to the public. The user should be the final authority. I also subscribe to "if it ain't broke, don't fix it". Unless it comes to a point where this stuff doesn't work anymore because the client becomes obsolete I see no need to update except the OS. So what was the need to upgrade the client? [Edit 2 times, last edit by BobbyB at Sep 28, 2020 5:29:03 PM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 802 Status: Offline Project Badges:
|
I upgraded because I wanted some of the bugfixes since the 7.14 release.
----------------------------------------Anyways, this thread isn't about the rationale but more about helping me get back into my machines! I put a password of "a" now, so it's not blank. On one of my machines, the password worked for a few minutes, but when I rebooted, it stopped working. I did chown to re-do some of the permissions so it's "boinc boinc." What am I doing wrong? When I try to "Connect to computer" I don't even get an error message anymore. It just doesn't connect. I'm not sure if there's a bug log I can check on the Linux boxes somewhere. Help!
|
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 609 Status: Offline Project Badges:
|
There is a gui_rpc_debug in the logging options. Have you tried that to see what it does?
----------------------------------------I'm presuming you can use the Boinc manager on the Linux box. I just tried it. Produced lots of stuff. Not sure how useful. Turned if off. These look interesting: <boinc_gui_rpc_reply><cc_status> <network_status>2</network_status> <ams_password_error>0</ams_password_error> I started a thread on Aug 4, 2020 when I started to play with this. Might help. https://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=636621 [Edit 4 times, last edit by BobbyB at Sep 28, 2020 8:24:58 PM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 802 Status: Offline Project Badges:
|
The Linux box is headless, so it's just boinc-client installed. I can SSH into it though and look at any log files. Can you point out where maybe?
----------------------------------------
|
||
|
|
PMH_UK
Veteran Cruncher UK Joined: Apr 26, 2007 Post Count: 771 Status: Recently Active Project Badges: 
|
Have you changed remote_hosts to allow connection from other hosts on your network?
----------------------------------------Also consider using BOINCtasks to manage systems, it remembers passwords. Paul.
Paul.
|
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 609 Status: Offline Project Badges:
|
seems to be /var/log/syslog
That sure is not obvious. I'm on that Linux machine now |
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 609 Status: Offline Project Badges:
|
Here is what I can figure out. You are using the Windows Boinc Manager and I presume 7.14.3 AND I don't know how you allowed remote RPC.
----------------------------------------From my thread above I found 3 ways to do it. For any IP, either <allow_remote_gui_rpc>1</allow_remote_gui_rpc> in the options section of a cc_config.xml OR the command line switch --allow_remote_gui_rpc For a selective IP(s) an address(es) in remote_hosts.cfg. The docs from Aug 4 stated that either of the first options above ignore remote_hosts.cfg. I found this to be true then. I found that the Windows Boinc Manager wants the password wrapped with <gui_rpc_password></gui_rpc_password>. I looked into the Windows Boinc executable and found it there and it worked. It's dumb but that is what I found. When I try to "Connect to computer" I don't even get an error message anymore. It just doesn't connect This is what I saw also.[Edit 1 times, last edit by BobbyB at Sep 28, 2020 10:40:42 PM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 802 Status: Offline Project Badges:
|
On my Windows box I'm using BOINC 7.16.11 (latest release), since the WCG custom version quickly gets outdated and obsolete with both bug fixes and the occasional security fix. Plus, it's not compatible (I believe) with other BOINC projects.
----------------------------------------On my two headless Linux boxes, remote_hosts.cfg hasn't changed, and I have the Windows box's hostname in that file. This prevents the need from setting <allow_remote_gui_rpc> in cc_config on the Linux machines, which allows it from any device. I'm fine with remote_hosts.cfg -- it's just a one time setting. BobbyB said: I found that the Windows Boinc Manager wants the password wrapped with <gui_rpc_password></gui_rpc_password>. I looked into the Windows Boinc executable and found it there and it worked. It's dumb but that is what I found. I think this doesn't apply because I'm using my Windows box to connect to my two Linux boxes. I'll check the /var/log/syslog on the Linux boxes. Otherwise I'm going to uninstall boinc-client 7.16.15 and revert back to 7.14.2 from buster-stable repository. And hope that my device ID/host ID is preserved on those machines so WCG doesn't create duplicate devices.
|
||
|
|
|