Bedrock Linux: a Void fetch problem

jr_bob_dobbs · 06-09-2020, 06:59 PM

Installed a Buildroot Linux system on a volume (real hardware, not emulated) and hijacked that. No problems. Got net. Tried to fetch a Void stratum:

Code:

# brl fetch void
[ 1/16 (  6%)] Determining name
* Using void
[ 2/16 ( 12%)] Determining CPU architecture
* Using x86_64
[ 3/16 ( 18%)] Determining release
* Using rolling
[ 4/16 ( 25%)] Determining mirror
* Checking bedrock.conf [brl-fetch-mirror] items
[\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\] 100%
* Finding fastest mirror from 4
[\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\] 100%
* Using https://alpha.us.repo.voidlinux.org/
[ 5/16 ( 31%)] Making bootstrap directory structure
[ 6/16 ( 37%)] Downloading package information database
Connecting to alpha.us.repo.voidlinux.org (198.204.250.219:443)
saving to '/bedrock/strata/void/brl-bootstrap/repodata.tar.zstd'
repodata.tar.zstd    100% |****************************************************| 1641k  0:00:00 ETA
'/bedrock/strata/void/brl-bootstrap/repodata.tar.zstd' saved
[ 7/16 ( 43%)] Downloading bootstrap software
* Using cached /bedrock/var/cache/brl-fetch-void-rolling-x86_64/xbps.tar.zstd
[ 8/16 ( 50%)] Preparing bootstrap software
[ 9/16 ( 56%)] Running bootstrap software[*] Updating repository `https://alpha.us.repo.voidlinux.org//current//x86_64-repodata' ...
Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
SSL_connect returned 1
ERROR: [reposync] failed to fetch file `https://alpha.us.repo.voidlinux.org//current//x86_64-repodata': Operation not permitted
ERROR: Unexpected error occurred.
If you let brl-fetch automatically choose a mirror, it may have chosen a bad one.  Try manually providing a mirror with --mirror
#

Tried several times over the next few days. I even specified a mirror manually: no difference.

Installed debian in qemu. hijacked it. Tried to fetch void. It fetched fine, first try.

My guess is that some handling of DNS or certificates is being handled oddly by buildroot. If this is so, then it is not a bedrock problem. I just thought i would mention it here in case my guess is incorrect.

Thank you.

p.s. in the mean time, the void strata was copied out from the qemu system to the bedrock on real hardware and has seen been run as an init stratum without incident.

ParadigmComplex · 06-09-2020, 07:57 PM

Other people have reported this as well. If it happened consistently, I'd think it was an issue on Void's end, as other people do report this independent of Bedrock:

However, in this case, some Bedrock users are running into this and some aren't, making me think it's not purely an upstream Void issue. I've yet to reproduce the issue myself or figure out what differentiates between those who run into this and those who don't.

Check is that time/timezone information is correct. It could be your system thinks the cert expired due to timezone shenanigans. Given other people have run into this, this guess is a long shot.

The step that's erroring runs in a chroot that's _almost_ independent of the host system. It shares things like `/proc` (that's almost certainly unrelated) and `/etc/ssl` (which totally could have been related, but in quick and dirty tests doesn't appear to be the case).

When I get the time, I'm probably going to ask someone who does reproduce this to strace it and look at the logs, but I don't have the bandwidth for that at the moment.

jr_bob_dobbs · 06-12-2020, 12:51 PM

OK, your reply gave me the clue: time zones. Thank you!

My computer uses GMT (aka UTC) so Buildroot has been displaying the correct time, but as UTC, not as my time zone. At Noon, my time, the "date" command was saying 4 PM, UTC. Correct, but it means I have to subtract four hours (five when not on DST) in my head.

Anyway, I booted my Bedrock install, into the Buildroot init, and then I typed this:

Code:

export TZ="America/New_York"

After that, "time" indicated that it was in my time zone (it said "EDT" rather than "UTC" and it displayed the correct time, as viewed in my actual time zone.

I then told brl to fetch a second Void stratum, using -n to prevent a name conflict with the first Void, and it fetched fine!

ParadigmComplex · 06-15-2020, 12:00 PM

Very happy to hear we got it