SETI has hiccuped again. Site is offline and the router graph has flatlined. Hope they can fixit easily in the morning when the staff comes in for the week.

Which is weird, as it's two different connections and systems. I mean, the 100Mbit pipe is only for data, their forums run off a separate 1Gbit pipe through campus. It's also different servers that it all runs on, so it sounds like a collective power-outage, but then how do we type on these boards? ;-)

Which is weird, as it's two different connections and systems. I mean, the 100Mbit pipe is only for data, their forums run off a separate 1Gbit pipe through campus. It's also different servers that it all runs on, so it sounds like a collective power-outage, but then how do we type on these boards? ;-)

It can't be either a connection, or a power, issue, for the reasons you state.

SETI has a number of different servers, and tends to have a separate server for each major BOINC function. At the moment, the file upload server and the scheduling server are both intact, and so is the BOINC database - reported results are being validated. But the download server and the web server are inaccessible.

Seti is back.

And now it seams to be down again and Milkyway too

Milkyway is still totally offline (been so for about 5 hours so far - 11AM PDT as I post). Of course with Milkyway, with their minimalist queues, being offline for more than an hour means out of work for users (on the GPU side).

Aqua remains in credit conundrum stasis -- perhaps they are discussing best approaches to deal with it -- though as of this morning, there has been no follow up from the project (nothing since Friday morning) on their home page or the message boards.

SETI of course is offline for their planned weekly outage (distinct from unplanned outages).

And now it seams to be down again and Milkyway too

I think the last time Milkyway had a big outage that Travis said that RPI would over the summer shut down non key IT Functions/Server rooms would be shutdown any time daytime temps were expected to top 90F. They say they are not in full session so students are not harmed by facilities being offline. Supposedly RPI gives them something like 1/2 hour notice to shut things down and then they turn the AC and Power off to that room/ Facility. This is supposed to be a cost savings for the University.

OK -- that makes some sense -- I shut down some of my farm during the day here. The issue for Milkyway of course is with their very short time cycle queues, that means folks run out of work very quickly. Then again, that is simply an incentive to carry multiple projects. These days there are at least four 'native' ATI GPU projects out there - Collatz, MooWrapper, Dnet, and Milkyway.

I think the last time Milkyway had a big outage that Travis said that RPI would over the summer shut down non key IT Functions/Server rooms would be shutdown any time daytime temps were expected to top 90F. They say they are not in full session so students are not harmed by facilities being offline. Supposedly RPI gives them something like 1/2 hour notice to shut things down and then they turn the AC and Power off to that room/ Facility. This is supposed to be a cost savings for the University.

And now it seams to be down again and Milkyway too

I think the last time Milkyway had a big outage that Travis said that RPI would over the summer shut down non key IT Functions/Server rooms would be shutdown any time daytime temps were expected to top 90F. They say they are not in full session so students are not harmed by facilities being offline. Supposedly RPI gives them something like 1/2 hour notice to shut things down and then they turn the AC and Power off to that room/ Facility. This is supposed to be a cost savings for the University.

It looks like it is a Scheduled Downtime I'm glad they informed us ;)

Regarding Milkyway, to a large degree it doesn't matter if downtimes are planned or not, the short queues mean you can't plan for an outage by stocking up in any manner, it just means that you need second (and third) projects configured and active.

The thing is, with MW, about the only way you can run it as a primary is to have the other GPU projects suspended. For me the reverse ends up being the case, the other projects get the GPU cycle time unless I manually intervene to push MW work units.

It looks like it is a Scheduled Downtime I'm glad they informed us ;)

Regarding Milkyway, to a large degree it doesn't matter if downtimes are planned or not, the short queues mean you can't plan for an outage by stocking up in any manner, it just means that you need second (and third) projects configured and active.

The thing is, with MW, about the only way you can run it as a primary is to have the other GPU projects suspended. For me the reverse ends up being the case, the other projects get the GPU cycle time unless I manually intervene to push MW work units.

It looks like it is a Scheduled Downtime I'm glad they informed us ;)

I run Folding@home as a backup to Milkyway so in my case it DOES mater to be informed if the mikyway server will shut down so I can put Milkyway on stand by and start Folding before going to work.

It looks like Aqua may end up in permanent stasis -- they feel they must rely on BOINC central for credit schemes and until (or if) those schemes are reasonable, the project won't proceed.

It looks like Aqua may end up in permanent stasis -- they feel they must rely on BOINC central for credit schemes and until (or if) those schemes are reasonable, the project won't proceed.

Slicker at Collatz has managed to bypass NewCredit, and still runs his Credit system with recent Boinc server software,

Claggy

I understand -- the admin over at Aqua is aware that this can be done, but doesn't want to have DA get upset with Aqua by 'hacking' the server releases to avoid submission to the NewCredit diktat -- even if the NewCredit credits result in some ridiculously high numbers (making a mockery of the concept behind the NewCredit scheme. The thing is, while I have no problems with seeing projects within a range of credit per cycle parity, trying to control that for all projects, in all stages of application development for all ranges of hardware seems a tad ... utopian to me. (Noting that not all utopias are good utopias).

Slicker at Collatz has managed to bypass NewCredit, and still runs his Credit system with recent Boinc server software,

Claggy

It seems that the scheduled (but not pre=reported) MW outage is continuing into a second day -- no evidence that it will conclude all that soon.

null

See my private message on this -- but for other eyes, it *may* have been a misread on my part on that thread, but that is qualitatively different from 'a deliberate lie' and I apologize for providing the grist for your mischaracterization.

That is a deliberate lie intended to slander the character of the AQUA@home admins. Anybody interested in the truth should read the Credit rollback!! and Crazy Credit threads at AQUA. The admin has stated in at least 2 posts that the reason they don't want to hack the server code is because it would require a lot of code merging in the future. You don't know squat about their problems so you make up bullshit. Those boys running AQUA are Canadians, they're my friends and they ain't afraid of DA or any other Yankee.