LDAP debugging not possible within LXC container? #105
Comments
|
Config should also have: Snap logs to syslog. So to debug inside LXC container, you should first go inside of LXC container: And then check syslog. |
|
Thanks Lauri. I am debugging within the container and wekan dees write to /var/log/syslog, which you can see above. Alas, it does not write LDAP debugging information there. I have set "debug": true but it makes no difference. This is what I'm running: Latest configuration: Running out of ideas here. Here's the syslog output (again): |
|
It could be related to some settings. Please check current values at: Also Univention appliance includes LDAP server and Wekan works with it: Wekan at Univention has this Docker template. I think setting depend on LDAP server. |
|
In general, same LDAP settings should work both with Snap and Docker. |
|
Hi @xet7 I would prefer to get the logging to work instead of endless trial-and-error... |
|
Do you mean this? |
|
Hi @xSET7 I know how to read the logfiles. What I'm saying is that LDAP is not logging debugging info. See my logfile excerpts further up in the thread. I cannot debug ldap. Full stop. I think this is a bug and I'm trying to help fix it. |
|
Hmm? Well, LDAP code is here: So I think, you just add there showing variables: Or alternatively, with checking that environment variable DEBUG=true is set. Then you rebuild from source code: Select 1 and Enter to install dependencies. Then: Select 2 to build Wekan. Then edit If you like to have meteor notice changed code files, and then rebuild, instead of To get lint / eslint to accept |
|
Hi @xet7, thank you for your recommendation but a) I'm running the snap version (hence https://github.com/wekan/wekan-snap/issues) and b) I just want the software to tell me what it does so I can see where my settings may be incorrect. I do everything according to the documentation but the syslog just says which is what I've posted above. According to some searching, other people seem to face the same issue. No debugging information. |
|
Ooops sorry for my too technical answer. I did re-read this issue and it seems Wekan does not show enough details. Do you know what are these settings? |
|
no worries :)- Unfortunately, snap doesn’t use environment variables - or I wouldn’t know how to set them.
…--
Ralf U. Holighaus - on my iPhone
Schopenhauerstr. 23
14129 Berlin, Germany
Mobile: +49.172.7108171
Am 05.10.2019 um 01:10 schrieb Lauri Ojansivu ***@***.***>:
Ooops sorry for my too technical answer. I did re-read this issue and it seems Wekan does not show enough details.
Do you know what are these settings?
Sep 18 16:05:49 snaptest wekan.wekan[46289]: [WARN] Lookup for unset variable: INTERNAL_LOG_LEVEL
Sep 18 16:05:49 snaptest wekan.wekan[46289]: [WARN] Lookup for unset variable: LDAP_USER_ATTRIBUTES
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I'm running wekan as a snap app within an unprivileged LXC Ubuntu 19.04 disco container unter Proxmox PVE 5.3. It's running well but I can't manage to LDAP to work. Unfortunately, I cannot see what Wekan is actually sending / receiving to/from the Active Directory server, no matter what I put into my config.
Here is my config:
In my syslog, all I can see is this when trying to login:
I can take tcpdump logs and try to find out what Wekan sends to the directory server but that's kind of frustrating and there must be a better way. Any idea why I can't get decent log information?
The text was updated successfully, but these errors were encountered: