Program or version mismatch errors can occur for multiple reasons and may be indicative of multiple issues that need to be addressed. In order to provide the most accurate fix, review each of the following resolutions as one or more may apply to the environment:
If you are getting this error only while using NetWorker License Manager (NML) to add/report a license, verify that you are using the appropriate syntax (nsrcap).
1. Restart the NetWorker processes in order to resolve and potential inter-communication issues.
2. Restart the operating system for the machine, if possible.
3. Use hosts file for name resolution between the NetWorker server, client(s), and any Storage Nodes (include reverse name lookup).
4. Verify that for the machine reporting the error message, there are not mixed binary versions. That is, all NetWorker binaries on the client are the same version.
5. Reduce server parallelism as much as possible in order to test if the error is due to resource limitation (network, memory, CPU).
6. Ensure all hops between the client and NetWorker server are set to the appropriate network speed rather than the default of 'Auto Negotiate'.
More Information:
Use rpcinfo to check if there is a problem with the RPC version numbers. The problem could be due to a mismatch in the RPC service requested by client and the service available on the server. Rpcinfo is a command that can be used to check the program and version number of the registered services on a machine.
rpcinfo -p (client_name)
program vers proto port service
100000 3 tcp 36890 portmapper
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
390103 2 tcp 846 nsrd
390109 2 tcp 846 nsrstat
390110 1 tcp 846 nsrjb
390103 2 udp 853 nsrd
390109 2 udp 853 nsrstat
390110 1 udp 853 nsrjb
390107 4 tcp 931 nsrmmdbd
390107 5 tcp 931 nsrmmdbd
390104 105 tcp 845 nsrmmd
390104 205 tcp 945 nsrmmd
390105 5 tcp 677 nsrindexd
390113 1 tcp 7937 nsrexec
"nsrd", always has "390103" for program number and "2" for version number.
The "recover" command from client, in turn, uses rpcinfo to get service from the NetWorker server. If the program and version numbers do not match, the error message, "RPC: Program/version mismatch;", can be returned.
That is, the following shows how the error message is returned when the machine "goldfarb" is "pinged" for "nsrd".
>rpcinfo -t goldfarb 390103 2 program 390103 version 2 ready and waiting
If we request "nsrd" with version "3" (and not "2"), the following is the error obtained:
>rpcinfo -t goldfarb 390103 3
rpcinfo: RPC: Program/version mismatch; low version = 2, high version =2 program 390103 version 3 is not available
We just started to see this same error on one of our Networker servers as well. Seeing it on multiple clients but not all. Some Windows clients and some Oracle RMAN backups.
Just curious if anyone has tried restarting Networker on the Networker server or rebooting the Networker server?
ble1
6 Operator
•
14354 Posts
•
56186 Points
2108
0
Posted January 6th, 2014 00:00
Do you get this during index save only? I assume, other backups are affected too? (or is it just index)?