docker-jitsi-meet icon indicating copy to clipboard operation
docker-jitsi-meet copied to clipboard

Room randomly crashes after joining

Open Inglebard opened this issue 3 years ago • 6 comments

Hi,

We notice today and month ago jitsi a crash after someone join the room. It seems to be random and I am not able to reproduce the issue. Restart the stack seems to "fix" temporary the issue. I was not able to capture the log until today.

We only use rooms with auth.

We use the "stable-5390-3" version but the issue appear multiple times since 1 year (I think). I notice the following in the log :

jicofo_1   | Jicofo 2021-04-22 09:59:11.063 SEVERE: [291] org.jitsi.jicofo.AbstractChannelAllocator.log() [email protected]/046ae4fc108c - failed to allocate channels, will consider the bridge faulty: Timed out waiting for a response.
jicofo_1   | org.jitsi.protocol.xmpp.colibri.exception.TimeoutException: Timed out waiting for a response.
jicofo_1   | 	at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.maybeThrowOperationFailed(ColibriConferenceImpl.java:328)
jicofo_1   | 	at org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.createColibriChannels(ColibriConferenceImpl.java:268)
jicofo_1   | 	at org.jitsi.protocol.xmpp.colibri.ColibriConference.createColibriChannels(ColibriConference.java:102)
jicofo_1   | 	at org.jitsi.jicofo.ParticipantChannelAllocator.doAllocateChannels(ParticipantChannelAllocator.java:110)
jicofo_1   | 	at org.jitsi.jicofo.AbstractChannelAllocator.allocateChannels(AbstractChannelAllocator.java:271)
jicofo_1   | 	at org.jitsi.jicofo.AbstractChannelAllocator.doRun(AbstractChannelAllocator.java:190)
jicofo_1   | 	at org.jitsi.jicofo.AbstractChannelAllocator.run(AbstractChannelAllocator.java:150)
jicofo_1   | 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
jicofo_1   | 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
jicofo_1   | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
jicofo_1   | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
jicofo_1   | 	at java.lang.Thread.run(Thread.java:748)

When the room begin to crash, it crashes every time. I have not tested what happens if we create another room.

Inglebard avatar May 03 '21 12:05 Inglebard

That looks like a communication problem between the JVB and Prosody.

saghul avatar May 03 '21 15:05 saghul

@saghul

That looks like a communication problem between the JVB and Prosody.

An idea to know why and how to fix this ?

Inglebard avatar May 04 '21 08:05 Inglebard

Check the JVB logs.

saghul avatar May 04 '21 08:05 saghul

@saghul Hmmm... seems some logs are missing. I will wait to happen again and post relevant log.

Inglebard avatar May 04 '21 10:05 Inglebard

Hi,

Here is a new part of a log : https://pastebin.com/Wqgc0iG3

Inglebard avatar May 18 '21 08:05 Inglebard

@saghul
I have encounter the issue today do you know what is wrong ?

Inglebard avatar Jun 04 '21 09:06 Inglebard