Forum Discussion

PratiqueManUtd's avatar
8 years ago

Could not query all volumes: not authorized to connect to vmd (126)

I am getting the below error while trying to run the command:

NodeA# vmquery -j32 -a -M NodeB
Could not query all volumes: not authorized to connect to vmd (126)

NodeA is already added to "Servers" list on NodeB. NodeA can run all netbackup/bin and netbackup/bin/admincmd commands on NodeB but issue comes up with Media Manager related commands. 

13 Replies

  • Saw the following in debug/reqlib logs:

    <16> vmglob_host: unable to send request to server: not authorized to connect to vmd (126)
    <16> vmglob_host: unable to get EMM Port: not authorized to connect to vmd (126)
    <16> query_multiple: Could not initialize emm server interface host NodeB (126)

  • Not enough info....

    What exactly are 'NodeA' and 'NodeB' in NetBackup terms?

    Are they nodes of a clustered master server? 
    Or media server nodes in NBU app_cluster?

    What does 'nbemmcmd -listhosts -verbose' on the master server show? 

    Also no idea what your command means.

    There is no -M option for vmquery : 

    https://www.veritas.com/support/en_US/doc/15263389-127350397-0/v14674451-127350397

    The master/EMM server name is specified with -h.
    -m is for media-id. 

    I also have no idea what -j32 means.

    Sorry that I cannot be of assistance..... 

    • PratiqueManUtd's avatar
      PratiqueManUtd
      Level 3

      Hi Marianne

      NodeA and NodeB are both NetBackup master servers (not in cluster). I have made NodeA as the reporting server which fetches data frmo multiple master servers including NodeB. 

      vmquery -M <master> -j32 : "-M" flag will connect to remote master NodeB while -j32 displays the format quivalent to the one seen in Java console. For more options, you can explore vmquery -Q.

      The thing is, this command fetches data from all other masters but problem is only with this particualr one (NodeB).

      • Marianne's avatar
        Marianne
        Level 6

        Apologies - I sometimes forget that there are undocumented options.... 

        Thanks for clarifying your environment and purpose of the command.

        Does any other command (admincmd commands for example - e.g. bppllist) work with -M NodeB?

        Were services/daemons restarted on NodeB after adding NodeA as Server? 

        Is there maybe anything in vm.conf on NodeB that may prevent requests?