| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Unable to attach to project |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 14
|
|
| Author |
|
|
Richard Hollins
Cruncher Joined: Nov 1, 2008 Post Count: 6 Status: Offline Project Badges: 
|
I rebooted, just to make sure there wasn't a change which hadn't been
started. [root@localhost boinc]# ./boinc_client --redirectio --daemon [root@localhost boinc]# ps -ef|grep boinc root 2816 1 0 16:21 ? 00:00:00 ./boinc_client --redirectio --daemon root 2825 2771 0 16:22 pts/1 00:00:00 grep boinc I started boincmgr, and immediately got the attach to project. I selected WCG, and it immediately began to download a task, and is now running it. But: [root@localhost /]# whereis boinc_client boinc_client: /usr/bin/boinc_client /usr/share/man/man1/boinc_client.1.gz So the startup script is not telling the system where the boinc_client is. boinc is in the list of services and checked to start up. The etc/rc.d/init.d/boinc file is marked as executable. what have I missed? There are links in /etc/rc.d/rcx.d which point to /etc/rc.d/init.d/boinc-client Should these point to: /var/lib/boinc/boinc_client, or should they be removed, since there are also links to /etc/init.d/boinc ? |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
Well, does the /etc/rc.d/init.d/boinc-client show anything
$ ls -lh /etc/rc.d/init.d/boinc-client Sometimes they put a symbolic link in here or a hard link if it is known that it is on the same filesystem. A symbolic link should have something like "filename <-- linkname" shown in the ls -lh listing. A hard link has something a little different, basically a count for the number of hard links to the file. -rw-r--r-- 2 keith keith 29 2009-07-06 01:05 versionshard.txt -rw-r--r-- 1 keith keith 29 2009-07-14 09:37 versionsorig.txt lrwxrwxrwx 1 keith keith 12 2009-07-14 09:37 versionssoft.txt -> versions.txt -rw-r--r-- 2 keith keith 29 2009-07-06 01:05 versions.txt example in the first line has a 2 which means it's 1 of 2 hard links to a file. the file is versions.txt in this example. in second line, you see that versionsorig.txt does not have any hard links to it since it is 1 of 1. line 3 is the soft link which just points to versions.txt. line 4 is the versions.txt file. But, unless they put some script in there for /etc/rc.d/init.d/boinc-client you should be able to point the start up script to use the /var/lib/boinc/boinc-client. -Uplinger |
||
|
|
Richard Hollins
Cruncher Joined: Nov 1, 2008 Post Count: 6 Status: Offline Project Badges:
|
boinc-client does not exist
[rich@localhost /]$ ls -lh /etc/rc.d/init.d/boinc-client ls: cannot access /etc/rc.d/init.d/boinc-client: No such file or directory [rich@localhost /]$ ls -lh /etc/rc.d/init.d/boinc -rwxr-xr-x 1 root root 6.7K 2009-07-08 16:21 /etc/rc.d/init.d/boinc /etc/rc.d/init.d/boinc is the startup script I can only conclude that /etc/rc.d/init.d/boinc-client was a startup script or a link to a startup script, or the boinc executable from a previous installation. They are also dated in June '09, whereas the ones which correctly reference boinc are about a month later, when I began to try to clean up this mess. There are similar links in /etc/rc.d/rc1.d, /rc2.d, etc, all the ones which reference boinc-client are K02boinc-client, and are broken links. If they did anything they would kill boinc whenever there was a change in run level. I discovered that the file /etc/sysconfig/boinc read: # BOINC daemon configuration settings. The examples below are the defaults # you'd get if you left them out, so you only need the lines that are different. # BOINCUSER=boinc BOINCDIR=/usr/local/bin/BOINC BUILD_ARCH=i686-pc-linux-gnu #BOINCEXE=/usr/local/bin/BOINC/boinc LOGFILE=boinc.log ERRORLOG=error.log #BOINCOPTS="-allow_remote_gui_rpc" #LOCKDIR=/var/lock/subsys It now reads: # BOINC daemon configuration settings. The examples below are the defaults # you'd get if you left them out, so you only need the lines that are different. # BOINCUSER=boinc BOINCDIR=/var/lib/boinc BUILD_ARCH=i686-pc-linux-gnu BOINCEXE=/var/lib/boinc/boinc_client LOGFILE=boinc.log ERRORLOG=error.log #BOINCOPTS="-allow_remote_gui_rpc" #LOCKDIR=/var/lock/subsys The boinc client started at system startup; now I get: [rich@localhost ~]$ ps -ef|grep boinc root 2187 1 0 02:35 ? 00:00:00 su boinc -c /var/lib/boinc/boinc_client boinc 2189 2187 0 02:35 ? 00:00:00 /var/lib/boinc/boinc_client rich 2697 1 7 02:37 ? 00:00:09 /var/lib/boinc/boincmgr rich 2736 2708 0 02:39 pts/1 00:00:00 grep boinc Although boinc manager initially came up error, I think that was due to being stopped and started, and it has now started a new task. Thie was an RTFM moment, since the /etc/sysconfig/boinc file is referred to here: Installing and Running the BOINC client in Linux http://www.spy-hill.net/~myers/help/boinc/unix.html#start where I had found most of the information for getting BOINC running. Thanks for your patience and assistance. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi, Richard.
Uplinger was trying to give you advice based on a different BOINC package to the one you are using. Unfortunately, simple things like names of scripts and executables are not consistent between packages. You will get the best results if you use a known good package supported by your distro. If you mix advice from different places (and that includes advice provided in the help pages here) you can end up in trouble. I'm glad you solved your problem. With hindsight, it appears your previous install left some detritus behind which conflicted with the defaults used by the new installation. |
||
|
|
|