Panic Mode On (46) Server problems

AAKKKKKKKKKKKKKKKKK!!! I got a herd of work but they are all shorties!!!! Man, it won't take anytime at all to run through them.
____________


PROUD MEMBER OF Team Starfire World BOINC

I must be 1 of the lucky 1's as my 3 PC's have been able to top up at the right times so I don't have any complaints. :)

Cheers.
____________

Mine have stayed pretty much filled for the past 2-3 weeks.

I say pretty much because every now and then, one AP runs 50% longer for no apparent reason and throws the DCF waaaay out, and then BOINC thinks I have 12 days of cache when it is really only ~8. Takes about a dozen tasks to complete with a normal duration for the DCF estimates to come back down to a reasonable number..and then it happens again.

So pretty much, every time my machine does actually ask for work, it usually gets a task or two.
____________

Linux laptop uptime: 1484d 22h 42m
Ended due to UPS failure, found 14 hours after the fact

That used to be true (technically, still is, but usually less than 5,000 seconds). When the pre-blanked WUs started happening, the observed effect is completely random. I have a spreadsheet of every AP I've ever done while using the optimized apps, and there's no correlation between the tasks running significantly longer and any aspects about the WU itself (amount of blanking or number of pulses found).

For example..

A while back, I had a task that had zero blanking, yet took 122,000 seconds. 14 WUs later, another zero blanked task took 88,000 seconds.

Inversely, I have one that had 91.06% blanked and took 96,000, whereas that recent one has 92.72% and took 121,000. It's random.

I've talked to Josef about it and there's a theory that it is one of the optimizations that started in r292 and can suffer tremendously from heavy L1/2 cache usage by other processes. Just a theory. The other theory is that it's probably a case of what has been known for a while about MB being on multiple cores and having bottleneck issues without some other kind of task running as well.
____________

Linux laptop uptime: 1484d 22h 42m
Ended due to UPS failure, found 14 hours after the fact

It seems the scheduler is disabled, and the cricket graph output has dropped.

Steve

It seems the scheduler is disabled, and the cricket graph output has dropped.

Steve

Is it Waily! Waily! time?

Methinks probably a disk punted itself from an array and caused everything to lock up, and scheduler was remotely disabled. That's my guess.
____________

Linux laptop uptime: 1484d 22h 42m
Ended due to UPS failure, found 14 hours after the fact

Well I'll be ok for a while yet before I start panicking. ;)

Cheers.
____________

any ideas as to what went wrong