NOT a panic issue:

The server status page appears to be frozen in time (the aliens are assuming control...do not adjust your refresh, do not adjust your resolution...:))

Does this happen often?

Martin

NOT a panic issue:

The server status page appears to be frozen in time (the aliens are assuming control...do not adjust your refresh, do not adjust your resolution...:))

Does this happen often?

Martin

Yes, quite often. It's easy to miss that line which shows the last update, too.

It is too a panic issue! How can we survive if we don't know everything that happened in the last ten minutes?

                                                                Joe

Server status page still not updating....over 24 hours old now.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

thought something was wrong as I had a no new work available message about six hours ago.

---

Server status page hasn't updated however the good news is work is flowing in at 64.77Mbits/sec and out at 7.41Mbits/sec as of Mon Aug 24 18:52:30 2009 I got these numbers from the Cricket graph.

---

No panic at all, just a general comment..

Did something change recently (barring no tech news update after the outage)? I requested work and got 22 new tasks instead of 20.

2009-08-25 22:15:57|SETI@home|Sending scheduler request: To fetch work. Requesting 169013 seconds of work, reporting 1 completed tasks
2009-08-25 22:16:54|SETI@home|Scheduler request succeeded: got 22 new tasks

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

... I requested work and got 22 new tasks instead of 20.

Obviously, those tasks where shorter than 8450,65 seconds each (i.e. they were 7682,41 seconds in average).

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

No panic at all, just a general comment..

Did something change recently (barring no tech news update after the outage)? I requested work and got 22 new tasks instead of 20.

Something changed...

26-Aug-2009 12:42:00 [SETI@home] Scheduler request completed: got 39 new tasks
26-Aug-2009 14:16:51 [SETI@home] Scheduler request completed: got 63 new tasks
26-Aug-2009 14:31:41 [SETI@home] Scheduler request completed: got 35 new tasks
26-Aug-2009 14:32:28 [SETI@home] Scheduler request completed: got 36 new tasks

just had trouble getting in maybe ISP problems or maybe just timing. Main page took awhile to download.Can I add why no further info on the technical page about yesterday?

---

just had trouble getting in maybe ISP problems or maybe just timing. Main page took awhile to download.Can I add why no further info on the technical page about yesterday?

Matt is the only one to ever update the technical page, so if he is off or otherwise engaged, it doesn't happen.

Bernie

---

No panic at all, just a general comment..

Did something change recently (barring no tech news update after the outage)? I requested work and got 22 new tasks instead of 20.

Something changed...

26-Aug-2009 12:42:00 [SETI@home] Scheduler request completed: got 39 new tasks
26-Aug-2009 14:16:51 [SETI@home] Scheduler request completed: got 63 new tasks
26-Aug-2009 14:31:41 [SETI@home] Scheduler request completed: got 35 new tasks
26-Aug-2009 14:32:28 [SETI@home] Scheduler request completed: got 36 new tasks

Changeset [trac]changeset:18255[/trac] to the BOINC source on June 1, 2009 modified the interpretation of the project <max_wus_to_send>. That had been a fixed limit, now the number of GPUs is first multiplied by the project's <gpu_multiplier> setting, added to the number of CPUs, then that sum is multiplied by the <max_wus_to_send>. The real limit for many hosts will be the 100 feeder slots. It might be more if there is a possibility of the Feeder refilling slots while the Scheduler is emptying them, but I haven't checked.

                                                            Joe

My GPU cruncher have since ~ 24 hours no contact to the scheduler..
~ 1,330 ULed results ready for to report.

Scheduler request failed: HTTP internal server error

Reboot didn't helped.


My other PC can contact fine.


Where is the prob?

---

Perhaps your sched_request file has grown beyond the maximum size the server is capable of processing?

yep.. we found a fix for this if you want to try it.. it's a little time consuming. i'll link you to the post if you want.

@ Richard Haselgrove

They have changed the max. size?

IIRC, in past the GPU cruncher could report 1xxx ULed results fine.


Ohh well.. not very kind for GPU cruncher user.


@ zpm

Thanks, got your PM.


Uhh.. but 'little' work to do..


-------------------------------------------

I like it very easy.. I don't have time for to 'babysit' my GPU cruncher.
The easiest would be to detach/attach the project.
Hmm.. very well.. - ~ 55,000 Cr. .. uhh nice.. :-(
If I will do it after sleep.. + ~ 18,000 = - ~ 73,000 Cr.


Maybe it's again time for me to get my 5 min. (one day) frustration time with my 'loved' project.


~ two weeks everything fine and then again a big punch into the face.. - ouch! *$§"%&&$%&"%$%*

---

@ Richard Haselgrove

They have changed the max. size?

IIRC, in past the GPU cruncher could report 1xxx ULed results fine.

I have no idea - you are the one with all the evidence on your machine. I merely suggested it as a possibility to explain the difference between your two machines. If a report including 1,330 results generates an error at the server, when other reports are going through normally, then size would seem to be worth considering.

I don't know what technique ZPM wants to keep secret (passing by PM instead of posting in the thread), but I guess it might involve breaking client_state.xml into smaller files and reporting piecemeal. If that works, then you have found a bug worth reporting to the developers. The easiest solution would seem to be to enforce a limit on the maximum number of tasks from a single project that can be held by a host at any one time - if you can't hold too many, you can't be embarrassed by failing to report that many.

@ Richard Haselgrove

They have changed the max. size?

IIRC, in past the GPU cruncher could report 1xxx ULed results fine.

I have no idea - you are the one with all the evidence on your machine. I merely suggested it as a possibility to explain the difference between your two machines. If a report including 1,330 results generates an error at the server, when other reports are going through normally, then size would seem to be worth considering.

I don't know what technique ZPM wants to keep secret (passing by PM instead of posting in the thread), but I guess it might involve breaking client_state.xml into smaller files and reporting piecemeal. If that works, then you have found a bug worth reporting to the developers. The easiest solution would seem to be to enforce a limit on the maximum number of tasks from a single project that can be held by a host at any one time - if you can't hold too many, you can't be embarrassed by failing to report that many.

your correct on the breaking of the the file into small batches...

it's just i didn't want to throw that out their as it's an approved use by another project and not this one. the lettering of the manual is in DD@H format.
and it was done by ageless/bok, both of whom i don't want people getting pissed off at b/c they(the user) made a mistake.

---

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/
Go Georgia Tech.

You can add now ~ 75,000 Cr. to my account.


After a 'well' sleep with some nightmares about BOINC/SETI@home..

I made the instructions, from the hint of zpm - but after two hours I gave up..
And - I needed maybe 5 hours or maybe the whole day for to report ~ 1,600 ULed results manually.

So I detached/attached the project.

And then.. what the '$%&/($§$%%&' , BOINC gave the message:
Reached daily WU quota of 400 WUs ?????

At Monday it was 2,000 WUs/whole Cruncher.


Ähmm.. sorry.. my GPU cruncher make ~ 580 AR 0.44x WUs/day !!!!!
(One WU in ~ 580 sec. = < 10 min.)

So if VLARs, shorties.. in some hours my GPU cruncher idle..


Matt made no new post after the weekly maintenance..

What's going on in Berkeley?

Why they disabled the 500 WUs/GPU ????


Sorry for my 'angry' post.. but I'm again frustrated about my 'loved' project..


Ohh well.. what a beautiful life..


If someone could reach the Berkeley crew with PM, EMail or something others.. maybe telegram ;-) ..please do it! Thanks! :-)


Vyper where are you?
Your big GPU cruncher will idle very very soon.. (top_host_#1)
His Cruncher have the double performance of my Cruncher.. so he make ~ 1,200 WUs/day !!!!



BTW.
If I remember correct I could report ~ 700 or 800 ULed results well.
IIRC, this is correct. The 1xxx was maybe little bit too high.. (I was tired..)


Maybe there is a kind person out there which could make a script or something for GPU cruncher user, for to report 'short/small report pieces' ?
The instructions [URL] gave me zpm.. so I don't want to post the URL.
Maybe it would be well to publish the URL?
Or maybe PM to zpm or me..
Thanks a lot! :-)

---

We're in process of fixing this problem. I don't yet know why it reared it head only this week.

Eric

---

@SETIEric@qoto.org (Mastodon)

We're in process of fixing this problem. I don't yet know why it reared it head only this week.

Eric

Thanks for checking in Eric....

And hang in there Sutaru.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster