Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 03 Jun 2003 14:37:15 -0600 From: Mark Paulus Subject: winsock error 10048 (errno 112) from ssh To: "cygwin AT cygwin DOT com" Message-id: <0HFX00D5GAM32E@pmismtp01.wcomnet.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit I am running CYGWIN_NT-5.0 WS117V0509 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin under Windows 2000 w/latest service pack. I have noticed this little odd behaviour for a while, and I have tried a couple of upgrades to ssh to see if that will alleviate the problem, but to no avail. When running ssh, I notice that after a variable amount of time, my ssh session locks up. I have also noticed this using scp with large transfers. The amount of time between locks can vary, but lately it seems to be happening more frequently. I have run an strace on the session, and I can include it if needed, but it's 4+ MB, so I won't unless asked for. However, here is the part that is wierd: 123 181642461 [main] ssh 3220 set_bits: me 0x100FFF60, testing fd 4 (/dev/tty0) 66 181642527 [main] ssh 3220 set_bits: ready 1 68 181642595 [main] ssh 3220 select_stuff::wait: gotone 1 60 181642655 [main] ssh 3220 select_stuff::wait: returning 0 75 181642730 [main] ssh 3220 select_stuff::cleanup: calling cleanup routines 60 181642790 [main] ssh 3220 socket_cleanup: si 0x10155A70 si->thread 0x610D1C20 67 181642857 [main] ssh 3220 socket_cleanup: connection to si->exitsock 0x3E45 91 181643448 [main] ssh 3220 __set_winsock_errno: socket_cleanup:1356 - winsock error 10048 -> errno 112 169 181643617 [main] ssh 3220 socket_cleanup: connect failed 89231 181732848 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0 226 181733074 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0 74 181733148 [ttyin] ssh 3220 fhandler_pty_master::accept_input: about to write 1 chars to slave 2624201 184357349 [ttyin] ssh 3220 fhandler_termios::line_edit: char ] 246 184357595 [ttyin] ssh 3220 fhandler_termios::line_edit: char ] 79 184357674 [ttyin] ssh 3220 fhandler_pty_master::accept_input: about to write 1 chars to slave 3306761 187664435 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0x1B 500 187664935 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0x1B 89 187665024 [ttyin] ssh 3220 fhandler_pty_master::accept_input: about to write 1 chars to slave 207901 187872925 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0x1B 255 187873180 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0x1B 137 187873317 [ttyin] ssh 3220 fhandler_pty_master::accept_input: about to write 1 chars to slave 185715 188059032 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0x1B 890 188059922 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0x1B 107 188060029 [ttyin] ssh 3220 fhandler_pty_master::accept_input: about to write 1 chars to slave 169991 188230020 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0x1B 255 188230275 [ttyin] ssh 3220 fhandler_termios::line_edit: char 0x1B 101 188230376 [ttyin] ssh 3220 fhandler_pty_master::accept_input: about to write 1 chars to slave up there at the line headed 91, there is the winsock error 10048, which I don't understand. The pattern of the file shows that the next file should be either fhandler_termios::line_edit: char0x1B or select_stuff::wait: woke up. But I don't get either. just a hard lock up. Has anyone else seen this, or have any ideas as to why this might be happening?? Thanks. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/