delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/12/20/20:54:19

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <003d01c2a884$4bf48260$2180a8c0@toshiba>
From: "Campbell Fethers" <cf AT cannex DOT com DOT au>
To: <cygwin AT cygwin DOT com>
Subject: Sshd: Resource temporarily unavailable
Date: Sat, 21 Dec 2002 10:02:42 +1000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Scanned-By: MIMEDefang 1.4 (www dot roaringpenguin dot com slash mimedefang)

------=_NextPart_000_0038_01C2A8D8.19E89370
Content-Type: text/plain; name="WARNING.TXT"
Content-Disposition: inline; filename="WARNING.TXT"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Content-Description: WARNING.TXT

WARNING: This e-mail has been altered by MIMEDefang.  Following this
paragraph are indications of the actual changes made.  For more
information about your site's MIMEDefang policy, contact
mimedefang AT cannex DOT com DOT au.  For more information about MIMEDefang, see:

                  http://www.roaringpenguin.com/mimedefang/

An attachment named sshd.log was removed from this document as it
constituted a security hazard.  If you require this document, please contact
the sender and arrange an alternate means of receiving it.
Alternatively zip your attachment and resend.

An attachment named ssh.log was removed from this document as it
constituted a security hazard.  If you require this document, please contact
the sender and arrange an alternate means of receiving it.
Alternatively zip your attachment and resend.

An attachment named cygcheck.log was removed from this document as it
constituted a security hazard.  If you require this document, please contact
the sender and arrange an alternate means of receiving it.
Alternatively zip your attachment and resend.


------=_NextPart_000_0038_01C2A8D8.19E89370
Content-Type: multipart/mixed; boundary="----------=_1040429063-11660-0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)

This is a multi-part message in MIME format...

------------=_1040429063-11660-0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

W2kpro, sp2
Appears to close the socket immediately after connection.
ssh -v reports "Read from socket failed: Connection aborted"

A log of sshd (thanks to Max's instructions) shows
"Read from socket failed: Resource temporarily unavailable"

Tried deleting cygwin installation and reinstalling. Results attached.

Also tried backdating OpenSSL lib. Still didn't work :-( which suggests that
something else has changed on my system. Likely.

A search of microsoft.com for "Resource temporarily unavailable" yields:
WSAEWOULDBLOCK (10035)
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be
completed immediately, for example recv when no data is queued to be read
from the socket. It is a nonfatal error, and the operation should be retried
later. It is normal for WSAEWOULDBLOCK to be reported as the result from
calling connect on a nonblocking SOCK_STREAM socket, since some time must
elapse for the connection to be established.

The only solution found so far is to completely reinstall W2k,
http://archive.erdelynet.com/ssh-l/2001-05/msg00003.php.

Spurious WSAEWOULDBLOCKs seem to have caused problems when closing sockets
http://www.cygwin.com/ml/cygwin-developers/2001-10/msg00212.html, and
also problems with postgres.

My theory, for what it is worth, is that windows is sending an event saying
that there is something ready to read from a socket, but returns
WSAEWOULDBLOCK when the program reads the socket. I think I read somewhere
in a Microsoft page that programs have to be able to cope with this
situation. It is likely a timing related.

HTH.

Regards
Campbell.


------------=_1040429063-11660-0--


------=_NextPart_000_0038_01C2A8D8.19E89370
Content-Type: text/plain; charset=us-ascii

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/
------=_NextPart_000_0038_01C2A8D8.19E89370--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019