New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boinc manager can't connect to client using "localhost" #1306
Comments
Tested on Windows 8.1, boinc version 7.6.69. |
Same error happened to me with boinc-manager 7.0.27 (from repos) on raspian from linux remote server. |
Confirming on Fedora 24, BOINC 7.6.22 |
Works with 7.6.33 on Debian. So it might be something Fedora (CentOS) specific. What happens if you don't enter a hostname. For me this defaults to "localhost". In the past the "could not connect to client" errors on CentOS systems could be tracked down to permission problems where the Manager couldn't access the gui_rpc_auth file. Maybe this is something along this way but where the manager can't resolve 'localhost' to '127.0.0.1'. Maybe the wrong IP is resolved. I would need to look up how the manager does the lookup. My guess is that this is done by curl. |
@ChristianBeer if I do not enter a username, the result is that BOINC manager remains not connected to any BOINC client. |
I guess you mean hostname. I have the feeling that somehow the Manager can not resolve Line 171 in 5c36ce2
You should check your /etc/hosts file on Fedora and see if there is a line that maps |
|
Strange, I guess I have to setup a Fedora 24 VM to reproduce the problem and try to debug it some more. Did you use a standard setup or something more fancy? |
I see essentially the same behavior on a couple of Gentoo systems from |
@Ferroin You mean that boinccmd also can't connect to |
Ah, I missed the part about connecting via IP working. That doesn't work in my case, so I'll do some more digging and probably open another issue under the assumption that it's an unrelated bug. |
The Client and Manager are communicating via TCP so there is always a possibility that a firewall is restricting access to the port the Client uses even on the loopback interface. |
|
I installed the FC25 live CD in a VM with default settings. This is what I had to do to get a running client:
What I see now is that
it works. So the problem on Fedora is that the normal User does not have access to the file in I'm not entirely sure how this ties in with the whole "localhost" thing above. I tried the following things and they work too:
Solutions:
Addendum: later discussion in this issue was about
Here is what does not work:
The parameters for
|
Hi @ChristianBeer , I did some tries with |
I did some tests. I tried to
So the problem is only with |
Can you try to reproduce my working test cases with boinccmd from above on the system that does not work?
All three should trigger a reread of local configuration files which is visible in the Client logfile. Your Client should have a problem with the one on the middle. |
I am sorry I have forgotten to write a part of my previous message:
returns |
That means the supplied password is wrong. Did you check that the password you used was the same as in gui_rpc_auth.cfg on this machine? Sometimes there can be a stray blank at the end of the line. |
|
Did you changed the password without restarting boinc? |
Mmh yes I changed the password without restarting boinc.
|
So it works and the problem was that the Client was not restarted? That would close this ticket I presume? |
boinc manager still does not work, only boinccmd works |
I just started my Fedora 25 VM and tried this in a terminal:
Which both works (opens the simple GUI Manager and asks me to add a project). Next try:
which works if I make For the next try I chdir into the Client directory and execute:
which works because This proves that boincmgr by itself works as expected. I now applied your change to |
After some more fiddling I was able to reproduce it finally. The sequence is as follows:
When I do the same but make |
It would be interesting to check if it is reproducible also on other Linux distributions |
Yes, I could reproduce it on Debian (the bug is present on all platforms). I tracked it down to the Select dialog and I'm working on a fix. So far no luck but I'm getting close. |
The hostname "localhost" was recognized as a special name which always prompted the Manager to try to read contents of gui_rpc_auth.cfg. The Manager used an empty password if the file is not readable but then can't connect because the Client actually uses a password. Any user supplied password was overwritten which made the dialog not work when using "localhost" but work when used with "127.0.0.1". Now the dialog checks if the user has entered an empty password which prompts reading gui_rpc_auth.cfg and uses the user supplied password otherwise. Fixes #1306
@Germano0 could you please check my fix on your system? |
@ChristianBeer I should test the fix in next 7 days |
@ChristianBeer I have just packaged and installed master branch. ===== EMPTY /var/lib/boinc/gui_rpc_auth.cfg === ===== /var/lib/boinc/gui_rpc_auth.cfg filled with a password === |
With an empty gui_rpc_auth.cfg the connection should always work. I just tried it again with the current master and I can connect using Keep in mind that you need to restart the client if you change the content of gui_rpc_auth.cfg and that you really have an empty file (some editors add a newline at the end). I can also connect if I enter |
No, the problem is still the same on BOINC 7.9.2 |
For anyone that still has a problem with this, like I did just a little bit ago, I would recommend doing "ln -ld /var/lib/boinc*" to see if the /var/lib/boinc and /var/lib/boinc-client are both there with the /var/lib/boinc being a symbolic link to /var/lib/boinc-client and that both of them are owned by boinc and can be read by the user. I would also recommend checking to see if /home/username/got populated with a bunch of things that should be in there. This can happen if boinc can not access the folder for whatever reason. With both /var/lib/boinc and /var/lib/boinc-client set up the way they should be and the contents of /var/lib/boinc-client all being group boinc and owned by boinc, the chances of things working right are much better. If you decide to use a different data directory, you need to have /var/lib/boinc-client exist as a symbolic link to point to wherever you keep the boinc data. You may need to "sudo chmod g+r gui_rpc_auth.cfg" as well. |
Reported by saldsl on 10 Sep 44020772 12:41 UTC
Tested on Fedora 19 x86_64 (with RPMs from repository), boinc version 7.2.33.
Without linking the gui_rpc_auth.cfg file to my home directory, when I select Advanced -> Select Computer and I type "localhost" as target and put the password Boinc Manager can't connect to client. If I type "127.0.0.1" it connects.
This happens only with 7.2.33, if I downgrade boinc to 7.0.65 "localhost" works, so I don't think to a firewall/hostnames configuration problem.
[https://bugzilla.redhat.com/show_bug.cgi?id=1048545]
Migrated-From: http://boinc.berkeley.edu/trac/ticket/1335
The text was updated successfully, but these errors were encountered: