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: 8
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1127 times and has 7 replies Next Thread
fablefox
Senior Cruncher
Joined: May 31, 2010
Post Count: 168
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Upgrade to 64 bit - how to work on old job?

First, I've installed 6.2.28 from this site. As I waiting a job to finish, reading more about World Community Grid, news, etc, I realized that there is 64 bit version at BOINC (not WCG). Thinking that the calculation will be done faster (I hope) I installed the stable .56.

The problem is that the .56 (65bit) didn't read the .28 (486) data.

Anyway, since I didn't uninstall the old 32 bit one, is there a way I can run it instead of the current one - just to finish some of the job and stop taking new ones.

Or is there a way to move the work to current 64bit installation.

I notice now there is two drop down of the same name (User-PC) at my result page, with jobs from both current and old installation. So what will happen if I didn't run old job?

If the workaround didn't worth it I'll just focus on future jobs (and turning my netbook into cruncher) and let bygones be bygones.
----------------------------------------
[Jun 1, 2010 1:19:14 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Upgrade to 64 bit - how to work on old job?

fablefox,

there's JDI and RBA. The 64 bit client assumes that those who install it want 64 bit science apps, so it does not migrate the data. Since you went with the JDI method, a new client was created, so now you have 2 with the same name, the one registered before still having the tasks to it's name that were not finished.

All is not lost yet.

Stop work fetch in the BOINC Manager and do a project reset.

Identify the new data_dir which is listed in the message log, probably C:\ProgramData\BOINC

Stop the 64 bit client completely.

Copy the data_dir completely and delete all content.

Find the old data dir, probably in C:\program files (x86)\BOINC, but it could be in other places.

Copy that OVER into data_dir of 64 bit.

Start client.

Good chance is BOINC will continue with the previously assigned tasks.

Or you let it be and those tasks will expire on passing of the deadline.

6.10.56 is not exactly stable in terms of having full job timekeeping recovery skill... it can make a mess of it. It's been able to do that since release 6.6.38 at least and the issue only fixed in the alpha 6.10.57.... buggy is the reason WCG has not been jumping on the 6.10 for Windows upgrade bandwagon, but it's getting closer.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jun 1, 2010 1:47:53 PM]   Link   Report threatening or abusive post: please login first  Go to top 
fablefox
Senior Cruncher
Joined: May 31, 2010
Post Count: 168
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Upgrade to 64 bit - how to work on old job?

And I've decided to keep on working on new jobs, because:

a) too much hassle
b) current job goes to waste
c) data might not accurate due to 32 bit / 64 bit
d) current installation might get corrupted.

I notice that other people job is waiting to be verified against mine, but can these job being reset (abort) from the server so that it can be downloaded / sent to other people?

workunitId=155155158
workunitId=156524292
workunitId=155155083
workunitId=155155077
workunitId=155155068
workunitId=155155062
workunitId=155155059
workunitId=155154981
workunitId=155154975
workunitId=156523998

I know two or three of the job is completed - it was my first time using this app when I decided to install the 64 bit version.
----------------------------------------
[Jun 3, 2010 2:22:57 AM]   Link   Report threatening or abusive post: please login first  Go to top 
fablefox
Senior Cruncher
Joined: May 31, 2010
Post Count: 168
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Upgrade to 64 bit - how to work on old job?

Still, I notice that even if I set additional work buffer to 0.00, it still download two extra work unit instead of none if I update - which cause there are two new work unit coming. I plan work all of it before doing this - but there are always two new work unit. So where actually this 'stop work fetch' option anyway? I just want it to finish all job - stop downloading new one.
----------------------------------------
[Jun 3, 2010 2:26:55 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: Upgrade to 64 bit - how to work on old job?

on the projects tab, select no new tasks
[Jun 3, 2010 2:39:07 AM]   Link   Report threatening or abusive post: please login first  Go to top 
fablefox
Senior Cruncher
Joined: May 31, 2010
Post Count: 168
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Upgrade to 64 bit - how to work on old job?

Ah..... thanks. Tonight I will try it again since I can finish all the current work.
----------------------------------------
[Jun 3, 2010 4:05:39 AM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Upgrade to 64 bit - how to work on old job?

Still, I notice that even if I set additional work buffer to 0.00, it still download two extra work unit instead of none if I update
If they are coming long before the end of the currently processed tasks it is probably because your "Connect about every..." parameter is not null. The actual cache size is the total of both parameters (connect + extra).

In my opinion, regarding your former 32-bit installation, reasons a and d of your previous post are good enough for forgetting it and going on with your new 64-bit setup.
When these WUs will reach their deadline they will be redistributed and that's all. Don't worry about it, it happens every day that a device "disappears" like that, and probably several times each day. smile

The techs would not even try to anticipate their redistribution although you were kind enough to give their ids. With the current ~700,000 WUs-a-day such micromanagement is simply not a valid option for them.

Thanks again for having tried to help.
Jean.

Edit: Reasons a and d (not a and b as I have miskeyed initially)
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
----------------------------------------
[Edit 2 times, last edit by JmBoullier at Jun 3, 2010 8:51:56 AM]
[Jun 3, 2010 8:50:01 AM]   Link   Report threatening or abusive post: please login first  Go to top 
fablefox
Senior Cruncher
Joined: May 31, 2010
Post Count: 168
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Upgrade to 64 bit - how to work on old job?

Sekerob - it didn't recognize any old file, which is to say it didn't work. Maybe it's the 32 bit & 64 bit thing. At least now I know how to use BOINC better.
----------------------------------------
[Jun 3, 2010 2:22:38 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread