Boinc fails to start projects on boot (execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!, Lucid)

Bug #608058 reported by KevinM
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
boinc (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: boinc

This problem occurs occasionally (approximately once every 20 boots). I am normally attached to at least 7 projects )including SETi, rosetta, malaria. No projects start and none are displayed under the project tab. If I reboot the projects will again be displayed and working. I'm also running conky at start-up and this confirms no projects run when the problem occurs. In xsession-errors I get
(evolution-alarm-notify:1511): evolution-alarm-notify-WARNING **: Could not create the alarm notify service factory, maybe it's already running…
** (update-notifier:1616): DEBUG: Skipping reboot required
*** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!
execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

** (update-notifier:1616): DEBUG: --security-updates-unattended: 0

(gnome-terminal:2050): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

(gnome-terminal:2339): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: boinc (not installed)
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Jul 21 07:43:10 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: boinc

Revision history for this message
Steffen Möller (moeller-debian) wrote : Re: [Bug 608058] [NEW] Boinc fails to start projects in Lucid

On 07/21/2010 08:53 AM, KevinM wrote:
> Public bug reported:
>
> Binary package hint: boinc
>
> This problem occurs occasionally (approximately once every 20 boots). I am normally attached to at least 7 projects )including SETi, rosetta, malaria. No projects start and none are displayed under the project tab. If I reboot the projects will again be displayed and working. I'm also running conky at start-up and this confirms no projects run when the problem occurs. In xsession-errors I get
> (evolution-alarm-notify:1511): evolution-alarm-notify-WARNING **: Could not create the alarm notify service factory, maybe it's already running…
> ** (update-notifier:1616): DEBUG: Skipping reboot required
> *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
> execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!
> execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!
> Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
> Please ask your system administrator to enable user sharing
Hi Kevin,

from what you describe this does not necessarily seem related to BOINC,
but I may be wrong. We have just uploaded the 6.10.58 version, and
Daniel has also backported that to Lucid, which should be available
through his PPA.
https://launchpad.net/~pkg-boinc/+archive/ppa

Steffen

Revision history for this message
KevinM (kevbert1) wrote : Re: Boinc fails to start projects in Lucid

My version from the standard repos for both the client and manager was 6.10.17+dfsg-3ubuntu1. I've now added the repo and installed 6.10.58. I'll post back in the problem is still occurring (it may be a few days...)
Thanks
Kevin.

Revision history for this message
KevinM (kevbert1) wrote :

The problem still occurs with the latest programs.
Linux kernel is now 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:20:59 UTC 2010 x86_64 GNU/Linux (updated recently).
I've attached my .xession-errors file as there's other things (but probably going on that are unrelated).

Revision history for this message
Daniel Hahler (blueyed) wrote :

The error apparently is:
   execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!

Can you provide the following files (only readable by root/boinc):

/var/lib/boinc-client/stdoutdae.txt
/var/lib/boinc-client/stderrdae.txt

Please look there for any indication of (startup) failure.

Changed in boinc (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
KevinM (kevbert1) wrote :

The stderrdae.txt file seems to be empty (i.e. no errors). The stdoutdae.txt file I've attached I've reduced in size so that it only shows recent activity (the original was 1.4Mb). When I first ran up the PC from cold this morning BOINC did not see any attached projects and so I rebooted (but still no attached projects, this is new). A second reboot and BOINC is again running fine. The stdoutdae.txt file looks OK.

Revision history for this message
Daniel Hahler (blueyed) wrote : Re: [Bug 608058] Re: Boinc fails to start projects in Lucid

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> When I first ran up the PC from cold this morning BOINC did not see
> any attached projects and so I rebooted (but still no attached
> projects, this is new). A second reboot and BOINC is again running
> fine.

So you've booted three times in a row?

When BOINC came up at ~7:05 this was your third attempt, correct?
And you've shutdown at ~9:20?

> The stdoutdae.txt file looks OK.

It's likely that the error which gets displayed in ~/.xsession-errors
prevents BOINC already from logging anything.

When this happens again, please do not reboot, but do the following:
% sudo -i
% cd /var/lib/boinc-client
% ls -lt | head

This should give you a list of the least recently changed files.
Please paste this, and inspect the least recently changed ones -
hopefully those are logfiles.

You could also try enabling apport (/etc/default/apport) and look for a
crash file in /var/crash.
Unfortunately, apport won't let you report this directly to Launchpad
(because the package is from a PPA), but this might be useful for
inspection nonetheless.

- --
http://daniel.hahler.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFMUxUAfAK/hT/mPgARApWBAJ9ioT/TvWo4Y7nN+ZYnl9dcwjSu5QCg5QVE
4rI5MS90xMmA4Z9ffR/vimQ=
=a4MY
-----END PGP SIGNATURE-----

Revision history for this message
Daniel Hahler (blueyed) wrote : Re: Boinc fails to start projects in Lucid

This _might_ be related, at least there's the same "failed with error 2" message, but after a connect:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360143

So, additionally, when this fails again, try the following (after inspecting the logs as described above):
1. Manually start the client using: sudo invoke-rc.d boinc-client start
2. Looking at other errors like that (via Google, e.g. http://128.32.18.189/trac/ticket/923), this appears to come from boincmgr, and not "boinc" itself; please check the list of running process via "ps aux | grep boinc" when it failed to start.

Revision history for this message
KevinM (kevbert1) wrote :

Thanks Daniel.
Booted three times in a row.
Will report back when Boinc next fails to start/load a project.
By the way, I have apport permanently enabled and the crash files in /var/crash don't seem to include one for Boinc (may be due to your comment about .xsession-errors in post #6.

Revision history for this message
KevinM (kevbert1) wrote :

Output of ls -lt | head
total 2232
-rw-r--r-- 1 boinc boinc 1532501 2010-07-31 18:45 stdoutdae.txt
-rw-r--r-- 1 boinc boinc 1013 2010-07-31 18:45 daily_xfer_history.xml
-rw-r--r-- 1 boinc boinc 22257 2010-07-31 18:45 time_stats_log
-rw-r--r-- 1 boinc boinc 147364 2010-07-31 18:45 client_state.xml
-rw-r--r-- 1 boinc boinc 147361 2010-07-31 18:25 client_state_prev.xml
-rw-r--r-- 1 boinc boinc 8613 2010-07-31 18:25 statistics_lhcathome.cern.ch_lhcathome.xml
-rw-r--r-- 1 boinc boinc 728 2010-07-31 18:25 sched_reply_lhcathome.cern.ch_lhcathome.xml
-rw-r--r-- 1 boinc boinc 7381 2010-07-31 18:25 sched_request_lhcathome.cern.ch_lhcathome.xml
-rw-r--r-- 1 boinc boinc 2981 2010-07-31 18:25 statistics_boinc.fzk.de_poem.xml

In stdoutdae.txt I get this:
31-Jul-2010 18:45:28 [---] Received signal 15
31-Jul-2010 18:45:29 [---] Exit requested by user
31-Jul-2010 18:45:30 [---] Received signal 15
when logging off of Ubuntu rather than just one signal 15 when things seem to work.

In time_stats.log I get:
1280568517.114744 platform x86_64-pc-linux-gnu
1280568517.114744 version 6.10.58
1280568517.114744 power_on
1280568527.276587 net_unknown
1280569747.258848 power_off
1280569739.121782 power_off
1280597135.775323 platform x86_64-pc-linux-gnu
1280597135.775323 version 6.10.58
1280597135.775323 power_on
1280597146.596822 net_unknown
1280598328.494169 power_off
I assume that I need two power_off messages (due to dual core processor ?) and only get one prior to problems.

I've also had an npviewer crash and will send a new crash file when the next one is created (the old one is huge) - I'm using a hotplug rather than wireless. Wireless was originally used when I installed Boinc.

Daniel Hahler (blueyed)
summary: - Boinc fails to start projects in Lucid
+ Boinc fails to start projects on boot (execvp(/var/lib/boinc-
+ client/boinc, --redirectio, --launched_by_manager) failed with error 2!,
+ Lucid)
Changed in boinc (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Daniel Hahler (blueyed) wrote : Re: [Bug 608058] Re: Boinc fails to start projects in Lucid

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> In stdoutdae.txt I get this: 31-Jul-2010 18:45:28 [---] Received
> signal 15 31-Jul-2010 18:45:29 [---] Exit requested by user
> 31-Jul-2010 18:45:30 [---] Received signal 15 when logging off of
> Ubuntu rather than just one signal 15 when things seem to work.

Looking at my log, I usually get only one "signal 15" line, too, but
sometimes the same as above, e.g.
29-Jul-2010 01:42:18 [---] Received signal 15
29-Jul-2010 01:42:19 [---] Exit requested by user
29-Jul-2010 01:42:26 [---] Received signal 15
29-Jul-2010 01:51:28 [---] Starting BOINC client version 6.10.58 for
i686-pc-linux-gnu

There was no other boot in between, and therefore this must not be a
reason for boinc failing to start (at least on my system).

> In time_stats.log I get:

I have there occurrences of a single "power_off", too (usually also two).

> I assume that I need two power_off messages (due to dual core
> processor ?) and only get one prior to problems.

Please observe this further: it does not appear to cause problems for
me. But I cannot be sure, I rarely check if BOINC is running - I will do
so now however.

> I've also had an npviewer crash and will send a new crash file when
> the next one is created (the old one is huge) - I'm using a hotplug
> rather than wireless. Wireless was originally used when I installed
> Boinc.

I do not think this is related.

- --
http://daniel.hahler.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFMValafAK/hT/mPgARAolZAKCcvV3IrMcIrZlYfitMU471khVrcwCePC/L
xAD31WmAJZDGPup/lr4Kdu4=
=0iVW
-----END PGP SIGNATURE-----

Revision history for this message
KevinM (kevbert1) wrote :

Failed to start again
$ ps aux | grep boinc
kevin 11034 2.7 0.6 343004 26016 ? S 06:27 0:05 gedit /var/lib/boinc-client/stderrdae.txt
kevin 11069 0.0 0.0 7624 892 pts/0 S+ 06:30 0:00 grep --color=auto boinc
$ sudo invoke-rc.d boinc-client start
[sudo] password for kevin:
 * Starting BOINC core client: boinc [ OK ]
 * Setting up scheduling for BOINC core client and children: [ OK ]
$
Boinc now running again
$ps aux | grep boinc
kevin 11034 1.3 0.6 343004 26088 ? S 06:27 0:05 gedit /var/lib/boinc-client/stderrdae.txt
boinc 11097 0.2 0.1 79700 6980 ? SN 06:31 0:00 /usr/bin/boinc --check_all_logins --redirectio --dir /var/lib/boinc-client
boinc 11376 84.4 0.5 24708 22900 ? SN 06:31 1:34 ../../projects/boinc.fzk.de_poem/poem_1.0_i686-pc-linux-gnu
boinc 11377 82.1 2.9 140764 119096 ? SNl 06:31 1:31 ../../projects/www.malariacontrol.net/openMalariaA_6.42_x86_64-pc-linux-gnu --compress-checkpoints=1
boinc 11389 0.0 0.5 24708 22900 ? SN 06:31 0:00 ../../projects/boinc.fzk.de_poem/poem_1.0_i686-pc-linux-gnu
boinc 11390 0.0 0.5 24708 22900 ? SN 06:31 0:00 ../../projects/boinc.fzk.de_poem/poem_1.0_i686-pc-linux-gnu
kevin 11407 2.3 0.5 273900 20392 ? Sl 06:32 0:02 /usr/bin/boincmgr
kevin 11425 0.0 0.0 7628 976 pts/0 R+ 06:33 0:00 grep --color=auto boinc

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

could you try to reproduce with the latest boinc fron oneiric or the official download site? thanks

Changed in boinc (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/608058
please try my ppa with the latest 7.0.23 from upstream source

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :
Revision history for this message
Dave (xclusive585) wrote : Re: [Bug 608058] Re: Boinc fails to start projects on boot (execvp(/var/lib/boinc-client/boinc, --redirectio, --launched_by_manager) failed with error 2!, Lucid)

I have never had the init for boinc work properly. I avoid it and instead
always run boinc manually as my user. You can use cron to fire up boinc
under your username. or perhaps the init settings should be changed to run
under the user account that installed boinc.
On Jul 26, 2012 3:45 PM, "LocutusOfBorg" <email address hidden>
wrote:
>
> please try boinc 7.0.31 from my ppa
> https://code.launchpad.net/~costamagnagianfranco/+archive/boinc
>
> --
> You received this bug notification because you are a member of Debian
> BOINC Maintainers, which is subscribed to boinc in Ubuntu.
> https://bugs.launchpad.net/bugs/608058
>
> Title:
> Boinc fails to start projects on boot (execvp(/var/lib/boinc-
> client/boinc, --redirectio, --launched_by_manager) failed with error
> 2!, Lucid)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/608058/+subscriptions
>
> --
> pkg-boinc-devel mailing list
> <email address hidden>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-devel

Revision history for this message
Dave (xclusive585) wrote :

As many of us run boinc under our user account, it is a common problem to
have the root init instance of boinc create issues as you cannot launch
your instance of boinc until killing the unused init process of boinc
On Jul 26, 2012 3:51 PM, "Xclusive Technology" <email address hidden>
wrote:

> I have never had the init for boinc work properly. I avoid it and instead
> always run boinc manually as my user. You can use cron to fire up boinc
> under your username. or perhaps the init settings should be changed to run
> under the user account that installed boinc.
> On Jul 26, 2012 3:45 PM, "LocutusOfBorg" <email address hidden>
> wrote:
> >
> > please try boinc 7.0.31 from my ppa
> > https://code.launchpad.net/~costamagnagianfranco/+archive/boinc
> >
> > --
> > You received this bug notification because you are a member of Debian
> > BOINC Maintainers, which is subscribed to boinc in Ubuntu.
> > https://bugs.launchpad.net/bugs/608058
> >
> > Title:
> > Boinc fails to start projects on boot (execvp(/var/lib/boinc-
> > client/boinc, --redirectio, --launched_by_manager) failed with error
> > 2!, Lucid)
> >
> > To manage notifications about this bug go to:
> >
> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/608058/+subscriptions
> >
> > --
> > pkg-boinc-devel mailing list
> > <email address hidden>
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-devel
>

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

what if you launch boincmgr from directory /usr/bin/ ?

Revision history for this message
Dave (xclusive585) wrote :

then boincmgr would connect to the proper instance of boinc-client I
assume. Problem is, that that instance of boinc-client will not use the
users added projects which are located in /home/user/projects/
Another thing to consider is you must always run boinc as the user that you
added projects with. If you for example add projects as root and then fire
up boinc without root permissions, you get errors.
On Jul 26, 2012 4:21 PM, "LocutusOfBorg" <email address hidden>
wrote:

> what if you launch boincmgr from directory /usr/bin/ ?
>
> --
> You received this bug notification because you are a member of Debian
> BOINC Maintainers, which is subscribed to boinc in Ubuntu.
> https://bugs.launchpad.net/bugs/608058
>
> Title:
> Boinc fails to start projects on boot (execvp(/var/lib/boinc-
> client/boinc, --redirectio, --launched_by_manager) failed with error
> 2!, Lucid)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/608058/+subscriptions
>
> --
> pkg-boinc-devel mailing list
> <email address hidden>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-devel
>

Changed in boinc (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Please try this ppa and boinc 7.8.1, and let me know if the problem still occurs by setting back the status to "new"
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc/

Changed in boinc (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.