All types of networks, network stacks, and protocols supported by OpenVMS.
-
Topic author
indy
- Member
- Posts: 9
- Joined: Tue Aug 01, 2023 7:14 am
- Reputation: 0
- Location: Switzerland
-
Status:
Offline
Post
by indy » Mon Nov 13, 2023 9:35 am
If I try to run the following commands on a OpenVMS System 9.2-1 running on VMware to mount some folders on another OpenVMS system via NFS. Two NFS mounts are working, the third always fails independent from the order of the commands.
The other system is an Alpha Workstation running OpenVMS V7.3-1.
Code: Select all
$ TCPIP MOUNT DNFS20: /HOST=PDS_BACKUP /PATH="/RDISK/EQUALRUN/ATO" /GROUP /WRITE /TIMEOUT=00:00:05 /UID=1 /STRUCTURE=5
$
$ TCPIP MOUNT DNFS10: /HOST=PDS_BACKUP /PATH="/RDISK/EQUALDTB/PDS_DB" /GROUP /WRITE /TIMEOUT=00:00:05 /UID=1 /STRUCTURE=5
$
$ TCPIP MOUNT DNFS11: /HOST=PDS_BACKUP /PATH="/RDISK/EQUALBAC/PDS_DB" /GROUP /WRITE /TIMEOUT=00:00:05 /UID=1 /STRUCTURE=5
Any ideas?
-
volkerhalle
- Master
- Posts: 201
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
-
Status:
Offline
Post
by volkerhalle » Mon Nov 13, 2023 10:45 am
Please provide the full messages returned by the 3 mount commands - the two successful mounts and also the failing mount.
Volker.
Last edited by
volkerhalle on Mon Nov 13, 2023 10:46 am, edited 1 time in total.
-
Topic author
indy
- Member
- Posts: 9
- Joined: Tue Aug 01, 2023 7:14 am
- Reputation: 0
- Location: Switzerland
-
Status:
Offline
Post
by indy » Tue Nov 14, 2023 12:38 pm
Hi
Thank you for your interest.
The mount commands
Code: Select all
$ TCPIP MOUNT DNFS10: /HOST=PDS_BACKUP /PATH="/RDISK/NYTCPDTB/PDS_DB" /GROUP /WRITE /TIMEOUT=00:00:05 /UID=1 /RETRIES=3 /STRUCTURE=5
$ TCPIP MOUNT DNFS11: /HOST=PDS_BACKUP /PATH="/RDISK/NYTCPBAC/PDS_DB" /GROUP /WRITE /TIMEOUT=00:00:05 /UID=1 /RETRIES=3 /STRUCTURE=5
$ TCPIP MOUNT DNFS20: /HOST=PDS_BACKUP /PATH="/RDISK/NYTCPRUN/ATO" /GROUP /WRITE /TIMEOUT=00:00:05 /UID=1 /RETRIES=3 /STRUCTURE=5
provide the following messages:
Code: Select all
%TCPIP$DNFSMOUNT-S-MOUNTED, /RDISK/NYTCPDTB/PDS_DB mounted on _DNFS10:[000000]
%TCPIP$DNFSMOUNT-S-MOUNTED, /RDISK/NYTCPBAC/PDS_DB mounted on _DNFS11:[000000]
%TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting _DNFS20:[000000]
-SYSTEM-F-REJECT, connect to network object rejected
If I change the mount sequence, I get the same error for one of the other devices e.g. DNFS11.
Last edited by
indy on Tue Nov 14, 2023 12:45 pm, edited 1 time in total.
-
volkerhalle
- Master
- Posts: 201
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
-
Status:
Offline
Post
by volkerhalle » Wed Nov 15, 2023 11:16 am
Indy,
I've tested this on OpenVMS x86-64 V9.2-1 against an VSI OpenVMS Alpha V8.4-2L2 NFS server running TCPIP V5.7 - ECO 5 and I can mount 3 NFS shares without problem.
A -SYSTEM-F-REJECT, connect to network object rejected message implies, that the problem most likely is on the remote NFS server. Check OPERATOR.LOG on that NFS server or enable OPCOM messages using $ REPLY/ENABLE. Then retry the mounts and look for error messages.
Volker.
-
Topic author
indy
- Member
- Posts: 9
- Joined: Tue Aug 01, 2023 7:14 am
- Reputation: 0
- Location: Switzerland
-
Status:
Offline
Post
by indy » Thu Nov 16, 2023 10:36 am
OK.
The Operator.log contains some logs.
Code: Select all
%%%%%%%%%%% OPCOM 15-NOV-2023 19:30:48.93 %%%%%%%%%%%
Message from user TCPIP$NFS on MERKUR
%TCPIP-S-NFS_MNTSUC, mounted file system /RDISK/NYTCPDTB/PDS_DB
-TCPIP-S-NFS_CLIENT, uid=1 gid=330 host_name = PDS_BACKUP
%%%%%%%%%%% OPCOM 15-NOV-2023 19:30:49.19 %%%%%%%%%%%
Message from user NFS Server on MERKUR
Accepted connection from host 192.168.1.45 port 604
%%%%%%%%%%% OPCOM 15-NOV-2023 19:30:49.26 %%%%%%%%%%%
Message from user TCPIP$NFS on MERKUR
%TCPIP-S-NFS_MNTSUC, mounted file system /RDISK/NYTCPBAC/PDS_DB
-TCPIP-S-NFS_CLIENT, uid=1 gid=330 host_name = PDS_BACKUP
%%%%%%%%%%% OPCOM 15-NOV-2023 19:30:49.69 %%%%%%%%%%%
Message from user NFS Server on MERKUR
Accepted connection from host 192.168.1.45 port 609
%%%%%%%%%%% OPCOM 15-NOV-2023 19:30:49.69 %%%%%%%%%%%
Message from user NFS Server on MERKUR
Accepted connection from host 192.168.1.45 port 610
To me it lokks like the third connection is accepted, but not the mount.
I also noticed, that the gid=330 is not correct. I tried the mount command with gid=320 (how the Proxy is defined) but the log shows gid=330, which is the gid from the client user.
-
volkerhalle
- Master
- Posts: 201
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
-
Status:
Offline
Post
by volkerhalle » Thu Nov 16, 2023 11:39 am
Indy,
please also check SYS$SYSDEVICE:[TCPIP$NFS]TCPIP$MOUNTD_RUN.LOG and/or the portmapper log file SYS$SYSDEVICE:[TCPIP$PORTM]TCPIP$PORTM_RUN.LOG
If you want to test, whether this problem is caused by the NFS server or the NFS client, you could try those 3 mount commands to your local V9.2-1 server after configuring the local NFS server accordingly.
Volker.