SFTP LS -L returns different view between 2 nodes

[CharlieCalhoun]

I have two 8.3 OpenVMS nodes. 1 production and the other development. Production is running TCPIP 5.6 ECO2 and development is running 5.6 without any ECO's.

When I issue the same command from each system, production returns the results as expected, development does not.

On production, the directory list appears similar to the following:
sftp> ls -l
drwxrwxrwx 1 SVC_DUB 1536 19968 Feb 12 8:49 INBOX.DIR;1/
drwxrwxrwx 1 SVC_DUB 1536 512 Feb 17 17:15 OUTBOX.DIR;1/
drwxr-xr-x 1 SVC_DUB 1536 512 Jan 18 2008 SSH2.DIR;1/
-rwxrwxr-x 1 SVC_DUB 1536 1164 Dec 29 2008 TCPIP$FTP_SERVER.LOG;3*
-rwxrwxr-x 1 SVC_DUB 1536 1164 Mar 31 2009 TCPIP$FTP_SERVER.LOG;4*
-rwxrwxr-x 1 SVC_DUB 1536 1164 Feb 3 16:38 TCPIP$FTP_SERVER.LOG;5*
-rwxrwxr-x 1 SVC_DUB 1536 1164 Feb 4 14:47 TCPIP$FTP_SERVER.LOG;6*
-rwxrwxr-x 1 SVC_DUB 1536 1164 Feb 17 16:41 TCPIP$FTP_SERVER.LOG;7*
-rwxrwxr-x 1 SVC_DUB 1536 112 Jan 5 15:39 TCPIP$SSH_SFTP-SERVER2.LOG;1*
-rwxrwxr-x 1 SVC_DUB 1536 6656 Jan 6 21:22 TCPIP$SSH_SFTP-SERVER2.LOG;2*

On development, the directory list appears similar to the following:
sftp> ls -l
INBOX.DIR;1
OUTBOX.DIR;1
SSH2.DIR;1
TCPIP$FTP_SERVER.LOG;1
TCPIP$FTP_SERVER.LOG;2
TCPIP$FTP_SERVER.LOG;3
TCPIP$FTP_SERVER.LOG;4
TCPIP$FTP_SERVER.LOG;5
TCPIP$FTP_SERVER.LOG;6
TCPIP$SSH_SFTP-SERVER2.LOG;1

I've examined the ssh2_config. and sshd2_config. files between the two nodes and they are identical (default).

Surely any symbol definition in the login.com would have no effect on this procedure. There is a symbol definition for the account on the prod side, but not the dev side.

Am I finding something that was resolved in ECO2? Any other reason why my development box isn't returning the detailed list?

Thanks,
Charlie

[RBrown_1]

>>>>Surely any symbol definition in the login.com would have no effect on this procedure. There is a symbol definition for the account on the prod side, but not the dev side.<<<<

I guess we need to see the symbol definition.

>>>>
On production, the directory list appears similar to the following:
sftp> ls -l
<<<<

What is this? Is this some unspecified ssh client asking production for ls -l? Or production asking some unspecified ssh server for ls -l? Same question for your other example.

And regardless of whether the unspecified entity is client or server, what is it?

[Steven Schweda]

Sure looks as if someone doesn't understand
"-l".

> I've examined the ssh2_config. and
> sshd2_config. files [...]

All of them? System-wide and personal? A
user can have a configuration file in his
own SYS$LOGIN:[.SSH2] directory.

Time to throw a "-v" (or "-vv", or more) onto
the SFTP command(s)?

> Production is running TCPIP 5.6 ECO2 and
> development is running 5.6 without any
> ECO's.

TCPIP is normally lame enough _with_ the
latest ECO. Around here:

alp $ tcpip show version

HP TCP/IP Services for OpenVMS Alpha Version V5.6 - ECO 4
on a COMPAQ Professional Workstation XP1000 running OpenVMS V8.3

I'd certainly try it again with something
newer than _no_ ECO.

[CharlieCalhoun]

The symbol definition is

$ dir:=="direc/width=file:75/date=cr"

I defined it on the development system where it isn't returning expected results and no change in the results were experienced.

<<>>

The VMS boxes are the server side. The connection is initiated by a client. The customer is coming from HP-UX, but the same behavior is seen using the VMS sftp client commands as well going from one VMS box to another.

<<>>
The process is trying to examine the file size of the files in the directory and bypass 0 block files in the automated process using sftp.

<<<
> I've examined the ssh2_config. and
> sshd2_config. files [...]

All of them? System-wide and personal? A
user can have a configuration file in his
own SYS$LOGIN:[.SSH2] directory.
>>>

Yes, all of them. I looked at the system files and there are no config files in the user's own [.ssh2] directory.

I threw in a -vv and here are the results.

sftp> ls -l
SshFCRecurse/SSHFC_RECURSE.C:398: File is "raw", and it needs to be parsed.
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
INBOX.DIR;1
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
OUTBOX.DIR;1
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
SSH2.DIR;1
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$FTP_SERVER.LOG;8
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$FTP_SERVER.LOG;7
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$FTP_SERVER.LOG;6
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$FTP_SERVER.LOG;5
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$FTP_SERVER.LOG;4
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$FTP_SERVER.LOG;3
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$FTP_SERVER.LOG;2
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$FTP_SERVER.LOG;1
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
TCPIP$SSH_SFTP-SERVER2.LOG;1
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connection
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection
SshFCRecurse/SSHFC_RECURSE.C:331: Received error `EOF' (1).
sftp> debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 2 to connec
tion
debug: Ssh2Transport/TRCOMMON.C:1105: Sending packet with type 94 to connection

[CharlieCalhoun]

This is what I get for trying to get a quick answer. Had I examined the release notes for the ECO, I would have found my answer.

---------------------------------------------------------------------------
Corrections for HP TCP/IP Services V5.6 SSH, SCP and SFTP Components
---------------------------------------------------------------------------
ECO 1 updates
-------------
Alpha and IA64

Problem:

The "ls -l" command in SFTP was not working.

Deliverables:

All SSH images

Reference:

PTR 70-5-2758 (part 2)

I loaded the ECO and it fixed it, as expected.