My logs started showing reporting problems starting around 5am EST. Uploads fine just scheduler reports.

Edit: And always as soon as I post here a request goes through...

Well, it worked that one time... now back to not reporting unless I NNT.

It's still a train wreck.
I have to get some more sleep sooner or later, so the update button shall have to rest. And then the asinine Boincmanager backoffs will take hold again.
As well as the asinine 100 WU GPU limits.

Whatever.

I have my rigs all pledged to 100% Seti service.
If the Seti servers are not up to that pledge, the kitties go elsewhere.
Not that I am happy about it.

I just don't have 24/7 to sit here and punch the buttons to avoid the dang backoffs.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Cricket bits out still spiraling ever so slowly downwards. Hope someone can fix it all before the weekend curtain.

---

I cant get a thing even with NNT set for all 3 computers.

---

[/quote]

Old James

Cricket bits out still spiraling ever so slowly downwards. Hope someone can fix it all before the weekend curtain.

No worries here no more.
The kitties have all the rigs set to full time Seti.
When that does not happen for any reason, Einstein sets in on the zero workshare default mode.

I just don't sweat it anymore. I may bitch about it from time to time, but I realize, as one who has been here for over 12 years, it just all works out.

Or doesn't, as the case may be. I know what I want to happen, and when it doesn't, I go to sleep and dream about what might be.

These things are quite apparent to myself, and wish they would be to most Seti users. It just DON't work all the time. Most of the user's computers don't either.

---

"Time is simply the mechanism that keeps everything from happening all at once."

still cannot report/get any w/u here yet. So I guess its not all fixed yet?

Nairb

---

Still borked- inbound network traffic has dropped off considerably. Looks like problems started around 12 hours ago, but it became really bad about 2-3 hours ago.
"Scheduler request failed: Couldn't connect to server" is about the only response i'm getting. Occasionally i get some work, but not often enough to keep what little cache i've got. It's not so slowly dwindling.

---

Grant
Darwin NT

Cricket still showing that "average bits out" is still declining slowly but steadily, so there must be a blockage in the pipe somewhere.
Call for DynaRod!

---

Problems connecting to scheduler:
12/01/2013 07:11:16 | SETI@home | [sched_op] Fetching master file
12/01/2013 07:11:16 | SETI@home | Fetching scheduler list
12/01/2013 07:11:19 | SETI@home | [sched_op] Got master file; parsing
12/01/2013 07:11:19 | SETI@home | [sched_op] Found 1 scheduler URLs in master file
12/01/2013 07:11:19 | SETI@home | Master file download succeeded
12/01/2013 07:11:24 | SETI@home | [sched_op] Starting scheduler request
12/01/2013 07:11:24 | SETI@home | Sending scheduler request: To report completed tasks.
12/01/2013 07:11:24 | SETI@home | Reporting 28 completed tasks, not requesting new tasks
12/01/2013 07:11:24 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
12/01/2013 07:11:24 | SETI@home | [sched_op] NVIDIA work request: 0.00 seconds; 0.00 devices
12/01/2013 07:11:47 | SETI@home | Scheduler request failed: Couldn't connect to server
12/01/2013 07:11:47 | SETI@home | [sched_op] Deferring communication for 1 min 57 sec
12/01/2013 07:11:47 | SETI@home | [sched_op] Reason: Scheduler request failed

Still the cricket graph shows green.....

---

Still the cricket graph shows green.....

The green is not the problem. Us crunchers reporting work are represented by the blue line. "Bits out" means out to Eric and pals. The green is "bits in" from Berkeley on their way to the world.
I know this is counter-intuitive but that's the way it works!

---

My scheduler contacts are slow, but they go through about 90% of the time. The most recent one was over 60 seconds to acknowledge 3 completed tasks.

I'm still not really a fan of the project back-off mechanism, but last night when I had 11 APs that were all trying to download at the same time, I was getting way too sleepy to help them along. I decided to just leave it be and BOINC will make it work. Woke up 7 hours later and they had all finished just fine.. in addition to four more.

But it is the scheduler contacts mainly that could use some tweaking to try to make them a little more reliable and speedy. Or a bigger download pipe. Or maybe an off-site download mirror that has a >= gigabit link and the existing 100mbit pipe can be used solely for sending new data to the mirror. Just some ideas. I know the off-site thing has been mentioned before and the staff isn't too keen on the idea, but unless we can get our 100mbit limit increased to 150 or 200, it's just going to be painful headaches from here on out.

---

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

Update on No New Tasks increases the retry timer....:(.. I have not been able to report WU for last 12 hours. Not getting any new WU either...

---

I don't believe they have the time and resources to do what they want but to say the guys in the lab "don't care" is to me and insult.

Bernie, I don't know what to suggest except that you either read what I wrote and accept that I used my words correctly, or that you just be insulted or offended all over the place.

I said that "I fear," meaning that I am afraid of that, not that I have evidence of that.

I fear one of my children may die before me, because I would find that a traumatic event.

In a similar, but far, far less important way, I would hate to learn that the guys in the lab don't care.

I'm hardly a coward. My word choice was not a clever way of saying something without saying it.

If I meant, "The guys in the lab at SETI don't care about this project anymore since they are busy with their high-speed spectrometer and other data they've recently acquired from Green Bank," I would have no problem, at all, saying that, on the record, right here.

If I held that opinion, it certainly wouldn't be pointed at, or meant to offend, or insult, you.

That isn't even what I said. Read it again with a different inflection.

Perhaps we are having a U.S. vs. U.K. usage of words problem?

"and insult" to whom, Bernie?

---

That they've gone to the effort to inform the fund raisers of their requirements would indicate to most people that they do care.

Hey Grant,

I may know more about that than you do, and it's entirely possible that I was the very first person to contribute to that fundraiser and made the first public plea for others to do likewise --- before it was even announced.

BUT, I don't need, or appreciate, you or anyone else putting words in my mouth.

The word is "fear" and denotes anxiety.

If I need someone to tell me what I meant, I'll be sure to call for help.

---

Very close to 3 minute TCP timeout for scheduler. The Scheduler transactions seems to take some time again:

12/01/2013 10:17:20 | SETI@home | update requested by user
12/01/2013 10:17:24 | SETI@home | [sched_op] Starting scheduler request
12/01/2013 10:17:24 | SETI@home | Sending scheduler request: Requested by user.
12/01/2013 10:17:24 | SETI@home | Reporting 36 completed tasks, not requesting new tasks
12/01/2013 10:17:24 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
12/01/2013 10:17:24 | SETI@home | [sched_op] NVIDIA work request: 0.00 seconds; 0.00 devices
12/01/2013 10:17:47 | SETI@home | Scheduler request failed: Couldn't connect to server
12/01/2013 10:17:47 | SETI@home | [sched_op] Deferring communication for 3 hr 3 min 49 sec
12/01/2013 10:17:47 | SETI@home | [sched_op] Reason: Scheduler request failed
12/01/2013 10:17:57 | SETI@home | work fetch resumed by user
12/01/2013 10:36:51 | SETI@home | update requested by user
12/01/2013 10:36:55 | SETI@home | [sched_op] Starting scheduler request
12/01/2013 10:36:55 | SETI@home | Sending scheduler request: Requested by user.
12/01/2013 10:36:55 | SETI@home | Reporting 36 completed tasks, requesting new tasks for CPU and NVIDIA
12/01/2013 10:36:55 | SETI@home | [sched_op] CPU work request: 202266.66 seconds; 0.00 devices
12/01/2013 10:36:55 | SETI@home | [sched_op] NVIDIA work request: 224640.00 seconds; 2.00 devices
12/01/2013 10:39:50 | SETI@home | Scheduler request completed: got 128 new tasks
12/01/2013 10:39:50 | SETI@home | [sched_op] Server version 701
12/01/2013 10:39:50 | SETI@home | Project requested delay of 303 seconds
12/01/2013 10:39:50 | SETI@home | [sched_op] estimated total CPU task duration: 206174 seconds
12/01/2013 10:39:50 | SETI@home | [sched_op] estimated total NVIDIA task duration: 88822 seconds

---

BUT, I don't need, or appreciate, you or anyone else putting words in my mouth.

I didn't put any words there, i used the exact words you posted.

I did say my "fear" is that nobody cares, and by "nobody" I meant anyone who could do anything about server issues.

right from the post you made- http://setiathome.berkeley.edu/forum_thread.php?id=70431&postid=1326112

I said that "I fear," meaning that I am afraid of that, not that I have evidence of that.

I fear one of my children may die before me, because I would find that a traumatic event.

In a similar, but far, far less important way, I would hate to learn that the guys in the lab don't care.

The only reason to fear something as you describe it there, is because you consider it possible.
No, you didn't come out & say out right that they don't care, you just implied it.

If I need someone to tell me what I meant, I'll be sure to call for help.

I have no idea what you meant, i can only go by what you post & what you posted implies that those running the project don't care about the issues they are having.

---

Grant
Darwin NT

The only reason to fear something as you describe it there, is because you consider it possible.

... what you posted implies that those running the project don't care about the issues they are having.

Non sequitur. Saying something is possible doesn't turn it into a certainty.

"When you have eliminated the impossible, whatever remains, however improbable, must be the truth" (Sherlock Holmes). But that doesn't apply here - there are a lot more possibilities left than the highly unlikely one that the project staff don't care, as evidenced by Matt's New Year post.

[panic on]
Last well scheduler server contact at 12 Jan 2013, 12:34:52 UTC.
Since then:

Scheduler request failed: Couldn't connect to server
Scheduler request failed: Failure when receiving data from the peer

[/panic on]

[panic off]
Just now.. - OK, at 14:14 UTC again contact. ;-)
[/panic off]

[EDIT:
[panic on]
It was just one well contact since then again ..

Scheduler request failed: Couldn't connect to server

[/panic on]]


* Best regards! :-) * Sutaru Tsureku, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

---

No work or scheduler connects for over 24 hours now per BOINCTasks. Have been out of gpu work for about 18 hours, crunching Einstein on zero resource share to stay busy.

I'm puzzled by the Cricket Graph. It still shows downloads are maxxed out, saying that many are getting work. Is this another issue like the old HE conncection issue where only certain computers or IP addresses are blocked?

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Finally got thru - logjam is slightly abating as the incoming traffic
has finally made it above 10
Cur: 10.12 Mbits/sec
First Contact in over 24 hours with or without proxy.
lost tasks were mostly shorties
funny thing was I got one of those red BOINC messages saying I lost contact
with the internet during the request that finally made it thru??

Im just going to let my machines go to other projects. two allready are, One still has work for maybe 8 hours. They are going to shut down for maintenace anyway so im not going to fight an uphill battle trying to get work.

---

[/quote]

Old James