This post is more than 5 years old
1 Rookie
•
17 Posts
0
1185
April 5th, 2016 05:00
New install on 7.2.1, NDMP logs filled with error.
On a brand new 7.2.1 install where ndmp is currently working (backes from isilon) I get the below error repeated over and over constantly.
2016-04-05T05:44:26-04:00 <3.3> node-2(id2) isi_ndmp_d[37692]: CRIT:NDMP security.c:377:securityAuthenticateClient Failed to get password of root
2016-04-05T06:03:56-04:00 <3.3> node-2(id2) isi_ndmp_d[38841]: CRIT:NDMP security.c:377:securityAuthenticateClient Failed to get password of root
2016-04-05T06:23:26-04:00 <3.3> node-2(id2) isi_ndmp_d[40113]: CRIT:NDMP security.c:377:securityAuthenticateClient Failed to get password of root
The NDMP user is working as the backup DMA is using it successfully. Additionally i can login as root. This error does not seem to have any ill effects, but it spams my log files constantly.
adminguy
1 Rookie
•
17 Posts
0
December 15th, 2016 13:00
This is caused by some device/application/script trying to connect to your configured NDMP port (default 10000) using the login of "root". Once this was explained to me by Isilon support i did a packet capture to see whom the offender was. In my case it was a Netapp Oncommand application that was configured to do auto discovery in the same range as my isilons (a common storage network).
johnsonka
130 Posts
0
April 5th, 2016 13:00
Hello,
Are you using root as your NDMP user? I spoke to the subject matter expert for Isilon NDMP and what he said was you should be using an NDMP user. You can learn how to create and manage these users in the backup and recovery guide for your OneFS version. I have included the one for OneFS 7.2.1 here:
https://support.emc.com/docu60094_OneFS-7.2.1-Backup-and-Recovery-Guide.pdf?language=en_US
In this guide, the instructions are on page 67. Please let me know if there is anything else I can do for you.
adminguy
1 Rookie
•
17 Posts
0
April 5th, 2016 13:00
No, i am not using "root" as the NDMP user. I have created a new user account for NDMP. That is why I am confused. I don't know why its trying anything to do with "root" account.