NetBackup Appliance CLISH (Command Line Interface SHell) produces errors when selecting certain options

Article:TECH215844  |  Created: 2014-03-16  |  Updated: 2014-03-20  |  Article URL http://www.symantec.com/docs/TECH215844
Article Type
Technical Solution

Product(s)

Issue



Many NetBackup Appliance CLISH operations do not work and result in an error.

 


Error



There are various error messages produced by the CLISH when this issue is present, these errors include:

-[Error] Failed to execute remote calls on host ‘localhost’ check if this node is part of the appliance using ‘appliance->listnodes"

-Not able to fetch data for node

-[Info] ERROR - Error running remote calls, err: -2

The messages log may produce the following error:

-sshd[PID]: Authentication refused: bad ownership or modes for directory /root

 


Environment



NetBackup Appliance 52xx (2.6, 2.6.0.x)

 


Cause



This issue can be caused by either of the following:

1. SSH Key mismatch between root and AppComm.   This can be caused after running ' ssh-keygen ' on an elevated ' root ' login. This command will then update the /root/.ssh/id_rsa and id_rsa.pub files, causing a mismatch from those in the /home/AppComm/.ssh/ folder.

2. Permissions\mode of " /root " directory have been modified from the default setting of 700 (drwx------).   NB:  This problem can occur with Appliance versions 2.5.x

 


Solution



Solution 1 :-  If the issue is caused by the SSH key mismatch, to correct the problem the id_rsa and id_rsa.pub files can be copied from the /home/AppComm/.ssh/ directory to the /root/.ssh/ directory, but first ensure backup copies are made prior to the copy.

 

Solution 2 :-  If the issues are being caused by the mode of  /root  being changed, the following should be verified:

From the Elevated Maintenance Command Line, run:

ls -ld /root

And ensure that the mode is set to the default 700 as per:

drwx------ 16 root root 4096 Mar 15 14:42 /root

Any other deviation of these modes can cause an issue.  These permissions should not be changed, and must remain 700 (drwx------).

 




Article URL http://www.symantec.com/docs/TECH215844


Terms of use for this information are found in Legal Notices