delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/01/10/12:33:11

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: SSH client hang running uncompressed tar on various servers
Date: Mon, 10 Jan 2005 09:32:59 -0800
Message-ID: <D790136A12A3CE4A952A873DE8B0CEE41EA245@aruba-server.arubanetworks.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From: "Dave Wang" <dave AT arubanetworks DOT com>
To: "Brett Porter" <brett DOT porter AT gmail DOT com>, <cygwin AT cygwin DOT com>
Note-from-DJ: This may be spam
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j0AHX9hI011028

Brett,

Just a few quick thoughts come to mind.

-- Have you tried other ssh clients (putty)?
-- have you tried logging into the terminal, and then executing the
command there?
-- if logging into the terminal and executing the command also locks up
on lots of output, try reducing the terminal size to 3 lines, and piping
the output to the "less" command.  If this works, then it may be mtu
issues where a router is dropping ip fragments.

The third comment is a long shot, but I've actually experienced it
before.

-dave

-----Original Message-----
From: Brett Porter [mailto:brett DOT porter AT gmail DOT com] 
Sent: Monday, January 10, 2005 3:09 AM
To: cygwin AT cygwin DOT com
Subject: SSH client hang running uncompressed tar on various servers

Hi,

I'm having a problem with my SSH client hanging executing a remote
command extracting an uncompressed tar. This occurs on different
servers (FreeBSD, localhost Cygwin SSHD, RHL9), though they are all
SSH2 and I've using the same private DSA key.

Given this, it isn't the tar executable (though I turned off my virus
scanner just in case). I know this has worked in the past, though I'm
not sure at what point it may have stopped. It happens on both my
machines, and I've had reports from other cygwin users using Maven.

Does anyone have any ideas, or seen it happen? I've had trouble
finding anything beyond virus scanners in the archives and
documentation.

The SSH version:
OpenSSH_3.9p1, OpenSSL 0.9.7e 25 Oct 2004

 1114k 2004/11/10 C:\cygwin\bin\cygwin1.dll
    Cygwin DLL version info:
        DLL version: 1.5.12

(I'm at the latest of what's installed - if there is any more info I
could provide, please let me know).

The exact command run is:
ssh -vvv -l brett www.apache.org 'cd /home/brett/test-dir;tar xf
maven-site-
plugin-1.6-SNAPSHOT-site.tar'"/>

The output with -vvv is:
    [exec] debug1: Authentication succeeded (publickey).
    [exec] debug2: fd 4 setting O_NONBLOCK
    [exec] debug2: fd 5 setting O_NONBLOCK
    [exec] debug2: fd 6 setting O_NONBLOCK
    [exec] debug1: channel 0: new [client-session]
    [exec] debug3: ssh_session2_open: channel_new: 0
    [exec] debug2: channel 0: send open
    [exec] debug1: Entering interactive session.
    [exec] debug2: callback start
    [exec] debug2: client_session2_setup: id 0
    [exec] debug1: Sending command: cd /home/brett/test-dir;tar xf
maven-site-
plugin-1.6-SNAPSHOT-site.tar
    [exec] debug2: channel 0: request exec confirm 0
    [exec] debug2: callback done
    [exec] debug2: channel 0: open confirm rwindow 0 rmax 32768
    [exec] debug2: channel 0: rcvd adjust 131072
    [exec] debug1: client_input_channel_req: channel 0 rtype exit-status
reply 0

    [exec] debug2: channel 0: rcvd eof
    [exec] debug2: channel 0: output open -> drain
    [exec] debug2: channel 0: rcvd close
    [exec] debug2: channel 0: close_read
    [exec] debug2: channel 0: input open -> closed
    [exec] debug3: channel 0: will not send data after close
^^^^^^^^^^^^^^
this is where is always stops. I have to kill the process - Ctrl-C
doesn't work.

BTW, I'm back to the cygwin list after a long time away - it's been so
stable for years. Great job all - I couldn't work day to day on
Windows without it :)

Cheers,
Brett

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