It's worsening.

07/01/2018 20:27:32 | SETI@home | Started download of blc05_2bit_guppi_57976_12239_HIP91971_0040.3044.818.21.44.69.vlar
07/01/2018 20:27:32 | SETI@home | Started download of blc05_2bit_guppi_57976_11873_HIP91144_0039.2611.818.21.44.58.vlar
07/01/2018 20:27:34 |  | Project communication failed: attempting access to reference site
07/01/2018 20:27:34 | SETI@home | Temporarily failed download of blc05_2bit_guppi_57976_12239_HIP91971_0040.3044.818.21.44.69.vlar: transient HTTP error
07/01/2018 20:27:34 | SETI@home | Backing off 00:02:48 on download of blc05_2bit_guppi_57976_12239_HIP91971_0040.3044.818.21.44.69.vlar
07/01/2018 20:27:34 | SETI@home | Temporarily failed download of blc05_2bit_guppi_57976_11873_HIP91144_0039.2611.818.21.44.58.vlar: transient HTTP error
07/01/2018 20:27:34 | SETI@home | Backing off 00:03:47 on download of blc05_2bit_guppi_57976_11873_HIP91144_0039.2611.818.21.44.58.vlar
07/01/2018 20:27:36 |  | Internet access OK - project servers may be temporarily down.

I'm not going to babysit this system.

---

I'm not going to babysit this system.

Edit, paste, save, walk away.

I really don't feel like editing in the command prompt, plus I'm packing and getting ready for taxes so.... That is why I have back up projects. Yes, the RAC will fall but I got my eye on a white beach with margaritas on them. I'll check back in next week, lol...

---

We just suggested Notepad. But have a nice holiday anyway.

I've always liked the trick where you use the File Manager to traverse to the desired directory. Then hold down the SHIFT key and then right-click in the File Manager window pane and select the "Open command window here" option. That pops open a command window where you can work on the files in that directory. If you are the Administrator already, not necessary to elevate to Administrator privileges to begin with.

---

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

A proud member of the OFA (Old Farts Association)

Richard and Keith,

I was too lazy to go edit the Hosts file on my own and your two notes did it all for me.

By the time I went back into BoincTasks, it had cleared all the files in retry mode that had been sitting there.

Thanks!

John

---

As I don't understand the remedy proposed I will leave the computer as is until the issue is fixed next week and just keep crunching best I can..

Cheers

Hmm... time to modify the hosts file :/ issue with the inability to download WUs occurred again.

Yes, thank you, Richard, for the reminder.
I had never used the hosts file in the past, but I am now, and it seems to have done the trick.

+1
Now the trick will be to remember this lesson the next time the issue arises, which I assume it will.

---

"Sour Grapes make a bitter Whine." <(0)>

Richard and Keith,

I was too lazy to go edit the Hosts file on my own and your two notes did it all for me.

By the time I went back into BoincTasks, it had cleared all the files in retry mode that had been sitting there.

Thanks!

John

@John, good to hear. Keep watching this thread or possibly the News forum for any mention next week from the staff fixing the download servers error. Good computer practice is to let the DNS servers do their normal job of keeping track of computer IP addresses and automatically manage any changes invisibly on your part. This override using the Hosts file for explicit discovery of the download servers is just to get work for now. When things are back to normal, you can comment out the respective SETI server lines in the Hosts file. No need to remove them and you can just uncomment them in the file for the next SETI upset if/when it happens.

---

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

A proud member of the OFA (Old Farts Association)

One quick solution that worked for 4 of my machines:

1. Start > Run > cmd.exe [Enter]
2. ipconfig /flushdns [Enter]
3. Re-try pending WU transfers
4. Repeat step #2 if necessary
5. Once workunit transfer(s) are successful, exit the command prompt window.

Note: If you receive access denied error on step 2, then exit the command prompt window, repeat step 1, and right click on cmd.exe and select Run as Administrator before pressing [Enter].

Alternatively, you can "block" the DNS lookup for the "Vader" Server, as it is taking a siesta/having issues.
This is best done by modifying the Windows HOSTS file (as others have stated above).

Well, if it helps, a brief explanation is given here. Below, is what is contained in my current file which is running under Win 7/64 Pro, so, you could always add to or modify your existing file manually or just cut and paste....then save. The relevant parts are the bottom three lines and the second of those is the one that needs the # restoring to the start of the line when the current problems are resolved. It has come in useful in recent months....a little more frequently than I'd appreciate!

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
#
#208.68.240.118 setiboincdata.ssl.berkeley.edu # upload server Oct 2016
208.68.240.119 boinc2.ssl.berkeley.edu # download server Oct 2016
#208.68.240.126 setiboinc.ssl.berkeley.edu # scheduler Oct 2016[/url]

---

Don't take life too seriously, as you'll never come out of it alive!

Uhh, No. You have commented out the scheduler. It is not having issues.

#208.68.240.118 setiboincdata.ssl.berkeley.edu # upload server Oct 2016
208.68.240.119 boinc2.ssl.berkeley.edu # download server Oct 2016
#208.68.240.126 setiboinc.ssl.berkeley.edu # scheduler Oct 2016[/url]

You want to comment out 208.68.240.127 which is Vader, the second download server

---

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

A proud member of the OFA (Old Farts Association)

Uhh, No. You have commented out the scheduler. It is not having issues.

#208.68.240.118 setiboincdata.ssl.berkeley.edu # upload server Oct 2016
208.68.240.119 boinc2.ssl.berkeley.edu # download server Oct 2016
#208.68.240.126 setiboinc.ssl.berkeley.edu # scheduler Oct 2016[/url]

You want to comment out 208.68.240.127 which is Vader, the second download server

No, Iona's file is perfect.

The host file ensures that ONLY Georgem is used for downloads, but all other servers (commented out) use DNS lookups as normal.

Found some hangs on the other machine and executed the fix.

@Iona: Just paste the following into the hosts file,

208.68.240.118 setiboincdata.ssl.berkeley.edu # upload server Oct 2016
208.68.240.119 boinc2.ssl.berkeley.edu # Georgem download server Oct 2016
208.68.240.126 setiboinc.ssl.berkeley.edu # scheduler Oct 2016
#208.68.240.127 vader.ssl.berkeley.edu # Vader download server Oct 2016

works like a charm.(even though it's not a daemon........ ":>)

---

"Sour Grapes make a bitter Whine." <(0)>

That will do the trick, but it's overkill - it will micro-manage servers that don't need any help (this time).

We needed to control every server back in August (when we lost DNS completely), but that's not the case this time.

Haha...thought I had all my ducks in a row when I edited the hosts file 6 months ago. Not so !
When I went to comment out vader, I discovered that I had saved the file as .txt, and had of course not been used at all with the BOM.
This can easily happen if your concentration slips, as mine did. Just a tip...

---

Humans may rule the world...but bacteria run it...

This.

07/01/2018 22:34:18 | SETI@home | Started download of blc05_2bit_guppi_57976_10703_HIP74981_0036.8260.409.22.45.174.vlar
07/01/2018 22:34:20 | SETI@home | Temporarily failed download of blc05_2bit_guppi_57976_10703_HIP74981_0036.8260.409.22.45.174.vlar: transient HTTP error
07/01/2018 22:34:20 | SETI@home | Backing off 00:07:58 on download of blc05_2bit_guppi_57976_10703_HIP74981_0036.8260.409.22.45.174.vlar
07/01/2018 22:34:21 | | Project communication failed: attempting access to reference site
07/01/2018 22:34:22 | | Internet access OK - project servers may be temporarily down.
07/01/2018 22:35:06 | SETI@home | Started download of blc05_2bit_guppi_57976_10365_HIP74315_0035.6135.409.21.44.88.vlar
07/01/2018 22:35:07 | SETI@home | Temporarily failed download of blc05_2bit_guppi_57976_10365_HIP74315_0035.6135.409.21.44.88.vlar: transient HTTP error
07/01/2018 22:35:07 | SETI@home | Backing off 00:04:08 on download of blc05_2bit_guppi_57976_10365_HIP74315_0035.6135.409.21.44.88.vlar
07/01/2018 22:35:08 | | Project communication failed: attempting access to reference site
07/01/2018 22:35:08 | SETI@home | Started download of blc05_2bit_guppi_57976_10703_HIP74981_0036.8221.409.21.44.31.vlar
07/01/2018 22:35:09 | | Internet access OK - project servers may be temporarily down.
07/01/2018 22:35:09 | SETI@home | Temporarily failed download of blc05_2bit_guppi_57976_10703_HIP74981_0036.8221.409.21.44.31.vlar: transient HTTP error
07/01/2018 22:35:09 | SETI@home | Backing off 00:04:13 on download of blc05_2bit_guppi_57976_10703_HIP74981_0036.8221.409.21.44.31.vlar

One quick solution that worked for 4 of my machines:

1. Start > Run > cmd.exe [Enter]
2. ipconfig /flushdns [Enter]
3. Re-try pending WU transfers
4. Repeat step #2 if necessary
5. Once workunit transfer(s) are successful, exit the command prompt window.

Note: If you receive access denied error on step 2, then exit the command prompt window, repeat step 1, and right click on cmd.exe and select Run as Administrator before pressing [Enter].

Alternatively, you can "block" the DNS lookup for the "Vader" Server, as it is taking a siesta/having issues.
This is best done by modifying the Windows HOSTS file (as others have stated above).

You need a space between ipconfig and /flushdns.

---

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

You need a space between ipconfig and /flushdns.

Umm, no ... either way is fine

C:\Users\Jim>ipconfig/flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

---