<html><head></head><body><div class="ydpe56b4a4byahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div>Try: <br></div><div dir="ltr" data-setdir="false">* Verifying the openssl <span>version(s) </span><br></div><div dir="ltr" data-setdir="false"> <span>* </span>Verifying the <span><span> <span>192.168.1.96:51400</span></span></span> port (nmap, netstat, etc.)<br></div><div dir="ltr" data-setdir="false"> <span>* V</span>erifying connection (<span>openssl s_client -connect <span>192.168.1.96:51400</span>)</span></div><div dir="ltr" data-setdir="false"><span> <span>* </span>Verifying the ciphersuite</span></div><div dir="ltr" data-setdir="false"> <span>* Verifying the </span>certificate</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">>>Is there a configuration item in stunnel to at least tell it to chill out a little and not try reconnecting 1000 times a second? <div>Not sure. TIMEOUTclose?<br></div></div><div dir="ltr" data-setdir="false"><div><br></div></div></div><div id="yahoo_quoted_1340163088" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Sunday, May 24, 2020, 6:00:07 a.m. EDT, stunnel-users-request@stunnel.org <stunnel-users-request@stunnel.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Send stunnel-users mailing list submissions to<br></div><div dir="ltr"> <a ymailto="mailto:stunnel-users@stunnel.org" href="mailto:stunnel-users@stunnel.org">stunnel-users@stunnel.org</a><br></div><div dir="ltr"><br></div><div dir="ltr">To subscribe or unsubscribe via the World Wide Web, visit<br></div><div dir="ltr"> <a href="https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users" target="_blank">https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users</a><br></div><div dir="ltr">or, via email, send a message with subject or body 'help' to<br></div><div dir="ltr"> <a ymailto="mailto:stunnel-users-request@stunnel.org" href="mailto:stunnel-users-request@stunnel.org">stunnel-users-request@stunnel.org</a><br></div><div dir="ltr"><br></div><div dir="ltr">You can reach the person managing the list at<br></div><div dir="ltr"> <a ymailto="mailto:stunnel-users-owner@stunnel.org" href="mailto:stunnel-users-owner@stunnel.org">stunnel-users-owner@stunnel.org</a><br></div><div dir="ltr"><br></div><div dir="ltr">When replying, please edit your Subject line so it is more specific<br></div><div dir="ltr">than "Re: Contents of stunnel-users digest..."<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">Today's Topics:<br></div><div dir="ltr"><br></div><div dir="ltr"> 1. /var/log/syslog is filling up with stunnel errors (digitek)<br></div><div dir="ltr"> 2. Re: /var/log/syslog is filling up with stunnel errors<br></div><div dir="ltr"> (Thomas Ward)<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">----------------------------------------------------------------------<br></div><div dir="ltr"><br></div><div dir="ltr">Message: 1<br></div><div dir="ltr">Date: Sat, 23 May 2020 18:17:49 -0500<br></div><div dir="ltr">From: digitek <<a ymailto="mailto:digitek@charter.net" href="mailto:digitek@charter.net">digitek@charter.net</a>><br></div><div dir="ltr">To: <a ymailto="mailto:stunnel-users@stunnel.org" href="mailto:stunnel-users@stunnel.org">stunnel-users@stunnel.org</a><br></div><div dir="ltr">Subject: [stunnel-users] /var/log/syslog is filling up with stunnel<br></div><div dir="ltr"> errors<br></div><div dir="ltr">Message-ID: <<a ymailto="mailto:434e3153-d94c-bb71-fc51-1716db588290@charter.net" href="mailto:434e3153-d94c-bb71-fc51-1716db588290@charter.net">434e3153-d94c-bb71-fc51-1716db588290@charter.net</a>><br></div><div dir="ltr">Content-Type: text/plain; charset=windows-1252; format=flowed<br></div><div dir="ltr"><br></div><div dir="ltr">Hi,<br></div><div dir="ltr">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></div><div dir="ltr">with messages like below[1].<br></div><div dir="ltr"><br></div><div dir="ltr">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></div><div dir="ltr">not try reconnecting 1000 times a second? My config from a client is here[2]<br></div><div dir="ltr"><br></div><div dir="ltr">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></div><div dir="ltr"><br></div><div dir="ltr">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></div><div dir="ltr">stunnel 5.44 on x86_64-pc-linux-gnu platform<br></div><div dir="ltr"><br></div><div dir="ltr">Thanks!<br></div><div dir="ltr"><br></div><div dir="ltr">[1]<br></div><div dir="ltr">May 23 17:42:04 shuriken stunnel: LOG5[44922183]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket<br></div><div dir="ltr">May 23 17:42:04 shuriken stunnel: LOG5[44922184]: Service [syslog_tunnel] accepted connection from 127.0.0.1:55440<br></div><div dir="ltr">May 23 17:42:04 shuriken stunnel: LOG3[44922184]: s_connect: connect 192.168.1.96:51400: Connection refused (111)<br></div><div dir="ltr">May 23 17:42:04 shuriken stunnel: LOG3[44922184]: No more addresses to connect<br></div><div dir="ltr">May 23 17:42:04 shuriken stunnel: LOG5[44922184]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket<br></div><div dir="ltr">May 23 17:42:04 shuriken stunnel: LOG5[44922185]: Service [syslog_tunnel] accepted connection from 127.0.0.1:55444<br></div><div dir="ltr">May 23 17:42:04 shuriken stunnel: LOG3[44922185]: s_connect: connect 192.168.1.96:51400: Connection refused (111)<br></div><div dir="ltr">May 23 17:42:04 shuriken stunnel: LOG3[44922185]: No more addresses to connect<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">[2]<br></div><div dir="ltr">client = yes<br></div><div dir="ltr">cert = /etc/stunnel/shared/stunnel.pem<br></div><div dir="ltr">pid = /var/run/stunnel4/syslog_stunnel.pid<br></div><div dir="ltr"><br></div><div dir="ltr">[syslog_tunnel]<br></div><div dir="ltr">accept = 127.0.0.1:5140<br></div><div dir="ltr">connect = 192.168.1.96:51400<br></div><div dir="ltr">TIMEOUTconnect = 10<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">------------------------------<br></div><div dir="ltr"><br></div><div dir="ltr">Message: 2<br></div><div dir="ltr">Date: Sat, 23 May 2020 20:09:48 -0400<br></div><div dir="ltr">From: Thomas Ward <<a ymailto="mailto:teward@thomas-ward.net" href="mailto:teward@thomas-ward.net">teward@thomas-ward.net</a>><br></div><div dir="ltr">To: digitek <<a ymailto="mailto:digitek@charter.net" href="mailto:digitek@charter.net">digitek@charter.net</a>>, <a ymailto="mailto:stunnel-users@stunnel.org" href="mailto:stunnel-users@stunnel.org">stunnel-users@stunnel.org</a><br></div><div dir="ltr">Subject: Re: [stunnel-users] /var/log/syslog is filling up with<br></div><div dir="ltr"> stunnel errors<br></div><div dir="ltr">Message-ID: <<a ymailto="mailto:49V0wH16GWz2QGD@mail.syn-ack.link" href="mailto:49V0wH16GWz2QGD@mail.syn-ack.link">49V0wH16GWz2QGD@mail.syn-ack.link</a>><br></div><div dir="ltr">Content-Type: text/plain; charset="utf-8"<br></div><div dir="ltr"><br></div><div dir="ltr">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.Sent from my Sprint Samsung Galaxy Note10+.<br></div><div dir="ltr">-------- Original message --------From: digitek <<a ymailto="mailto:digitek@charter.net" href="mailto:digitek@charter.net">digitek@charter.net</a>> Date: 5/23/20 19:18 (GMT-05:00) To: <a ymailto="mailto:stunnel-users@stunnel.org" href="mailto:stunnel-users@stunnel.org">stunnel-users@stunnel.org</a> Subject: [stunnel-users] /var/log/syslog is filling up with stunnel errors Hi,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 with messages like below[1].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 not try reconnecting 1000 times a second?? My config from a client is here[2]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.Any thoughts? The stu<br></div><div dir="ltr"> nnel 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 stunnel 5.44 on x86_64-pc-linux-gnu platformThanks![1]May 23 17:42:04 shuriken stunnel: LOG5[44922183]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socketMay 23 17:42:04 shuriken stunnel: LOG5[44922184]: Service [syslog_tunnel] accepted connection from 127.0.0.1:55440May 23 17:42:04 shuriken stunnel: LOG3[44922184]: s_connect: connect 192.168.1.96:51400: Connection refused (111)May 23 17:42:04 shuriken stunnel: LOG3[44922184]: No more addresses to connectMay 23 17:42:04 shuriken stunnel: LOG5[44922184]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socketMay 23 17:42:04 shuriken stunnel: LOG5[44922185]: Service [syslog_tunnel] accepted connection from 127.0.0.1:55444May 23 17:42:04 shuriken stunnel: LOG3[44922185]: s_connect: connect 192.168.1.96:51400: Conn<br></div><div dir="ltr"> ection refused (111)May 23 17:42:04 shuriken stunnel: LOG3[44922185]: No more addresses to connect[2]client?? = yescert???? = /etc/stunnel/shared/stunnel.pempid????? = /var/run/stunnel4/syslog_stunnel.pid[syslog_tunnel]accept?? = 127.0.0.1:5140connect? = 192.168.1.96:51400TIMEOUTconnect = 10_______________________________________________stunnel-users mailing <a ymailto="mailto:liststunnel-users@stunnel.orghttps" href="mailto:liststunnel-users@stunnel.orghttps">liststunnel-users@stunnel.orghttps</a>://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users<br></div><div dir="ltr">-------------- next part --------------<br></div><div dir="ltr">An HTML attachment was scrubbed...<br></div><div dir="ltr">URL: <<a href="http://www.stunnel.org/pipermail/stunnel-users/attachments/20200523/f6ef2500/attachment-0001.htm" target="_blank">http://www.stunnel.org/pipermail/stunnel-users/attachments/20200523/f6ef2500/attachment-0001.htm</a>><br></div><div dir="ltr"><br></div><div dir="ltr">------------------------------<br></div><div dir="ltr"><br></div><div dir="ltr">Subject: Digest Footer<br></div><div dir="ltr"><br></div><div dir="ltr">_______________________________________________<br></div><div dir="ltr">stunnel-users mailing list<br></div><div dir="ltr"><a ymailto="mailto:stunnel-users@stunnel.org" href="mailto:stunnel-users@stunnel.org">stunnel-users@stunnel.org</a><br></div><div dir="ltr"><a href="https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users" target="_blank">https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users</a><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">------------------------------<br></div><div dir="ltr"><br></div><div dir="ltr">End of stunnel-users Digest, Vol 190, Issue 13<br></div><div dir="ltr">**********************************************<br></div></div>
</div>
</div></body></html>