I'm getting a new PC next week I'm going to commit to this project.
Getting a new i7 10th Gen and hoping to get crunching soon.

Before you spend your money, i strongly suggest you checkout some reviews to see just how well those CPUs perform.
And how much better other CPUs perform, at often similar (and often enough cheaper) prices.

And given that in a couple of weeks Zen3 is being released, and if the initial leaks are true, the price for all other CPUs will drop significantly once the new ones are available in volume in order to clear that old stock.
Passmark CPU scores (The Ryzen5 5600X is at the bottom end of the new releases- Ryzen 7 5800X, the Ryzen 9 5900X and the Ryzen 9 5950X are the others to be released initially).

Greetings,

I predict that on or about October 6, 2020, I will hit my second million credits. It seems to take this PC 9 days now to hit 100K. Let's see how close I get. :)

Have a great day! :)

Siran

Greetings,

I'm back! :)

I'm sure many of you have heard about the major destructive storm running through the Mid West on Monday 8/10. We were without power for just over 48 hours. We got TV and Internet back late yesterday afternoon, 8/13. I now have some catchin' up to do here.

Have a great day! :)

Siran

Glad you're safe - infrastructure can be replaced, people can't.

Greetings,

Woohoo!!! In just 3.5 months, give or take, I finally reached a million credits. On to the next million. :)

Have a great day! :)

Siran

Impressive. Now you can consider increasing your runtime from 4hrs to 6hrs before bringing it up to the default 8hrs after another suitable amount of time

Yep, sorry that I didn't check twice, but somehow the escaping backslashs have been substituted away...

---

This forum seems to kill them for some reason, even inside a code block. Wait a sec...

It should look like:
https://pastebin.com/avKg94bv

Sorry, I cannot edit the old post to correct this :(.

The "!" in front of an entry marks a certificate as being deactivated, but you have to apply the changes via a "sudo update-ca-certificates". You could have put a "#" as well (which means "this is a comment"), but this would NOT remove any old existing symlink in "/etc/ssl/certs/" which is also necessary to get rid of the expired cert.

Hi,

to all the Ubuntu guys: Playing around with "/usr/local/share/ca-certificates" is the wrong way to get this fixed. It might be possible that, depending on the order of the certs inside "/etc/ssl/certs/ca-certificates.crt" and/or the version of libcurl, you have to deactivate the expired system-wide cert to get the Boinc client running. This is done by:

# sudo sed -i 's/mozilla/AddTrust_External_Root/!mozilla/AddTrust_External_Root/' /etc/ca-certificates.conf
# sudo update-ca-certificates
Updating certificates in /etc/ssl/certs...
0 added, 1 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.

Now the old cert is not linked within "/etc/ssl/certs/" and not present inside "/etc/ssl/certs/ca-certificates.crt" any longer and the Boinc client works without any restart.

My short tests showed me that Ubuntu 20.04 and 18.04.4 work flawlessly out of the box without the above fix, Ubuntu 16.04.6 though needed this procedure. On all these 3 systems both the old "AddTrust_External_Root" and the new "COMODO_RSA_Certification_Authority" were already installed. There was no need to add the new COMODO cert (also called "1720081") to any of my systems.

Windows users please note: https://github.com/BOINC/boinc/issues/3789#issuecomment-636400593
That means: If your client is no older than 7.9.1/7.10 (so it was shipped with the latest "ca-bundle.crt" from January 2018), it's sufficient to delete the "AddTrust External Root" block in "ca-bundle.crt" and you are done. But be aware: I did not check the exact Boinc client version numbers, they are a guess based on the source code repository!

You might adapt this on other Ubuntu versions and/or Debian based distributions.

Hth and best wishes,

walli

rick@Minty-Winders:~$ sudo sed -i 's/mozilla/AddTrust_External_Root/!mozilla/AddTrust_External_Root/' /etc/ca-certificates.conf
[sudo] password for rick:                 
sed: -e expression #1, char 34: unknown option to `s'
rick@Minty-Winders:~$

-[ snip ]-

Have a great day! :)

Siran

Are you 100% sure 1720081.crt was moved to /usr/local/share/ca-certificates before doing sudo update-ca-certificates?

btw if wasn't necessary to restart BOINC for me, it just worked.

Hopefully tomorrow they can have this resolved.

It isn't a Rosetta issue it is a BOINC issue and it won't be resolved tomorrow, however the solution is in the thread about expired Security Certificates.
Download the new Security Certificate file, copy it to the Programme files, BOINC folder, problem fixed.

The procedure that worked for me on Ubuntu 18.04.4:
(1) Download this file: https://crt.sh/?d=1720081
(2) Place "1720081.crt" in Home directory (e.g., move from desktop)
(3) sudo mv 1720081.crt /usr/local/share/ca-certificates
(4) sudo update-ca-certificates

Siran d'Vel'nahr wrote:

I looked in my Event log and didn't see anything about an expired certificate.

You might need to have http_debug selected in your Event Log options to see that.

Would the "attempting access to reference site" entry be due to an expired cert?

No; that message comes when BOINC is testing Internet access by fetching a ‘test’ URL (by default https://www.google.com/). Google uses its own certificates for SSL and shouldn’t be affected by the certificate expiry that is causing trouble with BOINC projects.

I saw the "transient HTTP error" entry

I see that from time to time, even when Internet access is available. I don’t think it’s necessarily connected to the certificate problem.

Sun 31 May 2020 04:27:35 AM CDT | Rosetta@home | Reporting 6 completed tasks
Sun 31 May 2020 04:27:35 AM CDT | Rosetta@home | Not requesting tasks: too many uploads in progress
Sun 31 May 2020 04:27:35 AM CDT | Rosetta@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
Sun 31 May 2020 04:27:35 AM CDT | Rosetta@home | [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 devices
Sun 31 May 2020 04:27:37 AM CDT | Rosetta@home | Scheduler request failed: Peer certificate cannot be authenticated with given CA certificates
Sun 31 May 2020 04:27:37 AM CDT | Rosetta@home | [sched_op] Deferring communication for 00:01:28
Sun 31 May 2020 04:27:37 AM CDT | Rosetta@home | [sched_op] Reason: Scheduler request failed
Sun 31 May 2020 04:28:00 AM CDT | | Project communication failed: attempting access to reference site
Sun 31 May 2020 04:28:02 AM CDT | | Internet access OK - project servers may be temporarily down.

Yes I also got the transient HTTP error, it´s only when BOINC contacts the scheduler server you get the certificate error.

Even though it says download server is not running it works.

Since you have stuck uploads you might have the certificates expired issue I'm guessing.

Sat 30 May 2020 03:31:30 PM CDT | Rosetta@home | Started upload of Junior_HalfRoid_design6_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_6rn4yt7s_929381_30_0_r1902247366_0
Sat 30 May 2020 03:31:31 PM CDT |  | Project communication failed: attempting access to reference site
Sat 30 May 2020 03:31:31 PM CDT | Rosetta@home | Temporarily failed upload of Junior_HalfRoid_design6_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_6rn4yt7s_929381_30_0_r1902247366_0: transient HTTP error
Sat 30 May 2020 03:31:31 PM CDT | Rosetta@home | Backing off 00:03:18 on upload of Junior_HalfRoid_design6_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_6rn4yt7s_929381_30_0_r1902247366_0
Sat 30 May 2020 03:31:33 PM CDT |  | Internet access OK - project servers may be temporarily down.