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

Issue #41: There are a few more lingering issues with properly handli… #43

Merged
merged 1 commit into from
Aug 10, 2023

Conversation

Castaglia
Copy link
Owner

…ng AWSHealthcheck requests after a SIGHUP.

@Castaglia Castaglia added the bug label Aug 10, 2023
@Castaglia Castaglia self-assigned this Aug 10, 2023
…ng `AWSHealthcheck` requests after a SIGHUP.
@@ -528,6 +528,7 @@ int aws_health_listener_destroy(pool *p, struct aws_health *health) {

if (health->conn != NULL) {
pr_inet_close(health->pool, health->conn);
health->conn = NULL;
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I encountered an unexpected segfault, running under gdb, due to this pointer not be null as expected after we close the connection.

aws_health_addr != NULL) {
(void) aws_health_listening(aws_pool, aws_health_addr, aws_health_port,
aws_health_uri);
}
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By moving this code to a core.postparse event handler, we ensure that our AWSHealthcheck listener is created even after a SIGHUP.

@Castaglia Castaglia merged commit 19d1efb into master Aug 10, 2023
8 checks passed
@Castaglia Castaglia deleted the aws-sighup-issue41-redux branch August 10, 2023 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant