HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

FTP-PROXY and Access Violation

 
Russ Carraro
Regular Advisor

FTP-PROXY and Access Violation

Customer replaced TCP/IP software (Pathway) with UCX 4.2 - ECO 5 on a VAX 7710 running OpenVMS 7.1. FTP commands
$ ftp
verbose on
open ftp-proxy
2410ftpupload@136.205.6.184
password
.
.
.

used to work but now return

ACED ON OR SENT OVER THIS SYSTEM MAY BE MONITORED. USE OF THI
230 User 2410ftpupload logged in.
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=52502019, PC
=0004FD12, PSL=03C00000

Improperly handled condition, image exit forced.

Signal arguments Stack contents

Number = 00000005 00000000
Name = 0000000C 00000000
00000001 00000000
52502019 00000000
0004FD12 00000000
03C00000 00000000
00000000
00000000
00000000
00000000

Register dump

R0 = 52502045 R1 = 000047A2 R2 = 00002200 R3 = 00002200
R4 = 00000001 R5 = 7FFE5EBC R6 = 00000001 R7 = 00000001
R8 = 7FFECA48 R9 = 7FFECC50 R10= 7FFED7D4 R11= 7FFE2BDC
AP = 7FE3B340 FP = 7FE3B300 SP = 7FE3B37C PC = 0004FD12
PSL= 03C00000

Any thoughts on what the problem is and how to avoid it?
6 REPLIES
Steven Schweda
Honored Contributor

Re: FTP-PROXY and Access Violation

Go back to PathWay?

"SHOW SYMBOL FTP"? Any chance that you're
still running the PathWay FTP client?

"SHOW LOGICAL TWG$TCP"? It shouldn't be
defined now. (Nor "TWG$*", for that matter.)
Richard Whalen
Honored Contributor

Re: FTP-PROXY and Access Violation

Does it work to other IP addresses?
If so, I would guess that 136.205.6.184 is sending a 230 response that your FTP client can not handle.
John Gillings
Honored Contributor

Re: FTP-PROXY and Access Violation

Russ,

As you're no doubt aware, UCX is very old and well outside its support window.

That said, it's probably worth making sure you're up to date with whatever patches are available. For old stuff see http://ftp.hp.com.au/

I'm curious about the apparently chopped up message:

"ACED ON OR SENT OVER THIS SYSTEM MAY BE MONITORED. USE OF THI"

Is that a cut and paste artifact or verbatim? I assume it's a chunk of SYS$ANNOUNCE or SYS$WELCOME on the target system?

I also note that the ACCVIO address looks like a fragment of ASCII text ". PR" - could this also be a part of the same message?

If possible, it might be interesting to see what happens if the message is removed, or perhaps reduced in length.

On my systems, the ANONYMOUS account is set to:

DISWELCOME, DISNEWMAIL, DISMAIL, DISREPORT

This might be a clue telling us that the FTP client doesn't like extra messages on login. Perhaps you could get the ftpupload account on the target system set similarly?
A crucible of informative mistakes
Russ Carraro
Regular Advisor

Re: FTP-PROXY and Access Violation

The message is verbatim. I tried the FTP from a Vax/Alpha cluster and found out that it works from the Alpha but fails from the Vax. Cluster has a common SYSUAF.
Volker Halle
Honored Contributor

Re: FTP-PROXY and Access Violation

Russ,

note that the contents of R0 shown in the register output translates to an ASCII string 'E PR'.

Please try to connect to this FTP-proxy from some other node or operating system and/or try to get the full string of this message shown. Maybe it contains a substring 'E PR'. This would indicate, that the VAX UCX V4.2 ECO 5 (this is the most recent patch) FTP client cannot handle such a long message.

Maybe you can reduce the message size on your FTP-proxy server to work around this limitation.

Volker.
Russ Carraro
Regular Advisor

Re: FTP-PROXY and Access Violation

Works from Alphas so I had user log onto an Alpha instead of a Vax (mixed architecture cluster).