Erratic behaviour with repository

Question

We are experiencing an issue with user access to a repository that is behaving erratically . 
 This repository has been functioning correctly until now. Other systems are accessing and querying the LDAP without any issues, but from our deployment, we are seeing various error messages when performing a full synchronization, such as "invalidCredentials (result=49)" or "Cannot connect to LDAP servers". Other times, the synchronization completes successfully. Also, when a user tries to authenticate in that repository, we get different error messages that seem related to repository authentication, such as "user does not exist" and "invalid access". Additionally, there are errors that appear to be related to AA configuration, such as when entering the user, more methods appear than those defined for that user. 
 I am looking through the logs but haven't found anything that helps me pinpoint the problem. 
 Which log should I check for connection errors with the repositories? 
 What tests could I run to try to determine what the issue might be? 
 P.S.: Everything works fine with other repositories. Any help or ideas regarding the possible issue or troubleshooting steps would be greatly appreciated. Thank you.

Daniel Rodríguez López de Lerma · Accepted Answer

The issue has finally been resolved, although we never discovered the exact cause. 
 I am still curious about where connection failures, authentication errors, synchronization errors, etc., are logged in the "Logs" section. My team and I have been searching but haven't found any messages except for the last two by entering the individual configuration of each repository.

Luciano Testa · Answer

Hello, 
 There is a section in the Admin Guide that describes the different logs in AAF: 
 
 https://www.netiq.com/documentation/advanced-authentication-64/server-administrator-guide/data/logging.html 
 
 For such an issue this would be the corresponding log: 
 Background Tasks Logs 
 
 These logs contain information about the queue tasks and about periodically running tasks (such as LDAP sync). 
 On the server, the celery.log file is stored in the /var/lib/docker/volumes/aaf_aucore-logs/_data/ directory. 
 After you export the Background Tasks logs, you can find the celery.log file in the /opt/AuCore/logs/ directory. 
 
 Also I would check for replication issues. 
 In the appliance itself you could execute a manual sync and save the output for errors: 
 
 docker exec aaf_aucore_1 sh -c '/opt/AuCore/aucore/scripts/repo/au_sync_all_ldap_repos.pyt --full' 
 
 In this particular case it seems the cause could have been a temporary environmental one. 
 
 Hope that helps. 
 
 Thanks. 
 Regards, 
 
 Luciano Testa

Menu

Advanced Authentication Discussions

Erratic behaviour with repository

Tags:

Top Replies

Verified Answer

Suggested Answer

Background Tasks Logs

Resources