Hi, i have a weirdness. other than updating the container, i haven't changed any settings in LLDAP, and, although it seems to be operating normally. the container is showing as unhealthy and outputs the following error: ``Loading configuration from /data/lldap_config.toml 2024-03-05T01:41:05.723186022+00:00 INFO set_up_server [ 5.05ms | 100.00% ] 2024-03-05T01:41:05.723205652+00:00 INFO ┝━ ｉ [info]: Starting LLDAP version 0.5.1-alpha 2024-03-05T01:41:05.731969233+00:00 INFO ┕━ ｉ [info]: Starting the LDAP server on port 3890 Error: while binding the LDAP server Caused by: 0: while binding to the port 3890 1: Address in use (os error 98) `` i connected to the container and ran netstat -tulpn | grep :3890 which only shows one thing using 3890, which i presume to be LLDAP since it's working fine. any suggestions?

Could you perhaps have 2 instances of LLDAP running?

Not as far as i can tell, but when i stop the LLDAP docker container which is unhealthy, the web panel is unreachable, but LLDAP still seems to be authenticating, which leads me to believe that somehow is the case, i'll have to investigate further..

I'd check with htop or similar to see if you have 2 lldap processes, or just

killall lldap

when i run the top command i get this. i've previously tried killing both PID 7 & 1 and restarted the container to no change

That's from inside the container. There might be something else than LLDAP running on that port, or another LLDAP container running. On the host, if you run

sudo ss -lptn 'sport = :3890'

Do you get anything? It should show you the process using that port

nothing on the host is using that port, i have docker forwarding from 25628 to the default port, when running it for that port i get this:

Maybe it's due to the proxy you set up?

it's how i have every other container set up

LLDAP really doesn't do anything weird with the ports

it certainly feels like i have a duplicate LLDAP process, because everything still works, but when authenticating with lldap, it hangs for a moment before working, as if it's trying to direct to multiple destinations

Docker swarm?

do you mean i should use swarm mode? or are you asking if i am? because not currently. i don't really know about it. i'm looking at the documentation

If you're not using it, then I don't think you can accidentally use it 😄

yea, it sounds like it's just basically a container for containers

Wait, I just saw your command and entrypoint

i never modified those. i just changed them to the default option instead of the override option, and still get the same result

Yeah, no, just read the docs, command is the arguments for the process defined by entrypoint

right? every time i probe, it seems like it should be correct.

Maybe @xaverius666 can help? He's very resourceful when it comes to deployment

sudo netstat -tunlp

this smells like double deployment, or some automatic restart due weird unhealthy state, maybe wipe out deployment from lldap and go to

docker compose up

deployment. or disabling healthcheck by adding

healthcheck:
    disable: true

using

sudo netstat -tunlp

i only see: ``tcp6 0 0 :::25628 :::* LISTEN 3193798/docker-prox tcp 0 0 0.0.0.0:25628 0.0.0.0:* LISTEN 3193791/docker-prox `` which appears to be the docker proxy and nothing using the default port. I can try and re-create it from compose up

is 3890 showing?

no, nothing on the host is using that port

Somehpw lldap started twice in container but it shouldn't be that.

welp, i'm not sure what was wrong, but i created a new LLDAP container from compose and it's healthy and working now 🤷‍♂️