-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[2.6 beta1 w/ dco] server side explicit-exit-notify not working #192
Comments
Do not randomly open new issues for the same problem. This is a duplicate of #189 and what we wrote there still holds - remove all the bits from your config that should not be there ( |
I want to start clean, this time disable reneg. |
IT'S NOT THERE. |
There is a boatload of lines in your config that should not be there - no matter if Let me be more blunt, dutch style: we are not interested in debugging problems that are caused by randomly copy-pasting ill-understood options together. We have better things to do. |
And you still refusing to provide complete log files. I asked for them several times. |
server client both 2.6 beta1 w/ dco
server config:
client config:
Describe the bug/To Reproduce
Establish a TLS config connection first
then send server a SIGUSR1/SIGHUP/SIGTERM
server will log(this one is SIGTERM):
but client receives nothing/log nothing, need a manual SIGUSR1 on client to reestablish connection.
Expected behavior
Client receives RESTART then generates an internal SIGUSR1. This makes client will reconnect after server reboot.
Version information (please complete the following information):
The text was updated successfully, but these errors were encountered: