Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go ยป
No member browsing this thread
Thread Status: Active
Total posts in this thread: 6
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 788 times and has 5 replies Next Thread
sunheng
Cruncher
Joined: Apr 12, 2005
Post Count: 2
Status: Offline
Reply to this Post  Reply with Quote 
aborting an overdue project

I am running BOINC client on Linux by command line execution of "boinc". Since it is run manually (I did not put it into a cron job), I forgot to do this for over a month. So these days I always get a message like:

2006-06-20 22:53:46 [World Community Grid] Result faah0371_d203n878_x1hpv_01_1 is 54.90 days overdue.
2006-06-20 22:53:46 [World Community Grid] You may not get credit for it. Consider aborting it.

So it seems I should abort the current project and fetch a new one. Before doing so, is there a way for me to know if the project has been performed by someone else?

Actually, I want to ask a more aggressive question. It seems boinc executible must be invoke with a project id specified. Is there a "dummy" mode of the program so that it could commucate with the server often and switch to the most needed project when appropriate? What I really want to see is something like Windows program -- I never worry about which project I should participate, which job I should run.... etc. I render all the decision makings to the program.

If I can have this "dummy" mode of boinc, then I would not need to worry about "overdue project" or "consider to abort", which I really have no idea how to proceed without spending lots of time to dig deeper on WCG help and forum -- and usually forget what I learned several days later.
[Jun 21, 2006 4:14:42 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: aborting an overdue project

I don't believe that you have to run the program from the command line any more. I think the same BOINC Manager program that automates things on Windows systems is also available for Linux now. A Linux version of what appears to be the whole BOINC 5.4.9 software set is available at Berkeley's web site.
[Jun 21, 2006 4:55:10 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: aborting an overdue project

RickH is correct, there is a GUI for Linux BOINC but you may not be running X . You can do anything from the command line that you can do with the GUI, I think, by using the appropriate switches/parms.

You have referred to faah0371_d203n878_x1hpv_01_1 as a project. Actually we call that a Work Unit or WU. The "result" referred to in the message you got from BOINC is the file containing the results of computing the WU. Project refers to a collection of thousands of WUs related to 1 research goal. Right now WCG has 2 projects, the Fight Aids at Home project and the Human Proteome Folding project (FAAH and HPF).

Abort your WU. It has certainly been assigned to someone else. Don't worry about it, happens all the time.

Your WU is so far past due date it may not appear in your records anymore. Normally, you can see the status of any WU assigned to you by logging in here at WCG website. Go MyGrid->Device Manager->Results Status to see a list of your WUs and a few details on each WU. Click on a WU in the list and a window pops up showing more detail on that WU. There you will see that the WU has been sent to at least 3 hosts. The copy sent to you is orange highlighted. They send each WU to 3 hosts and compare the 3 results returned. If a host does not return a result within 7 days then they send the WU to a 4th host. When they get 3 results that match (a quorum of 3) they declare it valid.

If you abort the overdue WU then BOINC should automatically retrieve another WU for you. If it does then you will be able to track the progress of the WU as I described above. If you have time, check in every 6 hrs. for a few days and watch how the info changes on the status pages. You'll get the hang of it fairly quick.

I am a recovering Windows luser who has almost finished converting over to Linux. I did have BOINC with GUI working on Linux a month ago but I broke it and haven't bothered to fix it yet. I hope the above info pertaining to Linux is correct and trust someone else will correct any mistakes and fill in any blanks.
[Jun 21, 2006 7:02:37 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: aborting an overdue project

As others have said, a GUI is available for Linux. Just run boincmgr.exe

If you do need to run BOINC from the command line, then there are startup scripts available to handle this for you. Also, you only need to provide the project URL the first time, when you are attaching to the project. On subsequent occasions, you can run boinc with no parameters, and it will happily crunch and download more work automatically.
[Jun 21, 2006 12:23:28 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sunheng
Cruncher
Joined: Apr 12, 2005
Post Count: 2
Status: Offline
Reply to this Post  Reply with Quote 
Re: aborting an overdue project

Thanks for all your helps. I also get some basic understandings on how this works -- no wonder I have run so much time on my two computers but only got 3 results: most of them were not credited since I ran them on and off.

No pain, no gain. So I went through the tutorial at
http://www.spy-hill.net/~myers/help/boinc/unix.html#start
And confirm that running GUI on Linux is a piece of cake. I also make boinc a cron job as suggested in the tutorial -- yes, my linux box has no monitor attached. I have to use either VNC or some X server.

The only peice of confusion in that tutorial (or in the boincmgr program) is about how to initialize. Since boinc is run as a cron job as user "boinc" (suggested in the tutorial), "root" does not need to set password for the user boinc. Then I could not "Select Computer" I want to admin. So I have to create "boinc" as a regular user and log in as "boinc" to run boincmgr.

The program boincmgr seems having a bug here. Once I "Select Computer ..." in the menu, I am always prompted for a password unless I run boincmgr as the user who runs boinc client. Actually, according to "boinc --help", there is no way I can set up a password for boinc client at all. Then which password should I supply? While I ran boincmgr as another user, I tried to type in the password of user "boinc" to "Select Computer..." but I got denied. If I cannot even run boincmgr as a user other than the user running boinc client, how can I remotely admin boinc client using boincmgr?
[Jun 22, 2006 5:29:40 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: aborting an overdue project

The password you are looking for when you "Select Computer" in the menu is in a file called gui_rpc_auth.cfg in the BOINC directory on the machine you want to access remotely. BOINC writes that file and password the first time it runs. You can change that password to something easier to remember but you might have to restart BOINC before it's recognised. One other thing you must do is create a file remote_hosts.cfg in the BOINC dir. In that file you list, one per line, the hosts that are allowed remote access.
----------------------------------------
[Edit 1 times, last edit by Former Member at Jun 22, 2006 10:29:11 AM]
[Jun 22, 2006 6:09:29 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread