[receiver/chrony] Issue with dead link on chrony.tuxfamily.org

[atoulme]

Component(s)

receiver/chrony

What happened?

Build reports a dead link:

FILE: receiver/chronyreceiver/README.md
  [✓] https://github.com/open-telemetry/opentelemetry-collector#alpha → Status: 200
  [✓] https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib → Status: 200
  [✖] https://chrony.tuxfamily.org/ → Status: 0 Error: connect ECONNREFUSED 212.85.158.4:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '212.85.158.4',
  port: 443
}

  ERROR: 1 dead links found!

https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5502194916/jobs/10026300369?pr=24045

Collector version

latest

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/chrony: @MovieStoreGuy @jamesmoessis

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[atoulme]

Seeing this notice on tuxfamily.org:

[Main services down](https://www.tuxfamily.org/en/news/2023070900)
Posted on Sunday 9 July 2023, at 15:51 UTC

Today, around 11:37 UTC, we lost contact with some of our most important hosts, presumably following yet another power hiccup. Consequently, our main services (web areas, databases, SCM repositories, access to mailboxes, etc.) are down. Secondary services (MX2, NS2, etc.) are still up and running, along with download repositories. As this is being written, we cannot predict when exactly our services will recover and can only apologize for the significant downtime incurred. Please bear with us.