[Info-vax] RPC and NFS Locking?
Tim Ellis
tellis3 at csc.com
Fri Mar 9 05:36:15 EST 2012
We have a process which makes use of RPC calls to fetch data from a
remote (non vms) server. This process was originally built on an
Alpha using OpenVMS 7.3-2 and TCPIP 5.4, and has worked without any
problems for 2+years
We recently migrated to a new VMS server running OpenVMS 8.4 and TCPIP
5.7 - We rebuilt and relinked the procedure under this version, and it
runs for between 15 mins to 4 hours, then starts to fail. Once it
starts failing it seems to continue to do so unless one or other of
the servers involved are rebooted.
Running the executable built under OpenVMS 7.3-2 continues to work
without displaying this problem.
The error returned is JCI_SERVER: RPC: Remote system error -
Connection refused
My suspicion is that something on the new build is triggering NFS
record locking, that is not called by the original build. Since we
don't make use of any other NFS services we don't have either STATD or
LOCKD running, and the thought was that starting these processes might
relieve the issue - however when I try running SYS$STARTUP:TCPIP
$STATD_STARTUP I get the following error message
%TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$STATD.EXE installed
%TCPIP-E-STARTERROR, error starting STATD service
-TCPIP-W-NORECORD, information not found
-RMS-E-RNF, record not found
%TCPIP-E-STARTFAIL, failed to start TCPIP$STATD
-TCPIP-E-ENABLERR, error enabling service
Either the manual is not much help, or I'm looking in the wrong one
(or the wrong place in the right one) as I can't see what record it is
looking for. Anyone able to help?
More information about the Info-vax
mailing list