Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

ftp to vms box no longer succeeds

SOLVED
Go to solution
Carlo Corthouts
Frequent Advisor

ftp to vms box no longer succeeds

Hello All,

Hope anyone can help me with this problem.
I am still pretty new to openvms so please bear with me.

Now all of a sudden we seem to have a problem going into vms with ftp, where the connection is closed stating the login is incorrect.

After some investigations into the problem, I found that in the ftp log there was a message with :

$ RUN SYS$SYSTEM:TCPIP$FTP_CHILD.EXE
%SYSTEM-W-NOSUCHDEV, no such device available

This file is there with the permissions set as they should be, but we can not execute this image.

Are there any other things I should look for as well?

Any help is really appreciated.
40 REPLIES
Kris Clippeleyr
Honored Contributor

Re: ftp to vms box no longer succeeds

Hi,

Have you checked the account with which you login via ftp. Anything changed there (login device, login directory)? Are any logical names redefined (that might point to the login device of the account)?

Regards,
Kris (aka Qkcl)
I'm gonna hit the highway like a battering ram on a silver-black phantom bike...
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

There was a little problem a few days ago but was resolved. For some reason permissions changed in the sys$util folder and we had to set them again to world readable executable for them to work.
There was a logical which was defined wrong but was resolved by a colleague but now we are still stuck with this ftp issue.

Karl Rohwedder
Honored Contributor

Re: ftp to vms box no longer succeeds

Since the rest of VMS is running, I assume, that SYS$SYSTEM is not the culprit of the NOSUCHDEV message, but perhaps the BG device.

Are there any TCPIP Prozesses ( SHO SYS/PRO=TCPIP*) running, is TELNET ... to another node possible, are there BG devices (SHO DEV BG)?

Any entries in SYS$MANAGER:OPERATOR.LOG or on the console?

regards Kalle
Ian Miller.
Honored Contributor

Re: ftp to vms box no longer succeeds

have you run into a socket limit parhaps?
____________________
Purely Personal Opinion
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

This is the output for SHO SYS/PRO=TCPIP*

OpenVMS V7.1-2 on node XXXXXX 23-JUN-2005 11:59:14.18 Uptime 33 00:47:58
Pid Process Name State Pri I/O CPU Page flts Pages
00000214 TCPIP$LPD_QUEUE HIB 4 62 0 00:00:00.49 237 117
00000215 TCPIP$INET_ACP HIB 9 152665 0 00:00:30.27 207 175
0000021F TCPIP$PORTM LEF 10 918 0 00:00:00.48 261 237 N
00000220 TCPIP$ESNMP LEF 9 539019 0 00:00:48.05 190 253
00000228 TCPIP$TNS1 HIB 4 2032 0 00:00:00.75 2388 20
0000022B TCPIP$TNS2 HIB 4 17401 0 00:00:03.15 3291 20
00000242 TCPIP$TNS3 HIB 4 111 0 00:00:00.35 256 176
0000868D TCPIP$TNS4 HIB 6 21048 0 00:00:03.07 3596 20
00008EA2 TCPIP$FTP LEF 9 22217 0 00:00:01.80 379 346 N
000090A3 TCPIP$FTPC00001 LEF 6 66817 0 00:00:14.39 299 285 N
00008AAF TCPIP$FTPC00002 LEF 6 1712 0 00:00:00.46 319 286 N
000040E5 TCPIP$NTP LEF 10 1920583 0 00:00:05.24 264 258 N
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

This is the sho dev bg output

Device Device Error
Name Status Count
BG0: Mounted 0
BG1: Mounted 0
BG4: Mounted 0
BG5: Mounted 0
BG6: Mounted 0
BG7: Mounted 0
BG8: Mounted 0
BG9: Mounted 0
BG13: Mounted 0
BG24: Mounted 0
BG35: Mounted 0
BG36: Mounted 0
BG37: Mounted 0
BG40: Mounted 0
BG41: Mounted 0
BG63: Mounted 0
BG64: Mounted 0
BG65: Mounted 0
BG80: Mounted 0
BG81: Mounted 0
BG102: Mounted 0
BG117: Mounted 0
BG118: Mounted 0
BG126: Mounted 0
BG137: Mounted 0
BG142: Mounted 0
BG143: Mounted 0
BG175: Mounted 0
BG184: Mounted 0
BG219: Mounted 0
BG999: Mounted 0
BG2683: Mounted 0
BG5514: Mounted 0
BG5515: Mounted 0
BG5523: Mounted 0
BG5524: Mounted 0
BG5761: Mounted 0
BG5762: Mounted 0
BG5763: Mounted 0
BG5765: Mounted 0
BG5766: Mounted 0
BG5767: Mounted 0
BG5853: Mounted 0
BG5854: Mounted 0
BG5855: Mounted 0
BG5965: Mounted 0
BG5966: Mounted 0
BG5967: Mounted 0
BG5969: Mounted 0
BG5970: Mounted 0
BG5971: Mounted 0
BG6042: Mounted 0
BG6045: Mounted 0
BG6047: Mounted 0
BG6048: Mounted 0
BG6049: Mounted 0
BG6050: Mounted 0
BG6055: Mounted 0
BG6193: Mounted 0
BG6200: Mounted 0
BG6206: Mounted 0
BG6207: Mounted 0
BG6208: Mounted 0
BG6209: Mounted 0
BG6531: Mounted 0
BG6650: Mounted 0
BG6794: Mounted 0
BG6795: Mounted 0
BG6796: Mounted 0
BG6797: Mounted 0
BG6804: Mounted 0
BG6807: Mounted 0
BG6808: Mounted 0
BG6809: Mounted 0
BG6810: Mounted 0
BG6814: Mounted 0
BG6817: Mounted 0
BG6821: Mounted 0
BG6831: Mounted 0
BG6837: Mounted 0
BG6844: Mounted 0
BG7627: Mounted 0
BG7628: Mounted 0
BG7630: Mounted 0
BG7631: Mounted 0
BG7753: Mounted 0
BG7754: Mounted 0
BG7755: Mounted 0
BG7756: Mounted 0
BG8088: Mounted 0
BG8089: Mounted 0
BG9933: Mounted 0
BG9934: Mounted 0
BG9935: Mounted 0
Willem Grooters
Honored Contributor

Re: ftp to vms box no longer succeeds

Is this generic (i.e. for all users using FTP) or just a number of them?

Check SYS$MANAGER:SYLOGIN.COM and the user's LOGIN.COM, and look for a definition of SYS$* logicals SYS$SYSTEM, SYS$SYSROOT and SYS$COMMON (the latter two should be embedded in the definition of SYS$SYSROOT). These should be removed - AT ALL TIMES.

Since it seems just FTP having a problem I think your standard settings are Ok, but nevertheless, it might be a good idea to check your system on these logicals using $ SHOW LOG /FULL. SYS$SYSROOT and SYS$COMMON should refer to the systemdisk as in:

$ sho log SYS$SYSROOT/full
"SYS$SYSROOT" [exec] = "VMS001$DKA0:[SYS0.]" [concealed,terminal] (LNM$SYSTEM_TABLE)
= "SYS$COMMON:"
1 "SYS$COMMON" [exec] = "VMS001$DKA0:[SYS0.SYSCOMMON.]" [concealed,terminal] (LNM$SYSTEM_TABLE)
$

and SYS$SYSTEM to the [SYSEXE] directory on this device:

$ sho log SYS$SYSTEM/full
"SYS$SYSTEM" [exec] = "SYS$SYSROOT:[SYSEXE]" (LNM$SYSTEM_TABLE)
$

BTW: SYS$SYSDEVICE should refer to the system disk:

$ sho log SYS$SYSDEVICE/full
"SYS$SYSDEVICE" [exec] = "VMS001$DKA0:" [concealed,terminal] (LNM$SYSTEM_TABLE)
$

If that seems Ok, check the user acccount for those whose login fails (MCR AUTHORIZE SHOW.../FULL):

Username: XXXX
Owner: Willem Grooters
Account: XXXXX UIC: [m,u] ([BPS])
CLI: DCL Tables: DCLTABLES
Default: DKA0:[USERS.XXXXXX]
LGICMD: LOGIN.COM

Does DEVICE point to an existing device? Does it contains a logical (either immediate or embeeded within), then this needs to be defined /SYSTEM and should ONLY have the TERMINAL translation aattribute if the translation contains a device or device label
such as:

...
Default: USER:[XXXX]
...

and

$ sho log user/full
"USER" [exec] = "VMS001$DKA0:[USERS.]" [concealed,terminal] (LNM$SYSTEM_TABLE)
$

You can check this by DIR (e. if DEVICE="USER" and DIRECTORY=[XXXX], DIR USER:[XXXX] should give any answer except that the device or directory does not exist.
Willem Grooters
OpenVMS Developer & System Manager
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

The answer the other questions :

ftp to other systems from this box works. Telnet to this box and from this box to other boxes work.

Found no relevant ftp messages in the operator.log
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

Willem,

$ sho log user/full
%SHOW-S-NOTRAN, no translation for logical name USER
$ sho log user /full
%SHOW-S-NOTRAN, no translation for logical name USER

Does this mean I am missing a logical?

I am able to access my home directory as everyone can.

Everybody is unable to ftp into the system.
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

It actually should be
$ sho log user$disk2 /full
"USER$DISK2" [super] = "DSA107:" [concealed] (LNM$SYSTEM_TABLE)
Kris Clippeleyr
Honored Contributor

Re: ftp to vms box no longer succeeds

Carlo,
I should define USER$DISK2 in executive mode instead of supervisor.
Greetz,
Kris (aka Qkcl)
I'm gonna hit the highway like a battering ram on a silver-black phantom bike...
Karl Rohwedder
Honored Contributor

Re: ftp to vms box no longer succeeds

FTP tries to create a logfile TCPIP$FTP_SERVER.LOG in your logindirectory.
Is everything o.k. with it, i.e. when you login via telnet using the same account as in FTP, can your create files in your logindirectory?

Note: a logical TCPIP$FTP_SERVER may override the name and location of FTP serverlogfile, if defined, check this instead of your logindirectory.

regards Kalle
Volker Halle
Honored Contributor

Re: ftp to vms box no longer succeeds

Carlo,

there seem to be 2 TCPIP$FTPC... processes running (or maybe hanging around ?) on your system. These processes should be executing the image TCPIP$FTP_CHILD.EXE and are end-points of FTP sessions from some FTP clients to your FTP server.

$ TCPIP SHOW DEV/PORT=20 should show the device sockets of active FTP sessions.

Did you try to restart your FTP server ? Use @SYS$MANAGER:TCPIP$CONFIG and stop and start the FTP server (or use @SYS$STARTUP:TCPIP$FTP_SHUTDOWN.COM and TCPIP$FTP_STARTUP.COM directly.

Volker.
Kris Clippeleyr
Honored Contributor

Re: ftp to vms box no longer succeeds

Btw,
What does
SHOW DEVICE DSA107
tell you?
Kris (aka Qkcl)
I'm gonna hit the highway like a battering ram on a silver-black phantom bike...
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

Volker,

Tried stopping the ftp server but now I can start it up again as there is no TCPIP$INET_STARTUP.COM.
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

SHOW DEVICE DSA107 shows me normal output.
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

there is an inet_startup but not a ftp_startup
Kris Clippeleyr
Honored Contributor

Re: ftp to vms box no longer succeeds

Hi,

TCPIP$INET_STARTUP.COM not found?
There must be something wrong with your system disk.
Here I have, 2 TCPIP$*.COM files in SYS$COMMON:[SYS$STARTUP] and 90 of those in SYS$COMMON:[SYSMGR].
Btw, TCPIP$FTP_STARTUP does not invoke TCPIP$INET_STARTUP (at least to my knowledge).
Greetz,
Kris (aka Qkcl)
I'm gonna hit the highway like a battering ram on a silver-black phantom bike...
Jan van den Ende
Honored Contributor

Re: ftp to vms box no longer succeeds

Carlo,

I did not yet notice enyone welcoming you, so first things first:

"Welcome to VMS"

For your access via ftp, I agree with Qkcl:
have your concealed devices defined /EXEC, if they are to be accessable from privileged mode.


After some investigations into the problem, I found that in the ftp log there was a message with :


In WHICH ftp log did you find that?

The error clearly indicates, that you are trying to access a device (probably via a logical name construct) which is not available, at least, not available via the given specification. Note: this means: not available as seen from the starting network process, (potentially from a privd mode).

If you DO have a TCPIP$FTP_SETVER.LOG in the users SYS$LOGIN directory, then you MAY have a means to investigate further:
(Together with your system manager) make a temporary addition to SYS$SYLOGIN

$ if f$getjpi("","mode") .eqs. "BATCH" .and.-
f$getjpi("","username") .eqs.
$ then
$ set verify
$ endif

Now your LOG will hold a lot more info, which might be very helpfull in identifying the problem.

Note that this introduces a potential security issue, and so, as soon as possible, this addition should be removed again.


Proost.

Have one on me.

jpe



Don't rust yours pelled jacker to fine doll missed aches.
Willem Grooters
Honored Contributor

Re: ftp to vms box no longer succeeds

Two answers:
Stop and start FTP:

Stopping thte server:
$ @sys$startup:tcpip$ftp_shutdown

Starting the server:
$ @sys$startup:tcpip$ftp_startup

Stopping the client (never user this but you could try):
$ @sys$startup:tcpip$ftp_client_shutdown

and starting up:
$ @sys$startup:tcpip$ftp_client_startup

Logical "user":
Just an example. If you can login and access files in your home directory, it's no problem - references are Ok. But check S$S$MANAGER:SYLOGIN.COM, see if there is no redefinition or deassign of USER$DISK2 for network access (F$MODE is "NETWORK").
Willem Grooters
OpenVMS Developer & System Manager
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

There is no file call sys$startup:tcpip$ftp_startup

Only the sys$startup:tcpip$ftp_shutdown is in there.

I do have a TCPIP$FTP_SETVER.LOG in my home directory.

Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

At the moment, it would be great if someone could tell me how I can startup the ftp server again.
Volker Halle
Honored Contributor

Re: ftp to vms box no longer succeeds

Carlo,

@SYS$MANAGER:TCPIP$CONFIG

3 - Server components

5 - FTP

3 - Stop Service on this node

E - exit

5 - FTP

3 - Enable & Start service on this node

E

E

Hope this helps.

Volker.
Carlo Corthouts
Frequent Advisor

Re: ftp to vms box no longer succeeds

Volker,

Did not help.
Ftp server is not getting started.