Error Detected On Socket Read File Descriptor Broken Pipe 32
pipe (32) Next message: [stunnel-users] [PATCH]: Debugging output Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] I wrote: > On Sat, 27 Aug 2011 06:03:24 -0400, Alex Magee wrote: >> Error detected on socket (read) file descriptor: Broken pipe (32) > > I have finally fixed this issue. Please try: > ftp://ftp.stunnel.org/stunnel/stunnel-4.47b1-installer.exe What I meant was: ftp://ftp.stunnel.org/stunnel/stunnel-4.47b1.tar.gz The problem was actually Unix-specific. 8-) Mike Previous message: [stunnel-users] Error detected on socket (read) file descriptor: Broken pipe (32) Next message: [stunnel-users] [PATCH]: Debugging output Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the stunnel-users mailing list
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
and receiving ACK prior to this glitch. I am on Ubuntu 12.04 LTS using stunnel 4.50. appsadmin@MIRTHTEST:/etc/stunnel.d$ http://www.serverphorums.com/read.php?10,364892 sudo tail -f /var/log/stunnel_mirth.log 2013.06.21 17:28:03 LOG7[30980:3077569344]: Service hl7_client prod finished (1 left) 2013.06.21 17:28:03 LOG7[30980:3077569344]: str_stats: error detected 0 block(s), 0 data byte(s), 0 control byte(s) 2013.06.21 17:28:14 LOG6[30980:3073227584]: SSL connected: previous session reused 2013.06.21 17:28:14 LOG7[30980:3073227584]: Socket closed on read 2013.06.21 17:28:14 LOG7[30980:3073227584]: Sending SSL write shutdown 2013.06.21 17:28:14 LOG6[30980:3073227584]: SSL_shutdown successfully sent error detected on close_notify 2013.06.21 17:28:24 LOG5[30980:3073227584]: Error detected on socket (read) file descriptor: Broken pipe (32) 2013.06.21 17:28:24 LOG5[30980:3073227584]: Connection reset: 661 bytes sent to SSL, 124 bytes sent to socket 2013.06.21 17:28:24 LOG7[30980:3073227584]: Service hl7_client prod finished (0 left) 2013.06.21 17:28:24 LOG7[30980:3073227584]: str_stats: 0 block(s), 0 data byte(s), 0 control byte(s) rmcwilli _______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users Previous message View by thread View by date Next message Reply via email to Search the site The Mail Archive home stunnel-users - all messages stunnel-users - about the list Expand Previous message Next message The Mail Archive home Add your mailing list FAQ Support Privacy A16BFB22F82A9B4E970734B2677050FB44C63E@EXCH-MBX.srhc.net
18, 2011 12:50PM Dear All , I am trying to setup a load balancing under webmail on my test servers. Here is my setup details :-- Total server are 3 servers. i.e ( 2 backend webmail server and 1 front server ) . There is no firewall rule between any servers. On one server I have installed haproxy-1.4.15.tar.gz + stunnel-4.41.tar.gz with http:// and https:// Another two servers are installed with squirrelmail . i.e End user browser --> stunnel --> haproxy ---> apache *my problem*:-- ========== 1) When I access the webmail by https://webmail.domain.com and compose any email and click on send button , the page is getting expire and I am getting log out from webmail. In Firefox there is no error on browser , where as in internet explorer I am getting below error with popup window :-- *Error Popup* :-- ============ "do you want to view only the webpage content that was deliver securely. This webpage contain the content that will not be delivered using the secure HTTPS connection, which could compromise the security of entire webpage." I found the solution for this on below link and its works from "Internet Explorer" but not for others browser. http://pariswells.com/blog/tag/this-webpage-contains-content-that-will-not-be-delivered-using-a-secure-https-connection Where as if I check with http://webmail.domain.com , then the mail compose and send work properly. * *If check the internal webmail server with same certificate , then compose email and send works properly. I also checked by replacing the stunnel with nginx but the problem is remain same. i.e problem come when request goes vai haproxy *My quires* :-- ======= 1) what correct configuration is require from server side , so that at end user's browser there will be no change. ? and will work for all browser ? 2|) Why such POPUP come ? Do I require any special type of SSL certificate.? 3) How do I achieve this with haproxy. 4) I checked the logs in debug mode , I am getting "Aug 18 15: