At this moment the server has no new work to send and my limited Milkyway caches are dry, and so am I!

HELP!
____________
Go away, I was asleep

+1
____________

Typical, just as I pass 200 million everything falls over!
____________

Well Travis did acknowledge impending doom & gloom :)

Murphy is alive and well!

Regards
Zy

so it gonna be a week of the server unavailability?
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1713&nowrap=true#39165
____________

Typical, just as I pass 200 million everything falls over!

Typical, just as I pass 200 million everything falls over!

Been running Collatz since I started this thread.

This is the third break in work generation in the time I am trying to see what the steady RAC my ATI GPU will produce. It produced an RAC of 154K on Collatz, and I am hoping to break 200K but these server "no work" is side stepping this ambition. ;-((
____________
Go away, I was asleep

... my limited Milkyway caches are dry, and so am I! ...

An odd thing, I have exactly 50 tasks waiting for credit, is this an coincidence?

It could well be related -- the number of work units awaiting validation is way up as well. I'm guessing the status page is doing the 'politician' thing and not representing things as they are (aside from the no work status).

An odd thing, I have exactly 50 tasks waiting for credit, is this an coincidence?

Work available again.

Travis has kicked the servers, the work waiting validation is dropping quickly.
____________
Go away, I was asleep

Validator crapped. Also no tasks.

Workunits waiting for validation 17,366

Dropped a kung fu bomb on the server last night...

Message from server: No work available.
Switching to Collatz.

+1

+1
____________

+1
____________

+1

Just noticed that instead of seeing FreeHAL and Einstein running on the CPU and Milkyway running on the GPU, I only see Einstein (and there is serious upload and download problems problems on theat project.

Now over to Collatz for a quarter of a day's work.
____________
Go away, I was asleep

No work available ...
Until WU exec time 1.5 minutes(my Rad-5870), we will have same situation very soon.
SerVal, Moscow, Russia.

I hope Travis was able to get information on the memory leak he was looking for!

Looks like it is back up as I just got work. Of course I also turned on Collatz as I will be away this weekend and I want to keep the card running.
____________

Anybody having trouble uploading results?

This seems to be intermittent, and I am getting this in the BM Messages tab -

09/05/2010 09:57:14 Milkyway@home update requested by user
09/05/2010 09:57:25 Milkyway@home Sending scheduler request: Requested by user.
09/05/2010 09:57:25 Milkyway@home Reporting 10 completed tasks, requesting new tasks for GPU
09/05/2010 09:57:46 Project communication failed: attempting access to reference site
09/05/2010 09:57:48 Internet access OK - project servers may be temporarily down.
09/05/2010 09:57:50 Milkyway@home Scheduler request failed: Failure when receiving data from the peer



____________
Go away, I was asleep

Must be due to the pentathlon, which is now concentrating on MW for the next week.

I've already seen BOINC hit my backup project.

ARRRGH! Out again.

Server Status 0 ready to send.

don't see any progres.
On server status page there are WU
on host: No work available


Edit: Now it's working.
Thanks
____________

Join us at www.boincatpoland.org

Time to add another bug to our longstanding issues list:

Travis cracking open a beer after a long day causes the server to crash.

To the previous list of:

Travis going to sleep frequently causes the server to crash.
and
Travis going on a ski/snowboarding trip frequently causes the server to crash.

Time to add another bug to our longstanding issues list:

Travis cracking open a beer after a long day causes the server to crash.

To the previous list of:

Travis going to sleep frequently causes the server to crash.
and
Travis going on a ski/snowboarding trip frequently causes the server to crash.

Lets see now, gathering all the words that are common to all three of the above:
"Travis causes the server to crash" ;-)
I suggest you have another beer after that revelation!
Travis, it would appear that you and Murphy are well acquainted.
Time to remove tongue from cheek...

Is Murphy is sitting in for Travis tonight?
____________

Murphy must have been offered a beer down the pub...things look good again.

Murphy must have been offered a beer down the pub...things look good again.

Cant be avoided. Lots of people will run out of work with hosts like this, http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=171705.

That host have over 2000 tasks in cache while my 3850 is limited to only 6 tasks in progress. *sigh*

Cant be avoided. Lots of people will run out of work with hosts like this, http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=171705.

That host have over 2000 tasks in cache while my 3850 is limited to only 6 tasks in progress. *sigh*

He's also using a very old version of Boinc and MW app. Time to pull the plug methinks....

____________
Don't drink water, that's the stuff that rusts pipes

He's also using a very old version of Boinc and MW app. Time to pull the plug methinks....

Somebody poke Travis, the tasks are now 2598. :)

That host is a wingman. At this rate, he might become a wingman on future tasks as well and we'll be stuck in pending limbo.

I would suggest putting MW on NNW untill this is fixed.
____________
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

That host is not mine, it belongs to Lord Nelloz. I only found out about it after I checked a task of mine that's been inconclusive for a week now.

By the way, that host have 2817 tasks now.

Arrrgghhh.

Gnnnnnnnnh! :)

Pbbfflliitt!


____________

haha - I dont think I should answer that one officially. LoLz
____________

I see the Server Status shows them all working (green), but there is no work yet.

Anyone know when new work might be created and issued?
____________
Go away, I was asleep

Could it be that http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=171705 is soaking it all up? That host's task count has now increased to 2920 :(
____________

Could it be that http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=171705 is soaking it all up? That host's task count has now increased to 2920 :(

Well boys and girls,

After a few times hitting the "Update" button, I got new stuff to crunch again.
____________
Greetings from,
TJ

I also got fresh WU's (was quite dry for some hours), seems we are up and running again =)

Although the Server Status says all is running OK, we have been out of work for 8+ hours now.

Looks like we need someone to kick the servers soon?
____________
Go away, I was asleep

Aaargh!

The servers have no work ready to dispense.

Kick the servers, we are nearly starving.


Travis must be asleep (most likely) or have gone away snowboarding?
____________
Go away, I was asleep

Must be... The trolls are acting up again...

Hello,

This is rediculous half on half off !!
Some work really needs to be done to the continuous output of work from the server on this project

best regards
Ian
____________
....Please Join team Scotland HERE

I wonder if the Milkyway server was made by the same guy that made this Alarm Clock?

Hi,

Nice one lol
I just wonder if the thing has Texas Instruments on the front :))

best regards
Ian
____________
....Please Join team Scotland HERE

Still nowt to crunch!
____________
Go away, I was asleep

Validator crapped out again.
____________
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

OK, back to Collatz, sigh ....
____________
Don't drink water, that's the stuff that rusts pipes

Told ya so.

and again no work :(

My GPU-fan went eerily silent a couple of minutes ago. I guess all those Collatz crunchers returned the favour with Collatz down and sucked our well dry as well :-)
____________

Argh!

The servers have little or no work to distribute, so we are in for another dry period until the servers are kicked.

It looks like the validator has a backlog of over 20K results to clear (again)

Oh woe is me, with Collatz offline as well


Just attached to DNETC as well for my HD4850 and the old AGP HD3850 so when Milkyway caches (24 WUS) are empty, then DNETC will crunch until MW returns.

On the older ATI cards the output looks like it is less productive, in output terms, than MW (lower RACs per GPU).
____________
Go away, I was asleep

Noooooooo

I just got my ati 5870 and amd x6 rig with every part now in it and no work to do :(

I also keep an account on DNETC, just in case. I downloaded 50 5xxx units to keep my GPU busy.
____________

This is great news. Time to swap out a failing PSU and do some maintainence

Dusting now, caugh, caugh.
____________

out of work. this starts to happen so often.

out of work. this starts to happen so often.

out of work. this starts to happen so often.

And its going to be out of work for awhile ..

http://milkyway.cs.rpi.edu/milkyway/server_status.php

Its got nothing to send..and with a growing number of people getting their WUs done that have yet passed validation..I imagine its going to be another mad rush when the server does get up again..

I got to say though..this is getting silly for server downtime. I think they need a new guy behind the scenes for the server or something..

Look at bright side... just think how boring the graphs would be without the occasional high hills and deep, wide valleys.
Then again, boring isn't so bad.

out of work. this starts to happen so often.

And its going to be out of work for awhile ..

http://milkyway.cs.rpi.edu/milkyway/server_status.php

Its got nothing to send..and with a growing number of people getting their WUs done that have yet passed validation..I imagine its going to be another mad rush when the server does get up again..

I got to say though..this is getting silly for server downtime. I think they need a new guy behind the scenes for the server or something..

I believe that the guy is good enough but the hardware lacks the capability to catch up. Maybe it is time to renew or upgrade the server.

Look at bright side...

If it is possible from the science, much longer WU could be a solution. It will reduce traffic and server load. Of course then a checkpoint-system must be implemented in the application code.

Maybe the constraint is not the server, but the brain...
____________

Maybe the constraint is not the server, but the brain...

There is 1 WU available, let´s look who get it ;)

