Replies: 15 comments 3 replies
-
That is not startup probe failure. If it cannot connect to ZooKeeper, it is not running and restarts. So you have to investigate why it cannot conennct to ZooKeeper. |
Beta Was this translation helpful? Give feedback.
-
It seems the zookeeper worked fine, I can resolve the zookeeper DNS. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
But resolving DNS doesn't say anything about ZooKeeper working or not. The error is not complaining about resolving ZooKeeper DNS. |
Beta Was this translation helpful? Give feedback.
-
OH, it seems I can't ping the zookeeper IP... |
Beta Was this translation helpful? Give feedback.
-
Not sure the ping is expected to work in Kubernetes. But maybe you can start by:
|
Beta Was this translation helpful? Give feedback.
-
It seems cause by the network policy:
How can I delete those policy, the operator will recreate it when I delete it? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
But the network policy allows the connection. Plus the TLS sidecar seems to connect and then disconnect. So I think this is more some general networking issue rather than network policy. |
Beta Was this translation helpful? Give feedback.
-
So how can I solve this issue or how to trouble shouting it ? |
Beta Was this translation helpful? Give feedback.
-
I delete the pod, now the TLS sidecar seems work now:
But the topic operator still can't start:
Life is hard...
|
Beta Was this translation helpful? Give feedback.
-
Once again, you would need to share the full logs in order to get any help. Not just some snippets you find interesting. |
Beta Was this translation helpful? Give feedback.
-
Got the similar kind of Issue, Tried removing the network policies even but no luck. Any solutions for this Issue? |
Beta Was this translation helpful? Give feedback.
-
Hi, I am experiencing the same thing. Has anyone found a solution for this? My zookeeper logs:
My kafka broker logs:
|
Beta Was this translation helpful? Give feedback.
-
I'm also having this issue attempting to run Strimzi on Minikube, did you solve this @akikoogawa7 / @fanux |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
The my-cluster-entity-operator can't start, one container start failed:
Describe the pod:
The container log:
The zookeeper dns is fine:
To Reproduce
Just apply it.
Environment (please complete the following information):
Beta Was this translation helpful? Give feedback.
All reactions