Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 15
|
![]() |
Author |
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 611 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() |
I think it does apply. That is how I was able to connect to my Ubuntu using a password.
The <gui_rpc_password></gui_rpc_password> is on the Linux box in the gui_rpc_auth.cfg where you put in an "a" as password. Did you try that? Can't hurt. it's a 5 second change. |
||
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 837 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Weird, I tried that. Then nothing. So I did sudo systemctl stop boinc-client then sudo systemctl start boinc-client to start the service.
----------------------------------------I then got something like "Invalid RPC password. Try reinstalling BOINC." I decided to restart the Linux box. Now I can't even connect to the target Linux machine from Windows. No error message or anything -- just unresponsiveness. I'm gonna uninstall and install 7.14.2. Good freaking riddance, BOINC developers. Edit: Successful downgrade on both boxes back to 7.14.2 from the debian buster-stable repository. I'll just stick with this for now instead of fussing with the 7.16 branch.
[Edit 1 times, last edit by hchc at Sep 29, 2020 4:04:59 AM] |
||
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 611 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() |
I tried this stuff over again and could not reproduce what I said about wrapping the password with <gui_rpc_password></gui_rpc_password> so I am out of ideas. The Linux client I was testing with is 7.9.3 and since I have things working the way I want them I am not motivated to do any playing around until I need to.
----------------------------------------My windows client is 7.14.3 I think you have the best idea: go back to what works... and now I know how to restart the service without booting -> sudo systemctl start boinc-client Did not know that. Am not a Linux guy but can tinker with it. [Edit 1 times, last edit by BobbyB at Sep 29, 2020 5:58:32 AM] |
||
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 837 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I'm a beginner as well.
----------------------------------------I think there's also: sudo service boinc-client restartor sudo service boinc-client stopor sudo systemctl stop boinc-client
[Edit 1 times, last edit by hchc at Sep 29, 2020 9:10:37 AM] |
||
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 611 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() |
I'm still going to try the lastest Berkley BOINC client (on another old laptop) for the 1 Windows cruncher I have because it is 64 bit but not if it enforces passwords.
----------------------------------------29-Sep-2020 15:06 UTC-4 It seems to enforce passwords, it does not create the cc_config.xml and other files plus a few more things. Not worth the time to play with it. Flushed! [Edit 1 times, last edit by BobbyB at Sep 29, 2020 7:10:11 PM] |
||
|
|
![]() |