You should do what message suggests and I would advise to disable nsrauth as well. You will find details in previous threads, but if this is new to you I would advise to contact support with complete and full list of steps to be on the safe side.

Hi,

this message is not new with jumbo patch. It has been around since at least NW 7.3. A solution for this issue can be found in thread "Message in daemon.log" (threadid 34061). The post is:



Perhaps your support can give you more detailed information.

best regards.

nsradmin -p nsrexec

nsradmin> delete type:NSR peer information
type: NSR peer information;
administrator: Administrators,"group=Administrators,host=serverbk";
name: client;
peer hostname: client;
Change certificate: ;
certificate file to load: ;
Delete? y

We are also getting same message in Demon.log file. Could you we have created the two client for same Host with two different save sets and twe different groups. But we dont know its due to this or not. Today only we have deleted one client. Lets see the error is disappearing or not.
You also can check at your end there could be same host against which you are trying to create one more client.

Removing PEER information while nsrauth is working is not always something you wish to do. As said before, disable nsrauth on storage nodes (including bck server) and your pain is gone.