Information: Forum is in read-only mode
For details and other support options see

Reliable logging and stunnel

This is the place for you, if you got rsyslog up and running but wonder how to make it do what you want.

Moderator: alorbach

Google Ads

Reliable logging and stunnel

Postby xen.rkar » Thu Aug 03, 2017 8:03 am


I am setting up a system to log to a remote host. Since we did not want to have multiple TLS libraries we wanted only an openSsl solution. This prompted the use of rsyslog over stunnel to achieve our goal of TLS based communication.

However introduction of "stunnel" seems to regress on the "buffering/queuing for temporary loss of network connectivity to remote server" functionality which worked when the rsyslog client directly paired with rsyslog on the remote server.

Any suggestions on configuration or what could be done on rsyslog to ensure that the rsyslog client starts queuing messages once it gets a "stunnel: LOG3[79]: s_connect: connect <dest_ip>:61514: Connection refused (111)"

Posts: 2
Joined: Thu May 04, 2017 11:07 am

Urgent Question?

  • Pulling out your Hair?
  • Wasting Time and Money?
  • Deadline Approaching?

Google Ads

Return to Configuration

Who is online

Users browsing this forum: No registered users and 0 guests