ftp failed connection

[Rupert_1]

Hi,

The error message is below;

%UCX-I-FTP_SESCON, FTPD: Session connection from TPFC01 at 26-SEP-2003 15:36:50.86

%UCX-I-FTP_NODE, Client Nodename : TPFC01
%UCX-I-FTP_USER, Username : PMEGA
%UCX-I-FTP_OBJ, Object : dka0:[pmega]
%UCX-I-FTP_CHINFO, UCX$FTPC_1: Failed to set default directory
%RMS-E-DNR, device not ready, not mounted, or unavailable
%UCX-I-FTP_USER, Username : PMEGA
%UCX-I-FTP_SESDCN, FTPD: Session disconnection from TPFC01 at 26-SEP-2003 15:37:41.19

the TPFC01 is a pc station name.
the ucx version is V4.2 eco 4
openvms version is 7.1-2
For your infomation, no log files have been created since 26-SEP-2003.
Any idea how to solve this
Regards,
Tankl

[Karl Rohwedder]

It seems as if DKA0:[PMEGA] is not available.
Log in interactively and try SH DEV DKA0 to check for errors.

[Willem Grooters]

FTP _logs_in_ as (in this case) user PMEGA - and will execute the WHOLE login sequence.
If either DKA0 is nor mounted, or this user's login directory does not exist or is inaccessable, FTP will fail (for obvious reasons). To find out, just login interactively with this username. You can also check accounting (if enabled) to get info.

[Ian Miller.]

enable auditing alarms of failed network logins as these sometimes give futher information. The simplest way forward is to login interactively as user PMEGA. Check the login command file for that user to see if it does change default directory. Check what the login device and directory of PMEGA is defined in the SYSUAF.

[Martin P.J. Zinser]

Hello Tankl,

the error message is pretty specific:

%UCX-I-FTP_OBJ, Object : dka0:[pmega]
%UCX-I-FTP_CHINFO, UCX$FTPC_1: Failed to set default directory
%RMS-E-DNR, device not ready, not mounted, or unavailable

Things to check:

1.) Is device DKA0 mounted and available?
2.) Does the directory [pmega] exist on DKA0?
3.) Is the protection on pmega.dir set so that user pmega can access it?

Greetings, Martin

[Mike Naime]

Also check and/or delete your FTP .LOG files. If this is an automated and re-occuring process, I would check to see if you have reached the version limit of 32767. If this is the case, the process would be unable to create a new log file. I have seen this problem more recently with NTP log files.