David B.

Thanks for following up on that one. So the cluster has become `Unreachable` again, not sure exactly when that happened: ``` crc status --log-level debug DEBU CRC version: 2.20.0+f3a947 DEBU...

> ... when it is in Running state it will also show correct disk usage. EDIT: didn't mean to close this issue. And yes indeed, it does show the current...

OK so the daemon seems to has crashed: ``` crc status CRC VM: Running OpenShift: Unreachable (v4.13.0) Disk Usage: 0B of 0B (Inside the CRC VM) Cache Usage: 26.29GB Cache...

> Either the service was 'stopped' (like socket activation has a timeout) or a crash does not cause a socket activation to record this as a restart So this is...

> @dabcoder what version of systemd ubuntu have? Also can you provide journalctl logs for service `journalctl --user -u crc-daemon` ? ``` systemd --version systemd 249 (249.11-0ubuntu3.7) ``` `journalctl` logs...

> You also run podman desktop with the extension, right? We're using a recent version of podman for Ubuntu which we installed following these instructions: https://podman.io/docs/installation#ubuntu (so not podman desktop)....

> it shows the errors and a clean 'stopped' about 8 mins later. This might be user interaction? ``` Aug 30 16:12:56 ns3220936 systemd[327429]: Stopping CRC daemon... Aug 30 16:12:56...

> Is there any ubuntu security which is causing the daemon failure or endpoint connection issue? Tomorrow I will try to setup a ubuntu system and see if able to...

@open-telemetry/collector-contrib-maintainer if anyone has a chance to take another look at this PR before it gets marked as stale again, that'd be great, thanks.

Thanks @dmitryax. They should be fixed now, I ran the tests locally and they're passing.