Hi,
I try to use an openldap as authentication provider. The openldap is a load-balanced master:slave system.
I am using AppD Controller Version 4.0.1.2 build 44.
The server.log of the AppD Controller is full of this log entry:
[#|2015-05-07T09:35:47.047+0200|WARNING|glassfish3.1.2|com.singularity.ee.controller.beans.model.LDAPAuthenticationBean|_ThreadID=217;_ThreadName=Thread-5;|ldap authentication failure: no ldap user found |#]
[#|2015-05-07T09:35:47.050+0200|WARNING|glassfish3.1.2|com.singularity.ee.controller.beans.model.LDAPAuthenticationBean|_ThreadID=224;_ThreadName=Thread-5;|ldap authentication failure: no ldap user found |#]
[#|2015-05-07T09:35:47.054+0200|WARNING|glassfish3.1.2|com.singularity.ee.controller.beans.model.LDAPAuthenticationBean|_ThreadID=68;_ThreadName=Thread-5;|ldap authentication failure: no ldap user found |#]
[#|2015-05-07T09:35:47.057+0200|WARNING|glassfish3.1.2|com.singularity.ee.controller.beans.model.LDAPAuthenticationBean|_ThreadID=67;_ThreadName=Thread-5;|ldap authentication failure: no ldap user found |#]
[#|2015-05-07T09:35:47.059+0200|WARNING|glassfish3.1.2|com.singularity.ee.controller.beans.model.LDAPAuthenticationBean|_ThreadID=216;_ThreadName=Thread-5;|ldap authentication failure: no ldap user found |#]
[#|2015-05-07T09:35:47.063+0200|WARNING|glassfish3.1.2|com.singularity.ee.controller.beans.model.LDAPAuthenticationBean|_ThreadID=55;_ThreadName=Thread-5;|ldap authentication failure: no ldap user found |#]
Every two - four milliseconds this Warning occurs. What could be the reason for this?
I get an "empty" user from ldap and I think this could be the reason:
The administrator of the ldap has no empty user and I cannot delet this entry in AppDynamics.
These are my queries for the ldap:
Both queries are working and I got results from the ldap.
Regards,
Thomas
We are running 4.2.1.0 and this is almost 18 months later, our logs are still filled with glassfish LDAP warnings. This has made our job of troubleshooting an outage at the weekend much more difficult.
Is this even in the pipeline to be fixed?
Hi Raymond,
Sorry to say that is yet to be fixed and we confirm this is in pipeline but no ETA on fix version as of now. Hope that answers your query.
This is documented as known issues at:
We request you to try Clyde suggestion in above post in logging changes to see if it helps for the interim, Also check if we are doing REST API automation calls:
<Controller_dir>/appserver/glassfish/domains/domain1/config/logging
com.singularity.ee.controller.beans.model.LDAPAuth
For now, I added the following to the appserver/glassfish/domains/domain1/config/logging.properties
com.singularity.ee.controller.beans.model.LDAPAuthenticationBean.level=SEVERE
Hi Thomas,
We come across similar warning messages earlier and you can safely ignore those warning messages for now as your actual ldap users imported looks to be logging fine as per your comments.
We have internal request for simialr warn messages already to address in future. Hope that answers your query.
Regards,
Arun
Hi,
any progress with this issue. The log file of the server becomes unreadable with dozens of this warning.
Regards,
Thomas
Hi Thomas,
Apologies for the issue you are seeing the internal request is yet to be fixed/implemented at this point of time, We appreciate your patience and cooperation with us.