Just got back from 3 weeks leave and when checking my rig, noticed that it hasn't been reporting work, or at least 90% of my work, as I have nearly 5500 taks completed and ready to report on.

I keep getting
28/08/2012 08:39:18 | SETI@home | Scheduler request failed: HTTP internal server error

Is there an issue reporting work at the moment, as when I check other peoples stats, they seem to be getting work through OK??

Im on the latest client...

---

You've got machines on 6.10.58 and 6.10.56 at a minimum.

I looked for it for you, but I can't find the thread about this. There is one.

So... asked and answered, but I can't find the answer. I'm sorry. It's here, somewhere.


EDIT: I've searched again. Eyes at half-mast, I'm not doing you any good except to say that there IS a thread about it here somewhere. I'm sorry I couldn't find it. It's probably obvious, but I'm half-asleep.

No widespread problem. Server will choke on 5k tasks. Use this option in a cc_config.xml file's options section:

<max_tasks_reported>256</max_tasks_reported>

Then on BOINC's, select "read config file". Some options require a restart of BOINC, not sure about this one. A recent modification to the server ode limits acceptance to 256 tasks anyway.

If you're not familiar with cc_config.xml, here's some info:

http://boinc.berkeley.edu/wiki/Cc_config.xml

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

If you have around 5500 tasks waiting to report, you can only be talking about host 5828319, with 5341 tasks in progress.

That host is running BOINC v6.10.58, which is very far from "the latest" client - it was released in July 2010.

To escape from this situation, you will have to upgrade that client. Your best bet will be to install BOINC v6.12.34, which is available as an 'older client' from the 'all versions' download page. Make sure you pick the version (32-bit or 64-bit) which matches your current version of BOINC.

After upgrading BOINC, add a line to the <options> section of your cc_config.xml file (if you have one), or create a cc_config.xml file according to the instructions in client configuration. The line you need is

<max_tasks_reported>256</max_tasks_reported>

Choose 'Read config file' from the Advanced menu in BOINC Manager, or restart BOINC so the option takes effect anyway.

Then, it's probably best to set 'No New Tasks' while you clear the backlog. With those settings, you should be able to report them, 256 at a time: if you're not requesting new work, you don't have to wait 5 minutes between updates, so it should just be 20 mouse clicks - but do check between the first few updates that it's working properly. With BOINC v6.12, you'll find that the 'messages' tab has become an 'Event log' - accessible from the advanced menu again, or with the key combination Ctrl+Shift+E.

After you've finished, you can re-install BOINC v6.10.58 if you prefer it. The alternative route - installing the current, recommended, v7.0.28 - cuts you off from that downgrade: the changes it makes to your client_state file are not backwards-compatible.

The site is out of date as I upgraded to 7.0.28 this morning when I arrived as I thought that might be the issue.
I downgraded to 6.10.58 a while back when there was the work fetch issue, as 6.10.58 was much better at getting wu's than the newer code.
Im now on the newest version available.

Fred, Richard, the <max_tasks_reported> fix you both suggested has worked just fine and I am reporting as we speak, so I am happy, will see how the new client works out, if it causes issues, then I will run down all my wu's and then install 6.10.58 again, but for now Im willing to give it a go.

Many thanks guys for your prompt replies and help - it is appreciated

---