Perhaps the server works now

Hello,

I must admit not usually being a complainer but having to baby sit this project through server downtime is a bit of a pain now
I would really like to just hook the system up leave it crunching and forget about it but now find myself having to check up on it way to often

more workunits per core has been discussed and ruled out the above suggestion of longer work units would cure two problems 1. less down time for our machines 2. less spin down down and spin up between work units
this idea also doesnt seem to be getting any attention for some reason

collatz doesnt quite give the same credit but seems online more often than here and dnetc seems to give more credit per gpu work done using longer work units

I'm stuck here just now because neither of the two projects above will work with my 3 ATI cards in crossfire but the longer this fiasco with the server carries on the more likely I am to set up another couple of machines splitting the cards so they each can work on the projects above

hopefully the hardware IT dept will announce on here there next set of upgrades soon so we can have a more consistant flow of work

best regards
Ian
____________
....Please Join team Scotland HERE

There is 1 WU available, let´s look who get it ;)

Perhaps the server works now

There is 1 WU available, let´s look who get it ;)

Perhaps the server works now

I just got ~20 wu's.
Don't give up!

Hello,

I must admit not usually being a complainer but having to baby sit this project through server downtime is a bit of a pain now
I would really like to just hook the system up leave it crunching and forget about it but now find myself having to check up on it way to often

more workunits per core has been discussed and ruled out the above suggestion of longer work units would cure two problems 1. less down time for our machines 2. less spin down down and spin up between work units
this idea also doesnt seem to be getting any attention for some reason

collatz doesnt quite give the same credit but seems online more often than here and dnetc seems to give more credit per gpu work done using longer work units

I'm stuck here just now because neither of the two projects above will work with my 3 ATI cards in crossfire but the longer this fiasco with the server carries on the more likely I am to set up another couple of machines splitting the cards so they each can work on the projects above

hopefully the hardware IT dept will announce on here there next set of upgrades soon so we can have a more consistant flow of work

best regards
Ian

hi,

great idea but in my case my rig with three crossfired cards wont run the other two projects so if this one dies thats it :(

best regards
Ian
____________
....Please Join team Scotland HERE

Hello,

I must admit not usually being a complainer but having to baby sit this project through server downtime is a bit of a pain now
I would really like to just hook the system up leave it crunching and forget about it but now find myself having to check up on it way to often

more workunits per core has been discussed and ruled out the above suggestion of longer work units would cure two problems 1. less down time for our machines 2. less spin down down and spin up between work units
this idea also doesnt seem to be getting any attention for some reason

collatz doesnt quite give the same credit but seems online more often than here and dnetc seems to give more credit per gpu work done using longer work units

I'm stuck here just now because neither of the two projects above will work with my 3 ATI cards in crossfire but the longer this fiasco with the server carries on the more likely I am to set up another couple of machines splitting the cards so they each can work on the projects above

hopefully the hardware IT dept will announce on here there next set of upgrades soon so we can have a more consistant flow of work

best regards
Ian

Why do you need to babysit this project? Just set a backup project and let BOINC do its thing. Yes it is annoying when MW stops but with two other project that support ATI cards your ATI GPUs shouldn't run out of work.

Zero work again.

Just as I am returning 2 rigs to Milkyway, do I detect another stoppage with ZERO work ready to send?

AAArrrgh!
____________
Go away, I was asleep

Yup - same here.

I'll watch the speed that the server status page shows the "results in progress" declining.

lol
this projects on ati cards suffer from work most of the time
these nvidia projects are much slower but get steadily work :)
nvidia luckers xD

____________
Its new, its relative fast... my new bicycle

What we are missing is a statement from the project stuff. Is somebody working for a solution?

Just thinking.

With the constantly malfunction server in mind, the never ending story of the 'Almost there' GPU page that turned up to be the 'Never there' GPU page and the currently ongoing project of the 'MilkyWay@home screensaver coming soon' that also seams to go the same way.

Would it not be just hilarious if the screensaver would come out when there was just one wu left to crunch :)

Hi,
this is a copy from the gpugrid forum, 'GPUGRID and ATI'

Hi,

We'll probably be in a position to start testing of an ATI application after SDK 2.2 is released in a month or so. It will require a 5800-series card initially.

MJH
It is dated 10th July. And they talk about OpenCL, which seems to be a source of problems until now. They say, its not stable.
And they posted, that 48xx-cards will not be supported. They lack some capabilities. But for the lucky owners of a 58xx card a new star is rising ...

Alexander

I wish I had a 58xx card, so I could complain more often ;-))
Maybe better to sing for her..

- To Miss Milkyway -

"Ain't no sunshine when she's gone.
It's not warm when she`s away.
Ain't no sunshine when she's gone
and she's always gone too long
anytime she goes away."

;-)
____________

On POETS Day there in no need to complain
as there is work elsewhere to gain.
Just move to Collatz and see,
or even to DNETC will take the p**.
____________
Go away, I was asleep

Indeed, the lack of information this time is getting a tad tedious. Oh well, at least both Dnetc and Collatz are (at the moment) running.

What we are missing is a statement from the project stuff. Is somebody working for a solution?

I wish I had a 58xx card, so I could complain more often ;-))
Maybe better to sing for her..

- To Miss Milkyway -

"Ain't no sunshine when she's gone.
It's not warm when she`s away.
Ain't no sunshine when she's gone
and she's always gone too long
anytime she goes away."

;-)

Correction -- Collatz is encountering one of their daily Comcast can't figure it out connectivity problems.
____________

Milkyway servers are up, but most are not running nor have any work.

Collatz is not available due to ISP problems

FreeHAL seems to have gone away (ISP as well or ...)

Just leaves DNETC

Ho! Hum!
____________
Go away, I was asleep

We're baaaack.

Sorta, I still don't have any work from here and I also have a pretty full cache of DNETC work to keep the 5830 warm.
____________

Kick It!
____________

I am down as well.
____________

Shake it!

Looks like the validator again?
____________
Go away, I was asleep

So all the GPU folks returned their wu's in less than 4 hrs (60,000 wu's) and now the CPU's are returning their wu's at 10,000 per 4hrs.



Care of Scarecrow

Maybe we should make a collection for something like an 'Weekend Automatic Validator Kicker'.

Could something be set up to automatically restart it?
____________
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Could something be set up to automatically restart it?

With apologies to DEVO ... (ah the eighties)
Whip it good - Werkstatt just dusted off the archives in the back of my head

When something's going wrong
You must kick it
Now whip it
into shape.
Shape it up
Get straight
go forward
move ahead
Try to detect it
it's not too late
to whip it
whip it good

When a good time turns around
you must kick it
You will never live it down
unless you kick it
No one gets away
until they kick it
I say kick it
kick it good
I say whip it
kick it good
crack that whip
give the past the slip

It's baaaaack....

No work, again, for a little while now, and caches running down.

There are 42,827 WUs awaiting validation, and possibly growing. I expect the usual validation server problem is associated with the lack of new work, as seen several times before.

Can someone kick the server, or it's over to Collatz for a burst of WUs there. :((
____________
Go away, I was asleep

I need wooooooooooooooooooooooooork! ;-))))))
____________
Lovely greetings, Cori

It seems we have a repetitive problem -- symptoms are that work isn't being produced for download and completed work isn't getting validated.

Perhaps there is some form of memory leak going on here -- and absent solving the root cause problem, perhaps a scheduled stop/start process to act as a bandaid might be an at least marginally proactive approach to the problem.

I haven't seen any information from Travis or others at the project regarding what they are seeing there (or if they are seeing anything there or for that matter that they are looking into it).

Perhaps we are seeing 'BOINC project middle age' syndrome in terms of the project side activity and communications level....

It would be nice if they could put this repetitive problem to bed - that might allow Travis even more off site time.
____________

It seems we have a repetitive problem -- symptoms are that work isn't being produced for download and completed work isn't getting validated.

I haven't seen any information from Travis or others at the project regarding what they are seeing there (or if they are seeing anything there or for that matter that they are looking into it).

Perhaps we are seeing 'BOINC project middle age' syndrome in terms of the project side activity and communications level....

It would be nice if they could put this repetitive problem to bed - that might allow Travis even more off site time.

i can say even more - this happens on bi-weekly basis...
____________

I need wooooooooooooooooooooooooork! ;-))))))

I gave the server a kick, let me know if it worked.

-Matthew

Yay, now there's frrrresh crrrrunchies! THX!
____________
Lovely greetings, Cori

It's working fine for me ATM, and I am d/ling new work as needed.
____________
Go away, I was asleep

Arrrgghhhh!

I need wooooooooooooooooooooooooork! ;-))))))

No wonder all the problem This is the server kicking staf ;)

I need wooooooooooooooooooooooooork! ;-))))))

Can anyone translate text to english please.

And yes: there is no work this time but DNETC@home is good backup project. :-)

Kick the serveR

Kick the validator!
____________
Go away, I was asleep

again...
____________

Travis you selfish bas!ard, you snuck out out of the building to have some sort of a life didn't you ?

OK Matthew, kicking the server really is not working so well these days. I suggest you try kicking the computer lab staff!
If they are bigger than you, feel free to use a bat :P

/OK back to my live ROV feeds.
____________

Every time a staff member kicks server, it gets broken sooner. Maybe all it needs a love? or a Xeon CPU he can make love to? so don't kick it, just love it.

Also I'm just happy to set DNETC@Home as a backup project.

Looks like the server(s) have been working and dishing out work for a few hours now. Just need to NNT Collatz and run a 5 hour cache down then MW resumes.
____________
Go away, I was asleep

bundesagentur für arbeitspakete translates to:
Federal department for work packages.

Now that's funny :-)

I see the validator is building again
____________
Go away, I was asleep

It was nearly Aaargh! again a couple of hours ago this morning. The validator seemed to be building up and the "Ready to send" read ZERO!

Seems to continue to be running OK ATM.
____________
Go away, I was asleep

A usual hiccup !

____________
Don't drink water, that's the stuff that rusts pipes

It looks like we are rapidly heading to a new Aaargh session according to the current server status.

The work ready to send had dropped well below it's normal levels (now = 304). But it does seem to be increasing slightly.

But the real give away is the numbers awaiting the validator - now 23,335. When we are running normally this is around 6,300.

Are we getting ready for the chorus - HELP! Please get ready to kick the servers?
____________
Go away, I was asleep

Definitely moved to Aaarrrrggghhhh!

The work ready is now ZERO and the "waiting-for-validation" has risen to over 30K
____________
Go away, I was asleep

Still no work

Please give the servers a kick soon!!
____________
Go away, I was asleep

I realize others have suggested this in the past, but it seems that either a bit of serious root cause identification/resolution effort ought to be done, or, alternatively, a automatic stop/restart process (perhaps once a week) to clear things out (or even daily off hours to insure no more than single day outages) needs to be in place.

By the way, since duplicate posts are subject to filtering, shouldn't duplicate outages also be dealt with? <just joking>

Still no work

Please give the servers a kick soon!!

A preemptive server reboot daily or every 48hrs sounds like a good idea!

The best and fastest way to get someone to restart the validator is to send an email to astro@cs.rpi.edu because all 11 administrators receive it. I have already sent an email this time.

I do not believe they monitor these forums on a regular basis. Last time I sent an email, they thanked me for reporting it even though the validator had been down for over 6 hours.

Work is up now.
____________
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Sighing with relief, and letting the raw patch at the back of my throat time to get better.

Where is my voice?
____________
Go away, I was asleep

Feeder is not running

10-08-2010 10:51:55 Milkyway@home Sending scheduler request: Requested by user.
10-08-2010 10:51:55 Milkyway@home Reporting 2 completed tasks, requesting new tasks for GPU
10-08-2010 10:51:57 Milkyway@home Scheduler request completed: got 0 new tasks
10-08-2010 10:51:57 Milkyway@home Message from server: Server error: feeder not running

____________

I've sent a email to stuff that servers are down.

Alexander

So did I, and the feeder works again!
____________

I presume a third request to the admins for a server reboot will not go amiss. The Validator has a balance of Workunits waiting for validation 34,273 , so the awaiting for work must have happened a while ago.
____________
Go away, I was asleep

.. well, no new Wu's again. just finished my batch now...

i was wondering why there was so many Wu's waiting to report...

Since I live on the other side of the planet, I think the project admin should give me a big RED button to push whenever this happens, so the servers reset.

At least three of my babies switch automatically over to the backup project now.
____________

.. well, no new Wu's again. just finished my batch now...

i was wondering why there was so many Wu's waiting to report...

I moved over to Collatz as the ATI HD3850 crunches DNETC incredibly slowly compered to either Milkyway (preferred) or Collatz (back up).

Now waiting the results of E-mails to the project admins to re-boot the servers.
____________
Go away, I was asleep

I'm already crunching elsewhere with backup projects! Micro management sucks though....

____________
Don't drink water, that's the stuff that rusts pipes

The reliabilty of this project is almost getting as bad as SETI. I managed to get about 12 work units 30 minutes ago, then it stopped again.

The reliabilty of this project is almost getting as bad as SETI. I managed to get about 12 work units 30 minutes ago, then it stopped again.

Have you ever tried orbit@home or lhc@home?
That could change your mind!

For your GPU Collatz Conjecture could be a backup project.

Alexander

As far as Collatz goes, after I installed my second ATI 5970 card, all Collatz will do for me is lock up my system. I wish I could get it to run. Evidently it doesn't like an i7 980x cpu, Win7 64bit, and 2 ATI 5970 cards.

Mike..

Mike,
collatz likes i7, win64 and 2 ATI-cards. As you can see, my mainsys is a similar configuration, except that I do not have 2 5970 but one 5830 and one 4870 and 'only' 8 threads. And collatz works fine.

But when I take a look onto your computers, I cannot find one with ATI-GPU's. There are two listed with nVidia.
Maybe you have a more basic problem?

Alexander

An automatic pre-emptive stop/start of the server (or server processes) is something of a brute force *work-around* which doesn't deal with what appears to be a root cause problem that could use some analysis and resolution efforts.

Back in the day when Travis was more closely involved, pleas here for that sort of corrective action seemed to have more effect.

Seemingly at this point, it is more a case of auto-pilot (where the best that can be had is frequent reboots) as the various admins have a lot of other things on their plate in addition to this project.


____________

Well not quite -- I mean the approach these days at SETI is a weekly *three day* outage -- preceded by 12 to 24 hour traffic jam and then followed by a post outage traffic jam of 12 to 24 hours. I believe the idea was to improve reliability when the outage wasn't going on -- it hasn't yet done that.

So for SETI, what is now in place is a part time project, but their message boards run about 162 hours a week. Rather a fair amount of resource there for message boards it seems to me. SETI moved to close to the bottom of my list rather a long time ago.

I suspect a large part of the problem here is that to a fair degree, the now *Doctor* Travis has moved on (as is to be expected) and there no longer is the motivational force behind this project.

The reliabilty of this project is almost getting as bad as SETI. I managed to get about 12 work units 30 minutes ago, then it stopped again.

For me, Milkyway dropped to my second project simply because I have a flock of GPU's that MW doesn't support (ie non-double precision cards).

With DNetC now available which provides largely the same GPU support as Collatz, MW will drop down to my number three project in terms of TC within a couple of months. It is interesting the sort of reliability that Collatz and Dnetc can provide with quite limited resources (of course with lower user counts).

I agree with you regarding the somewhat finicky nature of Dnetc -- there are clearly some GPU configurations it doesn't play well with (like the dual 5970 ATI's and your 3850), and it can push the cards to a distracting degree -- I can't run Dnet on my primary computer when I am doing even ordinary tasks, compared to Collatz.

I guess we can hope that Travis is able to pass on the torch here to someone at RPI who will be 'invested' in the project as he was in the past. My other hope is that additional 'low end' GPU projects, particularly ATI GPU projects, start showing as well.

I moved over to Collatz as the ATI HD3850 crunches DNETC incredibly slowly compered to either Milkyway (preferred) or Collatz (back up).

Now waiting the results of E-mails to the project admins to re-boot the servers.

Well not quite -- I mean the approach these days at SETI is a weekly *three day* outage -- preceded by 12 to 24 hour traffic jam and then followed by a post outage traffic jam of 12 to 24 hours. I believe the idea was to improve reliability when the outage wasn't going on -- it hasn't yet done that.

I suspect a large part of the problem here is that to a fair degree, the now *Doctor* Travis has moved on (as is to be expected) and there no longer is the motivational force behind this project.

With DNetC now available which provides largely the same GPU support as Collatz, MW will drop down to my number three project in terms of TC within a couple of months. It is interesting the sort of reliability that Collatz and Dnetc can provide with quite limited resources (of course with lower user counts).

I guess we can hope that Travis is able to pass on the torch here to someone at RPI who will be 'invested' in the project as he was in the past. My other hope is that additional 'low end' GPU projects, particularly ATI GPU projects, start showing as well.

Yes, I got that -- if that is the 'permanent' plan for SETI, then the folks most affected by that are the 'SETI uber alles' crowd -- for that group, the self-imposed 'only one project' makes them dependent on a project that, aside from the newsgroups, runs only 50% of the time and is pretty well stressed with folks crowding into the 'half-space' for uploads and downloads.

The plus side is that the much smaller active BOINC crowd that might have originally been brought into distributed processing by SETI and doesn't have a 'SETI only' DP world view might well help out other projects which are not half time.

As I understand it, the 3 day outage is to let Nitpicker run on 10 years worth of results to sift for likely candidates to re-examine. When they tried it in real time it zonked the servers and the database out. You can't upload or download work for 3 days, but the message boards are only out for 9-12 hours as they were before.

I run a GTX260 24/7 on Seti. it is no big deal. I needed to adjust my cache to 4 days to assure constant work, but that's no big deal.

As to DnetC, I find it makes an excellent backup project for me. I am running it now on two, twin 5790 computers. One 5790 and 4770 computer. And one single 5790 computer, so it is pretty adaptable from my point of view.

OK must go MW just downloaded on one of the boxes, so lets see if I can get the others back!
____________

hmm, i got some WU's, assimilation seems to be up and running. have to wait though. AFAICS, there are a small bunch ready to send.

Work is avilable again
____________
Go away, I was asleep

no validation though
____________
Blah blah blah you know the rest

no validation though

Looks like the root cause is either winning or being looked into -- web pages are on -- sort of in a SETI emulation mode we are at the moment.

____________

Back to Collatz, which has good uptime since Comcast repaired/replaced parts of the BB line.
____________
Go away, I was asleep

I just setup Collatz to be my primary project and Milky Way to be my backup. I really like Milky Way, but when you average in the downtime and the almost nonexistant cache, I am getting much better credit returns at Collatz.

If only I could get DNETC working om my system, I would set up as #1=DNETC, #2=Collatz, and #3=Milky Way.

I will keep checking back with the hope that I will find that the reliabilty of this project has improved.

Mike...

OK -- so could we PLEASE get some feedback from folks at the project as to what is going (or not going) on?

One thing more troublesome than outages is outages in a vacuum.

____________

OK -- so could we PLEASE get some feedback from folks at the project as to what is going (or not going) on?

One thing more troublesome than outages is outages in a vacuum.

Now the Server Status page is beginning to look ominous regarding another validatior backing up problem.

When all is running smoothly the status page Workunits waiting for validation usually runs with between 6,250 and 6,4000 results waiting. I see the status now gives us with 12,139 waiting validation. If this continues then the whole shebang will be down again.

I have PMed Matthew as a precaution, which I hope I am wrong about.


[Edit mode on - 35 minutes after first posting this potential panic]

Thanks Matthew.

The validator is back to it's usual numbers waithing for validation.

PANIC avoided

[Edit mode off]
____________
Go away, I was asleep

Knock knock!
____________

Sending scheduler request: To fetch work.
Requesting new tasks for GPU
Scheduler request completed: got 0 new tasks
Message from project server: No work sent
Message from project server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

Is N-Body the only style of work being assigned now? Or is this just a glitch in the matrix?

Sending scheduler request: To fetch work.
Requesting new tasks for GPU
Scheduler request completed: got 0 new tasks
Message from project server: No work sent
Message from project server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

Is N-Body the only style of work being assigned now? Or is this just a glitch in the matrix?

No panic boys, it is weekend....

Servers and validators have some days of too every now and then.
____________
Greetings from,
TJ

OK -- so this problem -- which has shown up every week or so remains unresolved -- frankly, not really a surprise.

Sending scheduler request: To fetch work.
Requesting new tasks for GPU
Scheduler request completed: got 0 new tasks
Message from project server: No work sent
Message from project server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

Is N-Body the only style of work being assigned now? Or is this just a glitch in the matrix?

I was getting the same thing, so I reset the project. It didn't help. The server page shows workunits available, but I am unable to get any of them.

They could be CPU N-Body workunits. But, the validator is backed up and looks like it is about to crash, also.

It's the validator again - it has backed up with 59K worth of work to knock off.
____________
Go away, I was asleep

Are the servers dishing up nBody work ATM?
____________
Go away, I was asleep

Looks like it. I am getting Nbody only at the moment. With about

10% giving "error while computing".

I've gone back to Collatz until the normal Milkyway WUs are being dished out.

I presume the Nbody work has it's own client, so how do I get my system to download this work? I am assuming this Nbody work is for GPUs, which I see from elsewhere appear not to exist?
____________
Go away, I was asleep

Nope. CPU only. Apparently GPU to come later.

Did the project stop using the old workunits in favor of the N-Body workunits? For about the last day, I can only get one or two workunits every now and then. And, the ones I do get are resends because of invalid results from another user. It looks like there are no new workunits being sent out.

And about every hour I loose and hour or so of completed work! How does that happen?
____________

And about every hour I loose and hour or so of completed work! How does that happen?

Feeder not running again.
____________
Cheers,

PeterV

.

Ican dowload normal MW GPU WUS now, so the system is feeding both Nbody and normal again (I hope)
____________
Go away, I was asleep

Aaah...the smell of GPU's working again.

It's Friday, the server has been working well for a few days, time for it to fall over...

Then you'll head for Collatz as DNETC is in the middle of a server upgrade/change.
____________
Go away, I was asleep

BOOM!!!
____________
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Indeed, absent dealing with the underlying problem (which is growing something of a beard), lots of server regular stop/starts just might keep things going. We the weekend in view, it seems that on every Friday a single or double server reboot should be done automatically.

It's Friday, the server has been working well for a few days, time for it to fall over...

At Dnetc, the maintenance was announced (though only an hour before the upload/download servers were taken offline), and then the message boards were up for another several hours. But as of about 5PM yesterday (PDT) poof -- it went gone. In the announcement, it was noted the outage was expected to take 5 hours -- perhaps each of the hours turns out to be 600 minutes long....

Then you'll head for Collatz as DNETC is in the middle of a server upgrade/change.

Ouch -- things might just have gotten worse -- can't connect to Collatz either.
____________

So it is clear that a number of us poor fools are (and have been) aware of MW being in dead state for several hours, do we have any wagers on the awareness of this in RPI land?

This many months long intermittent problem has not been a subject of much public discussion coming from the folks at RPI -- which of course does little in the way of confidence (or compassion) building......
____________