Thread 'BOINC manager can't find running BOINC client'

Message boards : BOINC Manager : BOINC manager can't find running BOINC client
Message board moderation

To post messages, you must log in.

AuthorMessage
Tehhund

Send message
Joined: 11 Sep 08
Posts: 4
United States
Message 20121 - Posted: 11 Sep 2008, 18:41:41 UTC

I'm using Fedora 8, but I've only been using Linux for about a week so I don't know how to troubleshoot this, and no amount of searching has turned up an answer so far.

I installed the BOINC client and manager, and set the client to run as a service at boot. I rebooted, and it seems to be running, because I checked:

@localhost ~]$ ps aux | grep boinc
boinc 2021 0.0 0.1 8904 2032 ? SNs 13:10 0:00 /usr/bin/boinc_client --daemon


However, when I launch the manager to attach to rosetta@home, I get this error:

Authorization failed connecting to running client.
Make sure you start this program in the same directory as the client.


I checked, and both the client (boinc_client) and the manager (boinc_manager) are in /usr/bin. So I'm lost.

I did find two text files named boinc-client in other folders, but I'm not sure if those are affecting anything.

Any ideas? Thanks in advance!
ID: 20121 · Report as offensive
Tehhund

Send message
Joined: 11 Sep 08
Posts: 4
United States
Message 20170 - Posted: 12 Sep 2008, 4:19:20 UTC - in response to Message 20133.  

Thanks for the reply, but those instructions didn't quite work out. I changed my RPC password per the instructions, then #4 says

When logged in as a regular user you will be required to give the GUI RPC password every time you start BOINC manager.


This is not the case - it just errors out when I open it, and I can't find any way to enter a password in the manager. Should I be trying to load it from the terminal instead of through GUI?

I went ahead and did steps 4.1 and 4.2, as well as 5.1 through 5.7, but I still have the same problem.

Any further troubleshooting steps? I think I'm missing something at the "You will be required to give the GUI RPC password..." stage, but I performed all of the steps and it still can't find the client.

If installing BOINC is a somewhat advanced Linux operation, just let me know and I'll come back to it in a month once I've had more time to explore. Thanks!
ID: 20170 · Report as offensive
Tehhund

Send message
Joined: 11 Sep 08
Posts: 4
United States
Message 20242 - Posted: 13 Sep 2008, 23:22:25 UTC - in response to Message 20173.  

click Advanced -> Select Computer


*duh* There we go, I entered localhost and my new password, and it found the client. So that's fixed - but how do I make it remember my new password? If that's already in the instructions you gave me, sorry but I didn't understand.

Also, this it brought up a new issue. It brings up the "Attach to project" dialogue and allows me to select rosetta@home, but when it tries to connect it says

Network communication failure

BOINC failed to communicate on the internet...


All of the information I found on this issue focuses on firewalls and proxies, but I don't think either applies in my case. My Linux firewall is currently disabled. I'm connected to the Internet via a wireless connection, and I'm able to surf unsecured and secured pages without entering any proxy information, so it's a good assumption that ports 80 and 443 aren't blocked. Also, BOINC is running just fine on my Windows laptop that is connected to the same wireless network, so I doubt that BOINC is selectively blocked. Any ideas?

Thanks for all the help!
ID: 20242 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15563
Netherlands
Message 20243 - Posted: 13 Sep 2008, 23:27:18 UTC - in response to Message 20242.  
Last modified: 14 Sep 2008, 1:29:00 UTC

click Advanced -> Select Computer


*duh* There we go, I entered localhost and my new password, and it found the client. So that's fixed - but how do I make it remember my new password?

I really don't know and have been wondering that myself. For all my machines that I reach remotely, it never remembers the right password, let alone for the local machine. Perhaps that someone else can help you and me there. :-)

Any ideas?

Other than it still being a firewall issue, no. What happens when you enable the firewall in Linux and allow BOINC through on those ports?
ID: 20243 · Report as offensive
Tehhund

Send message
Joined: 11 Sep 08
Posts: 4
United States
Message 20246 - Posted: 14 Sep 2008, 1:23:39 UTC - in response to Message 20243.  

Unfortunately, it gives me the same behavior.
ID: 20246 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15563
Netherlands
Message 20247 - Posted: 14 Sep 2008, 1:32:23 UTC - in response to Message 20246.  

Checking the source code, it only comes up with that message when you set to use a proxy, while you have none, or when you use a proxy, but didn't set BOINC to use it.

So, did you set a proxy through BM->Advanced view->Advanced->Options?
Or are you using a proxy and didn't you set BOINC up to use it?
ID: 20247 · Report as offensive
Paul Zarucki

Send message
Joined: 18 Sep 08
Posts: 1
United Kingdom
Message 20351 - Posted: 18 Sep 2008, 12:06:08 UTC - in response to Message 20121.  

However, when I launch the manager to attach to rosetta@home, I get this error:

Authorization failed connecting to running client.
Make sure you start this program in the same directory as the client.


I checked, and both the client (boinc_client) and the manager (boinc_manager) are in /usr/bin. So I'm lost.

Any ideas? Thanks in advance!


On Debian, the following script works for me:

#!/bin/sh
xhost +local:
cd /usr/bin
./boincmgr
# end of script

Type the above into a text file (I called the file boinc-run.sh) in your home directory and make it executable. You can then create a desktop icon which runs this script.

Hope this helps!
ID: 20351 · Report as offensive

Message boards : BOINC Manager : BOINC manager can't find running BOINC client

Copyright © 2024 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.