https://livekit.io logo
Join Slack
Powered by
Seems like redis works but logs show this ? ```/o...
# self-hosting
c
Seems like redis works but logs show this ?
Copy code
/opt/livekit# docker-compose logs redis | tail -5 
redis-1 | 1:M 25 Feb 2026 07:48:33.912 * Increased maximum number of open files to 10032 (it was originally set to 1024
). 
redis-1 | 1:M 25 Feb 2026 07:48:33.912 * monotonic clock: POSIX clock_gettime 
redis-1 | 1:M 25 Feb 2026 07:48:33.913 * Running mode=standalone, port=6379. 
redis-1 | 1:M 25 Feb 2026 07:48:33.914 # Warning: Could not create server TCP listening socket 127.0.0.1:6379: bind: Ad
dress in use 
redis-1 | 1:M 25 Feb 2026 07:48:33.914 # Failed listening on port 6379 (tcp), aborting.
looks like it two on localhost and then ipv6. could it be that ipv6 is not set up?
Copy code
sudo ss -tlnp | grep 6379
LISTEN 0      511        127.0.0.1:6379      0.0.0.0:*    users:(("redis-server",pid=2570162,fd=6))                
LISTEN 0      511            [::1]:6379         [::]:*    users:(("redis-server",pid=2570162,fd=7))
f
there's another redis thats already running and using that port 
address in use
message
👎 1
that would not conflict
check the host machine
c
nope if i kill the process and redo sudo systemctl restart livekit-docker show 2 again
f
seems like you're starting redis in docker? then there are two possibilities: 1. there are two redis containers starting, so one conflicts with the other 2. there is a redis server running on the host machine
2. you can verify by shutting down all docker containers, and checking if 6379 is still open
c
yo funny how i have 2 livekit servers running lmao how the heck
got it now thanks
f
👍
✅ 1
2 Views
Open in Slack
PreviousNext
Powered by