- stunnel-users - stunnel.org

PEM routines:PEM_read_bio Problem
by Metal Gear 28 Feb '05

28 Feb '05

Hi all, i was configuring my syslog-ng server with stunnel and it worked fine for somedays but after that i upgraded to new SSL libraries (OpenSSL 0.9.7e) from (OpenSSL 0x0090701f) then i m getting this "stunnel[2480]: SSL_CTX_use_RSAPrivateKey_file: 906D06C: error:0906D06C:PEM routines:PEM_read_bio" error (i have given the link of stunnel binary in rc.local, to start at boot time, at i get this error in logs) i m using stunnel (stunnel 4.07). Can anyone has any idea about it. Thanks (sorry for sending same message twice)

1 0

PEM routines:PEM_read_bio Problem
by Metal Gear 28 Feb '05

28 Feb '05

Hi all, i was configuring my syslog-ng server with stunnel and it worked fine for somedays but after that i upgraded to new SSL libraries (OpenSSL 0.9.7e) from (OpenSSL 0x0090701f) then i m getting this "stunnel[2480]: SSL_CTX_use_RSAPrivateKey_file: 906D06C: error:0906D06C:PEM routines:PEM_read_bio" error (i have given the link of stunnel binary in rc.local, to start at boot time, at i get this error in logs) i m using stunnel (stunnel 4.07). Can anyone has any idea about it. Thanks

1 0

Stunnel 4.08 released
by Michal Trojnara 27 Feb '05

27 Feb '05

Here is the ChangeLog entry for the new stunnel 4.08: Version 4.08, 2005.02.27, urgency: LOW: * New features - New -quiet option was added to install NT service without a message box. * Bugfixes - Using $(DESTDIR) in tools/Makefile.am. - Define NI_NUMERICHOST and NI_NUMERICSERV when needed. - Length of configuration file line increased from 256B to 16KB. - Stunnel sends close_notify when a close_notify is received from SSL peer and all remaining data is sent to SSL peer. - Some fixes for bugs detected by the watchdog. * Release notes - There were many changes in the transfer() function (the main loop). This version should be thoroughly tested before using it in the mission-critical environment. Home page & downloads: http://stunnel.mirt.net/ Best regards, Mike

1 0

Help Needed
by Alexander Lazic 25 Feb '05

25 Feb '05

Hi, i have try to add the X-Forwarded-For Header, based on http://www.stunnel.org/patches/desc/xforwardedfor_jrd.html, into stunnel 4.07, but i don't come to a solution :-( I have try to add i into 'client.c => transfer()'. Please can anybody review the attached Patch and point me to the right way ;-) I'am not shure that i add the 'insert' into the right place :-( Thanx for help ;-)) al ;-)

1 1

verify =3 error with certificate client
by Humberto Morell 25 Feb '05

25 Feb '05

Hello List I have stunnel 4.7 In the messages of the list I have not seen solution to my problem. This is VERIFY ERROR ONLY MY: no cert stunnel.log in Server ################## 2005.02.25 07:55:07 LOG5[2501:1076546480]: VERIFY OK: depth=1, /C=CU/ST=Ciudad Habana/L=Centro Habana/O=Segurmatica/OU=Agencia de Certificacion/CN=Segurmatica/emailAddress=ca(a)segurmatica.cu 2005.02.25 07:55:07 LOG4[2501:1076546480]: VERIFY ERROR ONLY MY: no cert for /C=CU/ST=Ciudad Habana/L=Centro Habana/O=Ministerio Informatica y Comunicaciones/OU=Segurmatica/CN=Humberto Morell/emailAddress=morell(a)seg.inf.cu 2005.02.25 07:55:07 LOG7[2501:1076546480]: SSL alert (write): fatal: certificate unknown ############# stunnel.conf in Server ############## #chroot = /var/lib/stunnel/ verify = 3 CApath = /etc/stunnel/certdb # or simply use CAfile instead: #CAfile = /etc/stunnel/certs.pem CAfile = /etc/stunnel/acsegurmatica.crt #cert = /etc/stunnel/stunnel.pem cert = /etc/stunnel/certstunnel.pem ################# File in /etc/stunnel ############### certdb morell.pem stunnel.prueba.pem certstunnel.pem stunnel.conf acsegurmatica.crt morell.crt stunnel.log certclient morell.key stunnel.pem ############### Link in /etc/stunnel/certdb ############### drwxr-xr-x 2 root root 176 Feb 25 11:06 . drwx------ 4 root root 472 Feb 25 10:52 .. lrwxrwxrwx 1 root root 24 Feb 25 11:00 2307a3fe.0 -> /etc/stunnel/stunnel.pem lrwxrwxrwx 1 root root 30 Feb 25 11:01 3f5b7ca8.0 -> /etc/stunnel/acsegurmatica.crt lrwxrwxrwx 1 root root 23 Feb 25 11:03 3fb3183e.0 -> /etc/stunnel/morell.pem lrwxrwxrwx 1 root root 28 Feb 25 11:06 d14abd18.0 -> /etc/stunnel/certstunnel.pem ################# client in Windows stunnel.conf ############## client = yes cert = d:\morell.pem debug = 7 output = d:\stunnel.log [lsd] accept = 9595 connect = 10.10.1.83:9500 [ssh] accept = 2222 connect = 10.10.1.83:9522 ##################### Note: I don't use chroot I have try, but idem error with. File morell.pem only client certificate and other time file morell.pem Key private crl Certificate With verify = 2 all is ok Please help Best regards Morell

1 0

openssl - generating stunnel.pem - stunnel.cnf
by k-i-r＠web.de 24 Feb '05

24 Feb '05

Using Stunnel under Windows I want to create a certificate (stunnel.pem) with Openssl. According to FAQ the syntax for creating a certificate with Openssl is openssl req -new -x509 -days 365 -nodes -config stunnel.cnf -out stunnel.pem -keyout stunnel.pem I use openssl for windows (as part of apache-windows-http-server) . Where do I get the file stunnel.cnf ? Or is this file not necessary for creating a certificate ? Thanks for help, k.

3 2

Stunnel and configuration
by Bohdan Linda 22 Feb '05

22 Feb '05

Hi all, I have configured stunnel to do the client authetication, but I have some question. I have used following config: cert = /etc/certificates/server.pem - file with signed server cert and key (passwordless) chroot = /var/run/stunnel/ CAfile = /etc/certificates/certs -file where first item is my CA certificate followed by list of all client certificates sgined by my CA. setuid = nobody setgid = nogroup pid = /stunnel.pid verify = 3 This setup is working, but this seems to me very "unlogical". If I create for me "more logic" setup: cert = /etc/certificates/server.pem chroot = /var/run/stunnel/ CAfile = /etc/certificates/CA/cacert.pem - only certificate of my CA CRLfile = /etc/certificates/crls - only certificates signed by my CA I get the following error: 2005.02.22 15:15:10 LOG5[22418:81926]: VERIFY OK: depth=1, /C= ..... 2005.02.22 15:15:10 LOG4[22418:81926]: VERIFY ERROR ONLY MY: no cert for /C= The question is ... why? Why CAfile has to contain all client certificates, when clients certs are not CA? Why I cannot have separate file for CA and separate file for certificates that I want accept? If I do the similar setup in mod_ssl, the configuration works as expected. Anyway, I'am newbie to deploy stunnel, thus I would like to ask you for giving me you opinion of this configuration, caveats and possible enhancements. Thanks for any comments, Bohdan Linda

3 4

SSL_read (ERROR_SYSCALL)
by Passreality 16 Feb '05

16 Feb '05

Hi Im trying to connect using mysql, there are no fw between the 2 boxes. I tested with stunnel 3.x and 4.x but when i use the 4.0.23 mysldb it just wount work. When i use the older db it works. Any ideas on how to solve this error ? /Christian Stunnel 4.07 Kernel 2.4.18 gcc version 3.3.5 (Debian 1:3.3.5-8) mysql Ver 12.22 Distrib 4.0.23 Dist Debian Testing Im using stunnel.pem (default one) Client Log 2005.02.16 15:04:19 LOG7[2147:16384]: mysql accepted FD=10 from 217.212.4.33:40797 2005.02.16 15:04:19 LOG7[2147:16384]: FD 10 in non-blocking mode 2005.02.16 15:04:19 LOG7[2322:49154]: mysql started 2005.02.16 15:04:19 LOG7[2322:49154]: TCP_NODELAY option set on local socket 2005.02.16 15:04:19 LOG5[2322:49154]: mysql connected from 217.212.4.33:40797 2005.02.16 15:04:19 LOG7[2322:49154]: FD 13 in non-blocking mode 2005.02.16 15:04:19 LOG7[2322:49154]: mysql connecting 217.212.4.198:3307 2005.02.16 15:04:19 LOG7[2322:49154]: connect_wait: waiting 10 seconds 2005.02.16 15:04:19 LOG7[2322:49154]: connect_wait: connected 2005.02.16 15:04:19 LOG7[2322:49154]: Remote FD=13 initialized 2005.02.16 15:04:19 LOG7[2322:49154]: TCP_NODELAY option set on remote socket 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): before/connect initialization 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 write client hello A 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 read server hello A 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 read server certificate A 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 read server done A 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 write client key exchange A 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 write change cipher spec A 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 write finished A 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 flush data 2005.02.16 15:04:19 LOG7[2322:49154]: SSL state (connect): SSLv3 read finished A 2005.02.16 15:04:19 LOG7[2322:49154]: 2 items in the session cache 2005.02.16 15:04:19 LOG7[2322:49154]: 3 client connects (SSL_connect()) 2005.02.16 15:04:19 LOG7[2322:49154]: 3 client connects that finished 2005.02.16 15:04:19 LOG7[2322:49154]: 0 client renegotiatations requested 2005.02.16 15:04:19 LOG7[2322:49154]: 0 server connects (SSL_accept()) 2005.02.16 15:04:19 LOG7[2322:49154]: 0 server connects that finished 2005.02.16 15:04:19 LOG7[2322:49154]: 0 server renegotiatiations requested 2005.02.16 15:04:19 LOG7[2322:49154]: 1 session cache hits 2005.02.16 15:04:19 LOG7[2322:49154]: 0 session cache misses 2005.02.16 15:04:19 LOG7[2322:49154]: 0 session cache timeouts 2005.02.16 15:04:19 LOG6[2322:49154]: SSL connected: new session negotiated 2005.02.16 15:04:19 LOG6[2322:49154]: Negotiated ciphers: DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 2005.02.16 15:04:19 LOG3[2322:49154]: SSL_read (ERROR_SYSCALL): Connection reset by peer (104) 2005.02.16 15:04:19 LOG5[2322:49154]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2005.02.16 15:04:19 LOG7[2322:49154]: mysql finished (0 left) Server Log 2005.02.16 15:04:51 LOG7[29786:16384]: mysql accepted FD=10 from 217.212.4.33:40798 2005.02.16 15:04:51 LOG7[29786:16384]: FD 10 in non-blocking mode 2005.02.16 15:04:51 LOG7[29814:49154]: mysql started 2005.02.16 15:04:51 LOG7[29814:49154]: TCP_NODELAY option set on local socket 2005.02.16 15:04:51 LOG5[29814:49154]: mysql connected from 217.212.4.33:40798 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): before/accept initialization 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 read client hello A 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 write server hello A 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 write certificate A 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 write server done A 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 flush data 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 read client key exchange A 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 read finished A 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 write change cipher spec A 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 write finished A 2005.02.16 15:04:51 LOG7[29814:49154]: SSL state (accept): SSLv3 flush data 2005.02.16 15:04:51 LOG7[29814:49154]: 1 items in the session cache 2005.02.16 15:04:51 LOG7[29814:49154]: 0 client connects (SSL_connect()) 2005.02.16 15:04:51 LOG7[29814:49154]: 0 client connects that finished 2005.02.16 15:04:51 LOG7[29814:49154]: 0 client renegotiatations requested 2005.02.16 15:04:51 LOG7[29814:49154]: 3 server connects (SSL_accept()) 2005.02.16 15:04:51 LOG7[29814:49154]: 3 server connects that finished 2005.02.16 15:04:51 LOG7[29814:49154]: 0 server renegotiatiations requested 2005.02.16 15:04:51 LOG7[29814:49154]: 1 session cache hits 2005.02.16 15:04:51 LOG7[29814:49154]: 0 session cache misses 2005.02.16 15:04:51 LOG7[29814:49154]: 1 session cache timeouts 2005.02.16 15:04:51 LOG6[29814:49154]: SSL accepted: new session negotiated 2005.02.16 15:04:51 LOG6[29814:49154]: Negotiated ciphers: DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 2005.02.16 15:04:51 LOG7[29814:49154]: FD 13 in non-blocking mode 2005.02.16 15:04:51 LOG7[29814:49154]: mysql connecting 127.0.0.1:3306 2005.02.16 15:04:51 LOG7[29814:49154]: connect_wait: waiting 10 seconds 2005.02.16 15:04:51 LOG3[29814:49154]: connect_wait: getsockopt: Connection refused (111) 2005.02.16 15:04:51 LOG3[29814:49154]: Failed to initialize remote connection 2005.02.16 15:04:51 LOG7[29814:49154]: mysql finished (0 left) __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com

1 0

Stunnel on Open-WRT..
by Andrew Frazer 16 Feb '05

16 Feb '05

I have got Stunnel running under Open-wrt, on a Linksys WRT54GS. However I don't seem to be able to get it to run the transparent mode.. (a) is it possible? (b) If the answer is no, would be possible to modifty either open-wrt or stunnel to make it work? Regards A.

1 0

Re: [stunnel-users] read sock return size 0 situation( it cause http web server to wait timeout for long time)
by Michal Trojnara 15 Feb '05

15 Feb '05

On 2005-01-18, at 02:43, Stanley wrote: > 1.In our case, the web server sent TCP fin,ack to stunnel > but the stunnel just sent TCP ack, so it is TCP half close. > 2.The stunnel use read() function that try to read more data from > sock_fd > but return 0(EOF) because TCP half close. > 3.At this moment, the stunnel call SSL_shutdown() function > that sent close_notify alert but a broswer(IE6 or firefox1.0) return > no message. > > I just modify stunnel 4.07 client.c to set sock_wr=0 > that will close TCP connection from stunnel to web server when read() > EOF. I'm NOT going to break SSL protocol in stunnel to support broken SSL clients. Use: TIMEOUTclose = 0 configuration option instead. Best regards, Mike

1 0

multiple stunnel client
by Manila, Dinesh - Contractor 15 Feb '05

15 Feb '05

Hi, I am working in a project, whereas the EMS application need to be secured while communicating with NE. To make it secure, we have decided to go with stunnel and openSSL. I have following questions while using stunnel in my application: 1. I read that stunnel limits the number of clients to be connected to 125. Can I increase this number. If so, by increasing this number, what is the implication in performance of stuunel. 2. Since my EMS is capable of managing more than 1000 NEs, I would want to have multiple stunnel client running on the same workstation. Is this possible to have multiple stuunel process running on the same server. if so, how should my stunnle.conf file look like. I appreciate greatly, If I could get the answers for the above queries. Thanks and Regards, Dinesh Wipro Technologies. Bangalore.

2 1

Multiple listeners with just one instance of Stunnel?
by Michael Zarlenga 15 Feb '05

15 Feb '05

It doesn't seem possible to start 1 instance of Stunnel for multiple accept ports. Judging by the format of the Stunnel configuration file, it seems that I need to 1 instance of Stunnel for each port that accepts connections from the outside world. Is this true?

3 6

HELP!!! Problem uploading files
by Bhavesh Patel 14 Feb '05

14 Feb '05

Hi all, I'm using stunnel verstion 4.05 and openssl 0.9.7d. When trying to upload a large file say 1Meg I always get the following: 2005.01.27 14:30:40 LOG7[72667165:0]: stunnel accepted FD=0 from 136.157.232.120:3372 2005.01.27 14:30:40 LOG7[72667165:0]: FD 0 in non-blocking mode 2005.01.27 14:30:40 LOG7[79306780:0]: stunnel started 2005.01.27 14:30:40 LOG5[79306780:0]: stunnel connected from 136.157.232.120:3372 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): before/accept initialization 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): SSLv2 read client hello A 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): SSLv2 write server hello A 2005.01.27 14:30:40 LOG7[79306780:0]: waitforsocket: FD=0, DIR=read 2005.01.27 14:30:40 LOG7[79306780:0]: waitforsocket: ok 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): SSLv2 read client master key A 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): SSLv2 server start encryption 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): SSLv2 write server verify A 2005.01.27 14:30:40 LOG7[79306780:0]: waitforsocket: FD=0, DIR=read 2005.01.27 14:30:40 LOG7[79306780:0]: waitforsocket: ok 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): SSLv2 read client finished A 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): SSLv2 write request certificate A 2005.01.27 14:30:40 LOG7[79306780:0]: SSL state (accept): SSLv2 write server finished A 2005.01.27 14:30:40 LOG7[79306780:0]: 1 items in the session cache 2005.01.27 14:30:40 LOG7[79306780:0]: 0 client connects (SSL_connect()) 2005.01.27 14:30:40 LOG7[79306780:0]: 0 client connects that finished 2005.01.27 14:30:40 LOG7[79306780:0]: 0 client renegotiatations requested 2005.01.27 14:30:40 LOG7[79306780:0]: 1 server connects (SSL_accept()) 2005.01.27 14:30:40 LOG7[79306780:0]: 1 server connects that finished 2005.01.27 14:30:40 LOG7[79306780:0]: 0 server renegotiatiations requested 2005.01.27 14:30:40 LOG7[79306780:0]: 0 session cache hits 2005.01.27 14:30:40 LOG7[79306780:0]: 1 session cache misses 2005.01.27 14:30:40 LOG7[79306780:0]: 0 session cache timeouts 2005.01.27 14:30:40 LOG6[79306780:0]: Negotiated ciphers: DES-CBC3-MD5 SSLv2 Kx=RSA Au=RSA Enc=3DES(168 ) Mac=MD5 2005.01.27 14:30:40 LOG7[79306780:0]: FD 1 in non-blocking mode 2005.01.27 14:30:40 LOG7[79306780:0]: stunnel connecting 127.0.0.1:80 2005.01.27 14:30:40 LOG7[79306780:0]: remote connect #1: EINPROGRESS: retrying 2005.01.27 14:30:40 LOG7[79306780:0]: waitforsocket: FD=1, DIR=write 2005.01.27 14:30:40 LOG7[79306780:0]: waitforsocket: ok 2005.01.27 14:30:40 LOG7[79306780:0]: Remote FD=1 initialized 2005.01.27 14:30:40 LOG7[79306780:0]: SSL_read returned WANT_: retrying 2005.01.27 14:30:40 LOG7[79306780:0]: SSL closed on SSL_write 2005.01.27 14:30:40 LOG5[79306780:0]: Connection closed: 0 bytes sent to SSL, 668 bytes sent to socket 2005.01.27 14:30:40 LOG7[79306780:0]: removing pid file /usr/local/var/run/stunnel.pid 2005.01.27 14:30:40 LOG7[72667165:0]: Process 79306780 finished with code 0 (0 left) Specifically: I get SSL_read returned WANT_: retrying I am using sslv2 because sslV3 does not work with windows explorer. Any help would be appreciated. __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

2 1

using no certificate
by Zohar 14 Feb '05

14 Feb '05

Hi, I'm very new to all this issue of SSL, so I apologize if this question sounds stupid. I currently have a server that listens to connections on a TCP port. Clients that connect to it may do so using SSL v3 (mobile clients, which use their own SSL packages, so I have very little control over it). I want to add stunnel to my server's setting, to enable SSL communication. I have no need for the client to authenticate the server, I am only interested in the data being encrypted. I tried setting this up, but the client complains that my server certificate cannot be authenticated (I produced it using http://www.stunnel.org/pem/) Any pointers on how to set such a thing up (even for the time being, while I develop), without having to pay lots of money to a CA ?

3 2

Multiple Instances of stunnel
by dps_maillists＠mac.com 11 Feb '05

11 Feb '05

Hi everyone; Is it possible to run multiple instances of stunnel (v 4.07) in client mode on a single machine? We sould like to use stunnel to secure connections from a small number of client applications (1 to 10) connecting to a larger number of server applications (200 per client app). Ideally, we would like to use one instance of stunnel per client. Many thanks in advance. Doug

2 1

connect_wait: s_poll_wait timeout
by Alexander Lazic 07 Feb '05

07 Feb '05

Hi, we run stunnel on an solaris 9 with unlimited FD. Today we get the follwing error: connect_wait: s_poll_wait timeout With 'top' we see ~190-~220 threads and the client can't connect to our site. our config is: --- cert = /usr/local/apache/our.pem setuid = stunnel setgid = apache options = ALL pid = /usr/local/apache/logs/stunnel_netbanking.pid ciphers = ALL:!EXP1024-DHE-DSS-RC4-SHA:!EXP1024-RC4-SHA:!EXP1024-DHE-DSS-DES-CBC-SHA:!EXP1024-DES-CBC-SHA:!EXP1024-RC2-CBC-MD5:!EXP1024-RC4-MD5:!ADH:!EXP56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL:@STRENGTH debug = 6 output = /usr/local/apache/logs/stunnel_netbanking.log [https] accept = 10.3.169.208:443 connect = 10.3.169.208:10800 TIMEOUTclose = 0 xforwardedfor = yes --- stunnel 4.07 on sparc-sun-solaris2.9 PTHREAD+POLL+IPv4 with OpenSSL 0.9.7d 17 Mar 2004 PRNG seeded successfully file ulimit = 2147483647 (can be changed with 'ulimit -n') poll() used - no FD_SETSIZE limit for file descriptors 8388607 clients allowed --- Please can you help us to solve the problem. thx al ;-)

2 1

Problem downloading large files with sslv2
by Bhavesh Patel 04 Feb '05

04 Feb '05

Hi, I'm trying to download files from Internet Explorer using sslv2 and I keep getting the following message: 2005.02.04 16:45:04 LOG7[8237077:0]: FD 1 in non-blocking mode 2005.02.04 16:45:04 LOG7[8237077:0]: stunnel connecting 127.0.0.1:80 2005.02.04 16:45:04 LOG7[8237077:0]: remote connect #1: EINPROGRESS: retrying 2005.02.04 16:45:04 LOG7[8237077:0]: waitforsocket: FD=1, DIR=write 2005.02.04 16:45:04 LOG7[8237077:0]: waitforsocket: ok 2005.02.04 16:45:04 LOG7[8237077:0]: Remote FD=1 initialized 2005.02.04 16:45:04 LOG7[8237077:0]: SSL_read returned WANT_: retrying 2005.02.04 16:45:04 LOG7[8237077:0]: SSL closed on SSL_write 2005.02.04 16:45:04 LOG5[8237077:0]: Connection closed: 0 bytes sent to SSL, 669 bytes 2005.02.04 16:45:04 LOG7[8237077:0]: removing pid file /usr/local/var/run/stunnel.pid 2005.02.04 16:45:04 LOG7[2375710:0]: Process 8237077 finished with code 0 (0 left) Also does anyone know if that 10 TIMEOUTconnect for IE really works? Thanks, Bhavesh

1 0

concurrency request
by kevin 01 Feb '05

01 Feb '05

hi, I've recently set up stunnel for SSL connect. When I test its performance with siege with 700 concurrency request, I got this log: "Error: socket: connection timed out.: Operation now in progress" So, may I ask what is the upper limit of concurrency in stunnel, if the performance of the machine is good enough. and how can I increase the concurrency upper limit. thanks

2 1

Q: rereading configuration file?
by Heiko Nardmann 01 Feb '05

01 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Does stunnel offer a way to signal a need for rereading the configuration file, i.e. some kind of SIGHUP ? I would like to add services while running stunnel without stopping the program ... it should compare currently available services with the new list of services, stop the ones not available any more and start those which are new in the new/changed configuration ... - -- Heiko Nardmann (Dipl.-Ing. Technische Informatik) secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de) Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 Besuchen Sie uns vom 10. - 16. März auf der CeBIT 2005 in Halle 7, Stand D38. Informationen zu unseren CeBIT-Themen finden Sie unter www.secunet.com <outbind://44/www.secunet.com> - wir freuen uns auf das Gespräch mit Ihnen. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFB/4Dzpm53PRScYygRAtg4AJ9Ku/8xfufFdrLq7cz2+1GDjrcvyQCffVLw v/2D0Fd8UtTHpssq7cgc71Y= =uG2t -----END PGP SIGNATURE-----

3 2

Q: error message during startup?
by Heiko Nardmann 01 Feb '05

01 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I just got the following stunnel error message in my syslog: File descriptor out of range (1024>=1024) The reason is that I have tried to let stunnel create 2000 services. But where do I change the maximum for this range? (Linux) Kernel? Or stunnel? Thanks in advance! PS: I already changed ulimit to 4000. - -- Heiko Nardmann (Dipl.-Ing. Technische Informatik) secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de) Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 Besuchen Sie uns vom 10. - 16. März auf der CeBIT 2005 in Halle 7, Stand D38. Informationen zu unseren CeBIT-Themen finden Sie unter www.secunet.com <outbind://44/www.secunet.com> - wir freuen uns auf das Gespräch mit Ihnen. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFB/4TWpm53PRScYygRAv2JAKCHTe6zNvhmWAkypK5xymm+LWstEACgt1vJ vSNr7eeFXUpRFCu2SiY/4ls= =huyB -----END PGP SIGNATURE-----

2 1

Q: need of restart after CRL/CA directory contents change?
by Heiko Nardmann 31 Jan '05

31 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Since I want to write CRL files from all relevant CAs based on a regular (daily) basis I wonder whether it is necessary to restart stunnel if the contents of the CRL or CA directory changes. The regular part is going to be handled by a cronjob which does an LDAP search which results in the CA certificate and crl files. How does stunnel work in this situation? Do I need a restart after a cron run or not? Thanks in advance! - -- Heiko Nardmann (Dipl.-Ing. Technische Informatik) secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de) Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 Besuchen Sie uns vom 10. - 16. März auf der CeBIT 2005 in Halle 7, Stand D38. Informationen zu unseren CeBIT-Themen finden Sie unter www.secunet.com <outbind://44/www.secunet.com> - wir freuen uns auf das Gespräch mit Ihnen. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFB/j+kpm53PRScYygRArxfAJ4mXXvjL+qEh6lBJlhpJJfC/jSoEQCgx4ie Xjv5/K3xcL6qPxp5ZH3SzOk= =4/pC -----END PGP SIGNATURE-----

2 1

Re: [stunnel-users] Stunnel 4.05/4.07 Crash
by PinLee_Su＠azuretech.com.sg 31 Jan '05

31 Jan '05

