This message was deleted.

could you show the log of the pod? the app didn’t respond to the request for the liveness probe. though it could be a networking issue, i’d suggest looking at the pod’s log first.

ts=2023-10-12T092627.459Z caller=stdlib.go:105 level=error caller="error encoding and sending metric family: write tcp 10.0.0.21:9796" msg="->10.0.0.2325006 write: broken pipe" ts=2023-10-12T092627.459Z caller=stdlib.go:105 level=error caller="error encoding and sending metric family: write tcp 10.0.0.21:9796" msg="->10.0.0.2325006 write: broken pipe" ts=2023-10-12T092627.459Z caller=stdlib.go:105 level=error caller="error encoding and sending metric family: write tcp 10.0.0.21:9796" msg="->10.0.0.2325006 write: broken pipe" ts=2023-10-12T092627.459Z caller=stdlib.go:105 level=error caller="error encoding and sending metric family: write tcp 10.0.0.21:9796" msg="->10.0.0.2325006 write: broken pipe"

Could you also generate a support bundle file for us if you still have the environment? And I’ll give it a try to see if I can reproduce this. Thanks!

supportbundle_b503d5ce-3648-4f0e-ba99-3a8daaa10f10_2023-10-12T09-58-13Z.zip

What's the CPU cores and memory size in your cluster ? Make sure it meets https://docs.harvesterhci.io/v1.2/install/requirements

AMD Ryzen™ 7 7735HS 8 *Cores 16 Threads 64G memory * 3*

It looks very likely to be realted to https://github.com/prometheus/node_exporter/issues/2500.