BOINC unable to connect to core client

log in

Advanced search

Message boards : Questions and problems : BOINC unable to connect to core client

Author Message
AT Hiker
Send message
Joined: 2 Jan 13
Posts: 12
Message 47015 - Posted: 2 Jan 2013, 22:18:22 UTC

Boinc says that the password provided is incorrect.

Where exactly is the password?

doggybob
Send message
Joined: 5 Dec 12
Posts: 42
Message 47016 - Posted: 2 Jan 2013, 23:11:38 UTC - in response to Message 47015.

The password is stored in the BOINC data directory in a file named gui_rpc_auth.cfg. BOINC client will create a random password and store it there if gui_rpc_auth.cfg is not present. You can open gui_rpc_auth.cfg in a text editor and change it to something shorter and easier to remember. Then restart BOINC client to force it read the new password (it reads it once at every startup and only once).

The name of the BOINC data directory is given near the top of the messages in the Event Log. The default on Windows is c:\programdata\boinc. On Linux its /var/lib/boinc-cient/ if installed by package manager, usually ~/BOINC/ if installled by Berkeley installer.

____________
"Windows" -- an American English word, meaning "A real operating system is too hard for me."

Claggy
Send message
Joined: 23 Apr 07
Posts: 894
Message 47017 - Posted: 2 Jan 2013, 23:21:04 UTC - in response to Message 47015.

You don't need to enter a password if you're only connecting to the localhost, so leave it blank,

Claggy

doggybob
Send message
Joined: 5 Dec 12
Posts: 42
Message 47020 - Posted: 3 Jan 2013, 0:15:35 UTC

A blank gui_rpc_auth.cfg creates security risks because then anybody can connect to your BOINC client, attach it to their project and make it run whatever application they want unless you've taken appropriate counter-measures. Have you done so? Do you want to spend time learning what you need to do? Or would you find it easier, less time consuming and more secure to just use a password? YMMV.

Tricking you into running their application is every hacker's dream. You can make it easy for them or you can make it hard, whatever creams yer twinky.

____________
"Windows" -- an American English word, meaning "A real operating system is too hard for me."

Claggy
Send message
Joined: 23 Apr 07
Posts: 894
Message 47021 - Posted: 3 Jan 2013, 0:29:39 UTC - in response to Message 47020.
Last modified: 3 Jan 2013, 0:30:35 UTC

A blank gui_rpc_auth.cfg creates security risks because then anybody can connect to your BOINC client, attach it to their project and make it run whatever application they want unless you've taken appropriate counter-measures. Have you done so? Do you want to spend time learning what you need to do? Or would you find it easier, less time consuming and more secure to just use a password? YMMV.

Tricking you into running their application is every hacker's dream. You can make it easy for them or you can make it hard, whatever creams yer twinky.

I didn't say that, you don't need to enter a password to connect to localhost, if you going to use Boinc Manager, BoincView, BoincTasks etc to connect to another host then yes you do need to enter the password from it's gui_rpc_auth.cfg

Claggy

doggybob
Send message
Joined: 5 Dec 12
Posts: 42
Message 47023 - Posted: 3 Jan 2013, 1:39:33 UTC - in response to Message 47021.

I misinterpreted your meaning, sorry. On the other hand your post was very open to misinterpretation. When you said "leave it blank" I though you meant leave gui_rpc_auth.cfg blank. You could have said "leave the password prompt blank" which would have made it perfectly clear what you meant.

The word "it" is always understood to refer to the last subject-noun referred to in the conversation which was gui_rpc_auth.cfg rather than the password prompt. Be very careful when using pronouns (it, them, they, that) instead of the nouns they stand for. They save typing but introduce ambiguity.

Now back to your advice to leave the password prompt blank... that doesn't always work for localhost. For example it fails when BOINC manager cannot find gui_rpc_auth.cfg. That can happen on Linux when gui_rpc_auth.cfg is not in the manager's current directory when the manager starts. In that case you must supply the password in the password prompt. There is a safeguard in the Linux version of the manager... if it cannot find gui_rpc_auth.cfg in the current directory it will look in user's home directory and if it finds gui_rpc_auth.cfg there it will use the password in it. So the smart thing to do on Linux is put a link to gui_rpc_auth.cfg in ~ (your home directory). That way no matter which directory you start the manager in it will always find the same gui_rpc_auth.cfg the client finds, the passwords will match and the manager will connect. Also put a link in the home directory of any other users who you wish to also be able to use manager to control client.

____________
"Windows" -- an American English word, meaning "A real operating system is too hard for me."

AT Hiker
Send message
Joined: 2 Jan 13
Posts: 12
Message 47027 - Posted: 3 Jan 2013, 4:31:34 UTC

I realize now that I did not ask the question correctly. I don't need the password, I need to know where to enter it.

I am assuming that since Boinc is saying the provided password is incorrect that there must be a place to enter it into Boinc.

If it matters, when Boinc didn't accept the password I was attempting to used Boinc in a separate identity on Win 7. Boinc works normally on the other identity.

And yes I have used Boinc on 2 different identities before and I told Boinc when I installed it to allow all users to use it.

doggybob
Send message
Joined: 5 Dec 12
Posts: 42
Message 47028 - Posted: 3 Jan 2013, 7:03:02 UTC - in response to Message 47027.

I realize now that I did not ask the question correctly. I don't need the password, I need to know where to enter it.

I am assuming that since Boinc is saying the provided password is incorrect that there must be a place to enter it into Boinc.

If it matters, when Boinc didn't accept the password I was attempting to used Boinc in a separate identity on Win 7. Boinc works normally on the other identity.

And yes I have used Boinc on 2 different identities before and I told Boinc when I installed it to allow all users to use it.


____________
"Windows" -- an American English word, meaning "A real operating system is too hard for me."

doggybob
Send message
Joined: 5 Dec 12
Posts: 42
Message 47029 - Posted: 3 Jan 2013, 7:03:35 UTC - in response to Message 47027.
Last modified: 3 Jan 2013, 7:04:35 UTC

I realize now that I did not ask the question correctly. I don't need the password, I need to know where to enter it.


Oh well that's easy. You type it in the box to the right of where it says "Password:".

No? You haven't seen a box with "Password:" to the left?

Then try this:

In BOINC manager's Advanced View click Advanced -> Select Computer. In the Host box type localhost or just leave it blank in which case it will assume you mean localhost and in the Password box type the password you find in gui_rpc_auth.cfg.

Yes I know, it's like I can read your mind isn't it. ;)
____________
"Windows" -- an American English word, meaning "A real operating system is too hard for me."

AT Hiker
Send message
Joined: 2 Jan 13
Posts: 12
Message 47035 - Posted: 3 Jan 2013, 20:08:27 UTC


Today, more specifically this afternoon, BOINC suddenly resolved the issue all on its own. Go figure.

dfbv
Send message
Joined: 3 Jan 13
Posts: 1
Message 47039 - Posted: 3 Jan 2013, 22:44:53 UTC - in response to Message 47035.

What BOINC giveth so shall BOINC take away. The problem will return. The reason you don't see it now is because you're not triggering it.

I think you haven't seen the box where you enter the password yet. In BOINC manager's Advanced View click Advanced -> Select Computer, a dialogue box pops up. For hostname just leave it blank if you want to connect to localhost. Enter the password from gui_rpc_auth.cfg in the password box.

On Linux the problem triggers when BOINC manager cannot find gui_rpc_auth.cfg. If it can't find that file it can't look up the password and then it cannot connect to the client. The reason it cannot find gui_rpc_auth.cfg is usually because it starts with a current directory that is not the BOINC data directory. It's strategy seems to be look in the current direct5ory and then in the home directory.

I think it probably works similar on Windows so use the same trick on Windows as Linux and in the user's home directory put a link (shortcut) that points to the gui_rpc_auth.cfg in the BOINC data directory. Don't place copies of gui_rpc_auth.cfg in the home directory because if the original one changes the copies become useless. Use a link. That way If the original changes the link still points to the correct password.

Message boards : Questions and problems : BOINC unable to connect to core client


BOINC home page · Log in · Create account

Copyright © 2014 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.