Hi Michal, The initial lines look like this:- 2005.01.25 15:21:23 LOG5[1160:2612]: stunnel 4.07 on x86-pc-mingw32-gnu WIN32+IPv4 with OpenSSL 0.9.7e 25 Oct 2004 2005.01.25 15:21:24 LOG5[1160:1828]: No limit detected for the number of clients 2005.01.25 15:21:24 LOG5[1160:1476]: HTTP connected from 10.3.5.137:2013 2005.01.25 15:21:25 LOG3[1160:1476]: readsocket: Connection reset by peer (WSAECONNRESET) (10054) 2005.01.25 15:21:25 LOG5[1160:1476]: Connection reset: 206 bytes sent to SSL, 250 bytes sent to socket 2005.01.25 15:21:25 LOG5[1160:2380]: HTTP connected from 10.3.5.137:2024 2005.01.25 15:21:25 LOG3[1160:2380]: readsocket: Connection reset by peer (WSAECONNRESET) (10054) 2005.01.25 15:21:25 LOG5[1160:2380]: Connection reset: 206 bytes sent to SSL, 226 bytes sent to socket 2005.01.25 15:21:25 LOG5[1160:1992]: HTTP connected from 10.3.5.137:2056 2005.01.25 15:21:27 LOG5[1160:2220]: HTTP connected from 10.3.5.137:2084 2005.01.25 15:21:31 LOG5[1160:2220]: Connection closed: 4969 bytes sent to SSL, 41208 bytes sent to socket 2005.01.25 15:21:31 LOG5[1160:1028]: HTTP connected from 10.3.5.137:2104 2005.01.25 15:21:40 LOG5[1160:1028]: Connection closed: 2528 bytes sent to SSL, 31275 bytes sent to socket 2005.01.25 15:21:40 LOG5[1160:512]: HTTP connected from 10.3.5.137:2122 2005.01.25 15:21:43 LOG5[1160:1992]: Connection closed: 12539 bytes sent to SSL, 56951 bytes sent to socket 2005.01.25 15:21:45 LOG5[1160:512]: Connection closed: 1689 bytes sent to SSL, 21416 bytes sent to socket 2005.01.25 15:21:46 LOG5[1160:2044]: HTTP connected from 10.3.5.137:2154 2005.01.25 15:21:47 LOG5[1160:2148]: HTTP connected from 10.3.5.137:2160 I have 11 config files as each one has its own client certificate. each one contains the follow:- CAfile=c:\STunnel\config\root.pem cert=c:\STunnel\config\myCert_A.pem client=Yes debug=7 output=c:\STunnel\logs\myCert_A.log [HTTP] accept=3885 connect=10.70.1.81:443 thanks and rgds,spl "Azure Technologies is the IT solutions provider of Hutchison Whampoa Limited and a member of Hutchison Global Communications Holdings Limited." The message is for information purposes only and is not intended to create legally binding relations. The shareholders, directors and management of Azure Technologies and any of its group companies accept no responsibility and accordingly shall have no liability to any party whatsoever with respect to the contents of this message. This message (including any attachments) is intended only for the use of the addressee(s) named above. It may contain information that is PRIVILEGED and CONFIDENTIAL and should not be read, copied or otherwise used by any other person. If you are not the intended recipient, please erase all copies of the message (including attachments) and notify us immediately. PinLee_Su@azuretech .com.sg To: stunnel-users(a)mirt.net Sent by: cc: stunnel-users-bounc Subject: [stunnel-users] Stunnel 4.05/4.07 Crash es(a)mirt.net 01/28/2005 06:28 PM Hi, I've initiated 11 stunnel processes in the same server. Each of the stunnel process has its own client certificate to communicate to application server. However after sometime of execution, the stunnel processes are crached (dying off) one by one. below is the last portion of my log (with debug level 7). I don't see any critical error in the log. Would appreciate if someone could highlight to me what cause the problem or anyone has similar experience. 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1424]: 486 session cache hits 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache timeouts 2005.01.25 16:02:41 LOG7[2244:1424]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1804]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1804]: Connection closed: 716 bytes sent to SSL, 359 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1804]: HTTP finished (7 left) 2005.01.25 16:02:41 LOG7[2244:1424]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1424]: Connection closed: 716 bytes sent to SSL, 304 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1424]: HTTP finished (6 left) 2005.01.25 16:02:41 LOG7[2244:2240]: HTTP accepted FD=516 from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:2240]: FD 516 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:02:41 LOG7[2244:2240]: New thread created 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP started 2005.01.25 16:02:41 LOG5[2244:1252]: HTTP connected from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:1252]: FD 704 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP connecting 10.1.11.56:443 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: waiting 10 seconds 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: connected 2005.01.25 16:02:41 LOG7[2244:1252]: Remote FD=704 initialized 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): before/connect initialization 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: 241 items in the session cache 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects (SSL_connect()) 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 489 client renegotiatations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:41 LOG6[2244:1252]: SSL connected: previous session reused 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:42 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:42 LOG7[2244:1252]: 242 items in the session cache 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects (SSL_connect()) 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 490 client renegotiatations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:42 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:43 LOG7[2244:2428]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG7[2244:2284]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG5[2244:2428]: Connection closed: 606 bytes sent to SSL, 242 bytes sent to socket 2005.01.25 16:02:43 LOG5[2244:2284]: Connection closed: 7758 bytes sent to SSL, 23278 bytes sent to socket 2005.01.25 16:02:43 LOG7[2244:2428]: HTTP finished (6 left) 2005.01.25 16:02:43 LOG7[2244:2284]: HTTP finished (5 left) 2005.01.25 16:02:45 LOG7[2244:1188]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:45 LOG5[2244:1188]: Connection closed: 1485 bytes sent to SSL, 7307 bytes sent to socket 2005.01.25 16:02:47 LOG7[2244:2228]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:47 LOG5[2244:2228]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:49 LOG7[2244:1644]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:49 LOG5[2244:1644]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:50 LOG7[2244:2268]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:50 LOG5[2244:2268]: Connection closed: 418 bytes sent to SSL, 1375 bytes sent to socket 2005.01.25 16:11:14 LOG7[2244:2240]: HTTP accepted FD=796 from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:2240]: FD 796 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:11:14 LOG7[2244:2240]: New thread created 2005.01.25 16:11:14 LOG7[2244:992]: HTTP started 2005.01.25 16:11:14 LOG5[2244:992]: HTTP connected from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:992]: FD 632 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:992]: HTTP connecting 10.1.11.56:443 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: waiting 10 seconds 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: connected 2005.01.25 16:11:14 LOG7[2244:992]: Remote FD=632 initialized 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): before/connect initialization 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:14 LOG7[2244:992]: 242 items in the session cache 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects (SSL_connect()) 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 490 client renegotiatations requested 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects (SSL_accept()) 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 0 server renegotiatiations requested 2005.01.25 16:11:14 LOG7[2244:992]: 488 session cache hits 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache misses 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache timeouts 2005.01.25 16:11:14 LOG6[2244:992]: SSL connected: previous session reused 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:2268]: HTTP finished (5 left) thanks and rgds,spl _______________________________________________ stunnel-users mailing list stunnel-users(a)mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users

1 0

Stunnel 4.05/4.07 Crash
by PinLee_Su＠azuretech.com.sg 28 Jan '05

28 Jan '05

Hi, I've initiated 11 stunnel processes in the same server. Each of the stunnel process has its own client certificate to communicate to application server. However after sometime of execution, the stunnel processes are crached (dying off) one by one. below is the last portion of my log (with debug level 7). I don't see any critical error in the log. Would appreciate if someone could highlight to me what cause the problem or anyone has similar experience. 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1424]: 486 session cache hits 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache timeouts 2005.01.25 16:02:41 LOG7[2244:1424]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1804]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1804]: Connection closed: 716 bytes sent to SSL, 359 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1804]: HTTP finished (7 left) 2005.01.25 16:02:41 LOG7[2244:1424]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1424]: Connection closed: 716 bytes sent to SSL, 304 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1424]: HTTP finished (6 left) 2005.01.25 16:02:41 LOG7[2244:2240]: HTTP accepted FD=516 from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:2240]: FD 516 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:02:41 LOG7[2244:2240]: New thread created 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP started 2005.01.25 16:02:41 LOG5[2244:1252]: HTTP connected from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:1252]: FD 704 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP connecting 10.1.11.56:443 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: waiting 10 seconds 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: connected 2005.01.25 16:02:41 LOG7[2244:1252]: Remote FD=704 initialized 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): before/connect initialization 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: 241 items in the session cache 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects (SSL_connect()) 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 489 client renegotiatations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:41 LOG6[2244:1252]: SSL connected: previous session reused 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:42 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:42 LOG7[2244:1252]: 242 items in the session cache 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects (SSL_connect()) 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 490 client renegotiatations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:42 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:43 LOG7[2244:2428]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG7[2244:2284]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG5[2244:2428]: Connection closed: 606 bytes sent to SSL, 242 bytes sent to socket 2005.01.25 16:02:43 LOG5[2244:2284]: Connection closed: 7758 bytes sent to SSL, 23278 bytes sent to socket 2005.01.25 16:02:43 LOG7[2244:2428]: HTTP finished (6 left) 2005.01.25 16:02:43 LOG7[2244:2284]: HTTP finished (5 left) 2005.01.25 16:02:45 LOG7[2244:1188]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:45 LOG5[2244:1188]: Connection closed: 1485 bytes sent to SSL, 7307 bytes sent to socket 2005.01.25 16:02:47 LOG7[2244:2228]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:47 LOG5[2244:2228]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:49 LOG7[2244:1644]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:49 LOG5[2244:1644]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:50 LOG7[2244:2268]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:50 LOG5[2244:2268]: Connection closed: 418 bytes sent to SSL, 1375 bytes sent to socket 2005.01.25 16:11:14 LOG7[2244:2240]: HTTP accepted FD=796 from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:2240]: FD 796 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:11:14 LOG7[2244:2240]: New thread created 2005.01.25 16:11:14 LOG7[2244:992]: HTTP started 2005.01.25 16:11:14 LOG5[2244:992]: HTTP connected from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:992]: FD 632 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:992]: HTTP connecting 10.1.11.56:443 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: waiting 10 seconds 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: connected 2005.01.25 16:11:14 LOG7[2244:992]: Remote FD=632 initialized 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): before/connect initialization 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:14 LOG7[2244:992]: 242 items in the session cache 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects (SSL_connect()) 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 490 client renegotiatations requested 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects (SSL_accept()) 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 0 server renegotiatiations requested 2005.01.25 16:11:14 LOG7[2244:992]: 488 session cache hits 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache misses 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache timeouts 2005.01.25 16:11:14 LOG6[2244:992]: SSL connected: previous session reused 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:2268]: HTTP finished (5 left) thanks and rgds,spl

2 1

Stunnel 4.05/4.07 Crash
by PinLee_Su＠azuretech.com.sg 28 Jan '05

28 Jan '05

