stunnel-users

8 participants
3311 discussions

stunnel - haproxy setup with protocol = proxy
by Robert Garcia 07 Jun '12

07 Jun '12

I am trying to setup stunnel with protocol = proxy through haproxy to my apache2 cluster. I have been using haproxy for a while, and wanted to try this before having to go to nginx, or some other proxy. My config works fine as is if I remove the "accept proxy" from the haproxy.cfg and the protocol=proxy from stunnel config, as soon as those are in, I get a 502 bad gateway. My haproxy.cfg: global log 127.0.0.1 local0 log 127.0.0.1 local1 debug #log loghost local0 info maxconn 50000 #chroot /usr/share/haproxy user haproxy group haproxy daemon #debug #quiet defaults log global mode http option httplog option dontlognull option forwardfor retries 3 option redispatch maxconn 50000 contimeout 5000 clitimeout 60000 srvtimeout 300000 stats uri /haproxy_xxxx stats realm Global\ statistics stats auth xxxxxx:xxxxxxx frontend dev-stg bind *:80 mode http timeout client 5m option forwardfor default_backend dev-www frontend dev-stg-ssl bind *:81 accept-proxy mode http option httpclose option forwardfor timeout client 5m default_backend dev-www backend dev-www mode http timeout connect 10s timeout server 600s balance roundrobin #begin_web_config server ws1 10.0.2.10 maxconn 1000 check port 80 #end_web_config stats uri /haproxy_xxxx stats realm Global\ statistics stats auth xxxxxx:xxxxxxx My stunnel config: ; ***************************************************************************** ; * Global Options * ; ***************************************************************************** ; A copy of some devices and system files is needed within the chroot jail ; Chroot conflicts with configuration file reload and many other features chroot = /var/lib/stunnel4/ ; Chroot jail can be escaped if setuid option is not used setuid = stunnel4 setgid = stunnel4 ; PID is created inside the chroot jail pid = /stunnel4.pid ; Debugging stuff (may useful for troubleshooting) debug = 7 output = /var/log/stunnel4/stunnel.log ; ***************************************************************************** ; * Service Defaults (may also be specified in individual service sections) * ; ***************************************************************************** ; Certificate/key is needed in server mode and optional in client mode cert = /usr/local/certs/server.crt key = /usr/local/certs/server.key ; Disable support for insecure SSLv2 protocol options = NO_SSLv2 ; Workaround for Eudora bug ;options = DONT_INSERT_EMPTY_FRAGMENTS ; The following options provide additional security at some performance penalty ; Default ECDH/DH parameters are strong/conservative, so it is quite safe to ; comment out these lines in order to get a performance boost ;options = SINGLE_ECDH_USE ;options = SINGLE_DH_USE ; ***************************************************************************** ; * Service Definitions (remove all services for inetd mode) * ; ***************************************************************************** ; Example SSL server mode services ; Example SSL front-end to a web server [proxy] accept = 443 connect = 127.0.0.1:81 ; "TIMEOUTclose = 0" is a workaround for a design flaw in Microsoft SSL ; It does not use SSL close-notify alert designed to prevent truncation attacks TIMEOUTclose = 0 protocol = proxy ; vim:ft=dosini And here is the syslog for haproxy and stunner (ip address in log and cfgs are changed to protect the innocent ;-) ) Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193127680]: Service [proxy] accepted (FD=3) from 1.2.3.4:35045 Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: Service [proxy] started Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG5[1737:140557193119488]: Service [proxy] accepted connection from 1.2.3.4:35045 Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG6[1737:140557193119488]: connect_blocking: connecting 127.0.0.1:81 Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: connect_blocking: s_poll_wait 127.0.0.1:81: waiting 10 seconds Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG5[1737:140557193119488]: connect_blocking: connected 127.0.0.1:81 Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG5[1737:140557193119488]: Service [proxy] connected remote server from 127.0.0.1:49010 Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: Remote socket (FD=8) initialized Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG6[1737:140557193119488]: Server-mode proxy protocol negotiations started Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: -> PROXY TCP4 1.2.3.4 10.0.2.9 35045 443 Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG6[1737:140557193119488]: Server-mode proxy protocol negotiations succeeded Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG6[1737:140557193119488]: SSL accepted: new session negotiated Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG6[1737:140557193119488]: Negotiated TLSv1/SSLv3 ciphersuite: DHE-RSA-AES256-SHA (256-bit encryption) Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG6[1737:140557193119488]: Compression: null, expansion: null Jun 7 07:10:50 localhost haproxy[1710]: 1.2.3.4:35045 [07/Jun/2012:07:10:50.496] dev-stg-ssl dev-www/ws1 214/0/1/-1/216 502 754 - - PH-- 0/0/0/0/0 0/0 "GET / HTTP/1.1" Jun 7 07:10:50 localhost haproxy[1710]: 1.2.3.4:35045 [07/Jun/2012:07:10:50.496] dev-stg-ssl dev-www/ws1 214/0/1/-1/216 502 754 - - PH-- 0/0/0/0/0 0/0 "GET / HTTP/1.1" Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: Socket closed on read Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: Sending close_notify alert Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG6[1737:140557193119488]: SSL_shutdown successfully sent close_notify alert Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG3[1737:140557193119488]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG5[1737:140557193119488]: Connection closed: 204 byte(s) sent to SSL, 137 byte(s) sent to socket Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: Remote socket (FD=8) closed Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: Local socket (FD=3) closed Jun 7 07:10:50 ec2-204-236-129-168 stunnel: LOG7[1737:140557193119488]: Service [proxy] finished (0 left) 1.2.3.4 = my external ip I am testing with 10.0.2.9 = haproxy/stunnel server 10.0.2.10 = my apache server Any ideas greatly appreciated. -- Robert Garcia BigHead Technology 15520 Coutolenc Rd Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 rgarcia(a)bighead.net (mailto:[email protected]) - http://bighead.net/

