Hello I use stunnel for rsyslog. And on the client equipment, I use also rsyslog queues for buffering in case of disconnection. But in case of reboot: * without stunnel, the buffered log messages are received on the rsyslog server * with stunnel, no buffered log messages are received on the rsyslog server On the client equipment, is it possible to refuse the local stunnel connections as long as the remote stunnel connection is down ? Regards Yann Rescourio
On Fri, Jun 25, 2021 at 07:07:43PM +0200, Yann RESCOURIO wrote:
Hello I use stunnel for rsyslog. And on the client equipment, I use also rsyslog queues for buffering in case of disconnection. But in case of reboot: * without stunnel, the buffered log messages are received on the rsyslog server * with stunnel, no buffered log messages are received on the rsyslog server On the client equipment, is it possible to refuse the local stunnel connections as long as the remote stunnel connection is down ?
So the short answer is "unfortunately no, this is impossible to do reliably in principle". For a longer explanation, see my message: https://www.stunnel.org/mailman3/hyperkitty/list/stunnel-users@stunnel.org/m... ...that was written in response to a similar question. Sorry to be the bearer of bad news :/ G'luck, Peter -- Peter Pentchev roam@ringlet.net roam@debian.org pp@storpool.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
On 25.06.21 19:07, Yann RESCOURIO wrote:
Hello I use stunnel for rsyslog.
... why? https://www.rsyslog.com/tag/gnutls/ https://documentation.solarwinds.com/en/success_center/loggly/content/admin/... I've been using rsyslog + GnuTLS + Buffering on a CentOS 6 Platform for ~8 years (until it was upgraded to CentOS 8) without a problem (other than that it didn't use RELP, which was not yet production ready in rsyslog at the time the platform was set up) ... Regards, -- Jochen Bern Systemingenieur Binect GmbH
participants (3)
-
Jochen Bern -
Peter Pentchev -
Yann RESCOURIO