Skip to content
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

fix: return correct exit code on SIGTERM #1530

Merged
merged 5 commits into from
Nov 9, 2022
Merged

fix: return correct exit code on SIGTERM #1530

merged 5 commits into from
Nov 9, 2022

Conversation

enocom
Copy link
Member

@enocom enocom commented Nov 7, 2022

@enocom enocom requested a review from a team November 7, 2022 18:48
When the client closes cleanly and max-sigterm-delay is enabled, the
Proxy will exit with a 0 exit code on SIGTERM or SIGINT.

Otherwise, the Proxy will exit with 143 (SIGTERM) or 130 (SIGINT).
@enocom enocom changed the title fix: SIGTERM results in exit code 143 fix: exit cleanly on SIGTERM Nov 8, 2022
@kurtisvg kurtisvg changed the title fix: exit cleanly on SIGTERM fix: return correct exit code on SIGTERM Nov 9, 2022
@enocom enocom merged commit 7bb15aa into main Nov 9, 2022
@enocom enocom deleted the graceful-exit branch November 9, 2022 18:53
enocom added a commit to GoogleCloudPlatform/alloydb-auth-proxy that referenced this pull request Jan 15, 2023
enocom added a commit to GoogleCloudPlatform/alloydb-auth-proxy that referenced this pull request Jan 18, 2023
enocom added a commit to GoogleCloudPlatform/alloydb-auth-proxy that referenced this pull request Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Proxy exits with wrong code after SIGTERM
2 participants