-
Notifications
You must be signed in to change notification settings - Fork 45
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
Need to close discovery socket on shutdown #748
Comments
gbregman
added a commit
to gbregman/ceph-nvmeof
that referenced
this issue
Jul 8, 2024
Fixes ceph#748 Signed-off-by: Gil Bregman <[email protected]>
gbregman
added a commit
to gbregman/ceph-nvmeof
that referenced
this issue
Jul 8, 2024
Fixes ceph#748 Signed-off-by: Gil Bregman <[email protected]>
gbregman
added a commit
to gbregman/ceph-nvmeof
that referenced
this issue
Jul 8, 2024
Fixes ceph#748 Signed-off-by: Gil Bregman <[email protected]>
gbregman
added a commit
to gbregman/ceph-nvmeof
that referenced
this issue
Jul 9, 2024
Fixes ceph#748 Signed-off-by: Gil Bregman <[email protected]>
gbregman
added a commit
to gbregman/ceph-nvmeof
that referenced
this issue
Jul 9, 2024
Fixes ceph#748 Signed-off-by: Gil Bregman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We sometimes get an issue when we can't start the discovery service as the address is already used. This might happen if we don't explicitly close the socket before exiting.
The text was updated successfully, but these errors were encountered: