This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: OpenSSH 2.3.0p1 Win98 listen: No buffer space available; the socket cannot be connected
- To: "Corinna Vinschen" <cygwin at cygwin dot com>
- Subject: RE: OpenSSH 2.3.0p1 Win98 listen: No buffer space available; the socket cannot be connected
- From: "Dr. Carsten Bormann" <cabo at tzi dot org>
- Date: Thu, 28 Dec 2000 01:07:14 +0100
> > | On Sunday 17 December 2000 09:12, Dr. Carsten Bormann wrote:
> > | > I assume you run 1.1.6?
> > | > This looks very similar to the problem I have reported under the
> > | > thread "OpenSSH + 1.1.6 strangely wedges W98SE networking".
> > | > There seems to be a resource leak somewhere; as I reported I can
> > | > get about 42 SSH tunnels opened before things wedge.
> > |
> > | Unfortunately you forgot to mention that the problem is solved in
> > | the developer snapshots.
> >
> > Exellent. I assume this is the SSH p1-1 version that I loaded with
> > setup.exe? Hm. tar is on latest/openSSH directory,
>
> This isn't related to OpenSSH. It's changed in the developers
> snapshots of the Cygwin DLL itself. It's not in latest but will be
> part of the 1.1.7 version when it will be released (no date yet).
Unfortunately, I can report that the repeated tunnelling problem is NOT
fixed in 1.1.7.
I'm attaching the output of cygcheck -svr.
I also have a 6 MB strace output which I'm not sure I should attach here
(and before that I would have to delete the passwords and all... very
tedious to find).
The place where I first see a symptom looks like this (this is in the 20th
tunnel on this ssh; I didn't get a 21st tunnel -- there was another ssh
running in parallel, though, with the same number of tunnels opening and
closing, so I probably got a total of 38 tunnels opened and closed before
this happened on the 39th):
201 -198454162 [main] ssh 711307 select_stuff::poll: returning 1
189 -198453973 [main] ssh 711307 select_stuff::~select_stuff: calling
cleanup routines
186 -198453787 [main] ssh 711307 socket_cleanup: si 0x46A27D8 si->thread
0x150
188 -198453599 [main] ssh 711307 socket_cleanup: connection to
si->exitsock 0x148
438 -198453161 [main] ssh 711307 __set_winsock_errno:
socket_cleanup:1287 - 10055 (WSAENOBUFS) -> 105
202 -198452959 [main] ssh 711307 socket_cleanup: connect failed
Of course, I have no idea whether that is any hint.
Gruesse, Carsten
a
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple