Unix Access Management

secd.authsys.lookup.failed causing informatica to stop communicating with storage

How can we troubleshoot these errors between NetApp appliances and Linux server

 

 

Occurred at 20:02

Event:

secd.authsys.lookup.failed: Unable to retrieve credentials for UNIX user with UID (20645) on Vserver (svmpa03_ldap_prod).

Message Name:

secd.authsys.lookup.failed

Sequence Number:

18181806

Description:

This message occurs when the incoming UNIX user ID (UID) that tries to mount or access a mount point cannot be looked up in any of the name-services (NIS, LDAP, file).

Action:

Ensure that the UNIX UID that is trying to mount or access a mount point is part of a name-service, such as NIS, LDAP, or file.

 

Occurred at 20:01

 

Event:

secd.authsys.lookup.failed: Unable to retrieve credentials for UNIX user with UID (20645) on Vserver (svmpa03_ldap_prod).

Message Name:

secd.authsys.lookup.failed

Sequence Number:

18181796

Description:

This message occurs when the incoming UNIX user ID (UID) that tries to mount or access a mount point cannot be looked up in any of the name-services (NIS, LDAP, file).

Action:

Ensure that the UNIX UID that is trying to mount or access a mount point is part of a name-service, such as NIS, LDAP, or file.

 

Thanks,

 

  • Hello,

    Jason Bauer here from One Identity Support.

    The error appears to be a lookup issue on the NetAPP side. Possibly not finding the data in AD. I would recommend contacting NetApp support first on this.

    If it's deemed that Authentication Services / NetApp integration is playing into this then NSS debug could be useful to determine the information being sent to the Linux system.

    Steps for enabling (and disabling) NSS debugging:

    1 - touch /var/opt/quest/vas/.qas_id_dbg

    Debug will start after 30 seconds in the file /tmp/qas_module.log (or /tmp/qas_id_dbg.log in some older versions of QAS)

    2 - Reproduce the issue and then check the file to ensure it captured the data.

    3 - Turn off nss debug by deleting the file created in step 1.