Hi, I've initiated 11 stunnel processes in the same server. Each of the stunnel process has its own client certificate to communicate to application server. However after sometime of execution, the stunnel processes are crached (dying off) one by one. below is the last portion of my log (with debug level 7). I don't see any critical error in the log. Would appreciate if someone could highlight to me what cause the problem or anyone has similar experience. 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1424]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1424]: 486 session cache hits 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1424]: 0 session cache timeouts 2005.01.25 16:02:41 LOG7[2244:1424]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1804]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1804]: Connection closed: 716 bytes sent to SSL, 359 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1804]: HTTP finished (7 left) 2005.01.25 16:02:41 LOG7[2244:1424]: SSL socket closed on SSL_read 2005.01.25 16:02:41 LOG5[2244:1424]: Connection closed: 716 bytes sent to SSL, 304 bytes sent to socket 2005.01.25 16:02:41 LOG7[2244:1424]: HTTP finished (6 left) 2005.01.25 16:02:41 LOG7[2244:2240]: HTTP accepted FD=516 from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:2240]: FD 516 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:02:41 LOG7[2244:2240]: New thread created 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP started 2005.01.25 16:02:41 LOG5[2244:1252]: HTTP connected from 10.3.5.137:1405 2005.01.25 16:02:41 LOG7[2244:1252]: FD 704 in non-blocking mode 2005.01.25 16:02:41 LOG7[2244:1252]: HTTP connecting 10.1.11.56:443 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: waiting 10 seconds 2005.01.25 16:02:41 LOG7[2244:1252]: connect_wait: connected 2005.01.25 16:02:41 LOG7[2244:1252]: Remote FD=704 initialized 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): before/connect initialization 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: 241 items in the session cache 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects (SSL_connect()) 2005.01.25 16:02:41 LOG7[2244:1252]: 979 client connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 489 client renegotiatations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:41 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:41 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:41 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:41 LOG6[2244:1252]: SSL connected: previous session reused 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:02:41 LOG7[2244:1252]: SSL state (connect): SSLv3 flush data 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_write returned WANT_: retrying 2005.01.25 16:02:41 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:42 LOG7[2244:1252]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:02:42 LOG7[2244:1252]: 242 items in the session cache 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects (SSL_connect()) 2005.01.25 16:02:42 LOG7[2244:1252]: 980 client connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 490 client renegotiatations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects (SSL_accept()) 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server connects that finished 2005.01.25 16:02:42 LOG7[2244:1252]: 0 server renegotiatiations requested 2005.01.25 16:02:42 LOG7[2244:1252]: 487 session cache hits 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache misses 2005.01.25 16:02:42 LOG7[2244:1252]: 0 session cache timeouts 2005.01.25 16:02:42 LOG7[2244:1252]: SSL_read returned WANT_: retrying 2005.01.25 16:02:43 LOG7[2244:2428]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG7[2244:2284]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:43 LOG5[2244:2428]: Connection closed: 606 bytes sent to SSL, 242 bytes sent to socket 2005.01.25 16:02:43 LOG5[2244:2284]: Connection closed: 7758 bytes sent to SSL, 23278 bytes sent to socket 2005.01.25 16:02:43 LOG7[2244:2428]: HTTP finished (6 left) 2005.01.25 16:02:43 LOG7[2244:2284]: HTTP finished (5 left) 2005.01.25 16:02:45 LOG7[2244:1188]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:45 LOG5[2244:1188]: Connection closed: 1485 bytes sent to SSL, 7307 bytes sent to socket 2005.01.25 16:02:47 LOG7[2244:2228]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:47 LOG5[2244:2228]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:49 LOG7[2244:1644]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:49 LOG5[2244:1644]: Connection closed: 667 bytes sent to SSL, 552 bytes sent to socket 2005.01.25 16:02:50 LOG7[2244:2268]: s_poll_wait timeout waiting for SSL close_notify 2005.01.25 16:02:50 LOG5[2244:2268]: Connection closed: 418 bytes sent to SSL, 1375 bytes sent to socket 2005.01.25 16:11:14 LOG7[2244:2240]: HTTP accepted FD=796 from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:2240]: FD 796 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:2240]: Creating a new thread 2005.01.25 16:11:14 LOG7[2244:2240]: New thread created 2005.01.25 16:11:14 LOG7[2244:992]: HTTP started 2005.01.25 16:11:14 LOG5[2244:992]: HTTP connected from 10.3.5.137:3973 2005.01.25 16:11:14 LOG7[2244:992]: FD 632 in non-blocking mode 2005.01.25 16:11:14 LOG7[2244:992]: HTTP connecting 10.1.11.56:443 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: waiting 10 seconds 2005.01.25 16:11:14 LOG7[2244:992]: connect_wait: connected 2005.01.25 16:11:14 LOG7[2244:992]: Remote FD=632 initialized 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): before/connect initialization 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 read finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:14 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:14 LOG7[2244:992]: 242 items in the session cache 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects (SSL_connect()) 2005.01.25 16:11:14 LOG7[2244:992]: 981 client connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 490 client renegotiatations requested 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects (SSL_accept()) 2005.01.25 16:11:14 LOG7[2244:992]: 0 server connects that finished 2005.01.25 16:11:14 LOG7[2244:992]: 0 server renegotiatiations requested 2005.01.25 16:11:14 LOG7[2244:992]: 488 session cache hits 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache misses 2005.01.25 16:11:14 LOG7[2244:992]: 0 session cache timeouts 2005.01.25 16:11:14 LOG6[2244:992]: SSL connected: previous session reused 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSL renegotiate ciphers 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server hello A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server certificate request A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 read server done A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client certificate A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write client key exchange A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write certificate verify A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write change cipher spec A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 write finished A 2005.01.25 16:11:15 LOG7[2244:992]: SSL state (connect): SSLv3 flush data 2005.01.25 16:11:15 LOG7[2244:992]: SSL_write returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:992]: SSL_read returned WANT_: retrying 2005.01.25 16:11:15 LOG7[2244:2268]: HTTP finished (5 left) thanks and rgds,spl

1 0

Re: [stunnel-announce] cannot create pid
by higuita 27 Jan '05

27 Jan '05

Hi On Tue, 25 Jan 2005 14:15:45 -0500 "Humberto Morell" <morell(a)seg.inf.cu> wrote: > Hello list please use the stunnel-users instead of stunnel-anounce 8) > Cannot create pid file /var/run/stunnel.pid (...) > prueba:/usr/local/etc/stunnel # ls -l /var/run (...) > chroot = /var/lib/stunnel/ (...) > pid = /var/run/stunnel.pid so you cant create the pid, and you think that /var/run is correct, but you are forgeting that you enabled the chroot, so you have to check the /var/run inside the chroot, not your main /var/run directory (that the chroot stunnel cant access) check the /var/lib/stunnel/var/run and you will find that you dont have that directory or it have the wrong permissions good luck higuita -- Daniel Mota Leite Gestor de Sistemas/System Manager Centro de Computação Gráfica Tel: +351 253 439 300 Rua Teixeira de Pascoais, 596 Fax: +351 253 439 348 4800-073 Guimarães Portugal CCG and University of Minho are Members of the INI-GraphicsNet

1 0