Rancher pods Readiness probe failed after docker restart

Yesterday I needed to add a in insecure registry in the docker configuration of the machine where I had a master node of rke running. After the restart everything seemed well except that the rancher pods never started again.

Since that moment and until now, they show this message:

Readiness probe failed: Get http://10.42.0.9:80/healthz: dial tcp 10.42.0.9:80: connect: connection refused

I tryed installing rancher in another workspace but it also faild. Desesperated I decided to get a clean instalation of the master node with rke so I followed the steps described here: https://rancher.com/docs/rancher/v2.5/en/cluster-admin/cleaning-cluster-nodes/ to delete everything in the machine.

The problem is that in the new instalation I have the same problem :frowning:

As far as I understand the pods restart because they are unhealthy but I don’t know why that happens.

What could I do to find the real problem?
Thanks in advance

1 Like

Well if anyone has the same problem we realized it was deep security agent the one that was blocking the resuqests.

Was this a security agent installed by default on the OS? How would I check to see if I am running it?

The deep secutiry agent was not installed by default in my server, actuallt it was installed by the security team.