Is there a way to get the ghost WU to go away from my account, so they can be sent out again. Because with the tips here it seems like my computer is geting real WU again and working on them. Now justwaitng tofinishone to see if it´s reported and validated tosee that averything is working again.

I dont no if this is the right thread or not but i'm so over this ..... out of all the wu's i downloaded across 5 machines i have 261 wu's left to crunch but when i checked my results page it turns out it supposedly downloaded out of whats left 395 wu's ..... i'm curious wheres the other 134 there not on any of the puters ...... are these the ghost wu's u've all been on about ?

---

...... are these the ghost wu's u've all been on about ?

Yes.

...... are these the ghost wu's u've all been on about ?

Yes.

thx Richard :) i gather theres nothing i can do but to wait for them to become overdue and disapear out of my results

...... are these the ghost wu's u've all been on about ?

Yes.

thx Richard :) i gather theres nothing i can do but to wait for them to become overdue and disapear out of my results

They will go away as the expiration date comes/goes, then they will be re-assigned.

I have many, many of them as well as I suspect everyone does.

---

I’m not sure what you mean by “the right app”. It is the optimized app I’ve been using all along, but now BOINC’s Tasks tab says it’s the stock v5.13. The host is only halfway through the batch of WUs it downloaded, and none have been reported yet, so I don’t know what BOINC will tell the servers about it.

Update: Just reported about half the results my G5 downloaded last night, looking pretty good. Most validated, a few pending, one checked-but-no-consensus. Reported as v5.13, just as shown in BOINC Manager.

My plan at present is to let the remaining tasks finish & get reported before I do the app_info switcheroo again, just to test Joe & Richard’s theory that it won’t work again with no tasks on board.

I’m not sure what you mean by “the right app”. It is the optimized app I’ve been using all along, but now BOINC’s Tasks tab says it’s the stock v5.13. The host is only halfway through the batch of WUs it downloaded, and none have been reported yet, so I don’t know what BOINC will tell the servers about it.

Update: Just reported about half the results my G5 downloaded last night, looking pretty good. Most validated, a few pending, one checked-but-no-consensus. Reported as v5.13, just as shown in BOINC Manager.

My plan at present is to let the remaining tasks finish & get reported before I do the app_info switcheroo again, just to test Joe & Richard’s theory that it won’t work again with no tasks on board.

I tried it this morning (here), and got Joe's expected result: but I've just tried it again using an older client (BOINC v5.3.12.tx36 for windows_intelx86), and got an immediate download/allocation to stock even with optimised apps still in the cache. Further experimentation on different platforms/clients will be useful.

Is there a way to get the ghost WU to go away from my account, so they can be sent out again. Because with the tips here it seems like my computer is geting real WU again and working on them. Now just waiting to finish one to see if it´s reported and validated to see that everything is working again.

Yes there is.

1. Completely drain your SETI queue and report all work completed.
2. Detach from SETI project (DO NOT *uninstall*). If you run multiple projects and uninstall BOINC, you will lose any work from those projects.
3. Attach to SETI project again (do not install optimized apps at this time)
4. If downloads do not start immediately, you may have to manually update a few times.

If you're not installing/reinstalling an optimized app, you're done. Crunch-on.
If you want to run an optimized app:
5. Once you have downloaded as many WUs as SETI will let you have, set no-new-work.
6. Shutdown BOINC and install optimized app.
7. Restart BOINC and let as least 1 SETI WU begin processing.
8. Shutdown BOINC and rename app_info.xml in SETI project folder to some save-name
9. Restart BOINC (do NOT set allow-new-work)
10. Crunch until queue is empty and all work reported (may have to do manual update)
11. To get more work, restart BOINC and set allow-new-work
12. Once you have downloaded as many WUs as SETI will let you have, set no-new-work.
13. Shutdown BOINC and rename saved app_info.xml in SETI project folder back to app_info.xml.
14. Repeat steps 7-13 until SETI/BOINC fixes this problem.

Obviously, if you have a large farm (or even a moderate one), this is impractical to do long term, so you might just run the stock app (steps 1-4) until SETI/BOINC is fixed.

[edit typo]

Carsten posted some interesting observations and instructions in a new thread.

I haven't verified his workaround yet, but it seems logical and should work.

It also will not need manual intervention at all after being installed, but it does require you to empty your cache before you do it. Using his method, you can continue using optimized apps without an app_info.xml.

Regards,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

I seem to be able to download units on both machines now, all I did was change the app_info.xml file, and change it back. Things seems to have cured themselves. Using both Alex and Simons optimized apps with no problems.

Yes, but just the two entries: one for v5.13 and one for v5.17 because of the ‘crossed wires’ with Beta.

That bug was fixed with 5.8.x, I believe. I haven't had that entry since upgrading to 5.8.x a while back, and everything works fine.

---

Dublin, California
Team: SETI.USA

Speculation on my part: since you mention Beta, do you have one of those multi-version app_info, with a version_number for stock and a version_number for Beta (and possibly some spares as well), all referring to the same application?

Yes, but just the two entries: one for v5.13 and one for v5.17 because of the ‘crossed wires’ with Beta. The tasks and results crunched by the optimized app have always been labelled v5.17 up to now.

When running with app_info.xml the Scheduler does not tell the core client which version to use, the client simply assigns work to the highest version of setiathome_enhanced it knows about and includes that version number when reporting.

When running without app_info.xml, the Scheduler tells the core client to use a specific version. If client_state.xml has an <app_version> section with the correct number which is already in use, the core client uses it for the new work too. Having additional <app_version> sections with different numbers has no effect.

                                                               Joe

Yes there is.

Basically, you are right RandyC, only too complicated.
My method is following:
1. Finish last unit.
2. Detach from the project.
3. Attach to the project again.
4. Copy in the optim files if used.
5. Restart BOINC.
Done.

---

Has anyone figured out a workaround for those of us that use an "anonymous platform". That is, platforms that are not officially supported?

Thanks.

---

Yes, please check out this thread.

Works fine for me on multiple hosts, and has just re-fetched work cleanly.

HTH,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

Yes, please check out this thread.

Works fine for me on multiple hosts, and has just re-fetched work cleanly.

HTH,
Simon.

Simon,

I think he means platforms like OS/2 Warp, HP-UX etc. - the ones that anonymous platform was designed to run, for self-compile or user-group compile.

And Linux 2.6.16-20061110.ydl.2ps3, which is what he's using.

No, I'm afraid I haven't seen anyone post a work-round for them.

Richard's recipe worked for me too and got two nice new shiny wu's - hooray. Then got the chicken running and fiddled with my cache. Requested more work and got none AND 4 ghosts - silly-billy.

I'm glad it worked for you. But you need to fiddle with the cache, and do all the work-fetching, while still in standard mode - only switch back to optimised when you've got enough work to keep you occupied.

I am assuming this recipe is written for those running BOINC and Seti under some variation of Windows.

I am not running Windows and when I try to follow the recipe I get "Message from server: platform 'i386-pc-os2-emx' nt found" messages after an update with the app_info.xml file renamed.

Also, there are parts of the recipe which I do not know how to mimic on my system.

Is there a recipe for those not running under Windows?

---

I have a feeling this method only works in cases where your platform is officially supported. For those of you that MUST use an app_info.xml, I suspect you are out of luck for now.

This method should work fine for platforms windows_intelx86 and i686-pc-linux-gnu (at least, since I have these).

---

You should be able to add Mac OS/X 10.3+, Mac OS X/Intel and SPARC/Solaris (so good, they named it twice) - anything listed on the Applications page - to SKutnar's list. But nothing else.

Simon,

I think he means platforms like OS/2 Warp, HP-UX etc. - the ones that anonymous platform was designed to run, for self-compile or user-group compile.

And Linux 2.6.16-20061110.ydl.2ps3, which is what he's using.

No, I'm afraid I haven't seen anyone post a work-round for them.

I have a feeling you're probably right about that, on second thought. I "solved" my 64-bit BOINC problem by reverting to 32-bit with a 64-bit science app (which does work with the workarounds)...

However, that's not a solution for most people running nonstandard platforms, x86_64 has it easy compared.

Regards,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information