So... another week another minor server crisis. This one was brewing for a while - we've been getting memory errors/upsets on our main internal file server (which hosts, among other things, all the files that make up the SETI@home web site). We got replacement memory, and were hoping for a quiescent moment to swap it out, but after two crashes in one day (on Tuesday) I just went ahead and did the swap.

So far so good (i.e. no further crashes), except we're still getting memory upsets in the server log. I only replaced 2 of the faulty DIMMs (which were noted as faulty by the motherboard), but maybe others need replacing as well.

In the meantime I found that project recovery today was significantly slowed by the result web pages on our site, so those are turned off at the moment (as I'm writing this).

Meanwhile other tasks this week included cleaning up the lab (the fire marshall is visiting today) and resurrecting SERENDIP code I haven't touched in over a decade. I got it to compile, now I'm just removing the non-fatal compiler warnings one by one. We'll use this code to help process Kepler data (which happens to be in a similar format to our old SERENDIP data). Maybe I'll even get back to analyzing the SERENDIP IV data set (also over a decade old and it may be worth taking another look at it with this code).

- Matt

____________
-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

@ Matt - I've been getting random memory errors on my home server for the last month, and bluescreen lockups, even with ECC memory.

Turned out to be a voltage regulator failure on the motherboard (affecting the memory termination voltage only) - the same memory is working fine in a replacement motherboard.

Might be worth checking voltages, if that motherboard has the right degree of instrumentation.

It also might be worth looking into seeing what the voltages the power supply are putting out. As was discovered/documented in my lengthy capacitor replacement thread, whilst bulged caps were part of the problem, the root of the problem was the power supply. After opening it up, every single capacitor in there is bulged and nearly to burst/ooze stage.

For days I have languished over my falling RAC; I am finally reading here that all is finally well in the land of Oz. Mr. Wizard: why, oh why does the server status say all is well in Oz, but in reality no project server can be found, either via proxy or direct?
____________

Is this why you have such a BIG problem keeping me full of SETI work? I've gone from 4,000+ units per day in late Jan (when I joined) thru mid Feb down to 2,400 and have often run compeletly out of work lately.
____________

That is exactly my point!! I went from 75K+RAC/day to ZERO. "Project has no tasks available." This does not keep my 5 systems happy at all. Now it is Friday; all personel have left for the weekend; and SETI is sitting idle (it seems).
____________

That is exactly my point!! I went from 75K+RAC/day to ZERO. "Project has no tasks available." This does not keep my 5 systems happy at all. Now it is Friday; all personel have left for the weekend; and SETI is sitting idle (it seems).

Your main problem could be the BOINC version that you're using, check out the Top Hosts table and see what most of the main setups are using (work is flowing here at a good rate). ;)

That is exactly my point!! I went from 75K+RAC/day to ZERO. "Project has no tasks available." This does not keep my 5 systems happy at all. Now it is Friday; all personel have left for the weekend; and SETI is sitting idle (it seems).

Your main problem could be the BOINC version that you're using, check out the Top Hosts table and see what most of the main setups are using (work is flowing here at a good rate). ;)

Cheers.

He's running 6.12.34, the most recent recommended version of the BOINC client... and well represented in the "top hosts" table
____________
.

Hi Folks,
I've re-installed the Lunatics apps:-) And once again I'm back to haveing ALL GPU tasks running in high priority mode.

Not only S@H but also E@H.

This doesnt apparently occur with CPU tasks.

Is this 'normal' behaviour?

Also since boinc is configured to use 100% resources in both S@H and E@H it 'normally' works at 50% for each, now however its persistantly running E@H GPU tasks non stop. Unless I suspend E@H, let S@H utilse both CPU & GPU then resume E@H.. If I then suspend S@H to let E@H CPU tasks get a look in [they take a long time and expire faster than S@H ones] Then I'm back to square one with E@H hogging the GPU..

So how does one adjust the priority of the GPU tasks. I dont know if this HP mode is detrimental to my GPU cards or not.. But I'm anyway wondering why its gone into hyperdrive as soon as Lunatics is installed

Another thing, it doesnt pick up dumped tasks and restart them, it grabs a new task and does that..
I see several tasks with various % done waiting to be restarted..
I guess they will eventually get to the top of the queue but I suspect only after all other WU are done..

That is exactly my point!! I went from 75K+RAC/day to ZERO. "Project has no tasks available." This does not keep my 5 systems happy at all. Now it is Friday; all personel have left for the weekend; and SETI is sitting idle (it seems).

Your main problem could be the BOINC version that you're using, check out the Top Hosts table and see what most of the main setups are using (work is flowing here at a good rate). ;)

Cheers.

He's running 6.12.34, the most recent recommended version of the BOINC client... and well represented in the "top hosts" table

That is exactly my point!! I went from 75K+RAC/day to ZERO. "Project has no tasks available." This does not keep my 5 systems happy at all. Now it is Friday; all personel have left for the weekend; and SETI is sitting idle (it seems).

Your main problem could be the BOINC version that you're using, check out the Top Hosts table and see what most of the main setups are using (work is flowing here at a good rate). ;)

Cheers.

He's running 6.12.34, the most recent recommended version of the BOINC client... and well represented in the "top hosts" table

Funny that, I see more of the later 6.10.xx versions myself there.

Cheers.

yes, but 6.12.34 is in there - so it isn't a problem with the client version... There's just more 6.10.60 clients out there...