ssh stack dumps

[Brian Schenkenberger]

OpenVMS V8.3 TCPIP V5.6

ssh -?
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000000, PC=00000000000EA240, PS=0000001B

Improperly handled condition, image exit forced.
Signal arguments: Number = 0000000000000005
Name = 000000000000000C
0000000000000000
0000000000000000
00000000000EA240
000000000000001B

Register dump:
R0 = 0000000000000000 R1 = 0000000000000014 R2 = 0000000000015E80
R3 = 0000000000000000 R4 = 0000000000010440 R5 = 000000000005AA40
R6 = 0000000000000001 R7 = 000000000005AA40 R8 = 0000000000000001
R9 = 0000000000000000 R10 = 0000000000000001 R11 = 0000000000000000
R12 = 0000000000000001 R13 = 00000000004E8708 R14 = 0000000000519958
R15 = 0000000000519B00 R16 = 0000000000000000 R17 = 00000000000615E0
R18 = 0000000000060C70 R19 = 0000000000000CF4 R20 = 0000000000015C78
R21 = 0000000000000000 R22 = 0000000000519C42 R23 = 0000000000000019
R24 = 0000000000021999 R25 = 0000000000000001 R26 = 00000000000FD918
R27 = 0000000000013EA0 R28 = 0000000000000000 R29 = 000000007AE26D50
SP = 000000007AE26D40 PC = 00000000000EA240 PS = 000000000000001B

[Dean McGorrill]

hi Brian,
if its installed correct it looks like
a trouble report should be issued to hp.

Dean

[Craig A Berry]

Interesting. I get the following:

$ tcpip show vers

HP TCP/IP Services for OpenVMS Alpha Version V5.6
on a COMPAQ Professional Workstation XP1000 running OpenVMS V8.3
$ tcpip show serv ssh/full

Service: SSH
State: Enabled
Port: 22 Protocol: TCP Address: 0.0.0.0
Inactivity: 5 User_name: TCPIP$SSH Process: TCPIP$SSH
Limit: 10000 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$SSH_RUN.COM
Flags: Listen IPv6

Socket Opts: Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: TCPIP$SSH_DEVICE:[TCPIP$SSH]TCPIP$SSH_RUN.LOG

Security
Reject msg: TCPIP SSH Connection refused

Accept host: 0.0.0.0
Accept netw: 0.0.0.0

$ ssh -?
dsa0:[sys0.syscommon.][sysexe]tcpip$ssh_ssh2.exe: FATAL: Unknown option -?


%TCPIP-F-SSH_FATAL, non-specific fatal error condition

[Brian Schenkenberger]

To put closure to this, the problem is documented in the TCPIP056.RELEASE_NOTES; albeit, the stack dump's footprint is completely different.

On this system, the SYSTEM account (UIC:[1,4]) and the SYSTEM identifier (UIC:[210,4]) did not match. This is called out as being problematic with ssh in the release notes. I fixed the SYSTEM identifier with:

$ MCR AUTHORIZE MODIFY/IDENTIFIER SYSTEM/VLUE=UIC=[1,4]

[Brian Schenkenberger]

BTW, once again my issue was solved in comp.os.vms. This forum would be much more useful if I didn't first have to go digging through old log books to find the cryptic username and then password which I can't ever remember because I'm forced to use a stupid 6-8 characters with a numeric.

[Robert Brooks_1]

BTW, once again my issue was solved in comp.os.vms. This forum would be much more useful if I didn't first have to go digging through old log books to find the cryptic username and then password which I can't ever remember because I'm forced to use a stupid 6-8 characters with a numeric.

---

I'm pretty sure you can log in with an email address instead of that nonsensical username.

-- Rob

[Doug Phillips]

Your forum email address works, but it's also case sensitive.

You can also search the forum for your name, find one of your post and click on your name. Then, if you look at that page's URL you'll see userId=CAnumber.

Log in and click "My Profile", then click "view or modify forums profile" to see your forum email address.

Use either the CA# or your email address.