2 Android tasks waiting to complete downloading

Pi-hole could be a solution.

Thanks for this suggestion, but I have to admit I don't feel confident I understand it or how to do it or whether it might mess something else up, so unfortunately I'm not going to try it.
Sometimes I need a bit of hand-holding and this seems to be just that kind of occasion.

It's definitely me, not you.

---

Now all my host except my Android phones can get Rosetta tasks again.
Too bad there's no known way to edit the hosts file on Android.

This Virtual Host App looks easier to handle than the workaround I mentioned before.

Too bad there's no known way to edit the hosts file on Android.

You can't edit hosts file on Android without root permission, however you can use a local VPN app that modify DNS responces so BOINC app receives "128.95.160.156" when it asked about "boinc-files.bakerlab.org".

personalDNSfilter and Virtual Host are both FOSS and on F-Droid, though I've used neither yet.

https://github.com/IngoZenz/personaldnsfilter
https://github.com/x-falcon/Virtual-Hosts/releases/

If you're using LineageOS or something similar then it's possible to bind mount a modified hosts file in-place with Rooted ADB. But this change will be reverted once your phone rebooted:

https://paste.debian.net/hidden/d218be28/

I was able to get Rosetta to download tasks again on Android. (Yay!)
I'm using both a Samsung Galaxy A13, and a Samsung Galaxy A14.
I installed Personal DNS Filter (pDNSf) from Google Play. In pDNSf,
advanced settings, I pressed Configure additional hosts. I added
>boinc-files.bakerlab.org 128.95.150.156, went back to the main
screen and rechecked to see if the entry was saved, and hit restart.
I also had to clear the DNS cache by running Google Chrome,
entering chrome://net-internals/#DNS as the URL, selecting
the DNS Option, and then clear Host Cache option. After this
I restarted Boinc, clicked reset on the Rosetta Project, and
Update.
I was finally able to download tasks on the A13, and A14.
4 Tasks are running on the A14, and I'm still waiting for Tasks to run
on the A13.
- Ian

I also had to clear the DNS cache

Would have been worth doing that first.
My system is having no issues now without any Rosetta entries in the Host file. If clearing the cache didn't get things going again, then Personal DNS Filter (pDNSf) would have been the next option.

---

Grant
Darwin NT

Too much effort, I wait awhile and if the stuck downloads don't move, I then abort the work units that aren't going to download anyway. Waited over 2 days the first time but don't have time to baby sit Rosetta.

After all these years I shouldn't have to as it should be a well oiled machine by now.

SiDock is working fine and work flow is good, so I will do some more of that.

Conan

---

And yes Conan is on target if Rosetta is running Ok.... fine.... else-wise good science is available on SiDock or Einstein or Milkyway.

Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

SI-Dock might be fine now but will soon be going to ARM only.

Any project will have glitches occasionally, this has an easy workaround so what’s the point of walking?

boinc-process has crapped out again.
Validation backlog resumes.

---

Grant
Darwin NT

Actually I never "walk away" from any Project that I compute for on any of my systems. I only set a Project to "no new tasks" if the Project Admin forecast's an extended outage. I continue to crunch Rosetta and Ralph work as it is available. But I don't modify any of my systems for the benefit of a single project unless the change is neutral or beneficial top all projects.

Have safe and wonderful Holidays

Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

This I know, different target.

Peace :-)

Actually I never "walk away" from any Project that I compute for on any of my systems.

I dropped a lot of projects. Well, some dropped me.

Seti@Home dropped me. So did Hydrogen and Malaria.
One now sends out only GPU work, and I do not do GPU work.
Denis has sent no work since June or July. WCG has been essentially down for two years, but it has MCM1 work from time to time. They just started ARP1, but will be down for a month.

