UNSOLVED

JohanRM

updated

13 years ago

J

JohanRM

1 Rookie

•

79 Posts

0

10908

January 5th, 2014 23:00

RPC error: RPC program or version mismatch; low version=305, high=305

Hi,

I am running Legato Networker V 7.6.4.5 on a Win2008-R2 server. The Legatio clients have the same version.

Suddenly, i get the following erro for a number of Legato clients:

olaf-client-227: index 39078: save: RPC error: RPC program or version mismatch; low version=305, high version=305

olaf-client-227: index 5777: save: cannot open save session with legato server olaf-server

I did not change the legato version on the serevr nor on the clients ?

Any idea how to solve this ?

Restarting the Legato services on the clients does not help.

Regards,

Johan

  • 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)?

  • nmc2

    268 Posts

    2108

    0

    Posted January 6th, 2014 01:00

    Refer to below link, It might help you to fix this issue.

    https://support.emc.com/kb/146764

    Regards,
    Prajith

  • tech88kur

    142 Posts

    2108

    0

    Posted January 6th, 2014 07:00

    Hi,

    Just adding to discussion here. I use Networker 8.0.1.1 build .132.

    Sometimes I get this error during VADP backups. On later restarts it runs fine, I could not figure out why this behaviour.

    @Prajith - could you please paste the content of KB article here. I am not able to access it.

    Regards

  • nmc2

    268 Posts

    2108

    1

    Posted January 6th, 2014 09:00

    Here is the content,

    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

  • rtfernandes

    21 Posts

    2108

    0

    Posted January 20th, 2014 14:00

    Hello guy's

    Prajith your recomendation apllies also to this?

    RMAN-03009: failure of backup command on IncrEIDC4 channel at 01/20/2014 20:08:07

    ORA-19506: failed to create sequential file, name="DifCumul_EIDC1_7gouikt3_1_1", parms=""

    ORA-27028: skgfqcre: sbtbackup returned error

    ORA-19511: Error received from media manager layer, error text:

      RPC program or version mismatch; low version = 123605, high version = 123605 (0:5:2)

    channel IncrEIDC4 disabled, job failed on it will be run on another channel

    channel IncrEIDC1: finished piece 1 at 20-JAN-14

    piece handle=DifCumul_EIDC1_7douikt3_1_1 tag=TAG20140120T200747 comment=API Version 2.0,MMS Version 1.1.0.0

    channel IncrEIDC1: backup set complete, elapsed time: 00:00:29

    channel IncrEIDC1: starting incremental level 1 datafile backup set

    channel IncrEIDC1: specifying datafile(s) in backup set

    input datafile file number=00002 name=/u02/oradata/EIDC1/sysaux01.dbf

    channel IncrEIDC1: starting piece 1 at 20-JAN-14

    RMAN-03009: failure of backup command on IncrEIDC3 channel at 01/20/2014 20:09:27

    ORA-19506: failed to create sequential file, name="DifCumul_EIDC1_7fouikt3_1_1", parms=""

    ORA-27028: skgfqcre: sbtbackup returned error

    ORA-19511: Error received from media manager layer, error text:

      RPC program or version mismatch; low version = 124605, high version = 124605 (0:5:2)

    channel IncrEIDC3 disabled, job failed on it will be run on another channel

    RMAN-03009: failure of backup command on IncrEIDC2 channel at 01/20/2014 20:11:03

    ORA-19506: failed to create sequential file, name="DifCumul_EIDC1_7eouikt3_1_1", parms=""

    ORA-27028: skgfqcre: sbtbackup returned error

    ORA-19511: Error received from media manager layer, error text:

       Direct saves are not enabled. (0:5:2)

    Best regards

  • crazyrov

    6 Operator

    •

    1319 Posts

    2108

    0

    Posted January 20th, 2014 23:00

    Hi Fernandes,

         Is this a new configuration or has this worked before, can you check if client direct is enabled ?

  • rtfernandes

    21 Posts

    2115

    0

    Posted January 21st, 2014 01:00

    Good morning,

    I have nw 7.6.5 this was work now fail with this error...

    Melhores cumprimentos/ Best regards

    Ricardo Fernandes -EMC

    #This email was send by a mobile device sorry for any typos.

  • crazyrov

    6 Operator

    •

    1319 Posts

    2115

    0

    Posted January 21st, 2014 02:00

    You might well try what Prajith has recommended.

  • Wendler97

    6 Posts

    2115

    0

    Posted January 8th, 2015 05:00

    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?

  • crazyrov

    6 Operator

    •

    1319 Posts

    687

    0

    Posted January 8th, 2015 05:00

    Please provide environment information.