https://github.com/lldap/lldap logo
Powered by
jensen - After bump to latest commit on master,...
# troubleshooting
j
After bump to latest commit on master, I'm seeing these in the log. Are they really unknown now? It seems to be working fine...
Copy code
WARNING: Unknown environment variable: LLDAP_DATABASE_URL
WARNING: Unknown environment variable: LLDAP_JWT_SECRET
WARNING: Unknown environment variable: LLDAP_LDAP_USER_PASS
a
message has been deleted
j
~~And, maybe a followup question, should I be worried about this message? `[warn]: "database \"lldap\" has a collation version mismatch"`~~ Not relevant, seems to a postgres issue after glibc update
At least "LLDAP_DATABASE_URL" seems to be defined as a possible envvar variable in clr.rs, but it's not clear to me, that LLDAP_JWT_SECRET and LLDAP_LDAP_USER_PASS are valid env variables, at least I'm not having much luck finding any references to those by grepping, besides in docs.
n
The first error is weird: it's supposed to detect unused env variables, but those are definitely used. I need to have a look
(I just realized I have had this message in my drafts for quite a while)
The authoritative answer is the config dump at the top of the verbose logs: if all looks good, then all is good and the warnings are buggy. I'd still like to look into this, though. Can you file an issue?
j
Thanks! Can definitely file an issue 👍 I'll also check the config dump. It'll probably be tomorrow for both of them. It seems to me, that those names have just been omitted from the expected_keys set/list, and especially for LLDAP_DATABASE_URL it just looks like it's an omission, as I can find where it's declared as a possible env var. It's a bit less clear where two last ones would be read from env, at least from grepping -- i haven't yet gone through the config loading step by step.
n
They're derived from the config keys
Should be fixed now
I think I broke it earlier while "cleaning it up"
j
Thanks! I saw the merge last night, will give it a try later today, just need to get rust bumped as well.
Do you still want the issue on it? Sorry I didn't get it done yesterday, little one was sick, so didn't leave much time for it
n
No it's fine, it's solved 🙂
j
👍 🙂
Can confirm that those warnings are no longer there 👍
PreviousNext
Powered by