Boinc manager wont attach to boinc client

Message boards : Questions and problems : Boinc manager wont attach to boinc client
Message board moderation

To post messages, you must log in.

AuthorMessage
Rob

Send message
Joined: 13 Nov 08
Posts: 11
Australia
Message 21209 - Posted: 13 Nov 2008, 2:40:40 UTC
Last modified: 13 Nov 2008, 2:42:55 UTC

I run Kubuntu 8.10 & wanted to try GPUGRID which required me to upgrade to Boinc 6.3.21.
I installed it in my home directory, edited /etc/default/boinc-client file in the old install so it pointed to the new client & started it on startup. Also deleted the original boincmgr file in that directory & replaced it with the new one.
Everything was fine except it wouldn't recognize my graphics card even after updating the drivers.
So I decided to start from scratch & uninstalled the original version with synaptic and deleted the new Boinc folder then reinstalled the new version.
Now boinc client runs, but when I start boinc manager it can't attach to the client. After some searching I found a heap of boinc files in /var/lib/boinc.client, which I assume are from the original installation & is where boinc client is starting from.
So what I want to know is what do I have to move or edit to get boinc manager to connect to the client again, or am I better off just deleting everything again manually & reinstalling again?
Sorry for the long winded post & thanks in advance for any help :-)
ID: 21209 · Report as offensive
Rob

Send message
Joined: 13 Nov 08
Posts: 11
Australia
Message 21211 - Posted: 13 Nov 2008, 7:27:33 UTC

Still no good :-(. The first 4 steps went off without a hitch. I verified it by checking under applications>system>user manager>groups. Although the line "boinc-user:x:<group ID number>:" is actually just "boinc:x:<group ID number>:" on my comp.
After that I typed in all the other lines, but boinc manager still remains "disconnected" even after a system restart. On lines 5,6,&7 I had to change boinc to boinc-client, otherwise it said something along the lines of directory not found or directory does not exist. So I was wondering if one of the boinc's in line 8 should also be changed to boinc-client ??
ID: 21211 · Report as offensive
Rob

Send message
Joined: 13 Nov 08
Posts: 11
Australia
Message 21214 - Posted: 13 Nov 2008, 10:35:35 UTC - in response to Message 21211.  

For trouble shooting purposes I thought I'd show error messages that come up at each stage.
6. chmod: cannot operate on dangling symlink `/var/lib/boinc-client/cc_config.xml'
chmod: cannot operate on dangling symlink `/var/lib/boinc-client/global_prefs_override.xml'
chmod: cannot operate on dangling symlink `/var/lib/boinc-client/gui_rpc_auth.cfg'
chmod: cannot operate on dangling symlink `/var/lib/boinc-client/remote_hosts.cfg'
7. ln: creating symbolic link `/home/rob/gui_rpc_auth.cfg': File exists
All other lines are accepted without comment.
ID: 21214 · Report as offensive
Profile KSMarksPsych
Avatar

Send message
Joined: 30 Oct 05
Posts: 1239
United States
Message 21220 - Posted: 13 Nov 2008, 12:23:21 UTC

Well, a dangling symlink is basically a broken link. It (in theory) should be safe enough to remove those symlinks and recreate them pointing to the new files.
Kathryn :o)
ID: 21220 · Report as offensive
Rob

Send message
Joined: 13 Nov 08
Posts: 11
Australia
Message 21229 - Posted: 13 Nov 2008, 21:07:46 UTC - in response to Message 21224.  

If the manager will not connect to the client automatically when you start the manager then maybe the client is not running?

It is running. gkrellm shows 100% cpu usage & I had checked in system monitor just to be sure :-)
I started following your latest suggestions but when I got to "Then create a symlink /etc/bin/gui_rpc_auth.cfg" I realized that no /etc/bin folder exists. So I thought to myself, I wonder what would happen if I just copied /home/rob/gui_rpc_auth.cfg to the /var/lib/boinc-client/ folder.
It worked :-D.
Trouble is I still have my original problem in that it wont recognise my graphics card "no cuda devices found" :-(
Anyway thanks for your help. Any suggestions for getting boinc to see my vid card ??? :-)
ID: 21229 · Report as offensive
Rob

Send message
Joined: 13 Nov 08
Posts: 11
Australia
Message 21232 - Posted: 13 Nov 2008, 23:05:24 UTC - in response to Message 21230.  

It works only with nVidia cards that use certain GPUs that are supported by CUDA. Support for ATI cards is planned.

My card is 8800GT & is supported. I think it all comes down too having remnants of 2 separate Boinc instalations lying around and some things aren't were they are supposed to be. May have to reinstall again yet :-(

Anyway, where are the BOINC binaries placed in Ubuntu?

No idea. I think the boinc version installed by the package manager puts them in /etc/bin/ but as for where a manual install places them, your guess is as good as mine, probably better :-)
If I uninstall/reinstall again, this time I'll use "mark for complete removal" which I didn't even notice last time so just used mark for removal instead. Then hopefully when I do a manual reinstall everything should be where it's supposed to be.
ID: 21232 · Report as offensive
Rob

Send message
Joined: 13 Nov 08
Posts: 11
Australia
Message 21234 - Posted: 14 Nov 2008, 0:34:07 UTC - in response to Message 21233.  

6.3.x comes with libcudart.so. You may have somehow excluded that file. It needs to be in the same directory as the binaries and the 6.3.x Berkeley installer (what I call the manual installer) will put it in /home/bob/BOINC where it needs to be.

It's there where it's supposed to be. Even put a copy in /var/lib/boinc-client/ when I was fiddling earlier to see if that helped. It didn't. I'm running down my cache now and will uninstall everything & start from scratch. Should be within 24 hours.
Thanks for your help :-)
ID: 21234 · Report as offensive

Message boards : Questions and problems : Boinc manager wont attach to 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.