Are you sure you didn't wake up still drunk?

Nothing different than the usual headache here.

On the DL side, all stalled DL finished and asking for more work. Will stop to ask for more work since i still have a lot of WU on my cache and leave the others DL first. Back in few hours after all returns to normal.

---

I just requested more work from SETI@home while capturing the network with Wireshark. Both download servers sent me RSTs initially. 208.68.240.119 sent me RST immediately after my computer sent ACK. 208.68.240.127 sent me RST after the HTTP request has been sent. Then I used my web browser to download one of my workunits from 208.68.240.127 and my file download dialog appears. HTTP requests to 208.68.240.119 always results in RSTs. At the moment my workunit is still not downloaded.

It could suggest that on 208.68.240.119 the web server process is crashed, so there is nobody listening on the port 80. The web server on 208.68.240.127 is overloaded and could only serve some of the TCP connections.

I have a computer elsewhere, and that is doing "OK", but main main pile are not getting anything, so it might be that a DNS table has got screwed somewhere, and that could take a good few hours to resolve....

The next machine I tried attempted the right stuff:

01/03/2019 13:42:09 | SETI@home | [http] [ID#2776] Info:  Hostname boinc2.ssl.berkeley.edu was found in DNS cache
01/03/2019 13:42:09 | SETI@home | [http] [ID#2776] Info:    Trying 208.68.240.119...
01/03/2019 13:42:11 | SETI@home | [http] [ID#2776] Info:  connect to 208.68.240.119 port 80 failed: Connection refused
01/03/2019 13:42:11 | SETI@home | [http] [ID#2776] Info:    Trying 208.68.240.127...
01/03/2019 13:42:11 | SETI@home | [http] [ID#2776] Info:  Connected to boinc2.ssl.berkeley.edu (208.68.240.127) port 80 (#3224)

but got the empty server reply, and no download. But at least Georgem is handing off properly, not leaving us to wait through a timeout.

And seven minutes later I got a connection and a dozen downloads on this machine too:

01/03/2019 13:49:06 | SETI@home | Started download of blc36_2bit_guppi_58405_84630_HIP86141_0024.13265.818.22.45.166.vlar
01/03/2019 13:49:06 | SETI@home | [http] [ID#2830] Info:  Re-using existing connection! (#3267) with host boinc2.ssl.berkeley.edu
01/03/2019 13:49:06 | SETI@home | [http] [ID#2830] Info:  Connected to boinc2.ssl.berkeley.edu (208.68.240.127) port 80 (#3267)
01/03/2019 13:49:09 | SETI@home | Finished download of blc36_2bit_guppi_58405_84630_HIP86141_0024.13265.818.22.45.166.vlar

I was finally able to force feed my dl's one at a time, so my queue is now sitting with 90 CPU & 116 GPU tasks that I will now attempt to force feed.

[edit] Looks like the server is handling 1 dl at a time automatically so I don't have to force feed it or someone kicked the side of the bad server and got it working again. [/edit]

[edit2] Looks like I got ahead of myself and ended up to having to force feed 1 @ a time. As soon as I reverted back to more than 1 d/l in the cc_config.xml, everything went to project backoff. So it's back to 1 and force feed. [/edit2].

---

I don't buy computers, I build them!!

Woo Hoo Finally!
Retry #82 cleared a stuck download on my daily Win8 computer that have been there for 8 hours or more, LOL

STILL ongoing retry issues ... Eric owes me a mouse -The clicker is clunky now :(

---

I have a split decision.

About half of my DL's are on "backoff" and half are pending. The ones that are pending are downloading.

Either we hit the magic "everyone is in 25+ hour backoff or something was magically fixed or someone got in there early and rebooted the downed server.

Tom

---

A proud member of the OFA (Old Farts Association).

It's going to be either a long or idle weekend if they don't get this fixed today.

---

Lots of people have given their method of starting the stuck downloads. I have two computers with stuck downloads. I have tried everything people have listed as doing to get theirs started, and still nothing here. I have rebooted computers and am almost at the point of perhaps aborting the downloads.
(back off time keeps changing every time I try a retry)
Is there perhaps something that I have not tried?

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

i just keep clicking retry until it goes through.

sometimes 5 clicks, sometimes 30 clicks.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

A couple of hours ago, topped up my cache for Main & Beta. Got 23 Beta & 15 Main.
4 stuck on Beta & 7 on Main. 4 main D/L without any interference. :-)

i just keep clicking retry until it goes through.

sometimes 5 clicks, sometimes 30 clicks.

I have hit over 100 clicks...………

Just added 50 more tries to one computer.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

The only thing that seems to help is:
<max_file_xfers_per_project>1</max_file_xfers_per_project>

Having with or w/o DNS entries for 119/127 don't seem to help. Although I seem to have better luck with 127.
It's more in timing, as in once you get a connection they start chugging though 200 no problem.

---

On TBar Boinc 7.4.4, the usual (in this type of situations) client crash as soon as I enable network (immediate effect).
I have changed nothing. Crunching is regular as long as cache is not empty.

Lots of people have given their method of starting the stuck downloads. I have two computers with stuck downloads. I have tried everything people have listed as doing to get theirs started, and still nothing here. I have rebooted computers and am almost at the point of perhaps aborting the downloads.
(back off time keeps changing every time I try a retry)
Is there perhaps something that I have not tried?

You have tried restarting the last "stuck" download?

---

A proud member of the OFA (Old Farts Association).

One at a time worked
Just as the last one in the log jam cleared over a hundred new ones arrived in the queue, and instantly stalled :-(

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

One at a time worked
Just as the last one in the log jam cleared over a hundred new ones arrived in the queue, and instantly stalled :-(

But when I hit the retry on the last one, they started up again.....

Tom

---

A proud member of the OFA (Old Farts Association).

There seem to be 2 different types of backoffs: "Rety in:", and "Project".

Selecting the last task when in Project backoff, it appears to try 3 tasks, before returning to Project.
Keep doing that and it eventually goes to individual Retries, where you can select which file to retry.

That is with v7.4, v7.8 may be different.

---

Yesterday I was able to manually retry one at a time until an AP task was stuck on each PC. It wouldn't download so I couldn't get any more. I aborted the DL on one and received 100 tasks. 10 were able to download but nothing more. Hopefully this is fixed soon.

That's been my experience. Everything is fine downloading one at at time UNTIL a AP gets stuck and that is the end of it. No matter how many times that single AP task is retried, (this morning I see an empty machine with one stuck AP task on retry count 36), the only way to get more work is abort that AP task and then then get another block of downloads. And hope that AP snowstorm has ended.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Lots of people have given their method of starting the stuck downloads. I have two computers with stuck downloads. I have tried everything people have listed as doing to get theirs started, and still nothing here. I have rebooted computers and am almost at the point of perhaps aborting the downloads.
(back off time keeps changing every time I try a retry)
Is there perhaps something that I have not tried?

You have tried restarting the last "stuck" download?

What do you mean by " restarting"? Do you mean Retry? If so that is what I have been doing.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Yesterday I was able to manually retry one at a time until an AP task was stuck on each PC. It wouldn't download so I couldn't get any more. I aborted the DL on one and received 100 tasks. 10 were able to download but nothing more. Hopefully this is fixed soon.

That's been my experience. Everything is fine downloading one at at time UNTIL a AP gets stuck and that is the end of it. No matter how many times that single AP task is retried, (this morning I see an empty machine with one stuck AP task on retry count 36), the only way to get more work is abort that AP task and then then get another block of downloads. And hope that AP snowstorm has ended.

I have some APs stuck on the one computer. If as you say they can not be downloaded I will try aborting them after lunch and see if that does anything for downloads on that computer. The other computer has no APs stuck.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours