HADSM4.
scheduler request failed; ssl peer certificate or ssh remote key was not ok.
Another problem is. on the first attempt to access the server page, I land somewhere else.
Intermittent service is another.

Just had a hadsm4 zip go through with no problems. if you are still getting problems could you post the output in the event log with http debug enabled please.

Linux and Internet problems. I will try later but this line is standard: scheduler request failed; ssl peer certificate or ssh remote key was not ok.

HADSM4.
scheduler request failed; ssl peer certificate or ssh remote key was not ok.
Another problem is. on the first attempt to access the server page, I land somewhere else.
Intermittent service is another.

We need to disentangle that issue from the other problems in this thread.

Most of the recent problems have been concerning the large data files being transferred to Australia / New Zealand. They stall, they try again, and sometimes they get through. That's a delay.

An SSL peer certificate error is a security issue. It's an absolute blocker. It'll never work. You need to do something about that.

What operating system are you using? What version of BOINC are you using?

Certificate problems have mainly affected BOINC users running Windows. Under Windows, you should be running either v7.16.20 or v7.20.2 of BOINC, following a certificate expiry in September last year. There are manual workrounds, but an upgrade it easiest.

"An SSL peer certificate error is a security issue. It's an absolute blocker. It'll never work. You need to do something about that."

I think that was something someone else brought up. They are asking their own questions over the top of mine.

I think that was something someone else brought up.

Yes, I was replying to KAMasud in message 65855, but it's an important point that shouldn't be overlooked.

Perhaps a mod could separate that part of the conversation into another thread?

Richard, that certificate issue, HADSM4 on Linux in VM, OS Mint.
Windows is also involved but with something else. Here
18/08/2022 9:35:34 pm | | Suspending computation - CPU is busy
18/08/2022 9:35:44 pm | | Resuming computation
18/08/2022 10:08:54 pm | climateprediction.net | Sending scheduler request: To send trickle-up message.
18/08/2022 10:08:54 pm | climateprediction.net | Requesting new tasks for CPU
18/08/2022 10:08:57 pm | climateprediction.net | Scheduler request completed: got 0 new tasks
18/08/2022 10:08:57 pm | climateprediction.net | No tasks sent
18/08/2022 10:08:57 pm | climateprediction.net | Project requested delay of 3636 seconds
18/08/2022 10:09:01 pm | climateprediction.net | Started upload of wah2_nz25_a07s_198705_25_936_012150042_0_r724561270_9.zip
18/08/2022 10:14:08 pm | climateprediction.net | Temporarily failed upload of wah2_nz25_a07s_198705_25_936_012150042_0_r724561270_9.zip: transient HTTP error
18/08/2022 10:14:08 pm | climateprediction.net | Backing off 00:02:18 on upload of wah2_nz25_a07s_198705_25_936_012150042_0_r724561270_9.zip
18/08/2022 10:14:09 pm | | Project communication failed: attempting access to reference site
18/08/2022 10:14:11 pm | | Internet access OK - project servers may be temporarily down.
19/08/2022 12:40:47 am | climateprediction.net | Started upload of wah2_nz25_a2db_200605_25_936_012152833_0_r1306077880_14.zip
19/08/2022 12:40:47 am | climateprediction.net | Started upload of wah2_nz25_a2db_200605_25_936_012152833_0_r1306077880_19.zip
19/08/2022 12:45:54 am | climateprediction.net | Temporarily failed upload of wah2_nz25_a2db_200605_25_936_012152833_0_r1306077880_14.zip: transient HTTP error
19/08/2022 12:45:54 am | climateprediction.net | Backing off 05:37:33 on upload of wah2_nz25_a2db_200605_25_936_012152833_0_r1306077880_14.zip
19/08/2022 12:45:54 am | climateprediction.net | Temporarily failed upload of wah2_nz25_a2db_200605_25_936_012152833_0_r1306077880_19.zip: transient HTTP error
19/08/2022 12:45:54 am | climateprediction.net | Backing off 05:44:54 on upload of wah2_nz25_a2db_200605_25_936_012152833_0_r1306077880_19.zip
19/08/2022 12:45:55 am | | Project communication failed: attempting access to reference site
19/08/2022 12:45:56 am | | Internet access OK - project servers may be temporarily down.
19/08/2022 1:26:36 am | climateprediction.net | Sending scheduler request: To send trickle-up message.
19/08/2022 1:26:36 am | climateprediction.net | Requesting new tasks for CPU
19/08/2022 1:26:38 am | climateprediction.net | Scheduler request completed: got 0 new tasks
19/08/2022 1:26:38 am | climateprediction.net | Project has no tasks available
19/08/2022 1:26:38 am | climateprediction.net | Project requested delay of 3636 seconds
19/08/2022 1:26:44 am | climateprediction.net | Started upload of wah2_nz25_a0i4_199005_25_936_012150414_0_r1403527717_23.zip
19/08/2022 1:31:51 am | climateprediction.net | Temporarily failed upload of wah2_nz25_a0i4_199005_25_936_012150414_0_r1403527717_23.zip: transient HTTP error
19/08/2022 1:31:51 am | climateprediction.net | Backing off 00:02:57 on upload of wah2_nz25_a0i4_199005_25_936_012150414_0_r1403527717_23.zip
19/08/2022 1:31:52 am | | Project communication failed: attempting access to reference site
19/08/2022 1:31:54 am | | Internet access OK - project servers may be temporarily down.
19/08/2022 1:32:40 am | climateprediction.net | Started upload of wah2_nz25_a1m2_199905_25_936_012151852_0_r334298915_15.zip
19/08/2022 1:37:48 am | climateprediction.net | Temporarily failed upload of wah2_nz25_a1m2_199905_25_936_012151852_0_r334298915_15.zip: transient HTTP error
19/08/2022 1:37:48 am | climateprediction.net | Backing off 00:03:12 on upload of wah2_nz25_a1m2_199905_25_936_012151852_0_r334298915_15.zip
19/08/2022 1:37:49 am | | Project communication failed: attempting access to reference site
19/08/2022 1:37:50 am | | Internet access OK - project servers may be temporarily down.


You are correct, there is a duel conversation going on. Mod's can separate them.

Richard, that certificate issue, HADSM4 on Linux in VM, OS Mint.

I'm out of my depth there. Linux uses system certificates, not the BOINC ones. I can't say whether it will be using the native host OS certificates, or the VM ones. I suspect the VM - you may need to update your VM Linux image.

Place holder to move items from another thread.

you may need to update your VM Linux image.

I have an Ubuntu VM using VB. I update the guest distribution every couple of weeks or so and have never had a certificate issue with it so it may be as simple as running

sudo apt update
sudo apt upgrade

in the guest OS.

you may need to update your VM Linux image.

I have an Ubuntu VM using VB. I update the guest distribution every couple of weeks or so and have never had a certificate issue with it so it may be as simple as running

sudo apt update
sudo apt upgrade

in the guest OS.

:) Thank you, Dave. That got rid of that thing.

My trickles are going somewhere but my "Ready to report" is going nowhere. I have two ready-to-report and one computation error just sitting. I have upgraded and updated. Zilch.

Those problems are a server side problem.
There's nothing that you can do at your end.

If they've been there a while, then they may be from when a server was having problems, such as being overwhelmed with files being returned. They may be a permanent feature of your computer list now.

I think you are correct. The last time the VM had this problem, I derated it to minimum RAM and one CPU then let it sit peacefully. One day they all vanished and the problem was solved.
PS. Can the spelling of the certificate be corrected?

I got a WSL not available. Went to check what it was and downloaded it and ended up with Ubuntu. All my VM's on Ubuntu got corrupted.
Anyway between the blue screen of death due to my experiment with Windows 11 and WSL all my WU's are in limbo. I have no WU just now. So, can someone show all the WU's against my computers as abandoned and get them re-issued?

Sadly not. This has been asked here several times in the past over the years.

Edit: Meaning the project either don't want to as if they did it for all the people who have that sort of issue, it would distract from other work. Pretty sure that is what they would say. I can't remember what was said last time the question was asked.

If you're referring to BOINC event log mention of WSL availability - that's normal. BOINC checks for it like it does for VBox automatically. That's to see if projects that require VBox or WSL can be run on your machine. I'm not aware of any projects that required WSL at the moment although WSL can be used to virtualize Linux in Windows to run Linux projects.

It's definitely best practice to let CPDN tasks run to completion without interruptions as the risk of crashing them is very real and setting up any kind of virtualization will pretty much always require a system restart.

Those tasks will be re-assigned but to other users, unless your attempt was the last attempt available for a given task/model.

Assuming you can still get BOINC up and running then detatch from CPDN, leave it several minutes then re-attatch. That should then mark them as abandoned and the tasks can be re-issued quickly. Otherwise they would have to wait until the "target" date is reached - which is some months down the line.