I’m out of time for a reboot. client is awake and busy (mid morning in St Johns) so will have to wait till tomorrow.
I did another bit of digging. in that installed.cache file was listed ldap-server=0 and ldap-client=0 that suggests (again to me) that webmin either uses that file to check or fills it with what it finds available. In either case =0 would say "not available`
Yes that would be boolean false I would guess but I’ll lock in that file and see if mines the same. However it could indicate that the check failed
Just checked on a different box (not exhibiting the problem)
Same flags are same values - so =0 does look like it is using the file to check (not the outcome of the check)
reboot done
/tmp/webmin (no dot) gone
/tmp/.webmin still empty
no obvious change in /etc/webmin/installed.cache.
Still implying that LDAP is installed and complaining it is not configured.
problem still exists
Actually its getting worse.
(this was Virtualmin -> List Virtual Servers)
and
Everything now appears to be looking for an LDAP server and throwing an error (this was editing/creating a template)
[Edit] following some post @Joe made on a different topic I just checked Webmin -> Un-used Modules and sure enough LDAP Server is asking me to install it - heh no surprise there as it is NOT installed.
So why does the configuration think it is?
and why immediately following a reboot does it think it isn’t, only to get the same error a little later?
The errors stop me doing things but do not appear to detriment the system as it is.
Virtualmin believes you’re using LDAP for something. So, somewhere you’ve enabled an LDAP related feature. Obviously, if you aren’t intending to use LDAP (and most people should not, as it is a wild amount of additional complexity for very little gain except in larger organizations).
The LDAP guide is here: Setting up LDAP – Virtualmin
You may have enabled Virtualmin Configuration->Advanced Options->Add mail attribute to LDAP users
But, there are probably other things you may have done to make Virtualmin believe it needs LDAP.
I would strongly recommend you not try to enable LDAP as a solution to this problem. Unless you must use LDAP, that would be an insane path forward.
Thanks. LDAP is not required (or indeed wanted) LDAP server is not installed (as we have already confirmed. The problem is that Virtualmin (for an unknown reason) seems to think it is and is looking for more (as in LDAP client and LDAP users) I would understand a configuration error being flagged up if something was set to use LDAP but no LDAP server exists, however the messages are indicating that the LDAP server does exist (it doesn’t).
This morning I have warned the clients on this (development box) to be aware I’m going to take it down over the weekend and rebuild from scratch as I cannot see any other option. The error messages seem to popup at every turn as if the problem is spreading.
Virtualmin Configuration->Advanced Options->Add mail attribute to LDAP users remains “No” (presumably the default).
I keep coming back to the point that if “Virtualmin believe it needs LDAP” why is it not telling me to install a LDAP server? (instead of just directing to the Module Config page - where it doesn’t exist to be ticked - because it has not been installed)
You don’t want it to tell you to do that. If it did you might have done it, and that would just be getting even deeper into this hole. Seems like you’re coming at it from the wrong angle. The problem is not that LDAP isn’t installed or that Virtualmin isn’t asking to install LDAP (which is too wildly complicated and environment dependent for it to even begin to do automatically), it’s that it’s trying to load LDAP-related module code.
I’m still not sure what’s going on, though. I can’t figure out why it would be trying to load ldap-useradmin, when you don’t have LDAP enabled. That seems bug-like, but nobody else has reported it, and I can’t make it happen.
Yes and it is only this box for me as well I have looked back through my notes on what has been done on this. Nothing stands out as peculiar or even special to this box.
As I’ve said it just popped up (and does so) despite a reboot when the config rerun comes back after a while. It doesn’t appear to be affecting the clients but it is preventing me from doing things. Hence my solution will be a complete destruct tomorrow and a rebuild.
Well a full clean install on a VM with new image and reload all the VS from backups.
Seems to have done the trick - at least for today. Not exactly enjoyable just time consuming plod. Clients notified and I await their feedback next week.
Kiss goodbye to LDAP !
Still no idea on how it manifested itself ?
No idea. But hopefully it is gone. New image and new root password so if it was external it is now solved. But thanks for your continued interest.