One requires /lib64/libm.so.6: version `GLIBC_2.29' and the latest for my OS (up to date as of today) is libm.so.6 -> libm-2.28.so

---

boinc-process has crapped out again.
Validation backlog resumes.

I strongly suspect that by the time boinc-process comes back online we'll have run out of tasks to download...

---

boinc-process has crapped out again.
Validation backlog resumes.

I strongly suspect that by the time boinc-process comes back online we'll have run out of tasks to download...

Already happened.
I was distracted because it appears the front page is no longer updating as well and the 94k tasks it shows have already been taken up... <sigh>

---

A couple of hours more and we should have 500,000 Tasks waiting for Validation.

---

Grant
Darwin NT

Hi.

Just wondering, is this issue I have been getting currently same as the one recently discussed on this thread? Note that the error does not seem to be related to expired certificate: SSL certificate problem: unable to get local issuer certificate

Thanks.

Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] HTTP_OP::init_get(): https://boinc-files.bakerlab.org/rosetta/download/301/8a_hal_v_hal_8aa_4jp9203_d0_0001_1.flags
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | Started download of 8a_hal_v_hal_8aa_4jp9203_d0_0001_1.flags
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] HTTP_OP::init_get(): https://boinc-files.bakerlab.org/rosetta/download/e4/8a_hal_w_hal_8aa_4jp5147_d368_0001_1.zip
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | Started download of 8a_hal_w_hal_8aa_4jp5147_d368_0001_1.zip
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  Too old connection (261 seconds idle), disconnect it
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  Connection 29 seems to be dead
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  shutting down connection #29
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  TLSv1.3 (OUT), TLS alert, close notify (256):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  Hostname in DNS cache was stale, zapped
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  Found bundle for host: 0x558c468b45b0 [serially]
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  Server does not support multiplex (yet)
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  Host boinc-files.bakerlab.org:443 was resolved.
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  IPv6: (none)
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  IPv4: 128.95.160.135, 128.95.160.134
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:    Trying 128.95.160.135:443...
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  Hostname 'boinc-files.bakerlab.org' was found in DNS cache
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:    Trying 128.95.160.135:443...
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  Connected to boinc-files.bakerlab.org (128.95.160.135) port 443
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  ALPN: curl offers h2,http/1.1
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  TLSv1.3 (OUT), TLS handshake, Client hello (1):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  Connected to boinc-files.bakerlab.org (128.95.160.135) port 443
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  ALPN: curl offers h2,http/1.1
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  TLSv1.3 (OUT), TLS handshake, Client hello (1):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  TLSv1.3 (IN), TLS handshake, Server hello (2):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  TLSv1.2 (IN), TLS handshake, Certificate (11):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  TLSv1.2 (OUT), TLS alert, unknown CA (560):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  SSL certificate problem: unable to get local issuer certificate
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info:  closing connection #32
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] HTTP error: SSL peer certificate or SSH remote key was not OK
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  TLSv1.3 (IN), TLS handshake, Server hello (2):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  TLSv1.2 (IN), TLS handshake, Certificate (11):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  TLSv1.2 (OUT), TLS alert, unknown CA (560):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  SSL certificate problem: unable to get local issuer certificate
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#24] Info:  closing connection #33
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] HTTP error: SSL peer certificate or SSH remote key was not OK
Fri 13 Dec 2024 05:50:07 PM |  | Project communication failed: attempting access to reference site
Fri 13 Dec 2024 05:50:07 PM |  | [http] HTTP_OP::init_get(): https://www.google.com/
Fri 13 Dec 2024 05:50:07 PM | Rosetta@home | Temporarily failed download of 8a_hal_v_hal_8aa_4jp9203_d0_0001_1.flags: transient HTTP error
Fri 13 Dec 2024 05:50:07 PM | Rosetta@home | Backing off 05:00:48 on download of 8a_hal_v_hal_8aa_4jp9203_d0_0001_1.flags

[/b]

Hi.

Just wondering, is this issue I have been getting currently same as the one recently discussed on this thread? Note that the error does not seem to be related to expired certificate: SSL certificate problem: unable to get local issuer certificate

A quick search turned up a few results along the lines of

What causes ‘ssl certificate problem unable to get local issuer certificate’
The unable to get local issuer certificate error is caused by the misconfiguration of the SSL certificate on your local machine. When pushing, pulling, or cloning, Git cannot verify your SSL certification, which leads to the error.
....
To prevent the error, ensure that you have a valid SSL certificate in your certificate store.
If you are using Git via Visual Studio Code and have a valid SSL certificate in your certificate store but still encounter the certificate problem error, use the --global flag on your SSL certificate configuration to grant the Git server accessibility.

Although most of these errors are in relation to Git, it looks like it's an issue on your system, relating to your system's ca-bundle.crt




Edit-
And boinc-process is still dead and Server Status on the main page is still frozen.

---

Grant
Darwin NT

Grant,
THE PROBLEM IS STILL WITH THE SERVER(S) & SSL CERTIFICATE AT THE ROSETTA/BAKER LABS FARM.
Nothing to do with his local certificate(s).

Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info: TLSv1.2 (OUT), TLS alert, unknown CA (560):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info: SSL certificate problem: unable to get local issuer certificate
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info: closing connection #32
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] HTTP error: SSL peer certificate or SSH remote key was not OK

---

Grant,
THE PROBLEM IS STILL WITH THE SERVER(S) & SSL CERTIFICATE AT THE ROSETTA/BAKER LABS FARM.
Nothing to do with his local certificate(s).

Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info: TLSv1.2 (OUT), TLS alert, unknown CA (560):
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info: SSL certificate problem: unable to get local issuer certificate
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] [ID#23] Info: closing connection #32
Fri 13 Dec 2024 05:50:06 PM | Rosetta@home | [http] HTTP error: SSL peer certificate or SSH remote key was not OK

Does changing the IP address in the hosts file as per the original work around post fix it?
For me, i had to change it, but after a few days, going back to the default was OK, and i have had no problems since.


And the fact that we're out now of work isn't going to help resolve things...





EDIT- the message you are getting is different to the message that you and others were getting when the problem was with the servers.

Your current message, and Petr's

Info: SSL certificate problem: unable to get local issuer certificate

The message that was occurring when the problem was with the server, posted by ArcSenda,

SSL certificate problem: certificate has expired

And the one you posted at that time

Info: schannel: next InitializeSecurityContext failed: SEC_E_CERT_EXPIRED (0x80090328) - The received certificate has expired.

Previously, the problem was that the server certificate had expired. Now the messages are pointing to an issue with the Certificates on your system(s).

---

Grant
Darwin NT

Problem is with Curl. Chrome doesn't have any problems connecting.
Complain here: https://github.com/curl/curl/issues