Hi! You can force syslog-ng to close the source connections in case of a reload. https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edit... keep-alive() Type: yes or no Default: yes Description: Specifies whether connections to sources should be closed when syslog-ng is forced to reload its configuration (upon the receipt of a SIGHUP signal). Note that this applies to the server (source) side of the syslog-ng connections, client-side (destination) connections are always reopened after receiving a HUP signal unless the keep-alive option is enabled for the destination. Regards, Gabor ________________________________ From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> on behalf of johns spam <jspam@skopis.com> Sent: Thursday, January 16, 2020 13:01 To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: [syslog-ng] Go away CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe. Hello, I am wondering if there is any facility to tell a client to go away? i.e. https://http2.github.io/http2-spec/#GOAWAY<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhttp2.github.io%2Fhttp2-spec%2F%23GOAWAY&data=02%7C01%7Cgabor.nagy%40oneidentity.com%7C1031a12745b94d320c7b08d79a7bfb48%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637147729626483809&sdata=W%2F3xgLLzQWAYqS4pxUwJf9QriKDI16VqvAugr8zsRjI%3D&reserved=0> I know syslog-ng is not http2 but is there any side-channel mechanism a central server can use to make a client go away? The use case I am thinking is doing a rolling restart of a pool of syslog-ng central server. I think this could also be useful to cycle connections periodically, i.e. to rebalance connections to a central server. Thanks