I have broused the Foura, checked the Tech news, and been to the server status page, and every thing seems Fine, apart from the fact that as of 3pm(UTC, ish) yesterday (20/12/05) I have been getting

21/12/2005 14:10:48|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi

21/12/2005 14:10:48|SETI@home|Requesting 18681 seconds of work, returning 0 results

21/12/2005 14:10:51|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

21/12/2005 14:10:51|SETI@home|No work from project

21/12/2005 14:10:52|SETI@home|Deferring communication with project for 10 minutes and 4 seconds

Uploads are going through fine.
Even though the server reports over 400,000 WUs to send, does anyone know why the project is not giving out work?

Both PC's affected.

E@H chugging along nicely as a backup project, but one is now out of seti, and the other will be soonish.

Any help appreciated. Dor.
{edit=Spelling}

---

Foamy is "Lord and Master".
(Oh, + some Classic WUs too.)

Yup... same here. Nothing for a day or so.

---

I have broused the Foura, checked the Tech news, and been to the server status page, and every thing seems Fine, apart from the fact that as of 3pm(UTC, ish) yesterday (20/12/05) I have been getting

21/12/2005 14:10:51|SETI@home|No work from project

Same here, except that one PC seems completely unable to get any WUs, other PCs have had a few retries and then got work.

Same here.
The problem isn't stable - sometimes my hosts get a WU, sometimes not. It's the same behaviour like an empty queue but the queue is growing...
Very strange.
Stefan

---

Looking over my host data, it appears I stopped getting new work about 10 hours ago for my fastest machine. I can even see where the weekend storage difficulties caused a blip in the usual pattern, but it never ran out of work during the period from Friday to 10 hours ago.

My slowest machine has been begging for work for about a day, but that was expected since it was coming off an extended debt payback run, and had no seti stockpiled when the server queue ran low from the storage space problems. What I don't understand is why the fast one was getting work for the 14 hours before the last one sent to it and the slow one couldn't get any at all.

Alinator

Looking over my host data, it appears I stopped getting new work about 10 hours ago for my fastest machine. I can even see where the weekend storage difficulties caused a blip in the usual pattern, but it never ran out of work during the period from Friday to 10 hours ago.

It loooks like we are back to the same problem from a couple weeks ago, as seen by all the -106 errors in my logs.

12/21/2005 7:38:28 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/21/2005 7:38:28 AM|SETI@home|Reason: To fetch work
12/21/2005 7:38:28 AM|SETI@home|Requesting 21496 seconds of new work, and reporting 1 results
12/21/2005 7:38:28 AM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
12/21/2005 7:38:33 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
12/21/2005 7:38:33 AM|SETI@home|No schedulers responded
12/21/2005 7:39:33 AM|SETI@home|Fetching master file
12/21/2005 7:39:33 AM||Couldn't resolve hostname [setiathome.berkeley.edu]
12/21/2005 7:39:38 AM|SETI@home|Master file fetch failed
12/21/2005 7:40:38 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/21/2005 7:40:38 AM|SETI@home|Reason: To fetch work
12/21/2005 7:40:38 AM|SETI@home|Requesting 21600 seconds of new work, and reporting 1 results
12/21/2005 7:40:38 AM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
12/21/2005 7:40:43 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
12/21/2005 7:40:43 AM|SETI@home|No schedulers responded
12/21/2005 7:40:45 AM||request_reschedule_cpus: process exited
12/21/2005 7:40:45 AM|SETI@home|Computation for result 04mr05aa.19194.17234.242328.84_1 finished
12/21/2005 7:40:47 AM|SETI@home|Started upload of 04mr05aa.19194.17234.242328.84_1_0
12/21/2005 7:40:47 AM||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
12/21/2005 7:40:48 AM|SETI@home|Temporarily failed upload of 04mr05aa.19194.17234.242328.84_1_0: can't resolve hostname
12/21/2005 7:40:48 AM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 04mr05aa.19194.17234.242328.84_1_0
12/21/2005 7:41:43 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/21/2005 7:41:43 AM|SETI@home|Reason: To fetch work
12/21/2005 7:41:43 AM|SETI@home|Requesting 21600 seconds of new work, and reporting 1 results
12/21/2005 7:41:43 AM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
12/21/2005 7:41:48 AM|SETI@home|Started upload of 04mr05aa.19194.17234.242328.84_1_0
12/21/2005 7:41:48 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
12/21/2005 7:41:48 AM|SETI@home|No schedulers responded
12/21/2005 7:41:49 AM||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
12/21/2005 7:41:49 AM|SETI@home|Temporarily failed upload of 04mr05aa.19194.17234.242328.84_1_0: can't resolve hostname
12/21/2005 7:41:49 AM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 04mr05aa.19194.17234.242328.84_1_0

---

I have 10 clients begging for Seti WU's but none of them are getting any. Sometimes it says "no work available from project"but other times it doesn''t give any error message. I request xxxxx seconds of work, connects to the server and then nothing. Finally it will just say deferring communications for xx minutes.

I am trying to fill my cache for 7 days of work to let them run over the Christmas holiday so this is very unfortunate timing. It's soon to be the normal Wed. shutdown for database backup too. Maybe they will notice that there is definately a problem... I would concur that this situation developed in the past 12 hours or so.

---

With the current increase in "Ready to Send" and the decrease in "In Progress" I am beginning to wonder if the feeder is actualy communicating with the scheduler in the way it is supposed to.

With the current increase in "Ready to Send" and the decrease in "In Progress" I am beginning to wonder if the feeder is actualy communicating with the scheduler in the way it is supposed to.

There is at least SOME backup in the chain..

