Jitsi Video Bridge crash: "failed to allocate channels, will consider the bridge faulty"

Hello everyone,

Earlier today I was having a large important meeting and about 2 hours into the call Jitsi crashed.
Everyone was immediately disconnected from the room, and if they tried to join again, it would give an error popup saying it will try to reconnect in 25 seconds. It eventually fixed itself in a couple of minutes, but by that time most people had stopped trying to connect.

I checked the Jicofo logs and found this error at the time that the crash happened:

Jicofo 2020-06-12 09:12:51.746 SEVERE: [211] org.jitsi.jicofo.AbstractChannelAllocator.log() jvbbrewery@internal.auth.my.domain.com/ac3d2484-147d-4bd9-845b-a359d561e247 - failed to allocate channels, will consider the bridge faulty: XMPP error: <iq to=‘focus@auth.my.domain.com/focus632648033603’ from=‘jvbbrewery@internal.auth.my.domain.com/ac3d2484-147d-4bd9-845b-a359d561e247’ id=‘Bcl4c-92616’ type=‘error’><error type=‘cancel’><internal-server-error xmlns=‘urn:ietf:params:xml:ns:xmpp-stanzas’/></error></iq>

Jicofo 2020-06-12 09:12:51.747 SEVERE: [211] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() One of our bridges failed: jvbbrewery@internal.auth.my.domain.com/ac3d2484-147d-4bd9-845b-a359d561e247

After these 2 errors, the log just had this same error over and over again:

org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Can not invite participant – no bridge available.

Does anyone have an idea of what might have caused the issue? And maybe suggestions on how to prevent the problem in the future?

1 Like

We had this bad experience some days age.
In addition to the errors you mentioned, we got lots of these warnings in jvb.log before crash:

TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 26499-26519. Couldn't find packet detail for the seq nums: 26499-26519. Latest seqNum was 27792, size is 1000. Latest RTT is 64.966918 ms.

and finally a fatal SIGSEGV error and then jvb crashed:

# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x00007f7987224207, pid=29882, tid=0x000074f38dddf700
# JRE version: OpenJDK Runtime Environment (8.0_252-b09) (build 1.8.0_252-8u252-b09-1~18.04-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.252-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libc.so.6+0x97207]  __libc_malloc+0x197
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
# An error report file with more information is saved as:
# /tmp/hs_err_pid29892.log`

I’m curious what is the cause of this problem. and how we can prevent its recurrence.

1 Like