Operating System - OpenVMS
1748199 Members
2711 Online
108759 Solutions
New Discussion юеВ

Re: Cant run SSH OpenVMS 8.4 TCPIP 5.7 ECO2

 
SOLVED
Go to solution
Arne Korpas
Advisor

Re: Cant run SSH OpenVMS 8.4 TCPIP 5.7 ECO2

I submitted a case to HP and I got the DECC$SHR patch from them, installed it and everything is ok now :)
Thank you all for your engagement in this issue.

Cheers /Arne
Hoff
Honored Contributor

Re: Cant run SSH OpenVMS 8.4 TCPIP 5.7 ECO2

Um, so would somebody mind elaborating on the "known problem" here?

And which versions and architectures are involved other than V8.4?

That the C library DECC$SHR can apparently trigger ACCVIO access violation errors (in a VMS security component!) when the system disk is shadowed covers a whole lot of territory and a whole lot of servers.
Arne Korpas
Advisor

Re: Cant run SSH OpenVMS 8.4 TCPIP 5.7 ECO2

Here's the note from HP

This is a know issue after applying VMS84I_UPDATE-V0400 to OpenVMS with a shadows systemdisk
Article extract:
Problem description:
After installing Update Kit V4 in OpenVMS 8.4 Integrity, SSH will stop working if running TCPIP V5.7 ECO1.
Typing the SSH log file shows:

TCPIP$SSH_DEVICE:[TCPIP$SSH]TCPIP$SSH_RUN.LOG

Fri 08 18:09:27 WARNING: ssh_privkey_read from ssh2/hostkey failed.
Fri 08 18:09:27 ERROR: FATAL ERROR: Unable to load any hostkeys
dsa0:[sys0.syscommon.][sysexe]tcpip$ssh_sshd2.exe[320]: FATAL: Unable to load any hostkeys
%TCPIP-F-SSH_FATAL, non-specific fatal error condition
TCPIP$SSH job terminated at 8-OCT-2010 18:09:27.83
Solution
This issue was elevated to OpenVMS Engineering and a fix has been provided.
Engineering analysis:
We created a dump file and our analysis revealed that a crash was occurring in OpenVMS CRTL DECC$SHR.EXEin stat() API routine. OpenVMS CRTL tries to find the "$ " character in a loop to retrieve the node name from the disk name, however for a shadow set device, this logic would fail because the shadow set device naming convention does not include a node name in the "shadow set device name " (ssdn), and as a node name is not present at all in a ssdn it would never find the terminating "$ ". Hence the loop would not end and corruption would occur.
Solution description:
We found that the algorithm to retrieve the node name from the disk-name did not have a check for the boundary condition. This would cause the loop to corrupt the data and hence the crash.
Duncan Morris
Honored Contributor

Re: Cant run SSH OpenVMS 8.4 TCPIP 5.7 ECO2

Hoff,

looks like it is covered in the latest ACRTL for itanium 8.31H1

5.2.7 Stat() ACCVIO.s for a file on Shadow Set

5.2.7.1 Problem Description:

The algorithm to obtain the st_dev for a file on Shadow
Set device (when the ALLOCATION Class of the device is
ZERO) does not check for the boundary condition resulting
in ACCVIO.

Images Affected:

- [SYSLIB]DECC$SHR.EXE

Also present for Alpha 8.3 and I64 8.3 in the latest ACRTL updates.

Presumably, the corresponding updates are in the pipeline for 8.4.
Hoff
Honored Contributor

Re: Cant run SSH OpenVMS 8.4 TCPIP 5.7 ECO2

So stat() is broken.

Interesting.

This bug may well hit any device that doesn't use an allocation class prefix or the SCSNODE prefix, based on reading the replies.

DSs are only one example of that ilk.

A stat against LD, too, would probably break.

Somebody directly and incorrectly parsed a device name somewhere deep in the RTL, and got caught. Ah, well.