| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: [Q] Sometimes Boinc-client doesn't start on Ubuntu |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
sepmsk
Cruncher Russia Joined: Dec 31, 2007 Post Count: 24 Status: Offline Project Badges: 
|
Hello, need your advice.
----------------------------------------I have boinc-client as a service running on Linux Ubuntu 10.04 LTS. I configured that service to start automatically. And it usually does, but not always. Sometimes I see that the service is not running and I have to start it manually. This issue concerns the PC of my brother with Ubuntu 10.04 LTS as well. He doesn't monitor the system, so if the Boinc service doesn't start, a lot of CPU time is wasted. I noticed also if I the Boinc service doesn't start, some other services do not as well (Bluetooth service, CUPS). Could you please advice how can I have the services to start reliably, each time Ubuntu starts? Thank you! [Edit 3 times, last edit by sepmsk at Feb 13, 2011 10:05:31 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi,
----------------------------------------could be multiple reasons why, for instance the ownerships and permissions in the /etc/boinc-client directory. Do an ls -l and see if anything is not owned by the boinc account. If so do sudo chown boinc:boinc * (just tested this to make sure it works on Ubuntu 10.10) Some reading material: http://www.linuxquestions.org/questions/linux...-to-start-at-boot-384357/ http://www.spy-hill.com/~myers/help/boinc/unix.html --//-- edit: fixed links [Edit 1 times, last edit by Former Member at Feb 13, 2011 10:36:55 AM] |
||
|
|
sepmsk
Cruncher Russia Joined: Dec 31, 2007 Post Count: 24 Status: Offline Project Badges:
|
Many thanks, SekeRob!
----------------------------------------I found that all files in /etc/boinc-client directory were owned by root but the group was boinc. So I chowned them and now all files belong to boinc:boinc. BTW, I looked into /etc/init.d/boinc-client file and found # Default values for the variables that are also set in the defaults file. ENABLED=0 SCHEDULE=0 BOINC_USER=boinc BOINC_DIR=/var/lib/boinc-client BOINC_CLIENT=/usr/bin/boinc BOINC_OOM_ADJ=15 Are ENABLED=0 and SCHEDULE=0 normal? Do you know what they mean? Thank you! [Edit 1 times, last edit by sepmsk at Feb 13, 2011 11:29:01 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes looks identical to mine.
Reading the script, think it's the var that sets the check if the settings of the /etc/default should apply or the content of the /etc/init.d/boinc-client # Source defaults file. Edit that file to configure this script. if [ -e /etc/default/boinc-client ]; then . /etc/default/boinc-client fi # Quit quietly, if $ENABLED is 0. test "$ENABLED" != "0" || exit 0 Where in /etc/default/boinc-client the ENABLED="1" If you have 2 systems, same OS, same setup, one working, the other not, it's handy to compare how each is set up. In System > Preferences there a Startup Applications where one can conveniently add programs to start. At least in 6.12 on Windows the Manager is able to start the service, so it may become a problem for many of the past. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Been experimenting a bit with System > Preferences > Startup Applications. Added there a new app with
Name: BOINC Daemon Command: sudo services boinc-client start Comment: Start BOINC core client at sign-in After stopping the BOINC service, watching that temps went down as did the fan speed, signed out from the system. After logging in, the service launched instantly, with the 15 second delay I've set in the config. Subsequent signouts left the service running. BOINC is set to only allow 1 instance of the daemon. Hope this is a functioning workaround for others as well, if all else fails to get it going again before first sign-in. --//-- |
||
|
|
|