Because no data has been transmitted on the socket, the client didn't send an RST, and SO_KEEPALIVE wasn't set on the socket.
-Kyle H On Tue, Aug 5, 2008 at 10:19 AM, Du, Jinsong <[EMAIL PROTECTED]> wrote: > Hi Urjit, > > Unfortunately, I can't reach the computers with problem when running > the client software, I don't even know where they are. > > I just checked the server, and the stuck process is still there, > running more than two weeks: > 20743 jdu ./reg_mpt 14-18:43:57 > > #ls /proc/20743/fd/ -l > total 4 > lr-x------ 1 jdu jdu 64 2008-08-05 08:00 0 -> /dev/null > l-wx------ 1 jdu jdu 64 2008-08-05 08:00 1 -> /home/..... > l-wx------ 1 jdu jdu 64 2008-08-05 08:00 2 -> /home/..... > lrwx------ 1 jdu jdu 64 2008-08-05 08:00 4 -> socket:[210395564] > > After # lsof | grep 20743 > reg_mpt 20743 jdu 0r CHR 1,3 > 861 /dev/null > reg_mpt 20743 jdu 1w REG 9,3 32814994 > 6784 /home/..... > reg_mpt 20743 jdu 2w REG 9,3 32814994 > 6784 /home/..... > reg_mpt 20743 jdu 4u IPv4 210395564 > TCP xxx.xxx.net:17117->2x.9x.x0.x0.xxx.xxx.xxx.xxx:19048 (ESTABLISHED) > > I don't think that socket connection is still there, but why the Linux > is not aware of the broken socket connection? > > > On Sun, Aug 3, 2008 at 10:20 PM, Urjit Gokhale > <[EMAIL PROTECTED]> wrote: >> Looks like the server doesn't even get the Client hello message. >> Did you check the state of your client. Is it stuck in SSL_connect (it >> should be, I believe)? where is it stuck ? >> use s_client / s_server applications (comes with openssl.), if possible to >> figure out the issue. >> You may wish to use strace or like to figure out what calls your >> client/server make. This may hint towards the problem. >> >> Let us know what you get, and we might be able to help you further. >> >> ~ Urjit >> >> ----- Original Message ----- >> From: "Jinsong Du" <[EMAIL PROTECTED]> >> To: <openssl-users@openssl.org> >> Sent: Friday, August 01, 2008 4:07 AM >> Subject: SSL3_accept makes Server stuck >> >> >>> (I sent the following post through Google Group, but it seems not appear >> on >>> the maillist) >>> >>> Hi all, >>> >>> I have a simple server using blocked socket and OpenSSL, its only >>> function is for user registering an account. When an user connect to >>> this server, it spawns a child process to handle the request. I found >>> sometime child processes got stuck. >>> >>> I checked these malfunctioned process with gdb, and got the following >>> output: >>> >>> (gdb) bt >>> #0 0x00002b80dffd7352 in read () from /lib/libc.so.6 >>> #1 0x00002b80de4160a1 in BIO_new_socket () from >> /usr/lib/libcrypto.so.0.9.8 >>> #2 0x00002b80de41449f in BIO_read () from /usr/lib/libcrypto.so.0.9.8 >>> #3 0x00002b80de23d57d in ssl3_read_n () from /usr/lib/libssl.so.0.9.8 >>> #4 0x00002b80de23dabd in ssl3_read_bytes () from /usr/lib/libssl.so.0.9.8 >>> #5 0x00002b80de23e795 in ssl3_get_message () from >> /usr/lib/libssl.so.0.9.8 >>> #6 0x00002b80de2340aa in ssl3_check_client_hello () from >>> /usr/lib/libssl.so.0.9.8 >>> #7 0x00002b80de236855 in ssl3_accept () from /usr/lib/libssl.so.0.9.8 >>> #8 0x0000000000437945 in main () >>> >>> seems like during the function call of ssl3_accept(), server waits for >>> hand-shaking packet from user machine, but never get it. Or maybe the >>> user machine was cut off from Internet accidentally, so server never >>> got any hint, still wait for input. The socket is blocked one. >>> >>> Anyone has any idea about this situation? >>> >>> Thanks in advance. >>> ______________________________________________________________________ >>> OpenSSL Project http://www.openssl.org >>> User Support Mailing List openssl-users@openssl.org >>> Automated List Manager [EMAIL PROTECTED] >>> >> >> >> DISCLAIMER >> ========== >> This e-mail may contain privileged and confidential information which is the >> property of Persistent Systems Ltd. It is intended only for the use of the >> individual or entity to which it is addressed. If you are not the intended >> recipient, you are not authorized to read, retain, copy, print, distribute >> or use this message. If you have received this communication in error, >> please notify the sender and delete all copies of this message. Persistent >> Systems Ltd. does not accept any liability for virus infected mails. >> ______________________________________________________________________ >> OpenSSL Project http://www.openssl.org >> User Support Mailing List openssl-users@openssl.org >> Automated List Manager [EMAIL PROTECTED] >> > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
