| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Boinc client shuts down SuSE 10.0 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm trying to run the boinc client as a daemon using the startup script found here:
http://www.spy-hill.net/~myers/help/boinc/unix.html#start The script starts boinc just fine, but then boinc stops after a few seconds leaving the lockfile in place so that boinc then can't restart. Boinc runs just fine as a standalone program (i.e. not as a daemon). There are no messages in boinc's error.log when boinc stops (only when it tries to restart with the lockfile still there). Has anyone else met this? And, better still, does anyone know how to fix it? Cheers Peter |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
What are the symptoms of it stopping?
What is in the boinc.log file? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi,
Thanks for the swift reply. There are no symptoms. The client starts and is allocated a PID, but after about 10 seconds it just silently shuts down, leaving the lockfile in place. There is nothing in boinc.log. Nothing at all. I've also checked AppArmor to see if there's anything there, but there isn't. Neither can I see anything in /var/log/messages. I've copied (as root) the relevant files to all the places suggested in the script, but I've left default permissions (755); and I've created the boinc user with default permissions and group memberships - which should be OK as it's the same permissions I have and I can run the client from the command line (i.e. ./run_manager from the directory with all the installed in it) Does that help you (more than it helps me)? Cheers Peter |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's an old script, and I've never tried it myself.
BOINC is at least one major version further on since then, and backward compatibility isn't maintained for major version changes. Please will you have a quick look for other log files? BOINC handles redirection itself now. You could also try --daemon in $BOINCOPTS. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi again Didactylos. Thanks for the effort you're putting into this.
I seem to have partly cracked it. I'd moved all the files to the places suggested in the script, as root. The meant that the permissions to the /var/lib/boinc directory and all sub-files and directories were root:root. I did chown -R boinc:users on /var/lib/boinc everything worked as far as the client was concerned. Unfortunately, I now have another problem. I copied boincmgr to /usr/local/bin as suggested by the script, but when I try to run it, I now get the message: "Authorization failed connecting to running client. Make sure you start this program in the same directory as the client." I'm not quite sure what that means. Both the executables (boinc_client (i.e. boinc renamed as suggested in the script) and boincmgr) are in /usr/local/bin. Can I pick your brains again on this one? If you think it would be better, I'll start a new thread. Just let me know. Many thanks for you help. Cheers Peter |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Follow the instructions about gui_rpc_auth.cfg and you should be fine.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Weeeelll...
I googled for gui_rpc_auth.cfg and found that there had to be a blank line after the automatically generated password: so I did that. I can now get boincmgr to run, but only if I su to root and cd to /var/lib/boinc before I issue the boincmgr command. Is that how it's supposed to work? Cheers Peter |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If you need to su, your permissions are still wrong.
Are you following this advice to connect? This will pop of the scary message "Authorization failed connecting to running client. Make sure you start this program in the same directory as the client." Well, that's one way to do it, but this message is not quite accurate. Click "OK", then pull down "Advance -> Select computer..." and enter "localhost" for the compuer name, and then the password you set above as the password. This will connect the BOINC Manager (in the window which just opened) with the BOINC client which is running in the background. You can avoid this scary message and enable authentication automatically (you won't have to enter the password) if you cd to a directory which contains a copy of the file gui_rpc_auth.cfg before you run the Manager. One good way to do this is to put a copy of the gui_rpc_auth.cfg file in your own home directory, and then lanuch the Manager from there. (The way the Manager gets this information is a bit crude and will hopefully be improved in the future.) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks very much, Didactylos.
I hadn't found the instructions you quoted (which probably means I haven't looked hard enough, so apologies for that). However, you were quite right about the permissions. I did a chmod 664 on everything in /var/lib/boinc, then chmod - R 775 on the projects and slots folders. That sorted out the user required to run boincmgr. Finally, I copied the gui_rpc_auth.cfg file to my home directory as suggested in the doc you quote, and all is well. Great stuff. Thanks a lot. Peter |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
They were from the page you linked to - section 3.5.
Glad you have it working. |
||
|
|
|