1 0

Re: [stunnel-users] Outlook and stunnel
by James Devine 05 Jun '12

05 Jun '12

I'm using stunnel as a reverse proxy. I have an smtp server smtp1 and an stunnel server proxy1. Clients connect to and negotiate ssl on proxy1 which then connects to smtp1 via a plaintext connection. stunnel does not reside on the client. If I connect the client directly to smtp1 via ssl it works fine. On Tue, Jun 5, 2012 at 12:20 PM, Pierre DELAAGE <delaage.pierre(a)free.fr>wrote: > Hmmm if you are using stunnel on client side (as suggested by your > correction) it is that YOU DO NOT WANT TO USE SSL OPTION in OUTLOOK. > > because stunnel will act as an "almost transparent' ssl tunnel. > > So in outlook : uncheck ssl option and give "localhost" as your smtp > server. > > and adapt local port according to your stunnel conf. > > Apart from that : I use stunnel on the server ONLY, with self signed > certificate coming from openssl, > and outlook configured as ssl client is working. > SSLversion = all is always GOOD > > works with stunnel 4.20 on linux mandriva 2008, outlook 2007 > > Pierre > > > > Le 05/06/2012 20:08, James Devine a écrit : > > > On Tue, Jun 5, 2012 at 10:52 AM, James Devine <fxmulder(a)gmail.com> wrote: > >> I am trying to setup stunnel to ssl proxy mail to an smtp server and this >> seems to work fine for thunderbird but when I try using outlook 2010 to >> connect via ssl I get the error: >> >> Send test e-mail message: Your server does not support the connection >> encryption type you have specified. Try changing the encryption method. >> >> For sslVersion I have the option of SSLv3 and TLSv1, all and SSLv2 do >> not seem to work so I'm not sure if that is the problem >> >> Anyone else run in to this or know what I might do to resolve it? >> > > I can get it to work if I setup ssl on the end server directly and bypass > stunnel > > > _______________________________________________ > stunnel-users mailing [email protected]://stunnel.mirt.net/mailman/listinfo/stunnel-users > > >

1 0

Outlook and stunnel
by James Devine 05 Jun '12

05 Jun '12

I am trying to setup stunnel to ssl proxy mail to an smtp server and this seems to work fine for thunderbird but when I try using outlook 2010 to connect via ssl I get the error: Send test e-mail message: Your server does not support the connection encryption type you have specified. Try changing the encryption method. For sslVersion I have the option of SSLv3 and TLSv1, all and SSLv2 do not seem to work so I'm not sure if that is the problem Anyone else run in to this or know what I might do to resolve it?

1 1

stunnel 4.53 released
by Michal Trojnara 03 Jun '12

03 Jun '12

