Forum > Windows
WARNING - unified installer may (currently) delete all work units
Pynda:
Windows 7 64 bit
Intel E8400, Nvidia GF8800 GTX
Boinc 6.10.18
Since a lot of people seem to be having this problem I thought I would start a new thread that has a subject which is a little more clear. The best information I've been able to find so far can be found in this thread, though (the possible?) workaround is still not explained simply enough that I myself would be tempted to try it.
http://lunatics.kwsn.net/windows/help-i-guess.0.html
The problem comes about because the project doesn't have separate applications for the windows_x86_64 platform, so the work downloaded for stock uses an <alt_platform> mechanism to enable use of the windows_intelx86 applications. The <alt_platform> mechanism isn't available in app_info.xml so the work is deleted because you no longer have windows_intelx86 applications.
It is possible to put <platform>windows_intelx86</platform> entries in app_info.xml for each app_version, but that causes other problems under some circumstances. We've thought about doubling the number of app_version sections to have both platforms listed for each, but that's untested.
I think I'd edit BOINC's client_state.xml if I were making that transition. First I'd do the optimized install, then change the platform for each <result> listed in client_state.xml to windows_x86_64 before starting BOINC again. Since you are smart enough to make a backup, you might try this approach.
My own trouble is that I just did a fresh install of Win7 64 bit, installed Boinc and Seti, and got a whole buttload of work units (30+) because my preferences hadn't kicked in yet. And now I'm pretty sure these WUs are gone for good. I also wasn't smart enough to back them up before I installed Seti Optimized - allthough I did read the FAQ first and saw no mention of this particular horror.
- Is there any way to cancel these lost work units? Let alone having all of them go unfinished for the next month, I'm actually afraid I might be kicked from the program.
- If anyone can do a step by step explanation for dummies on how to currently install optimized (64 bit is the problem area?), I'm sure others here might appreciate it.
- Shouldn't the current installer be withdrawn, or at least a very strong warning placed next to the download and in the install FAQ until these issues are resolved?
Here's my app_info.xml in case it will help with anything. It looks to me like the astropulse units are still listed (the WU themselves may also still be around?), but that all the CUDA files have been dumped and are not listed.
--------------------------------------------------------------------------------------------------------------------
E:\BOINC\Program Data\BOINC\projects\setiathome.berkely.edu
- <app_info>
- <app>
<name>setiathome_enhanced</name>
</app>
- <file_info>
<name>AK_v8b_win_x64_SSE41.exe</name>
<executable />
</file_info>
- <app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
- <file_ref>
<file_name>AK_v8b_win_x64_SSE41.exe</file_name>
<main_program />
</file_ref>
</app_version>
- <app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
- <file_ref>
<file_name>AK_v8b_win_x64_SSE41.exe</file_name>
<main_program />
</file_ref>
</app_version>
- <app>
<name>astropulse_v5</name>
</app>
- <file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable />
</file_info>
- <app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
- <file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program />
</file_ref>
</app_version>
- <app>
<name>astropulse_v505</name>
</app>
- <file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable />
</file_info>
- <app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
- <file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program />
</file_ref>
</app_version>
</app_info>
Pynda:
If it may be of any help, "Reset" ing the project did nothing to cancel my outstanding work units. Perhaps that command is based off information that needs to be in the app.xml file? And even more disappointingly, "Detaching" from Seti@home didn't work either. I waited a couple of days and then rejoined, and there were all the same incomplete work units still outstanding on my results page. Guess there's nothing left to do but to let them time out.
Jason G:
Having the same issues here. Something has changed in recent version(s) of Boinc that has made it dump tasks when a new application is installed via the installer... Will be investigating a bit later in the week.
To release tasks to other users would require a full detach followed by reattach. Unfortunately that resets back to stock applications, for which then boinc immediately attempts to download tasks ... It appears these are being marked with *something* incompatible with the current installer version, so tasks are dumped (rather unceremoniously, creating 'ghost tasks'), and new ones downloaded.
Whether this probllem is isolated to Windows 7 x64, combined with current Boinc version, or that the issue applies to 32 bit OSes / apllications now also, is unclear.
For now, the best advice I can think of Is to run your cache down prior to installing the optimised applications.
Jason G:
We beleive we have isolated the mechanism to blame, primarily that the project in fact does not actually have or distribute any stock Windows x64 applications, whch means stock tasks are marked with windows_intelx86 platform.
We will verify and incorporate in the next installer release, platform tags to match stock applications. This should smooth new installation, but could potentially cause complications for existing optimised installations.
I have added the following warning to the Installer v0.2 release info page & Readme FAQ.
[WARNING - drain cache first, recommend detach/reattach as effective release of tasks prior to installation] Added 30th November 2009
Doing this before installation should minimise the number of tasks that need to time out, by releasing them to other users, and restore the instalaltion to a 'known state'.
Jason
k6xt:
Hope I am in the right thread for this. On a laptop Dell M6300, XP 64 bit, FX1600GPU 256MB, Core 2 Duo T9300, RAM 4GB. Running BOINC/SETI without optimised apps everything seems OK. I get CPU and GPU WU.
I flushed my cache, set SETI temporarily to "no new tasks". I installed using the Windows 64 bit unified installer, enabled new tasks. I get no WU downloads. My other PCs, all 32 bit versions of XP or W7, are not having problems.
Only this msg is returned, and the same without "Update requested by user" if I leave the PC alone for a time:
1/22/2010 9:05:59 AM SETI@home update requested by user
1/22/2010 9:06:02 AM SETI@home Sending scheduler request: Requested by user.
1/22/2010 9:06:02 AM SETI@home Requesting new tasks for GPU
1/22/2010 9:06:07 AM SETI@home Scheduler request completed: got 0 new tasks
1/22/2010 9:06:07 AM SETI@home Message from server: No work sent
1/22/2010 9:06:07 AM SETI@home Message from server: No work is available for SETI@home Enhanced
1/22/2010 9:06:07 AM SETI@home Message from server: No work is available for Astropulse v5
1/22/2010 9:06:07 AM SETI@home Message from server: (reached daily quota of 10 tasks)
1/22/2010 9:06:07 AM SETI@home Message from server: (Project has no jobs available)
I thought to try the fix posted below. But of course I have no SETI <results> in client_state.xml.
Any hints what I should try next?
Thanks Art
Edit: According to SETI Server status there are plenty of WU available.
Edit2: BOINC is installed as a service.
Navigation
[0] Message Index
[#] Next page
Go to full version