Noticed today that one of my pc's downloaded a few Pirates wu's as well as the starboard 5.13 .exe. I thought to myself that's weird, that pc has been running that app for days. Today however it's downloading the same app every time it gets more work, 2-3 times since I've started paying attention to it.

I've seen rumors of troubleshooting, so is this a deliberate thing to load the server or is it somehow an effect of the server being loaded? Sorry in advance if this has been answered elsewhere, the site's too clogged for me to get response on forums search. If this is a load test it's a good one :)

No, it's not part of any testing.

I released 5.14 on July 4th, but deprecated it the day following. I wonder if it's related to that?

What version of the client and OS?

What other projects are active?

____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Noticed today that one of my pc's downloaded a few Pirates wu's as well as the starboard 5.13 .exe. I thought to myself that's weird, that pc has been running that app for days. Today however it's downloading the same app every time it gets more work, 2-3 times since I've started paying attention to it.

I did find it strange that any host that downloaded 5.14 continues to run only 5.14

Sorry for the delay, I just got home. 5.8.16 Windows client, XP Pro SP2
Other projects on that machine: Cosmology@Home was about it at the time.

I have no Pirates work on it now and I looked in the project directory and starboard 5.13 is gone, only starboard 5.14 is there. Makes sense since only 5.14 is listed in client_state.xml. I did verify the pc I'm talking about has been crunching with 5.13. So does Boinc not let you go backwards, i.e. erase older versions if a newer one exists??

... I just looked at another host and it does show 5.13 and 5.14 in client_state.xml but it also has current wu's on it. It should finish them shortly so I'll see what happens then. Edit: sure enough, I forced an update on this 2nd host when the work was done and it deleted the starboard 5.13 exe as soon as it acknowledged and removed the wu's from the client... and it's no longer in client_state.xml. So I'm guessing all 3 of my hosts are downloading 5.13 every time now. By "every time" I mean that if no Pirates wus are on the client already (waiting to run or be reported) and it downloads new work, it has to download 5.13 again.

If there's a quick fix I can apply at my end I'd like to hear it. And/or if there's any useful information I can provide please let me know.
____________

If there's a quick fix I can apply at my end I'd like to hear it. And/or if there's any useful information I can provide please let me know.

Just happily crunching, cap'n!
____________
Dragons can fly because they don't fit into pirate ships

Today however it's downloading the same app every time it gets more work, 2-3 times since I've started paying attention to it.

Normally I would do that but that particular version appears way too unable/damaging a version of the client, sorry.
I would think people wouldn't notice unless they watch for it, or look through their Pirates messages.
I'm travelling soon and will be offline for weeks and I think I will live with this and hope a 5.15 comes out sometime to make it moot.

Meanwhile to summarize: of my 3 boxes, 2 have run 5.14 and one never has. The fist two are downloading 5.13 and deleting it every time, the third is not.

I hadn't reported on the third because it can't seem to catch the window to download work amd prove my statement above, but it does have 5.13 in its project directory and no trace of 5.14, nor have I found a result in the database for that host with that version.

This is expected behaviour when an app is repealed. Only the latest version of an app is saved, older versions may be deleted to save space when not active.

Projects should rerelease the old app with a new version number to avoid this problem.
____________
BOINC WIKI

Dirty John Rackham

Normally I would do that but that particular version appears way too unable/damaging a version of the client.

This is expected behaviour when an app is repealed.

This is expected behaviour when an app is repealed. Only the latest version of an app is saved, older versions may be deleted to save space when not active.

Projects should rerelease the old app with a new version number to avoid this problem.

It's an extra bit of work to release a new version with a higher version number just because you decided you wanted to withdraw an app version. Hopefully it would be possible to get it to work as I've just described without the extra step?

Clients who've never heard of 5.14 will just use 5.13.

I don't think so. When this problem cropped up before the only solutions were resetting the project on the client side and releasing a new version on the project side.

That's the part I thought was weird -- I thought work units were tied to a particular version of their app, at least that was my impression from some other projects but I guess I need to do some reading. Also if 5.14 has been deprecated why would a client still run it?
All very curious ;)