Continued from thread 8857 (re moving BOINC from SSD to HDD)

Message boards : Questions and problems : Continued from thread 8857 (re moving BOINC from SSD to HDD)
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile el_gallo_azul

Send message
Joined: 19 Jan 14
Posts: 79
Message 57250 - Posted: 1 Nov 2014, 1:05:27 UTC - in response to Message 57233.  
Last modified: 1 Nov 2014, 1:05:47 UTC

Since you now should have the symlink there

Yes that symlink is there.

have you modified the icon/.desktop-file

No

Your account also needs to be a member of boinc group

I'm afraid I'm not sure exactly what you mean, but symlink /var/lib/boinc-client which goes to /mnt/InternalHDD/boinc-client/, and /mnt/InternalHDD/boinc-client/ itself, both have

Owner: BOINC core client
Group: boinc
Others: None
ID: 57250 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 57253 - Posted: 1 Nov 2014, 20:45:50 UTC - in response to Message 57250.  

Your account also needs to be a member of boinc group

I'm afraid I'm not sure exactly what you mean, but symlink /var/lib/boinc-client which goes to /mnt/InternalHDD/boinc-client/, and /mnt/InternalHDD/boinc-client/ itself, both have

Owner: BOINC core client
Group: boinc
Others: None

In Unix, user accounts are also member of a number of different groups. Adding your user account, el_gallo_azul, to 'boinc' group might get Manager working. Ubuntu should have some GUI tool to manage users and groups.

I have to admit I don't really have a clue why the Manager icon stopped working.
ID: 57253 · Report as offensive
Profile el_gallo_azul

Send message
Joined: 19 Jan 14
Posts: 79
Message 57254 - Posted: 1 Nov 2014, 21:15:59 UTC - in response to Message 57253.  

Adding your user account, el_gallo_azul, to 'boinc' group might get Manager working

That sounds worth trying.

sudo usermod -a -G boinc el_gallo_azul


That all looked hunky-dory, then I got this from a terminal which doesn't make any sense to me (again):

el_gallo_azul@W2600CR-850Pro:~$ groups
el_gallo_azul adm cdrom sudo dip plugdev lpadmin sambashare


Oh well. In any case, I suspended BOINC, rebooted, and clicked on the BOINC Manager icon.

It started! Done.
ID: 57254 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 57256 - Posted: 1 Nov 2014, 21:25:29 UTC - in response to Message 57254.  
Last modified: 1 Nov 2014, 21:25:40 UTC

Yeah, forgot to mention that log out+back in is needed after changing groups.
ID: 57256 · Report as offensive
Profile el_gallo_azul

Send message
Joined: 19 Jan 14
Posts: 79
Message 57258 - Posted: 1 Nov 2014, 22:17:02 UTC - in response to Message 57256.  

OK I think I understand. The command 'groups' gives the groups of the current user. Got it.

Well done for babysitting me successfully to the end of this thread.

I think as SSDs become more ubiquitous, and until the current SSD write-cycle limitation problem has been resolved, this process is likely to be useful for many people. In my opinion, it would be worth publishing it neatly and concisely in the user manual, perhaps under "Running BOINC: advanced".
ID: 57258 · Report as offensive
Claggy

Send message
Joined: 23 Apr 07
Posts: 1112
United Kingdom
Message 57259 - Posted: 2 Nov 2014, 1:29:36 UTC - in response to Message 57258.  

I think as SSDs become more ubiquitous, and until the current SSD write-cycle limitation problem has been resolved, this process is likely to be useful for many people. In my opinion, it would be worth publishing it neatly and concisely in the user manual, perhaps under "Running BOINC: advanced".

One problem there, the Debian/Ubuntu Repository Boinc isn't done by Berkeley, it's done by the Debian Boinc Maintainers, using their version of the Boinc source:

http://anonscm.debian.org/cgit/pkg-boinc/boinc.git

it would be better if you asked them for a method/instructions to move their installation to another drive on their package pages:

https://packages.qa.debian.org/b/boinc.html

Claggy
ID: 57259 · Report as offensive
boistordu

Send message
Joined: 8 Jan 12
Posts: 46
Belgium
Message 57443 - Posted: 7 Nov 2014, 10:23:39 UTC

hi guys. I'm new to debian. I was on ubuntu before.

So I ve followed all the instructions but I always have a computation error whith something like :
7/11/2014 11:22:00 | SETI@home | Output file 16se14ab.31251.390677.438086664208.12.105_2_0 for task 16se14ab.31251.390677.438086664208.12.105_2 absent



i took the example of seti because it s the simpliest to work with.
on ubuntu it wasn t a problem to change the directory but in debian seems to be a big one.


I have of course done the permissions process but it could be come from there of course. And I have done the symbolic link. anyone has an idea?
ID: 57443 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 57458 - Posted: 7 Nov 2014, 22:22:45 UTC - in response to Message 57443.  

Next time please include a link or some other way to find the host in question. Host 7425458?

With an error 'execv: No such file or directory' I'm afraid I have to ask what exactly did you do. The more details the better.
ID: 57458 · Report as offensive
boistordu

Send message
Joined: 8 Jan 12
Posts: 46
Belgium
Message 57499 - Posted: 9 Nov 2014, 20:24:31 UTC - in response to Message 57458.  

ID: 7425458 so that s correct
and sorry about the information. I wanted first a lead to investigate.

So I m working on debian now 7.7. As you know there aren t easy way to change the data dir of boinc. So I ve moved to one of my hdd. I've put the location in the init script and i ve made a sym link at /var/lib for boinc-client and it s a good link. After I ve try permission for only boinc and also permission for everyone. nothing works. But I think it find the folder because it write in it when it downloads the materials for the projects. Also If it can't find the folder usually, boinc don't start as simple as that.
ID: 57499 · Report as offensive
Profile el_gallo_azul

Send message
Joined: 19 Jan 14
Posts: 79
Message 57506 - Posted: 9 Nov 2014, 22:21:42 UTC - in response to Message 57499.  

I think that if you follow what I had to do, step by step, it will work. Each step makes sense (but for me, only once I knew that that step had to be done).
ID: 57506 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 57522 - Posted: 10 Nov 2014, 21:38:09 UTC - in response to Message 57499.  
Last modified: 10 Nov 2014, 21:41:23 UTC

Well, that wasn't much details. So, you've mounted what? Where? What filesystem? What mount options? In other words, what's in your /etc/fstab?

And logs. Shutdown the client, open std{out,err}dae.txt files and mark the last line in both of them. Then restart the client and wait until it has tried to start at least one task and failed. Then copy-paste all the new lines from both files to here. Don't use BOINC's Event Log, the files might have something from the failed app start that the Event Log doesn't have.

And lets make sure the science app files are ok. For S@H MB7 you should have setiathome_7.01_i686-pc-linux-gnu and/or setiathome_7.01_x86_64-pc-linux-gnu. Make sure the files exist and 'boinc' user has permission to execute them. What 'file' tells of them? Try to run them from command line yourself (but cd to temp directory first). [edit] 'ldd' should say 'not a dynamic executable' for them. Check that too. [/edit]


There's something weird in the exit code for the failed task. errno=2 is 'No such file or directory'. The exit code should match the errno but instead the exit code is 22. errno=22 is 'Invalid argument'.
ID: 57522 · Report as offensive
Previous · 1 · 2

Message boards : Questions and problems : Continued from thread 8857 (re moving BOINC from SSD to HDD)

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.