nsrmmd #5: bad MM_DEACTIVATE peer. What does that mean?

[PBJ]

Hi,

I am responsible for the backups of 150 clients, mostly servers. We have exchanged the Wintel-machine for a newly bought AIX-machine from IBM for about a month ago.

The first 2 weeks everything worked just fine! Every backup went alot, and I mean ALOT faster, but after the honeymoon it stopped working.

As out of the blue sky we had serious problems, we couldnt even unmount the tapes, connect to the server with GUI Networker Administrator: "Server :cancelled" it works fine with telnet and ftp. After changing one tape for Hardware failure the problem still occured. Some clients works but fails the next day. Etc

In the Daemon.log it sais:

"nsrmmd #5: bad MM_DEACTIVATE peer, application id 0"

OR

server:All 1 retry attempted
server:All nsrexec: authtype nsrexec
server:All savefs: RPC error, Cancelled
server:All savefs: cannot retrieve client resources
01-02-15 21.16.44 savegrp: serverrobe will retry 0 more time(s)
01-02-15 21.16.44 savegrp: serverrobe failed.

OR

01-02-16 00.07.47 nsrd: re-setting overall number of authorized save sessions, changing value from (8) to (9)

These are just some of the messages...

Can anyone pls tel me what these errormessages are? or what they mean? My local support sais that some of these is network problems, like RPC but the others? Cant find anything on the web...

Thanks in advance.

Pierre

 

[cfowler]

Hello,

The RPC errors are indicative of an improperly configured client or server. Check to see that, if you are using host files, the correct entries reside within them. Your host file on the server should contain entries for the server and each client. Your host file on each server should contain entries for the server and that host.

You should also check to see that the correct alias is entered in the client setup for the client that is failing. If you are missing an entry, add it and run a probe on that client to verify communication is working.

For the client in question, check the rpc info:

prompt:> rpcinfo -p clientname
prompt:> rpcinfo -p clientname.dns suffix

Be certain to check / verify all client names / aliases. The alias that fails is the alias you will have to enter through Client Management.

Hope this helps,

CF
cfowler@city.london.on.ca