World Community Grid - View Thread - Password missing

Had the FMC[??] Password issue and rebooted computer and RESET the WCG project. Transient HTTP error on downloading WCG project file set.

So, I checked https://boinc.berkeley.edu/download.php for an updated version (there was none) and downloaded the same version and re-installed from the new copy of boinc_7.20.2_windows_x86_64_vbox.exe and selected REPAIR.

Again got the Transient HTTP error when attempting to restore project file set again.

Then noticed that I had the TIME STAMP OF 12/31/1969... in Event log:

8/25/2022 9:22:03 AM | World Community Grid | [http] [ID#123] Info: ALPN: server accepted http/1.1
8/25/2022 9:22:03 AM | World Community Grid | [http] [ID#123] Sent header to server: GET /boinc/slideshow/scc1_04_v01.png HTTP/1.1
8/25/2022 9:22:03 AM | World Community Grid | [http] [ID#123] Sent header to server: Host: download.worldcommunitygrid.org
12/31/1969 7:00:00 PM | World Community Grid | [http] [ID#123] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.20.2)
8/25/2022 9:22:03 AM | World Community Grid | [http] [ID#123] Sent header to server: Accept: */*
8/25/2022 9:22:03 AM | World Community Grid | [http] [ID#123] Sent header to server: Accept-Encoding: deflate, gzip
8/25/2022 9:22:03 AM | World Community Grid | [http] [ID#123] Sent header to server: Accept-Language: en_US

Note timestamp of 12/31/1969!! system PAUSED at that point for 2 or 3 seconds, then resumed displaying the log and attempting downloading of WCG file set.

System currently is not connecting to server so WCG may have that portion offline for planned work.

Anyone have any ideas?
Bruce

Yes, just wait.

Sorry, but I am sometimes really puzzled to see to what length people sometimes go to "troubleshoot" a problem, with the possibility just to make things worse and introduce new variables in the mix.

By now, everyone trying to crunch for WCG should know that WCG/Krembil has major issues with their setup, months into the "restart"/testing. That means that at any time, you can get all kinds of error messages.

"Transient http" error means it is a "temporary" transmission error, and most commonly, on the server side. The https protocol has been designed with a lot of resilience in mind and transient means here that the client (be it a web browser, which is commonly suppressing these kinds of errors, as they are considered "non-critical") and keeps retrying the connection. Reinstalling/updating a http (in this case BOINC) client isn't going to do anything in such a case (maybe one in a million).

Also, there is no http error code being shown, that means it is not even considered an "informational error" (with an 1xx error code). Only 4xx error codes are client side (like the infamous 404) while 5xx error codes would be hard server side error conditions (like 503 Service not available).

Also an indicator that this is not an issue on your side (which obviously is a Windows host, going by the client file you said you downloaded) is that erroneous time stamp you have been referring to.
12/31/1969 is the day before the start of what is called the "epoch" for Unix (Linux) time stamping, which starts counting at 00:00h 1/1/1970 and an indication of an invalid time stamp. That also indicates that this is an error on the server side, running Unix/Linux (or a Unix derivative) and not your local Windows host. If a Windows host would through an error with an invalid timestamp, it would be most likely 1/1/1980, which is actually the old DOS epoch, though newer version of Windows have the "start of time" as 1/1/1601 now.

Please don't see this anything personal, it really just bugs me deeply that there is no plan or concept on either side on how to properly deal with the ongoing issues with WCG... sad

Ralf