Skip to content

Is it possible to gracefuly handle ssl connection errors? #5

@moredure

Description

@moredure
22520:M 25 Nov 2019 06:00:55.552 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
22520:M 25 Nov 2019 06:00:55.552 # Server initialized
22520:M 25 Nov 2019 06:00:55.552 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with KeyDB. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. KeyDB must be restarted after THP is disabled.
22520:M 25 Nov 2019 06:00:55.553 * Initializing SSL configuration
22520:M 25 Nov 2019 06:00:55.595 * Module 'modssl' loaded from /modssl/modssl.so
22520:M 25 Nov 2019 06:00:55.595 * Ready to accept connections
22520:M 25 Nov 2019 06:00:55.595   Thread 0 alive.
22520:M 25 Nov 2019 06:01:34.591 # SSL Negotiation unsuccessful due to Error: TLS alert received: Error encountered in /modssl/submodules/s2n/tls/s2n_alerts.c line 96 : TLS alert received
Segmentation fault

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions