Help... rebuilt my computer and now can't run BOINC/SETI

Hello, all...
I'm not new to BOINC, Seti@Home, or linux. However, my computer died (F11) and I had to replace most of the guts as well as reinstall Fedora 11. Now, when I go to run Seti@Home/BOINC, it won't let me do anything. If I run it from the command line it tells me I need to connect to a project, but I don't know how to do that from a command-line and the GUI won't let me do anything!
Can someone please advise how to set this up? As I said, I was running BOINC/SETI before the crash, but now it's not working. :-(
____________

Hello, all...
I'm not new to BOINC, Seti@Home, or linux. However, my computer died (F11) and I had to replace most of the guts as well as reinstall Fedora 11. Now, when I go to run Seti@Home/BOINC, it won't let me do anything. If I run it from the command line it tells me I need to connect to a project, but I don't know how to do that from a command-line and the GUI won't let me do anything!
Can someone please advise how to set this up? As I said, I was running BOINC/SETI before the crash, but now it's not working. :-(

change into your boinc data directory where all the .xml files will be kept (on my system that is /var/lib/boinc but i am not running redhat so it may be different with yours).

from cmdline just type:


boinc --attach_project <project URL> <project password>

Well, I can run it in a console window, but for some reason I can *not* get the GUI to work. :-( Any ideas? It just says "disconnected" and won't connect to anything! This is SOOO aggravating!
____________

change into your boinc data directory where all the .xml files will be kept (on my system that is /var/lib/boinc but i am not running redhat so it may be different with yours).

from cmdline just type:


boinc --attach_project <project URL> <project password>

*sigh* Why does everything in linux have to be 10 times as hard? Why won't the GUI just work? This is really freakin' annoying! Thanks! I followed your instructions above and it appears to be working!

Well, I can run it in a console window, but for some reason I can *not* get the GUI to work. :-( Any ideas? It just says "disconnected" and won't connect to anything! This is SOOO aggravating!

from the console prompt type

ifconfig

make sure you have both a valid eth0 and a valid lo

or you can just ping localhost and make sure it pings 127.0.0.1 if it does not then you need to be sure that lo is in the network startup setups. it is very easy to miss some configuration on a new install.

also as an experiment after verifying the network, i assume you log into the gui as a normal user without root priv.. try from a terminal window either su to root or use sudo

and simply execute boincmgr with no options and see if as root it can connect.

it may be a user permissions thing. make sure both boinc and your username are members of the same group

what version of boinc are you running? unless you are doing cuda processing on more than one cuda device make sure you are running the latest code at least version 6.6.37. even then i have found that with doing multiple device cuda, 6.6.11 is what needs to be used but use the 6.6.37 boincmgr gui since the one in 6.6.11 is broken (at least on my system it doesn't sort columns).

from the console prompt type

ifconfig

make sure you have both a valid eth0 and a valid lo

or you can just ping localhost and make sure it pings 127.0.0.1 if it does not then you need to be sure that lo is in the network startup setups. it is very easy to miss some configuration on a new install.

also as an experiment after verifying the network, i assume you log into the gui as a normal user without root priv.. try from a terminal window either su to root or use sudo

and simply execute boincmgr with no options and see if as root it can connect.

it may be a user permissions thing. make sure both boinc and your username are members of the same group

what version of boinc are you running? unless you are doing cuda processing on more than one cuda device make sure you are running the latest code at least version 6.6.37. even then i have found that with doing multiple device cuda, 6.6.11 is what needs to be used but use the 6.6.37 boincmgr gui since the one in 6.6.11 is broken (at least on my system it doesn't sort columns).

[john@slave1 boinc]$ rpm -qa | grep boinc
boinc-client-6.6.37-2.r18632svn.fc11.x86_64
boinc-manager-6.6.37-2.r18632svn.fc11.x86_64

Oh, and I assure you that my network is fine... I'm writing this on the very machine I'm trying to run BOINC on... And I execute boincmgr with sudo permissions already. I'm well aware of the restrictions on running it as a user. I had that problem when I rebuilt my system last (Fedora 10)

Well, that's interesting... NOW it decides to work... This incarnation of my machine has been a real headache... trying to get SSH access working and BOINC not cooperating and having to install the VNC server package... Sheesh... I don't know what I've done to pi$$ off the $deity of luck, but I seem to have done so!

Oh, well... it's working now! Thanks!

I ran into the same thing. Commandline boinc --attach worked, but GUI still wouldn't. Ran into this will every machine so far.
Narrowed it down to run_manager as root, then stop after benchmarks, chown everything under BOINC back to original owner, then run_manager as normal.
Still no idea why. Localhost is 127.0.0.1, machine_name is 127.0.0.2, which is what the XMLs were referencing...maybe. Don't know, just know that's how I got around it.
____________

you may benefit from backing off to boinc 6.4.5 I assume you are using the beta 6.6.37. 6.6.36 had/has problems occasionally starting on Linux. I'm not sure what the problem is/was. it may still be a part of 6.6.37
____________
Proud member of TSWB.

End terrorism by building a school

I was at 6.4.5 on all the linux boxes. Interface was saying, upgrade to 6.6.36. Upon checking, it's stable now, so I started to proceed with upgrades. Halfway through, went to lunch, probably won't continue with the rest.

It's happening on FC11, OS11.1, all my linuxes so far. I'll leave these that I had upgraded and observe. They appear to run ok after jumping through the hoops, but, we'll see.
____________

my mandriva box installed fine but wouldnt start BOINC at all on 6.6.36 I backed off to 6.4.5 and it works fine.
____________
Proud member of TSWB.

End terrorism by building a school

my mandriva box installed fine but wouldnt start BOINC at all on 6.6.36 I backed off to 6.4.5 and it works fine.