[stunnel-users] Stunnel error

Mon Feb 23 15:29:25 CET 2009

Hi, I use the STunnel tool to connect to my Ms-SQL database. And so far
this works nice. However at one organization I have the following
problem:

<< connect_wait: s_poll_wait timeout>> And the connection fails.

Here is the log file and config file. Can you give me any hints how to
check where it goes wrong?

Thanks.

Reinier.

2009.02.23 14:45:12 LOG7[2156:3096]: RAND_status claims sufficient
entropy for the PRNG

2009.02.23 14:45:12 LOG7[2156:3096]: PRNG seeded successfully

2009.02.23 14:45:12 LOG7[2156:3096]: Certificate: stunnel.pem

2009.02.23 14:45:12 LOG7[2156:3096]: Certificate loaded

2009.02.23 14:45:12 LOG7[2156:3096]: Key file: stunnel.pem

2009.02.23 14:45:12 LOG7[2156:3096]: Private key loaded

2009.02.23 14:45:12 LOG7[2156:3096]: SSL context initialized for service
SQLServer

2009.02.23 14:45:12 LOG5[2156:3096]: stunnel 4.26 on x86-pc-mingw32-gnu
with OpenSSL 0.9.8i 15 Sep 2008

2009.02.23 14:45:12 LOG5[2156:3096]: Threading:WIN32 SSL:ENGINE
Sockets:SELECT,IPv6

2009.02.23 14:45:12 LOG5[2156:3852]: No limit detected for the number of
clients

2009.02.23 14:45:12 LOG7[2156:3852]: FD 184 in non-blocking mode

2009.02.23 14:45:12 LOG7[2156:3852]: SO_REUSEADDR option set on accept
socket

2009.02.23 14:45:12 LOG7[2156:3852]: SQLServer bound to 127.0.0.1:31433

2009.02.23 14:49:25 LOG7[2156:3852]: SQLServer accepted FD=208 from
127.0.0.1:2912

2009.02.23 14:49:25 LOG7[2156:3852]: Creating a new thread

2009.02.23 14:49:25 LOG7[2156:3852]: New thread created

2009.02.23 14:49:25 LOG7[2156:996]: SQLServer started

2009.02.23 14:49:25 LOG7[2156:996]: FD 208 in non-blocking mode

2009.02.23 14:49:25 LOG7[2156:996]: TCP_NODELAY option set on local
socket

2009.02.23 14:49:25 LOG5[2156:996]: SQLServer accepted connection from
127.0.0.1:2912

2009.02.23 14:49:25 LOG7[2156:996]: FD 232 in non-blocking mode

2009.02.23 14:49:25 LOG7[2156:996]: SQLServer connecting
10.17.98.33:8080

2009.02.23 14:49:25 LOG7[2156:996]: connect_wait: waiting 60 seconds

2009.02.23 14:50:25 LOG6[2156:996]: connect_wait: s_poll_wait timeout

2009.02.23 14:50:25 LOG5[2156:996]: Connection reset: 0 bytes sent to
SSL, 0 bytes sent to socket

2009.02.23 14:50:25 LOG7[2156:996]: SQLServer finished (0 left)

; Sample stunnel configuration file by Michal Trojnara 2002-2006

; Some options used here may not be adequate for your particular
configuration

; Certificate/key is needed in server mode and optional in client mode

; The default certificate is provided only for testing and should not

; be used in a production environment

cert = stunnel.pem

;key = stunnel.pem

; Some performance tunings

socket = l:TCP_NODELAY=1

socket = r:TCP_NODELAY=1

; Authentication stuff

;verify = 2

; Don't forget to c_rehash CApath

;CApath = certs

; It's often easier to use CAfile

;CAfile = certs.pem

; Don't forget to c_rehash CRLpath

;CRLpath = crls

; Alternatively you can use CRLfile

;CRLfile = crls.pem

; Some debugging stuff useful for troubleshooting

debug = 7

;output = stunnel.log

; Use it for client mode

client = yes

; Service-level configuration

[SQLServer]

accept = 127.0.0.1:31433

;connect = xx.xx.xxx.xxx:443

connect = 10.17.98.33:8080 

protocol = connect

protocolHost = xx.xx.xxx.xxx:443

;session cache timeout 

session = 60

;time to wait for expected data 

TIMEOUTbusy = 60

;time to wait for close_notify (set to 0 for buggy MSIE) 

;TIMEOUTclose = 30

;time to wait to connect a remote host 

TIMEOUTconnect = 60

;time to keep an idle connection 

;TIMEOUTidle = 60

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stunnel.org/pipermail/stunnel-users/attachments/20090223/20df3dbc/attachment.html>