Boinc Manager is not working


log in

Advanced search

Questions and Answers : Unix/Linux : Boinc Manager is not working

Author Message
Clare Jarvis
Send message
Joined: 12 Nov 05
Posts: 3
Credit: 20,008
RAC: 0
United States
Message 202280 - Posted: 3 Dec 2005, 20:53:36 UTC
Last modified: 3 Dec 2005, 21:21:35 UTC

Obicously I have internet connectivity or I wouldn't be sending you this message. I check the box indicating no restriction on connectiving. I cut and paste the url for seti at home. Apparnetly boinc is supposed to be run from the manager but the manager doesn't do anything apparently useful, and the feed back is not aparently useful. Using the manager to attached to projects doesn;t work. I managed to figure out how to attached to a project without using the manager. I set my prefrerences. When I run ./boinc from the command line I get a report about what is is doing and it stops. After days of letting it sit I finally hit ^C and the program tells me I am 7 days late report the result and that I won't get credit. Why don't you publish a install and running
proceedure manual, so I would know how to use this program. I have seen others request this but the 3 sentence responses hardly are reassuring. If you think I am a newbe I have beening working with unix since 1988 and been running linux
for 5 years. I think the support on the web pages is deficient or so well hidden that I am not finding it.

Every time I start boinc manager I instantly get a message about a bad password
and I am unable to connect (presumably to boinc that is ruynning) How do
I fix this problem.




____________

BorgQueen
Send message
Joined: 21 Feb 01
Posts: 4
Credit: 287
RAC: 0
United States
Message 202303 - Posted: 3 Dec 2005, 21:49:28 UTC

I have the same problems and the same complains. The time limits are dumb. The boinc manager is way too buggy and I also think the website and accompanying software is buggy.
The problem isn't you, as you now doubt know, its the software. They should have left well enough alone or come up with something better than what they've used to replace it with.

I don't want to hurt anyone's feelings. I know they're trying very hard but the transfer is just too problematic, too sloppy, too undocumented, too untested in the real world and the termination notice for setiathome classic was way too late. The transfer should have been conducted over a 12 month period where all these bugs could have been worked out before shutting down SAH classic.

Once again, I don't mean to hurt anyone's feelings. I know how hard all of you worked in this.
____________

Profile Scarecrow
Avatar
Send message
Joined: 15 Jul 00
Posts: 4376
Credit: 452,143
RAC: 378
United States
Message 202309 - Posted: 3 Dec 2005, 21:59:15 UTC

Every time I start boinc manager I instantly get a message about a bad password
and I am unable to connect (presumably to boinc that is ruynning) How do
I fix this problem.]

Let's start here and then progress onwards. In the boinc directory is a file named gui_rpc_auth.cfg. This contains the password. If the file doesn't exist, it is automatically created, with a long alpha-numeric password, when boinc runs. This is the password that the manager is wanting. You can cat this file, or open it in a text editor to view the password. You can manually edit the gui_rpc_auth.cfg file to contain either an 'easier to remember' password, or no password at all. The password should be on the first line of the file, and should have a single carriage return at the end. To eliminate the password, a single carriage return on the first line of the file is needed. The use of the password will depend on how you have things set up from a security standpoint. If you change the password, you will have to stop and restart the boinc client for the new password to take effect.
Once you have determined, or changed your password, (and restarted boinc if you change it) you can use the File>Select Computer menu option in boincmgr to select the computer (localhost) and enter the password. This should now have you connected via the manager, and allow further inspection of other problems.

Some common reasons for failure to connect and recieve or return work are system firewall settings that are blocking boinc from the outside world, or settings in boinc itself like "project suspended" or "network activity suspended". Once the manager is running it's easy to see and change these settings if they happen to be what's stopping the show

Clare Jarvis
Send message
Joined: 12 Nov 05
Posts: 3
Credit: 20,008
RAC: 0
United States
Message 202328 - Posted: 3 Dec 2005, 22:41:41 UTC - in response to Message 202303.

I have the same problems and the same complains. The time limits are dumb. The boinc manager is way too buggy and I also think the website and accompanying software is buggy.
The problem isn't you, as you now doubt know, its the software. They should have left well enough alone or come up with something better than what they've used to replace it with.

I don't want to hurt anyone's feelings. I know they're trying very hard but the transfer is just too problematic, too sloppy, too undocumented, too untested in the real world and the termination notice for setiathome classic was way too late. The transfer should have been conducted over a 12 month period where all these bugs could have been worked out before shutting down SAH classic.

Once again, I don't mean to hurt anyone's feelings. I know how hard all of you worked in this.


Try the password thing, in the first answer to to my original query. It really did answer the question.

I will add. Start boinc first. It is apparently some sort od daemon and is
necessary to connect to projects. Then Use the manager to monitor and
start other projects. I haven't found the password thing in any of the online documentation, but not the manager has connected to poinc and I can see that something is happening. Thanks for the first reply.

____________

flim
Send message
Joined: 18 Apr 06
Posts: 8
Credit: 0
RAC: 0
United Kingdom
Message 284469 - Posted: 19 Apr 2006, 0:30:31 UTC - in response to Message 202309.

Every time I start boinc manager I instantly get a message about a bad password
and I am unable to connect (presumably to boinc that is ruynning) How do
I fix this problem.]

Let's start here and then progress onwards. In the boinc directory is a file named gui_rpc_auth.cfg. This contains the password. If the file doesn't exist, it is automatically created, with a long alpha-numeric password, when boinc runs. This is the password that the manager is wanting. You can cat this file, or open it in a text editor to view the password. You can manually edit the gui_rpc_auth.cfg file to contain either an 'easier to remember' password, or no password at all. The password should be on the first line of the file, and should have a single carriage return at the end. To eliminate the password, a single carriage return on the first line of the file is needed. The use of the password will depend on how you have things set up from a security standpoint. If you change the password, you will have to stop and restart the boinc client for the new password to take effect.
Once you have determined, or changed your password, (and restarted boinc if you change it) you can use the File>Select Computer menu option in boincmgr to select the computer (localhost) and enter the password. This should now have you connected via the manager, and allow further inspection of other problems.

Some common reasons for failure to connect and recieve or return work are system firewall settings that are blocking boinc from the outside world, or settings in boinc itself like "project suspended" or "network activity suspended". Once the manager is running it's easy to see and change these settings if they happen to be what's stopping the show


I have the same problem whereby boincmgr tells me I'm using the wrong password. I have no gui_rpc_auth.cfg file, no matter how many times I start and stop boinc. I created one and put a blank password, but I still get the same message. Any ideas would be very useful!
____________

QuickSilver
Send message
Joined: 16 Jul 99
Posts: 1
Credit: 282,951
RAC: 0
United States
Message 413557 - Posted: 2 Sep 2006, 16:22:44 UTC - in response to Message 202309.

... the boinc directory is a file named gui_rpc_auth.cfg. This contains the password. If the file doesn't exist, it is automatically created, with a long alpha-numeric password, when boinc runs. This is the password that the manager is wanting. You can cat this file, or open it in a text editor to view the password. You can manually edit the gui_rpc_auth.cfg file to contain either an 'easier to remember' password, or no password at all. The password should be on the first line of the file, and should have a single carriage return at the end. To eliminate the password, a single carriage return on the first line of the file is needed. The use of the password will depend on how you have things set up from a security standpoint. If you change the password, you will have to stop and restart the boinc client for the new password to take effect.


THANK YOU! The directions for running this as a daemon never mention this file, so I was going NUTS trying to figure it out. Now I can run the manager as myself again!

____________
-Sal
---
My gun has killed less people than Ted Kennedy's Oldsmobile.
-- Various
Be wary of strong drink. It can make you shoot at tax collectors and miss.
-- Lazarus Long, "Time Enough for Love"

Questions and Answers : Unix/Linux : Boinc Manager is not working

Copyright © 2014 University of California