<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">This is indicative of the remote server not running on the right ports normally or actively blocking you, given the "Connection Refused" errors. Verify your system stunnel is on actually can connect to the specified IP and port combo independently of stunnel to start with.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Sprint Samsung Galaxy Note10+.</div></div><div dir="auto"><br></div><div><br></div><div style="font-size:100%;color:#000000" dir="auto"><!-- originalMessage --><div>-------- Original message --------</div><div>From: digitek <digitek@charter.net> </div><div>Date: 5/23/20 19:18 (GMT-05:00) </div><div>To: stunnel-users@stunnel.org </div><div>Subject: [stunnel-users] /var/log/syslog is filling up with stunnel errors </div><div><br></div></div>Hi,<br>I've been running stunnel for years to shuttle my syslogs off to a syslog server. It's performed flawlessly up until a few weeks ago. Recently, rebooting my syslog server results in the clients filling up /var/log/syslog <br>with messages like below[1].<br><br>I'm not certain where the issue is. We've gone through some Ubuntu 16.04 > 18.04 upgrades on some hosts, as well as the syslog server. Is there a configuration item in stunnel to at least tell it to chill out a little and <br>not try reconnecting 1000 times a second? My config from a client is here[2]<br><br>Last time this happened (few weeks ago) I googled around and found the TIMEOUTconnect parameter to try and get stunnel to at least wait 10 seconds before attempting another connect, but guess it doesn't work that way.<br><br>Any thoughts? The stunnel client is on Ubuntu 18.04. I'd rather not compile out-of-band for the latest stunnel version unless I must. I"m assuming this is a config issue on my end. The version I'm stuck with right now is <br>stunnel 5.44 on x86_64-pc-linux-gnu platform<br><br>Thanks!<br><br>[1]<br>May 23 17:42:04 shuriken stunnel: LOG5[44922183]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket<br>May 23 17:42:04 shuriken stunnel: LOG5[44922184]: Service [syslog_tunnel] accepted connection from 127.0.0.1:55440<br>May 23 17:42:04 shuriken stunnel: LOG3[44922184]: s_connect: connect 192.168.1.96:51400: Connection refused (111)<br>May 23 17:42:04 shuriken stunnel: LOG3[44922184]: No more addresses to connect<br>May 23 17:42:04 shuriken stunnel: LOG5[44922184]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket<br>May 23 17:42:04 shuriken stunnel: LOG5[44922185]: Service [syslog_tunnel] accepted connection from 127.0.0.1:55444<br>May 23 17:42:04 shuriken stunnel: LOG3[44922185]: s_connect: connect 192.168.1.96:51400: Connection refused (111)<br>May 23 17:42:04 shuriken stunnel: LOG3[44922185]: No more addresses to connect<br><br><br>[2]<br>client = yes<br>cert = /etc/stunnel/shared/stunnel.pem<br>pid = /var/run/stunnel4/syslog_stunnel.pid<br><br>[syslog_tunnel]<br>accept = 127.0.0.1:5140<br>connect = 192.168.1.96:51400<br>TIMEOUTconnect = 10<br>_______________________________________________<br>stunnel-users mailing list<br>stunnel-users@stunnel.org<br>https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users<br><br></body></html>