Transitioner backlog (hours) 2

---

https://youtu.be/iY57ErBkFFE

#Texit

Don't blame me, I voted for Johnson(L) in 2016.

Truth is dangerous... especially when it challenges those in power.

With the current increase in "Ready to Send" and the decrease in "In Progress" I am beginning to wonder if the feeder is actualy communicating with the scheduler in the way it is supposed to.

Could be.

Since I posted both machines have managed to get some work each, but are still requesting more, as the work supplied was not the amount requested (2 day cache setting).

Question, do I increase my cache, in-case of continuing problems over Xmas, (if I get WU, this means others go without,) or just run out of seti (if the problem persists) and do E@H?
I will leave both asking o/night (which is berkeley's working day) and see the state of play in the morning.

---

Foamy is "Lord and Master".
(Oh, + some Classic WUs too.)

Could be.

Since I posted both machines have managed to get some work each, but are still requesting more, as the work supplied was not the amount requested (2 day cache setting).

Question, do I increase my cache, in-case of continuing problems over Xmas, (if I get WU, this means others go without,) or just run out of seti (if the problem persists) and do E@H?
I will leave both asking o/night (which is berkeley's working day) and see the state of play in the morning.

LOL, lucky you!

My fast box just ran dry on seti and everybody else who was asking is still begging!

Looks like the other projects are gonna get some short term extra crunch time right now.

Alinator

PS: Personally, I'd just leave it alone and let BOINC sort it out o its own.

With the current increase in "Ready to Send" and the decrease in "In Progress" I am beginning to wonder if the feeder is actualy communicating with the scheduler in the way it is supposed to.

...Question, do I increase my cache, in-case of continuing problems over Xmas, (if I get WU, this means others go without,) or just run out of seti (if the problem persists) and do E@H?

Looking at cricketgraph, it looks like something is rate limiting in the system. Data out and data in are both smoothly reduced compared to that expected.

As for what cache size... That is almost a religious question with just as many "interpretations"!

For myself, I have a small cache size set (0.5) and a share with a second project. JM7's LTD will keep things evened up across any s@h outage.

If you insist on staying s@h only, then watch out for getting caught by the returns deadline so I'd advise no more than 7 days absolute max. The penalty of such a large cache is that you slow down the credits and validation by those 7 days and some people seem to be "very touchy" about getting their credits now...

Hang in there,

Happy crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

Right after things came back up from the last outage, I bumped to 10 days for about 12 hours to let all my machines soak up a bit of a reserve, then bumped back down to around 2-3.

I also have E@H to fall back on if things here go sour, but I imagine we'll see a cycle of a brief 'stable period' and not until the population curve that migrated here settles in and Berkeley is able to balance allocation of resources.

---

Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT

Hmmm... Maybe the SETI Santa's been looking at the Naughty and Nice list.

:-)

As for what cache size... That is almost a religious question with just as many "interpretations"!
<snip>
If you insist on staying s@h only, then watch out for getting caught by the returns deadline so I'd advise no more than 7 days absolute max. The penalty of such a large cache is that you slow down the credits and validation by those 7 days and some people seem to be "very touchy" about getting their credits now...

If you run a large cache, it probably won't delay credits unduly, as most of the time the other 3 units will be returned & validated first.

However, you will be returning the 4th work unit most of the time, which can touch off the "4th work unit is wasted effort" religious war, so there's still room for "interpretation". [snicker]

I'd just let BOINC handle it, and if someone else gets some crunch time over the holidays, that's fine. I've got one machine that mostly does SETI, with Einstein at a small resource share as backup. During this last outage Einstein got some extra time, and it'll probably be months before it gets to download again...unless SETI runs dry.

---

If you think education is expensive, try ignorance.

Hmmm... Maybe the SETI Santa's been looking at the Naughty and Nice list.

Ahh crap..I'm SOL if that's the case. :)


Plenty of the the -106 errors here...

It's now switched to "no schedulers responded"..

I thought GRRRR..

Then I rememberd It's Wednesday backup time and called myself a prat.

Perhaps if there is a tech issue behind this things will get fixed by the "stop/start" of the various backend processes?

Mean time, E@H is at the sidelines, waiting for a substition to be called... ;-)

---

Foamy is "Lord and Master".
(Oh, + some Classic WUs too.)

Transitioner backlog (hours) 7

been a long time since a number like that was on the serverstatus page.

after the normal outtage at Wednesday

this time it take a bit longer than usuall

21.12.2005 23:30:04||request_reschedule_cpus: process exited
21.12.2005 23:42:24||request_reschedule_cpus: process exited
21.12.2005 23:42:24|SETI@home|Computation for result 29se04ab.3901.28289.940902.15_1 finished
21.12.2005 23:42:24|SETI@home|Starting result 29se04ab.3901.28289.940902.14_2 using setiathome version 411
21.12.2005 23:42:26|SETI@home|Started upload of 29se04ab.3901.28289.940902.15_1_0
21.12.2005 23:42:31|SETI@home|Finished upload of 29se04ab.3901.28289.940902.15_1_0
21.12.2005 23:42:31|SETI@home|Throughput 9765 bytes/sec
21.12.2005 23:48:23|SETI@home|Started upload of 13fe05aa.24442.22050.304816.243_3_0
21.12.2005 23:48:28|SETI@home|Finished upload of 13fe05aa.24442.22050.304816.243_3_0
21.12.2005 23:48:28|SETI@home|Throughput 12483 bytes/sec


it is working again

Greetings from Germany NRW
Ulli

Ulli,

getting rid of our work wasn't the problem, the problem was/is in getting new work ;)