Skip to main content
NetApp Knowledge Base

How to repair corrupt or missing name services files

Views:
720
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • Name Services

Description

Even while name services files in vserver space on cluster level appear to be normal (located in the cluster configuration database and in memory), as example:

cluster::> services name-service unix-user show -vserver svm
               User            User   Group  Full
Vserver        Name            ID     ID     Name
-------------- --------------- ------ ------ --------------------------------
svm            nobody          65535  65535
svm            pcuser          65534  65534
svm            root            0      1

cluster::> services name-service unix-group show -vserver svm
Vserver        Name                ID
-------------- ------------------- ----------
svm            daemon              1
svm            nobody              65535
svm            pcuser              65534
svm            root                0

cluster::> services name-service ns-switch show -vserver svm
                               Source
Vserver         Database       Order
--------------- ------------   ---------
svm             hosts          files,
                                 dns
svm             group          files
svm             passwd         files
svm             netgroup       files
svm             namemap        files

cluster::> services name-service dns show -vserver svm
                        Vserver: svm
                        Domains: x.x.x
                   Name Servers: x.x.x
                 Timeout (secs): 2
               Maximum Attempts: 1

  • It is still required to have native name services files in the vserver space
  • If these name services files are corrupted, damaged or missing, the Security Daemon (SECD) will report these events, as example:

[kern_secd:info] ERR  :NSLIBC: Vsid = 3 Failed to open file: /mroot/etc/cluster_config/vserver/.vserver_3/config/name_services//etc/pwd.db. Error: No such file or directory
[kern_secd:info] info :NSLIBC: Vsid = 3 Could not stat file: /mroot/etc/cluster_config/vserver/.vserver_3/config/name_services//etc/nsswitch.conf. Error: No such file or directory
[kern_secd:info] ERR  :NSLIBC: Vsid = 3 Failed to open file: /mroot/etc/cluster_config/vserver/.vserver_3/config/name_services//etc/group. Error: No such file or directory

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.