since recovery all boxes have uploaded ok, except one. this box is trying to report 2500+ wus and am getting "sceduler request failed: internal server error" each time it tries to report the wus...

cheers

---

Is this your errant cruncher?
http://setiathome.berkeley.edu/results.php?hostid=6624102

A look at some of its more recent attempts at returning results gives that they have been returned by two users, and both have errored out, then there's a "system error" message to the effect that the WU has been cancelled. I wonder if this is a symptom of one of the RAIDs that required re-synching mentioned by Matt in one of his posts?

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

since recovery all boxes have uploaded ok, except one. this box is trying to report 2500+ wus and am getting "sceduler request failed: internal server error" each time it tries to report the wus...

cheers

Try upgrading to Boinc 6.12.x then use the following cc_config.xml

<cc_config>
   <log_flags>
   </log_flags>
   <options>
      <max_tasks_reported>200</max_tasks_reported>
   </options>
</cc_config>

I managed to report ~700 Wu's in one go yesterday, while Mark needed to use this to report his 1800 to 2400 Wu's

Afterwards uninstall 6.12.x and reinstall 6.10.58

Claggy

to be honest i don't know but it is a problem at this end ... and the cache on this machine is heading south and not topping up ...

the other boxes have errors as well so I guess its the work that we are getting, not the box itself ...

gonorrhea has about 171 errors out of 6577 in progress
scury has about 57 errors out of 5150 in progress
syphilis (box in question) has about 72 errors out of 2968 in progress

the laptop, 0 out of 698 ...

---

since recovery all boxes have uploaded ok, except one. this box is trying to report 2500+ wus and am getting "sceduler request failed: internal server error" each time it tries to report the wus...

cheers

Try upgrading to Boinc 6.12.x then use the following cc_config.xml

<cc_config>
   <log_flags>
   </log_flags>
   <options>
      <max_tasks_reported>200</max_tasks_reported>
   </options>
</cc_config>

I managed to report ~700 Wu's in one go yesterday, while Mark needed to use this to report his 1800 to 2400 Wu's

Afterwards uninstall 6.12.x and reinstall 6.10.58

Claggy

I really don't want to upgrade to 6.12.xx at the moment. All the others are on 6.whatever at the moment and are fine ....

---

since recovery all boxes have uploaded ok, except one. this box is trying to report 2500+ wus and am getting "sceduler request failed: internal server error" each time it tries to report the wus...

cheers

Try upgrading to Boinc 6.12.x then use the following cc_config.xml

<cc_config>
   <log_flags>
   </log_flags>
   <options>
      <max_tasks_reported>200</max_tasks_reported>
   </options>
</cc_config>

I managed to report ~700 Wu's in one go yesterday, while Mark needed to use this to report his 1800 to 2400 Wu's

Afterwards uninstall 6.12.x and reinstall 6.10.58

Claggy

I really don't want to upgrade to 6.12.xx at the moment. All the others are on 6.whatever at the moment and are fine ....

A hundred at a time worked a charm for me........
Gawd, if not for the forums and their work arounds............sheesh.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Try renaming your computers - LOL!

Actually I'm in the same situation - I'm not going anywhere near an upgrade, so am just going to leave it.

Try renaming your computers - LOL!

Actually I'm in the same situation - I'm not going anywhere near an upgrade, so am just going to leave it.

In that case, the likelihood is that all the work you computed during the outage, and all the electricity you used, will have gone to waste.

As Claggy said, if you temporarily install BOINC 6.12 to use the reporting facility, there's nothing to stop you returning to your comfort blanket afterwards.

Try renaming your computers - LOL!

Actually I'm in the same situation - I'm not going anywhere near an upgrade, so am just going to leave it.

In that case, the likelihood is that all the work you computed during the outage, and all the electricity you used, will have gone to waste.

As Claggy said, if you temporarily install BOINC 6.12 to use the reporting facility, there's nothing to stop you returning to your comfort blanket afterwards.

And the whole procedure can probably be done in 15 to 20 minutes, and 5 minutes after that they could be refilling their cache again,

Claggy

Try renaming your computers - LOL!

Actually I'm in the same situation - I'm not going anywhere near an upgrade, so am just going to leave it.

In that case, the likelihood is that all the work you computed during the outage, and all the electricity you used, will have gone to waste.

As Claggy said, if you temporarily install BOINC 6.12 to use the reporting facility, there's nothing to stop you returning to your comfort blanket afterwards.

Infernal server errors......
Sufferin' succhotash.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Try renaming your computers - LOL!

Actually I'm in the same situation - I'm not going anywhere near an upgrade, so am just going to leave it.

In that case, the likelihood is that all the work you computed during the outage, and all the electricity you used, will have gone to waste.

As Claggy said, if you temporarily install BOINC 6.12 to use the reporting facility, there's nothing to stop you returning to your comfort blanket afterwards.

Infernal server errors......
Sufferin' succhotash.

Yeah, I just had to do it. Upgrade, write a cc_config, restart, hit "update" about 20 times...

But... I just freakin' left it upgraded. With the limits off, it's not so bad.

Now if the @#$% thing makes me downgrade, I've gotta start over from scratch since I used the 7.x BOINC to upgrade-to. I'm hoping that with limits lifted that its "backing-off" up to a couple of days isn't going to bother me.

Someone better tell someone to do whatever is necessary to fix this reporting bug, though. The longer and more total the outage, and the bigger the cruncher, the more likely more work will be crunched and uploaded, but unreported.

That kinda vacuums a basketball through a garden hose.

In which case 6.12.xx it is.

That's one hell of a bug - think of all the people who set-&-forget & will end up in a situation where they can't report... Guess it's because it's an older version.

That's one hell of a bug - think of all the people who set-&-forget & will end up in a situation where they can't report... Guess it's because it's an older version.

I doubt many of of the set-and-forget crowd will be trying to report thousands of tasks at a time.

I just had a thought.

Someone who really knows what they are doing instead of "hacking at it" like I do should start a thread, make it sticky, name it something identifiable like "Can't Report? Read This!!!" and put CLEAR and concise instructions as to what BOINC version can be "fixed," how to upgrade to a newer version, point to it, tell how to write the necessary cc_config file (or better still, make one downloadable from somewhere), where and how to find the path to the BOINC data directory, and make it EASY on people to apply this work-around.

Probably ought to be here, and in help, and in wherever Q&A is found.

What a pain.

I think it would be easier to do it server-side since someone who knows what they are doing could do it once and cover multiple BOINC versions; IF that can be done.

It would save a lot of lost work, frustrated users, etc.

I couldn't even discover why three of my computers with similar backlogs could successfully report but the fourth one couldn't.

I had a computer lose communication with my network during the outage. When the project came back up I reconnected it and watched it uploading results, I was amazed, befuddled, and dumbfounded watching the uploads.

Zip,zing,whiz,zip,slam,whoosh... Pages and pages of uploads only took a few minutes.

Somebody did something good.

I expected it to take days to upload the completed work at 0.05kbps.

That's one hell of a bug - think of all the people who set-&-forget & will end up in a situation where they can't report... Guess it's because it's an older version.

I doubt many of of the set-and-forget crowd will be trying to report thousands of tasks at a time.

I hope you are right, Richard.

The computer of mine that got stuck just has a pair of GTX 560ti cards in it and only two CPU cores crunching. That's not really that exotic these days, and is nothing for dedicated gamer rigs.

If you get some shorties in there, add four days of project lack of communication (for whatever reason; lab or lost internet connection while you're away for the weekend), and suddenly 2,000 WUs waiting to report aren't really exclusive to SETI enthusiasts.

I only crunch SETI.

Is this phenomenon happening over at Einstein? I guess I'm asking if it's a BOINC thing or a SETI@Home thing.

Wow it worked - thank you very much.

Having the rest of this Dairy Milk now to 'celebrate'...

That kinda vacuums a basketball through a garden hose.

When I was a younger man, I had a girlfriend like that once.......

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Wow it worked - thank you very much.

Having the rest of this Dairy Milk now to 'celebrate'...

Was that the dual 580 computer? Gaming rig?

Yes. No.

LOL! Always one for clear communications...