Dear Users, I have released version 4.53 of stunnel. This is major a bugfix release. Upgrade is highly recommended. The ChangeLog entry: Version 4.53, 2012.03.19, urgency: MEDIUM: * New features - Added client-mode "sni" option to directly control the value of TLS Server Name Indication (RFC 3546) extension. - Added support for IP_FREEBIND socket option with a pached Linux kernel. - Glibc-specific dynamic allocation tuning was applied to help unused memory deallocation. - Non-blocking OCSP implementation. * Bugfixes - Compilation fixes for old versions of OpenSSL (tested against 0.9.6). - Usage of uninitialized variables fixed in exec+connect services. - Occasional logging subsystem crash with exec+connect services. - OpenBSD compilation fix (thx to Michele Orru'). - Session id context initialized with session name rather than a constant. - Fixed handling of a rare inetd mode use case, where either stdin or stdout is a socket, but not both of them at the same time. - Fixed missing OPENSSL_Applink http://www.openssl.org/support/faq.html#PROG2 - Fixed crash on termination with FORK threading model. - Fixed dead canary after configuration reload with open connections. - Fixed missing file descriptors passed to local mode processes. - Fixed required jmp_buf alignment on Itanium platform. - Removed creating /dev/zero in the chroot jail on Solaris platform. - Fixed detection of WSAECONNREFUSED Winsock error. - Missing Microsoft.VC90.CRT.manifest added to Windows installer. Home page: http://www.stunnel.org/ Download: ftp://ftp.stunnel.org/stunnel/ SHA-256 hash for stunnel-4.53.tar.gz: 3e640aa4c96861d10addba758b66e99e7c5aec8697764f2a59ca2268901b8e57 Best regards, Mike

3 2

Re: [stunnel-users] BEAST Attack
by Scott McKeown 31 May '12

31 May '12

Hi Mike, Thank you for your input. I'll rebuild today and retest. Our company openly supports Open Source projects that we use and we will continue to do so. However, since we are still in a R&D position with STunnel at the moment I thought it would be better to continue to use the users group. I'll post again once I've rebuilt and tested, which might not be until the end of next week now as we have an nice extended weekend in the UK for the Golden Jubilee which is nice. ~Yours, Scott -- With Kind Regards. Scott McKeown Loadbalancer.org http://www.loadbalancer.org

1 0

Re: [stunnel-users] BEAST Attack
by Scott McKeown 30 May '12

30 May '12

Hi Michal, Thanks for following this up. I'm using the latest build of STunnel v4.53 as shown below (I check the site once a week just to make sure too) # stunnel -version stunnel 4.53 on x86_64-unknown-linux-gnu platform Compiled/running with OpenSSL 1.0.0-fips 29 Mar 2010 Threading:PTHREAD SSL:+ENGINE+OCSP+FIPS Auth:none Sockets:POLL+IPv6 Global options: debug = daemon.notice pid = /usr/local/var/run/stunnel/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level options: ciphers = FIPS (with "fips = yes") ciphers = ALL:!SSLv2:!aNULL:!EXP:!LOW:-MEDIUM:RC4:+HIGH (with "fips = no") session = 300 seconds sslVersion = TLSv1 (with "fips = yes") sslVersion = TLSv1 for client, all for server (with "fips = no") stack = 65536 bytes TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none I've also included a copy of my stunnel.cfg file below: # more /etc/stunnel/stunnel.cfg # STunnel configuration file generated by loadbalancer.org appliance setgid = nobody pid = /stunnel.pid debug = 0 [S1] accept = 192.168.82.182:443 connect = 192.168.82.181:81 cert = /etc/loadbalancer.org/certs/S1.pem ciphers = RC4:HIGH:!MD5:!aNULL options = NO_SSLv2 protocol = proxy I'm looking to include the STunnel Product within our Loadbalancer Appliance in our next upcoming release but with everyone now using the SSL checker that I mentioned in one of my last e-Mails more customers are becoming concerned about MITM Attacks etc. so I would really like to get this solved before I move forward with the project. Oh, I guess I should also mention that this is running on a Centos 6.2 box. ~Yours, Scott

2 1

BEAST Attack
by Scott McKeown 29 May '12

29 May '12

Hi All, Has anyone looked at the current issue with the BEAST Attack. I'm looking at https://www.ssllabs.com/ssltest/index.html which can be used for testing SSL Certificates I also use Pound Proxy which I have now patched and this has removed the threat. However, I don't seem to be able to get the same result from a STunnel installation. If anyone can give some advice that would be great. ~Yours, Scott

3 5

limit to number of services
by Terren Suydam 25 May '12

25 May '12

Hi there, I seem to be hitting a limit on the number of stunnel services I can run simultaneously. According to the log, they appear to set up without any issues, but after 64 services they don't pass traffic. Is this something stunnel itself limits, or is it an OS limitation? I am running the latest windows build on Windows Server 2008. Either way, is there an easy way to increase the number of services? Thanks, Terren

1 0

Stunnel quitted unexpectedly repeated for a number of times
by Im Q 24 May '12

24 May '12

Hi all, We have encountered a strange situation that stunnel We have the following setup in our production servers. > Windows [ ... -> Apache -> Stunnel 4.50 ] --> AIX [Stunnel 4.50 -> JBoss] * As we had experienced the Stunnel in AIX died in a random time during testing stage, we added a cron job to start Stunnel in case stunnel disappeared. Recently, in our production servers, the stunnel disappeared and being started by corn repeatedly during a short period of time in the same day. We so far encounter similar problem for 2 times. Below are the restart time of the most recent incident. > 09:22:00,09:38:00,09:45:00, > 10:24:00,10:34:00,10:50:00, > 11:06:00,11:16:01,11:17:00,11:19:00,11:22:00,11:23:00,11:29:01,11:32:00,11:34:01,11:35:00,11:39:01 We found that in the logs, they always ended with the following: > 2012.05.23 11:16:03 LOG7[12517524:1]: Dispatching signals from the signal pipe > ... > 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD > ...(same message repeatly for serveral time) > 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD Here is the active options in config file: [Windows Side] > debug = 7 > output = D:\app-logs\stunnel\stunnel.log > verify = 0 > options = NO_SSLv2 > client = yes > taskbar = no > [prdweb01_out_app01] > accept = PRDWEB01:18009 > connect = PRDAPP01:18010 > [prdweb01_out_app02] > accept = PRDWEB01:18019 > connect = PRDAPP02:18010 [AIX Side] > pid = /opt/stunnel/4.50/prd/stunnel0-app/stunnel.pid > debug = 7 > output = /opt/stunnel/4.50/prd/stunnel0-app/log/stunnel.log > cert = /opt/stunnel/4.50/prd/stunnel0-app/PRD.certnew-b64.cer > key = /opt/stunnel/4.50/prd/stunnel0-app/PRD.private.key > options = NO_SSLv2 > [prdweb_in] > accept = PRDAPP01:18010 > connect = PRDAPP01:8009 Start up command > nohup stunnel /opt/stunnel/4.50/prd/stunnel0-app/stunnel-server.conf Attached at the end is the one of the log during the incident. Is there any suggestion on how to find out the cause of the problem? What are the possible causes that would make it disappeared after those processing of SIGCHLD signal? What may caused the signal dispatching other than killing them manually for shutdown? Thank you very much! Best Regards, Jacky -- LOG FILE CONTENT BELOW -- 2012.05.23 11:16:01 LOG7[11862064:1]: Clients allowed=31999 2012.05.23 11:16:01 LOG5[11862064:1]: stunnel 4.50 on powerpc-ibm-aix6.1.0.0 platform 2012.05.23 11:16:01 LOG5[11862064:1]: Compiled/running with OpenSSL 0.9.8m 25 Feb 2010 2012.05.23 11:16:01 LOG5[11862064:1]: Threading:PTHREAD SSL:ENGINE Auth:none Sockets:POLL,IPv6 2012.05.23 11:16:01 LOG5[11862064:1]: Reading configuration from file /opt/stunnel/4.50/prd/stunnel0-app/stunnel-server.conf 2012.05.23 11:16:01 LOG6[11862064:1]: Unable to retrieve any random data from /home/appadmin/.rnd 2012.05.23 11:16:01 LOG7[11862064:1]: Wrote 0 new random bytes to /home/appadmin/.rnd 2012.05.23 11:16:01 LOG7[11862064:1]: PRNG seeded successfully 2012.05.23 11:16:01 LOG6[11862064:1]: Initializing SSL context for service prdweb_in 2012.05.23 11:16:01 LOG4[11862064:1]: Insecure file permissions on /opt/stunnel/4.50/prd/stunnel0-app/PRD.private.key 2012.05.23 11:16:01 LOG7[11862064:1]: Certificate: /opt/stunnel/4.50/prd/stunnel0-app/PRD.certnew-b64.cer 2012.05.23 11:16:01 LOG7[11862064:1]: Certificate loaded 2012.05.23 11:16:01 LOG7[11862064:1]: Key file: /opt/stunnel/4.50/prd/stunnel0-app/PRD.private.key 2012.05.23 11:16:01 LOG7[11862064:1]: Private key loaded 2012.05.23 11:16:01 LOG7[11862064:1]: Could not load DH parameters from /opt/stunnel/4.50/prd/stunnel0-app/PRD.certnew-b64.cer 2012.05.23 11:16:01 LOG7[11862064:1]: Using hardcoded DH parameters 2012.05.23 11:16:01 LOG7[11862064:1]: DH initialized with 2048-bit key 2012.05.23 11:16:01 LOG7[11862064:1]: SSL options set: 0x01000004 2012.05.23 11:16:01 LOG6[11862064:1]: SSL context initialized 2012.05.23 11:16:01 LOG5[11862064:1]: Configuration successful 2012.05.23 11:16:01 LOG7[11862064:1]: Option SO_REUSEADDR set on accept socket 2012.05.23 11:16:01 LOG7[11862064:1]: Service prdweb_in bound to 10.18.7.71:18010 2012.05.23 11:16:01 LOG7[11862064:1]: Service prdweb_in opened FD=7 2012.05.23 11:16:01 LOG7[12517524:1]: Created pid file /opt/stunnel/4.50/prd/stunnel0-app/stunnel.pid 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=0 from 10.18.7.11:61657 2012.05.23 11:16:01 LOG7[12517524:258]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:258]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:258]: Service prdweb_in accepted connection from 10.18.7.11:61657 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=1 from 10.18.7.11:61685 2012.05.23 11:16:01 LOG7[12517524:515]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:515]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:515]: Service prdweb_in accepted connection from 10.18.7.11:61685 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=2 from 10.18.7.11:61667 2012.05.23 11:16:01 LOG7[12517524:772]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:772]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:772]: Service prdweb_in accepted connection from 10.18.7.11:61667 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=9 from 10.18.7.11:61659 2012.05.23 11:16:01 LOG7[12517524:1029]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1029]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:1029]: Service prdweb_in accepted connection from 10.18.7.11:61659 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=10 from 10.18.7.12:64270 2012.05.23 11:16:01 LOG7[12517524:1286]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1286]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:1286]: Service prdweb_in accepted connection from 10.18.7.12:64270 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=11 from 10.18.7.11:61669 2012.05.23 11:16:01 LOG7[12517524:1543]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1543]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:1543]: Service prdweb_in accepted connection from 10.18.7.11:61669 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=12 from 10.18.7.12:64268 2012.05.23 11:16:01 LOG7[12517524:1800]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1800]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:1800]: Service prdweb_in accepted connection from 10.18.7.12:64268 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=13 from 10.18.7.11:61671 2012.05.23 11:16:01 LOG7[12517524:2057]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:2057]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:2057]: Service prdweb_in accepted connection from 10.18.7.11:61671 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=14 from 10.18.7.11:61673 2012.05.23 11:16:01 LOG7[12517524:2314]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:2314]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:2314]: Service prdweb_in accepted connection from 10.18.7.11:61673 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=15 from 10.18.7.11:61677 2012.05.23 11:16:01 LOG7[12517524:2571]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:2571]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:2571]: Service prdweb_in accepted connection from 10.18.7.11:61677 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=16 from 10.18.7.11:61676 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=18 from 10.18.7.12:64272 2012.05.23 11:16:01 LOG7[12517524:3085]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:3085]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:3085]: Service prdweb_in accepted connection from 10.18.7.12:64272 2012.05.23 11:16:01 LOG7[12517524:2828]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:2828]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:2828]: Service prdweb_in accepted connection from 10.18.7.11:61676 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=17 from 10.18.7.11:61661 2012.05.23 11:16:01 LOG7[12517524:3342]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:3342]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:3342]: Service prdweb_in accepted connection from 10.18.7.11:61661 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=19 from 10.18.7.11:61687 2012.05.23 11:16:01 LOG7[12517524:3599]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:3599]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:3599]: Service prdweb_in accepted connection from 10.18.7.11:61687 2012.05.23 11:16:01 LOG6[12517524:1286]: SSL accepted: new session negotiated 2012.05.23 11:16:01 LOG6[12517524:1286]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:01 LOG6[12517524:1286]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:1286]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:1286]: Service prdweb_in connected remote server from 10.18.7.71:56505 2012.05.23 11:16:01 LOG7[12517524:1286]: Remote FD=20 initialized 2012.05.23 11:16:01 LOG7[12517524:1286]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=21 from 10.18.7.11:61663 2012.05.23 11:16:01 LOG7[12517524:3856]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:3856]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:3856]: Service prdweb_in accepted connection from 10.18.7.11:61663 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=22 from 10.18.7.11:61665 2012.05.23 11:16:01 LOG7[12517524:4113]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=23 from 10.18.7.12:64274 2012.05.23 11:16:01 LOG7[12517524:4370]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:4113]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG7[12517524:4370]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:4370]: Service prdweb_in accepted connection from 10.18.7.12:64274 2012.05.23 11:16:01 LOG5[12517524:4113]: Service prdweb_in accepted connection from 10.18.7.11:61665 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=24 from 10.18.7.11:61681 2012.05.23 11:16:01 LOG7[12517524:4627]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:4627]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:4627]: Service prdweb_in accepted connection from 10.18.7.11:61681 2012.05.23 11:16:01 LOG6[12517524:1800]: SSL accepted: new session negotiated 2012.05.23 11:16:01 LOG6[12517524:1800]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:01 LOG6[12517524:1800]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:1800]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:1800]: Service prdweb_in connected remote server from 10.18.7.71:35492 2012.05.23 11:16:01 LOG7[12517524:1800]: Remote FD=25 initialized 2012.05.23 11:16:01 LOG7[12517524:1800]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=26 from 10.18.7.11:61689 2012.05.23 11:16:01 LOG7[12517524:4884]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:4884]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:4884]: Service prdweb_in accepted connection from 10.18.7.11:61689 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=27 from 10.18.7.12:64276 2012.05.23 11:16:01 LOG7[12517524:5141]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:5141]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:5141]: Service prdweb_in accepted connection from 10.18.7.12:64276 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=28 from 10.18.7.12:64278 2012.05.23 11:16:01 LOG7[12517524:5398]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:5398]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:5398]: Service prdweb_in accepted connection from 10.18.7.12:64278 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=29 from 10.18.7.12:64280 2012.05.23 11:16:01 LOG7[12517524:5655]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:5655]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:5655]: Service prdweb_in accepted connection from 10.18.7.12:64280 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=30 from 10.18.7.11:61680 2012.05.23 11:16:01 LOG7[12517524:5912]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:5912]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:5912]: Service prdweb_in accepted connection from 10.18.7.11:61680 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=31 from 10.18.7.12:64282 2012.05.23 11:16:01 LOG7[12517524:6169]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:6169]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:6169]: Service prdweb_in accepted connection from 10.18.7.12:64282 2012.05.23 11:16:01 LOG6[12517524:3085]: SSL accepted: new session negotiated 2012.05.23 11:16:01 LOG6[12517524:3085]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:01 LOG6[12517524:3085]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:3085]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:3085]: Service prdweb_in connected remote server from 10.18.7.71:52373 2012.05.23 11:16:01 LOG7[12517524:3085]: Remote FD=32 initialized 2012.05.23 11:16:01 LOG7[12517524:3085]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=33 from 10.18.7.11:61683 2012.05.23 11:16:01 LOG7[12517524:6426]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:6426]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:6426]: Service prdweb_in accepted connection from 10.18.7.11:61683 2012.05.23 11:16:01 LOG7[12517524:1]: Service prdweb_in accepted FD=34 from 10.18.7.12:64284 2012.05.23 11:16:01 LOG7[12517524:6683]: Service prdweb_in started 2012.05.23 11:16:01 LOG7[12517524:6683]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:01 LOG5[12517524:6683]: Service prdweb_in accepted connection from 10.18.7.12:64284 2012.05.23 11:16:01 LOG6[12517524:258]: SSL accepted: new session negotiated 2012.05.23 11:16:01 LOG6[12517524:258]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:01 LOG6[12517524:258]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:258]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:01 LOG5[12517524:258]: Service prdweb_in connected remote server from 10.18.7.71:33167 2012.05.23 11:16:01 LOG7[12517524:258]: Remote FD=35 initialized 2012.05.23 11:16:01 LOG7[12517524:258]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:4370]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:4370]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:4370]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:4370]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:4370]: Service prdweb_in connected remote server from 10.18.7.71:53609 2012.05.23 11:16:02 LOG7[12517524:4370]: Remote FD=36 initialized 2012.05.23 11:16:02 LOG7[12517524:4370]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:5398]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:5398]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:5398]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:5398]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:5398]: Service prdweb_in connected remote server from 10.18.7.71:40822 2012.05.23 11:16:02 LOG7[12517524:5398]: Remote FD=37 initialized 2012.05.23 11:16:02 LOG7[12517524:5398]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=38 from 10.18.7.11:61691 2012.05.23 11:16:02 LOG7[12517524:6940]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:6940]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:6940]: Service prdweb_in accepted connection from 10.18.7.11:61691 2012.05.23 11:16:02 LOG6[12517524:5655]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:5655]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:5655]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:5655]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:5655]: Service prdweb_in connected remote server from 10.18.7.71:53430 2012.05.23 11:16:02 LOG7[12517524:5655]: Remote FD=39 initialized 2012.05.23 11:16:02 LOG7[12517524:5655]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=40 from 10.18.7.12:64286 2012.05.23 11:16:02 LOG7[12517524:7197]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:7197]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:7197]: Service prdweb_in accepted connection from 10.18.7.12:64286 2012.05.23 11:16:02 LOG7[12517524:5655]: SSL closed on SSL_read 2012.05.23 11:16:02 LOG7[12517524:5655]: Sending socket write shutdown 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=41 from 10.18.7.11:61693 2012.05.23 11:16:02 LOG7[12517524:7454]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:7454]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:7454]: Service prdweb_in accepted connection from 10.18.7.11:61693 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=42 from 10.18.7.11:61695 2012.05.23 11:16:02 LOG7[12517524:7711]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:7711]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:7711]: Service prdweb_in accepted connection from 10.18.7.11:61695 2012.05.23 11:16:02 LOG6[12517524:515]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:515]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:515]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:515]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:515]: Service prdweb_in connected remote server from 10.18.7.71:50558 2012.05.23 11:16:02 LOG7[12517524:515]: Remote FD=43 initialized 2012.05.23 11:16:02 LOG7[12517524:515]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:1029]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:1029]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:1029]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:1029]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:1029]: Service prdweb_in connected remote server from 10.18.7.71:57414 2012.05.23 11:16:02 LOG7[12517524:1029]: Remote FD=44 initialized 2012.05.23 11:16:02 LOG7[12517524:1029]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=45 from 10.18.7.12:64288 2012.05.23 11:16:02 LOG7[12517524:7968]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:7968]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:7968]: Service prdweb_in accepted connection from 10.18.7.12:64288 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=46 from 10.18.7.12:64290 2012.05.23 11:16:02 LOG7[12517524:8225]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:8225]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:8225]: Service prdweb_in accepted connection from 10.18.7.12:64290 2012.05.23 11:16:02 LOG6[12517524:772]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:772]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:772]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:772]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:772]: Service prdweb_in connected remote server from 10.18.7.71:33957 2012.05.23 11:16:02 LOG7[12517524:772]: Remote FD=47 initialized 2012.05.23 11:16:02 LOG7[12517524:772]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:8225]: SSL accepted: previous session reused 2012.05.23 11:16:02 LOG6[12517524:8225]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:8225]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG6[12517524:7968]: SSL accepted: previous session reused 2012.05.23 11:16:02 LOG5[12517524:8225]: Service prdweb_in connected remote server from 10.18.7.71:36648 2012.05.23 11:16:02 LOG6[12517524:7968]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG7[12517524:8225]: Remote FD=48 initialized 2012.05.23 11:16:02 LOG7[12517524:8225]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG5[12517524:7968]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:7968]: Service prdweb_in connected remote server from 10.18.7.71:38529 2012.05.23 11:16:02 LOG7[12517524:7968]: Remote FD=49 initialized 2012.05.23 11:16:02 LOG7[12517524:7968]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=50 from 10.18.7.11:61697 2012.05.23 11:16:02 LOG7[12517524:8482]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:8482]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:8482]: Service prdweb_in accepted connection from 10.18.7.11:61697 2012.05.23 11:16:02 LOG6[12517524:3599]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:3599]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:3599]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:3599]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:3599]: Service prdweb_in connected remote server from 10.18.7.71:65426 2012.05.23 11:16:02 LOG7[12517524:3599]: Remote FD=51 initialized 2012.05.23 11:16:02 LOG7[12517524:3599]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:3856]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:3856]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:3856]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:3856]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:3856]: Service prdweb_in connected remote server from 10.18.7.71:51278 2012.05.23 11:16:02 LOG7[12517524:3856]: Remote FD=52 initialized 2012.05.23 11:16:02 LOG7[12517524:3856]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:3856]: SSL closed on SSL_read 2012.05.23 11:16:02 LOG7[12517524:3856]: Sending socket write shutdown 2012.05.23 11:16:02 LOG7[12517524:4370]: SSL closed on SSL_read 2012.05.23 11:16:02 LOG7[12517524:4370]: Sending socket write shutdown 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=53 from 10.18.7.11:61699 2012.05.23 11:16:02 LOG7[12517524:8739]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:8739]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:8739]: Service prdweb_in accepted connection from 10.18.7.11:61699 2012.05.23 11:16:02 LOG6[12517524:4113]: SSL accepted: new session negotiated 2012.05.23 11:16:02 LOG6[12517524:4113]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:02 LOG6[12517524:4113]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:4113]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:4113]: Service prdweb_in connected remote server from 10.18.7.71:33279 2012.05.23 11:16:02 LOG7[12517524:4113]: Remote FD=54 initialized 2012.05.23 11:16:02 LOG7[12517524:4113]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG6[12517524:8482]: SSL accepted: previous session reused 2012.05.23 11:16:02 LOG7[12517524:4113]: SSL closed on SSL_read 2012.05.23 11:16:02 LOG7[12517524:4113]: Sending socket write shutdown 2012.05.23 11:16:02 LOG6[12517524:8482]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:8482]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:02 LOG5[12517524:8482]: Service prdweb_in connected remote server from 10.18.7.71:50727 2012.05.23 11:16:02 LOG7[12517524:8482]: Remote FD=55 initialized 2012.05.23 11:16:02 LOG7[12517524:8482]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=56 from 10.18.7.11:61701 2012.05.23 11:16:02 LOG7[12517524:8996]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:8996]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:8996]: Service prdweb_in accepted connection from 10.18.7.11:61701 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=57 from 10.18.7.11:61703 2012.05.23 11:16:02 LOG7[12517524:9253]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:9253]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:9253]: Service prdweb_in accepted connection from 10.18.7.11:61703 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=58 from 10.18.7.11:61705 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=59 from 10.18.7.11:61707 2012.05.23 11:16:02 LOG7[12517524:9510]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:9510]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:9510]: Service prdweb_in accepted connection from 10.18.7.11:61705 2012.05.23 11:16:02 LOG7[12517524:9767]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:9767]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:9767]: Service prdweb_in accepted connection from 10.18.7.11:61707 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=60 from 10.18.7.11:61709 2012.05.23 11:16:02 LOG7[12517524:10024]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:10024]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:10024]: Service prdweb_in accepted connection from 10.18.7.11:61709 2012.05.23 11:16:02 LOG7[12517524:1]: Service prdweb_in accepted FD=61 from 10.18.7.12:64292 2012.05.23 11:16:02 LOG7[12517524:10281]: Service prdweb_in started 2012.05.23 11:16:02 LOG7[12517524:10281]: Option TCP_NODELAY set on local socket 2012.05.23 11:16:02 LOG5[12517524:10281]: Service prdweb_in accepted connection from 10.18.7.12:64292 2012.05.23 11:16:03 LOG6[12517524:5912]: SSL accepted: new session negotiated 2012.05.23 11:16:03 LOG6[12517524:5912]: Negotiated ciphers: DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 2012.05.23 11:16:03 LOG6[12517524:5912]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:5912]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:5912]: Service prdweb_in connected remote server from 10.18.7.71:59860 2012.05.23 11:16:03 LOG7[12517524:5912]: Remote FD=62 initialized 2012.05.23 11:16:03 LOG7[12517524:5912]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:8739]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:8739]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:8739]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:8739]: Service prdweb_in connected remote server from 10.18.7.71:33186 2012.05.23 11:16:03 LOG7[12517524:8739]: Remote FD=63 initialized 2012.05.23 11:16:03 LOG7[12517524:8739]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:8996]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:8996]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:8996]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:8996]: Service prdweb_in connected remote server from 10.18.7.71:46952 2012.05.23 11:16:03 LOG7[12517524:8996]: Remote FD=64 initialized 2012.05.23 11:16:03 LOG7[12517524:8996]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:9510]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:9510]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9510]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9510]: Service prdweb_in connected remote server from 10.18.7.71:48237 2012.05.23 11:16:03 LOG7[12517524:9510]: Remote FD=65 initialized 2012.05.23 11:16:03 LOG7[12517524:9510]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:9253]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:9253]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9253]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9253]: Service prdweb_in connected remote server from 10.18.7.71:54984 2012.05.23 11:16:03 LOG7[12517524:9253]: Remote FD=66 initialized 2012.05.23 11:16:03 LOG7[12517524:9253]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:9767]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:9767]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9767]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:9767]: Service prdweb_in connected remote server from 10.18.7.71:33305 2012.05.23 11:16:03 LOG7[12517524:9767]: Remote FD=67 initialized 2012.05.23 11:16:03 LOG7[12517524:9767]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:10024]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:10024]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:10024]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:10024]: Service prdweb_in connected remote server from 10.18.7.71:48123 2012.05.23 11:16:03 LOG6[12517524:7197]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:7197]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:7197]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:7197]: Service prdweb_in connected remote server from 10.18.7.71:38228 2012.05.23 11:16:03 LOG7[12517524:7197]: Remote FD=69 initialized 2012.05.23 11:16:03 LOG7[12517524:7197]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:6683]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:6683]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:6683]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:6683]: Service prdweb_in connected remote server from 10.18.7.71:51522 2012.05.23 11:16:03 LOG7[12517524:6683]: Remote FD=70 initialized 2012.05.23 11:16:03 LOG7[12517524:6683]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG6[12517524:10281]: SSL accepted: previous session reused 2012.05.23 11:16:03 LOG6[12517524:10281]: connect_blocking: connecting 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:10281]: connect_blocking: connected 10.18.7.71:8009 2012.05.23 11:16:03 LOG5[12517524:10281]: Service prdweb_in connected remote server from 10.18.7.71:51109 2012.05.23 11:16:03 LOG7[12517524:10281]: Remote FD=71 initialized 2012.05.23 11:16:03 LOG7[12517524:10281]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG7[12517524:10024]: Remote FD=68 initialized 2012.05.23 11:16:03 LOG7[12517524:1]: Dispatching signals from the signal pipe 2012.05.23 11:16:03 LOG7[12517524:10024]: Option TCP_NODELAY set on remote socket 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD 2012.05.23 11:16:03 LOG7[12517524:1]: Processing SIGCHLD

1 0

Re: [stunnel-users] Stunnel not working
by Ludolf Holzheid 21 May '12

21 May '12

On Mon, 2012-05-21 18:09:35 +1000, Peter Connor wrote: > > Hi > I tried to reload stunnel.conf but I received error message says "Stunnel server is down due to error. You need to exit and correct the problem. Click OK to see the error log window". So I looked in error log window, it says: > "Server is downReading configuration from file stunnel.confFIPS mode is enabledCompression not enabledSnagged 64 random bytes from C:/.rndWrote 1024 new random bytes to C:/.rndPRNG seeded successfullyLine 66: "connect secure.giganews.com:563": No '=' found > Server is down" > My operating system windows home XP. Any ideas how to fix this problem. Please help. Thanks > Peter Peter, I don't know why you are asking me and not the stunnel users list. Anyway, it seems to be what the error log says: Line 66 of your stunnel.conf is lacking an equal sign. HTH, Ludolf -- --------------------------------------------------------------- Ludolf Holzheid Tel: +49 621 339960 Bihl+Wiedemann GmbH Fax: +49 621 3392239 Floßwörthstraße 41 e-mail: lholzheid(a)bihl-wiedemann.de D-68199 Mannheim, Germany ---------------------------------------------------------------

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users