watlingj
03/05/2024, 1:43 AMnitnelave
03/05/2024, 6:03 AMwatlingj
03/07/2024, 1:55 AMnitnelave
03/07/2024, 5:11 AMkillall lldapwatlingj
03/24/2024, 2:17 AMhttps://i.imgur.com/7ax9XIS.png▾
watlingj
03/24/2024, 2:18 AMhttps://i.imgur.com/BpKTWXR.png▾
nitnelave
03/24/2024, 4:43 AMsudo ss -lptn 'sport = :3890'
Do you get anything? It should show you the process using that portwatlingj
03/24/2024, 4:00 PMhttps://i.imgur.com/8sdVO9Y.png▾
watlingj
03/24/2024, 5:22 PMwatlingj
03/24/2024, 5:23 PMwatlingj
03/24/2024, 5:26 PMnitnelave
03/24/2024, 5:46 PMwatlingj
03/24/2024, 5:58 PMwatlingj
03/24/2024, 5:59 PMnitnelave
03/24/2024, 6:00 PMnitnelave
03/24/2024, 6:00 PMwatlingj
03/24/2024, 6:02 PMnitnelave
03/24/2024, 6:04 PMwatlingj
03/24/2024, 6:07 PMnitnelave
03/24/2024, 6:09 PMnitnelave
03/24/2024, 6:09 PMnitnelave
03/24/2024, 6:09 PMwatlingj
03/24/2024, 6:09 PMnitnelave
03/24/2024, 6:42 PMnitnelave
03/24/2024, 6:42 PMnitnelave
03/24/2024, 6:42 PMwatlingj
03/24/2024, 6:45 PMwatlingj
03/24/2024, 6:45 PMnitnelave
03/24/2024, 6:45 PMnitnelave
03/24/2024, 6:46 PMnitnelave
03/24/2024, 6:46 PMwatlingj
03/24/2024, 6:46 PMnitnelave
03/24/2024, 6:46 PMxaverius666
03/25/2024, 2:01 AMsudo 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: truewatlingj
03/25/2024, 2:08 AMsudo 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 upxaverius666
03/25/2024, 2:09 AMwatlingj
03/25/2024, 2:09 AMxaverius666
03/25/2024, 2:16 AMwatlingj
03/25/2024, 2:38 AMwatlingj
03/25/2024, 2:38 AM