Hello, I would like to address three issues: 1) For the last two days the package build site, https://pkg-status.freebsd.org), does not show any output. Only the column headings are displayed. 2) For many months it is not possible to view https://beefy6.nyi.freebsd.org using ipv4 as access has been restricted to ipv6. I then reconfigured my system to use tunnelling 4to6 which worked perfectly until I switched my ISP to verizon FIOS. Consequently I am not able to access the site either through ipv4 or ipv6. About a year ago it was mentioned that ipv4 access to this site would be set up but apparently it is still pending. What is the current status? 3) Periodically, after all the packages have been built, the rsync process becomes constipated and the mirrors are not updated for many days. Where is the appropriate place to report this? In any event I am very pleased and amazed how the whole package infrastructure just works, day after day. With thanks ... Marek
1) I see output on https://pkg-status.freebsd.org as of this morning (UTC+8). 2) This is still on my list. I forget that there are still people who only have access to legacy IP. I'll try to set up a proxy for those in the coming days. Assigning this bug to me so it can whine at me. 3) There's no need to report it. We (clusteradm@) notice. For "big" package runs (e.g. when a dependency like gettext is bumped) it can take several days before the mirrors catch up. There isn't much we can do about this.
(In reply to mfv from comment #0) >2) For many months it is not possible to view https://beefy6.nyi.freebsd.org >using ipv4 as access has been restricted to ipv6. I then reconfigured my >system to use tunnelling 4to6 which worked perfectly until I switched my ISP >to verizon FIOS. Consequently I am not able to access the site either through >ipv4 or ipv6. > >About a year ago it was mentioned that ipv4 access to this site would be set >up but apparently it is still pending. What is the current status? I took a closer look at this this morning. I was thinking of simply adding A records to each of the package builders and pointing them at a dual-stack proxy. Before I do this, I need to make sure that nothing inside the cluster tries to connect to the package builders directly over IPv4. There are a couple of places in the cluster to look at. Off the top of my head: distcache, pkg-status and master-poller.sh. If I can force all of these to connect only over IPv6, I can add A records.
(Incidentally: the package builder status pages don't (and won't) have HTTPS. It's http://beefy6.nyi.freebsd.org etc.)
Hello Philip, After you reported that you were able to accees the site https://pkg-status.freebsd.org/, I did some debugging and discovered that I could also access the same site. It was previously blocked due to Privacy Badger of the EFF. As soon as I enabled the tracker (cdnjs.cloudflare.com) all was well. If this tracker is blocked only the column headings are visible. The the rows of data do not appear. As to the issue of a stalled rsync process, it occurs infrequently, only about 18 to 24 months. The last time was Dec 2020 (bug id 249359). The symptom is the completion of multiple builds without the mirrors being updated. I have taken note of the diffence between http and https. Thanks for your prompt response. Marek
^Triage: apparently only issue #3 still applies, and it is not actively "In Progress".
I think all these issues are actually "fixed", but "overcome by events" feels more correct for a >1 year old bug report.
(In reply to Philip Paeps from comment #6) IPv6 still required, is this expected? % lynx 'http://beefy12.nyi.freebsd.org/build.html?mastername=140amd64-default&build=517a7ce81e3e' Looking up beefy12.nyi.freebsd.org Making HTTP connection to beefy12.nyi.freebsd.org Alert!: Unable to connect to remote host. lynx: Can't access startfile http://beefy12.nyi.freebsd.org/build.html?mastername=140amd64-default&build=517a7ce81e3e % sudo ifconfig gif0 up grahamperrin's password: % lynx 'http://beefy12.nyi.freebsd.org/build.html?mastername=140amd64-default&build=517a7ce81e3e' % (I don't expect the site to be usable with lynx, it's solely to demonstrate that I can't connect without a tunnel for IPv6 purposes.)
If you are only directly connected to the 20th century internet, you still need the dual-stack proxy: http://beefy12.nyi.freebsd.org/build.html?mastername=140amd64-default&build=517a7ce81e3e -> https://pkg-status.freebsd.org/beefy12/build.html?mastername=140amd64-default&build=517a7ce81e3e The package builders are only directly connected to the 21st century internet.