1 |
On Wednesday 27 Apr 2016 10:03:58 Peter Humphrey wrote: |
2 |
> On Tuesday 26 Apr 2016 19:54:09 Gregory Woodbury wrote: |
3 |
> > On Tue, Apr 26, 2016 at 5:40 AM, Peter Humphrey <peter@××××××××××××.uk> |
4 |
> > |
5 |
> > wrote: |
6 |
> > > Has anyone here succeeded in getting this BOINC project to run? No |
7 |
> > > matter |
8 |
> > > what I try, I get "task postponed 86400.000000 sec: Communication with |
9 |
> > > VM |
10 |
> > > Hypervisor failed." |
11 |
> > |
12 |
> > Is the "user" boinc runs as in the vboxusers" group? |
13 |
> > By default, boinc runs as a non-root (daemon?) user and if its group is |
14 |
> > not in the vboxusers group, |
15 |
> > VirtualBox will not start or run for the user. |
16 |
> > |
17 |
> > The recommended workaround is to run boinc as a real user (generally |
18 |
> > "you") so that things operate properly. Additionally, the actual way |
19 |
> > that the cernvm runs can change "just a bit" and it will upset the |
20 |
> > balance of getting VBox to run boinc tasks. |
21 |
> |
22 |
> Thanks for the reply. Yes, boinc is running as me, as shown below, and I |
23 |
> am in the vboxusers group. Boinc is also in that group. All the files and |
24 |
> directories under ~/boinc and ~/.VirtualBox are owned prh:prh. But I've |
25 |
> just noticed that the files under ~/.VirtualBox are all 0600; I wonder if |
26 |
> that's thet problem: that the boinc user can't read them. But then boinc |
27 |
> is running as me, the owner of all the files involved. |
28 |
> |
29 |
> I'm going round in circles again. |
30 |
> |
31 |
> $ ps U prh |
32 |
> 710 ? SNsl 4:10 /usr/bin/boinc_client --daemon --dir |
33 |
> /home/prh/boinc --redirectio 880 ? Sl 22:23 /usr/bin/boincmgr |
34 |
> [...] |
35 |
> 19613 ? RN 372:47 |
36 |
> ../../projects/www.cosmologyathome.org/camb_2.16_i686-pc-linux-gnu |
37 |
> params.ini [...] |
38 |
> 24897 ? SNl 0:08 |
39 |
> ../../projects/pogs.theskynet.org_pogs/wrapper_x86_64-pc-linux-gnu_4.02 |
40 |
> [...] |
41 |
> 28001 ? RN 7:17 ./fit_sed 10 filters.dat observations.dat |
42 |
> [...] |
43 |
|
44 |
The fix has already been done, silently - no outward evidence other than the |
45 |
dates on a couple of files. I only found out when I compared a new |
46 |
installation with what I'd backed up a few hours earlier. |
47 |
|
48 |
The problem was that /etc/init.d/boinc was starting the client with an su |
49 |
command, but now a start-stop-daemon call has been substituted. Job done. I |
50 |
can now move on to the next problem. :) |
51 |
|
52 |
-- |
53 |
Rgds |
54 |
Peter |