That would be molasses in January with a liberal sprinkling of "503 system not available " results.

Cheers

Yup; recent new WUs have numbers up in the high 5233xxxxx range and the low 5234xxxxx range and retries for high 519XXXXXX WUs are now getting trapped...

A couple of my Pending Validation tasks that had been held up actually validated, but in both cases that turned out to be because the No Reply result that spawned the stuck retry had eventually returned nearly 60 hours after the deadline :-)

I have seen some recent successful retries amongst wingmen but they are all for WUs where one of the initial tasks failed (or was user aborted or detached) fairly early -- I have only received one retry since this issue appeared (and that showed up just under 3 days from the initial tasks being issued...)

It's sometimes difficult to know the best place for us to post potential issues such as this if we want to catch someone's eye.

Some topics (such as there being lots of 503 errors and long waits or timeouts on the non-BOINC parts of the system) have News items we can post into; even if they are quite old, TigerLily seems to spot them eventually :-) The same is [mostly] true for new posts in the Website Support forum.

However, this particular issue isn't really Website related and it appears that posts in the MCM1 forum don't seem to have been picked up; perhaps the latest manifestation of this Chat Room thread should be on the "must read" list :-)

(And if the non-BOINC servers are playing up [as is presently the case] trying to use "Contact us" is impossible...)

Cheers - Al.

P.S. whilst building this message and using preview I got a dozen or so 503 errors and each page refresh that worked took about 30 seconds; I think that something in the database interface might have got messed up again -- it only ever seems to manage a few days without some sort of congestion evidence showing up :-(

[Edit: the last preview was quick but it took three attempts to get it to post!]

The issue with "Waiting to be sent" tasks still isn't solved. My Results list should have been empty by now, since I do not crunch anything. I still have 8 tasks in the list, all of them due to the "Waiting to be sent".problem.

But at least, it's summer temperatures, and no ice or snow

A standard BOINC server set-up has quite a range of feeder options for control of which tasks get preference for being offered up. Some will tend to give precedence to tasks for newer WUs, and that would appear to be how WCG does it at present...

If the choice of options is designed to reduce the number of complaints about not being able to get work (often accompanied by the "committed to other platforms" message!) it certainly works -- however, it seems to result in this build-up of retries for older units (spawned by missed deadlines) that are waiting to be sent. Without knowing what options WCG have selected for MCM1, it's difficult to work out how bad the problem might become if there isn't an interruption in the supply of new work :-(

Personally, as we aren't going to be able to stop the missed deadline problem I'd rather we had to put up with people complaining about the lack of work for a relatively short period of time once (or twice?) a week rather than the build-up of waiting retries getting so large that when it does get cleaned up there may well be no new work for quite a long period (because of the "other platforms" issue plugging up the ready-to-send buffer on a fairly regular basis...)

By the way, some of my oldest results stuck at Pending Validation because of this issue have now been waiting for validation for nearly a fortnight, the retries having been stuck for over a week!

Cheers - Al.

TIGERLILY !!

Can you please pass on the issue "waiting to be sent" to the tech team.

Thank you.