superset: Not able to get the debug logs or python stacktrace on errors even after LOG_LEVEL is set to 'DEBUG'

Make sure these boxes are checked before submitting your issue - thank you!

[can’t find the stacktrace ] I have checked the superset logs for python stacktraces and included it here as text if any
[check ] I have reproduced the issue with at least the latest released version of superset
[ check] I have checked the issue tracker for the same issue and I haven’t found one similar

I’m using the following 2 parameters to define the log level of superset

LOG_FORMAT = ‘%(asctime)s:%(levelname)s:%(name)s:%(message)s’ LOG_LEVEL = ‘DEBUG’

But when I start superset using superset runserver, I cannot see the debug logs (or python stacktrace on errors) on the console. I’m trying to login to superset using LDAP, but not able to do so, and hence need the debug logs/python stacktrace. Can someone please help me out.

Superset version

0.24.0 superset.txt

Expected results

Debug logs on the console

Actual results

Info logs on the console superset_log_issue

Steps to reproduce

The config file is attached. When I try to login, the login fails and I get the following message

Invalid login. Please try again.

and there is no debug log on the console.

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 1
Comments: 17 (3 by maintainers)

Most upvoted comments

I got this working. I added the following 3 parameters

AUTH_USER_REGISTRATION = True AUTH_ROLE_PUBLIC = 'Public' AUTH_USER_REGISTRATION_ROLE = 'Public'

Superset config specifically needs the user registration as True for any user that logs in the first time. Closing this issue now.

deepak-goel on Apr 11, 2018

@deepak-goel could you share with your pip freeze results? I have the same problem and adding public role doesnt solve my issue. I am still not able to check if my LDAP configuration works. So, to better understand… after such configuration - should I register a new user (where username == uid from LDAP)?

EDIT: I checked BaseSecurityManager line by line and in my case that solved the issue:AUTH_LDAP_USERNAME_FORMAT = "uid=%s,ou=YOUR,o=ORG"

us3r on Apr 12, 2018