https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
d
that might be a bug with the connection tester.. It did state passed.. so I wouldn't worry about it.
f
yes but it is creating different rooms with same name and dividing the users
d
hmm can you share the server logs when this happened? (not results from the connection test)
f
can you guide me how to get the server logs? I am on ubuntu. There are many log files in /var/log
have this been fixes? even i have the 
signal_relay
set to 
true
https://livekit-users.slack.com/archives/C01KVTJH6BX/p1682073055225479
d
logs are printed to the console.. so you would have to figure out how that's saved. you are running 1.4.4 right?
f
Yes I have 3 instances running and each instance running livekit with version 1.4.4 Moreover, I checked, all the logs are present in syslog file. downloading them from each server and upload here
Here are the logs I got from 2 servers running behind load balancers, just after 2 rooms were created with the same room name/id Server 1:
Copy code
INFO        livekit        rtc/dynacastmanager.go:227        committing quality change        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpadbup0wcikf1jofo531ti", "pID": "PA_CmJm3vhzy8RP">
Jul 30 10:17:46 ip-172-31-8-134 livekit-server[31420]: 2023-07-30T10:17:46.212Z        INFO        livekit        rtc/participant.go:1511        sending max subscribed quality        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpadbup0wcikf1jofo531ti", "pID": "PA_CmJm3vhzy8R>
Jul 30 10:19:02 ip-172-31-8-134 livekit-server[31420]: 2023-07-30T10:19:02.352Z        WARN        livekit        connectionquality/scorer.go:257        error getting expected distance        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpadbup0wcikf1jofo531ti", "pID": "PA_Cm>
Jul 30 10:20:17 ip-172-31-8-134 livekit-server[31420]: 2023-07-30T10:20:17.352Z        WARN        livekit        connectionquality/scorer.go:257        error getting expected distance        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpadbup0wcikf1jofo531ti", "pID": "PA_Cm
Server 2:
Copy code
Jul 30 09:39:21 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T09:39:21.716Z        INFO        livekit        service/roommanager.go:481        room closed        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_RZVBJmqMXZAR"}
Jul 30 10:16:43 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:16:43.363Z        INFO        livekit        service/rtcservice.go:284        new client WS connected        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpae52p0webkf1jp6gtojx3", "pID": "PA_PCH6moKsZbcd", >
Jul 30 10:17:40 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:17:40.626Z        INFO        livekit        service/rtcservice.go:352        exit ws read loop for closed connection        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpae52p0webkf1jp6gtojx3", "pID": "PA>
Jul 30 10:17:40 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:17:40.626Z        INFO        livekit        service/rtcservice.go:247        finishing WS connection        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpae52p0webkf1jp6gtojx3", "pID": "PA_PCH6moKsZbcd", >
Jul 30 10:17:40 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:17:40.626Z        INFO        livekit        service/rtcservice.go:309        nothing to read from response source        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpae52p0webkf1jp6gtojx3", "pID": "PA_PC>
Jul 30 10:17:40 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:17:40.627Z        INFO        livekit        routing/signal.go:122        signal stream closed        {"room": "animal-telepathy-znmmg6t71", "reqNodeID": "ND_npOHwSZo", "participant": "clkpae52p0webkf1jp6gtojx3", "connID": "CO_D9X42hKXff2B", "erro>
Jul 30 10:18:57 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:18:57.026Z        INFO        livekit        service/rtcservice.go:284        new client WS connected        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpah0720wj8kf1jp1srnxek", "pID": "PA_DHBzn6E9Xopf", >
Jul 30 10:19:02 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:19:02.449Z        INFO        livekit        service/rtcservice.go:352        exit ws read loop for closed connection        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpah0720wj8kf1jp1srnxek", "pID": "PA>
Jul 30 10:19:02 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:19:02.449Z        INFO        livekit        service/rtcservice.go:247        finishing WS connection        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpah0720wj8kf1jp1srnxek", "pID": "PA_DHBzn6E9Xopf", >
Jul 30 10:19:02 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:19:02.449Z        INFO        livekit        service/rtcservice.go:309        nothing to read from response source        {"room": "animal-telepathy-znmmg6t71", "roomID": "RM_VdUp2uMJN69U", "participant": "clkpah0720wj8kf1jp1srnxek", "pID": "PA_DH>
Jul 30 10:19:02 ip-172-31-26-218 livekit-server[98689]: 2023-07-30T10:19:02.450Z        INFO        livekit        routing/signal.go:122        signal stream closed        {"room": "animal-telepathy-znmmg6t71", "reqNodeID": "ND_KEAOPOQ5", "participant": "clkpah0720wj8kf1jp1srnxek", "connID": "CO_b3NvFsEuZgA4", "error>
My participant id is: 
clkpadbup0wcikf1jofo531ti
which is currently connected to the livekit but I can't find this user in the redis server. Currently, 2 people are only present on the server, in different rooms with the same room name/id, and their ids are as follows: • 
clkpadbup0wcikf1jofo531ti
• 
clkpae52p0webkf1jp6gtojx3
but in logs, I can see another participant with id 
clkpah0720wj8kf1jp1srnxek
I don't know how that one is created. 
signal_relay
is set to 
true
in all the server configs Update: I joined the same room from another device and now I can't see any participant in the redis server... The room is empty
Also, we have noticed that whenever we try to test livekit from our localhost (next.js server) this happens more often.
d
I'm not sure what you mean by 
can't see any participant in the redis server
sometimes devs have other jobs that are wiping their redis instances. this doesn't sound like an issue with livekit
f
I get it but for us livekit is totally unusable because of 2 rooms issue. We invite people in one room and some people goes to other room with same name
@dry-elephant-14928 is there anyway i can fix this issue?
d
sorry, I don't quite understand what you are seeing. the logs do not show any issues.. both users are assigned the same room ID. You should ensure that nothing else is accessing Redis.
we've seen folks having other background jobs that flushed data from Redis.. things like that will mess up how livekit discovers other nodes.
f
We dont use redis for our backend… and it is not configured in our code base… only livekit servers has access to it
@dry-elephant-14928 I shifted from the 
EC2 Redis Instance
to 
AWS Elastic Cache
, it worked great when there were 120 users, and suddenly it created a new room with the same name and new participants started to populate the other room. This is seriously so annoying for us. Can you please help us with this?
d
we'd be glad to help.. if there's a way for us to reproduce it. Can you file an issue on github with a step by step on how to reproduce?
Open in Slack
PreviousNext
Powered by