delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/04/28/03:07:20

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <4815777F.3060005@cwilson.fastmail.fm>
Date: Mon, 28 Apr 2008 03:06:39 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: inetutils 1.5 / ftpd problem: 426 Data connection: No buffer space available.
References: <3ee066b40804272035p45746b2bwc5bebd0252d92426 AT mail DOT gmail DOT com>
In-Reply-To: <3ee066b40804272035p45746b2bwc5bebd0252d92426@mail.gmail.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

antony baxter wrote:

> ftp> get BCUpdateXP.exe
> 'EPSV': command not understood.
> local: BCUpdateXP.exe remote: BCUpdateXP.exe
> 227 Entering Passive Mode (192,168,1,99,4,110)
> 150 Opening BINARY mode data connection for 'BCUpdateXP.exe' (226020663 bytes).
>   0% |
>                        |     0       0.00 KB/s    --:-- ETA
> 426 Data connection: No buffer space available.

This means that very first call to the cygwin1.dll function 'write(int 
networkSocketFd, const void *buf, size_t nbyte)' failed for some reason: 
ENOBUFS is not one of the valid error codes for write(), so it's set to 
that by something internal to cygwin's implementation of write().

e.g. smells like a cygwin (or windows) bug -- cygwin is unable to create 
a Mutex or an Event for managing the socket communications (e.g. 
CreateMutex or CreateEvent in net.cc: (handler_socket::init_events) failed)

I'm wondering if you have different versions of cygwin on the two 
machines -- not that it should matter, but if so then the answer may be 
simple.  Can you send -- as attachments, not cut-n-paste -- the result 
of 'cygcheck -s -v -r' on each of the two cygwin machines?

--
Chuck


--
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/

- Raw text -


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