# AWX ldap logs verbosity.

**URL:** <https://forum.ansible.com/t/awx-ldap-logs-verbosity/27327>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [April 19, 2018, 12:55pm UTC](https://forum.ansible.com/t/awx-ldap-logs-verbosity/27327 "2018-04-19T12:55:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarcG](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@MarcG](https://forum.ansible.com/u/MarcG)\
**Post date:** [April 19, 2018, 12:55pm UTC](https://forum.ansible.com/t/awx-ldap-logs-verbosity/27327/1 "2018-04-19T12:55:26Z")

</div>

Hi I am trying to troubleshoot an LDAP integration issue and I need a way to get more verbose logs.

I have put the following line in /etc/tower/settings.py LOGGING[‘handlers’][‘tower\_warnings’][‘level’] = ‘DEBUG’

I then pull the logs from the awx-web container.

docker logs

If I enter a non-existent username I get something in the logs.

2018-04-19 12:45:19,706 DEBUG django\_auth\_ldap search\_s(‘CN=users,DC=sales,DC=local’, 2, ‘(sAMAccountName=%(user)s)’) returned 0 objects:

2018-04-19 12:45:19,706 DEBUG django\_auth\_ldap Authentication failed for sDszc: failed to map the username to a DN.

However if I use a correct username with correct or incorrect password I get nothing and the login fails.

Is there anyway to increase the logging verbosity to see what on earth in going on?

Many thanks.

```auto

```

---

<div class="post-metadata">

**Author:** ![MarcG](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@MarcG](https://forum.ansible.com/u/MarcG)\
**Post date:** [April 22, 2018, 12:12pm UTC](https://forum.ansible.com/t/awx-ldap-logs-verbosity/27327/2 "2018-04-22T12:12:56Z")

</div>

I ended up just using wire shark to determine the issue

---

<div class="post-metadata">

**Author:** ![Eugene\_Archibald](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@Eugene\_Archibald](https://forum.ansible.com/u/Eugene_Archibald)\
**Post date:** [May 1, 2018, 10:13pm UTC](https://forum.ansible.com/t/awx-ldap-logs-verbosity/27327/3 "2018-05-01T22:13:30Z")

</div>

So what was the issue? I’m facing the same thing in one environment, but not the other, and the lack of valid debugging logs is driving me batshit.

---

<div class="post-metadata">

**Author:** ![MarcG](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@MarcG](https://forum.ansible.com/u/MarcG)\
**Post date:** [May 1, 2018, 11:27pm UTC](https://forum.ansible.com/t/awx-ldap-logs-verbosity/27327/4 "2018-05-01T23:27:00Z")

</div>

My issue was something as simple as the group DN being incorrect.

If you use Wireshark it can dissect the ldap traffic and it should give you a clear idea of what is going on if you are just using straight LDAP and not ldaps

---

<div class="post-metadata">

**Author:** ![Eugene\_Archibald](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@Eugene\_Archibald](https://forum.ansible.com/u/Eugene_Archibald)\
**Post date:** [May 2, 2018, 4:11pm UTC](https://forum.ansible.com/t/awx-ldap-logs-verbosity/27327/5 "2018-05-02T16:11:56Z")

</div>

Thanks!

Annoyingly in my case it had cached something in AWX from prior LDAP work that was causing logins to fail even after the LDAP was configured correctly.

I removed the cached accounts and login worked properly.