-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/etcd] Intermittent Port 2380 Conflict Error on Pod Restart for Single-node ETCD Deployment #75295
Comments
I'm sorry @finday3 but I haven't been able to reproduce your issue. Freshly installed the latest version of the
In my case, the pod was able to start without issues, no bind errors in the logs:
Could you please provide more information about your deployment? Are you using any custom values? |
Thank you for your response. Here is the deployment information:
We have modified the image to use the openEuler base image, while keeping the contents consistent with Bitnami. The issue does not occur consistently, and out of several dozen tests, it appeared only three times. In this latest occurrence, the logs indicate a larger amount of data in etcd. Could there be any correlation with the data volume? Any insights or suggestions you could provide would be greatly appreciated. Thank you. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Name and Version
bitnami/etcd:3.5.14
What architecture are you using?
amd64
What steps will reproduce the bug?
What is the expected behavior?
ETCD should start normally after a POD restart without encountering port conflicts.
What do you see instead?
Intermittently, ETCD fails to start with the error:
listen tcp 0.0.0.0:2380: bind: address already in use
. This issue does not occur consistently.Additional information
Logs:
In cases where ETCD starts successfully, the logs contain the following snippet:
Here is a snippet of the failed logs:
The text was updated successfully, but these errors were encountered: