jitsi-meet: Can not invite participant -- no bridge available.

Hi!

This is a long running jitsi installation (0.5 year) that after some time started failing.

After some time jitsi-meet is running, when someone tries to do a conference both browser clients crash.

jvb.log says:

JVB 2017-11-14 10:10:09.829 FINE: [501] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId 83a76-51612): <iq id="83a76-51612" type="result" to="jitsi-videobridge.meet.guifi.net" from="meet.guifi.net"/>
JVB 2017-11-14 10:10:09.829 FINE: [501] org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq id="83a76-51612" type="result" to="jitsi-videobridge.meet.guifi.net" from="meet.guifi.net"/>
JVB 2017-11-14 10:10:11.138 FINE: [503] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId AkQL6-236189): <iq type="get" to="jitsi-videobridge.meet.guifi.net" from="focus@auth.meet.guifi.net/focus1071006487923453" id="AkQL6-236189"><query xmlns="http://jabber.org/protocol/disco#info"/></iq>
JVB 2017-11-14 10:10:11.138 FINE: [503] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component 'JitsiVideobridge') Processing IQ request (packetId AkQL6-236189).
JVB 2017-11-14 10:10:11.138 FINE: [503] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Responding to IQ (packetId AkQL6-236189) with: <iq type="result" id="AkQL6-236189" from="jitsi-videobridge.meet.guifi.net" to="focus@auth.meet.guifi.net/focus1071006487923453"><query xmlns="http://jabber.org/protocol/disco#info"><identity category="component" type="conference" name="JitsiVideobridge"/><feature var="http://jabber.org/protocol/disco#info"/><feature var="urn:xmpp:ping"/><feature var="jabber:iq:last"/><feature var="urn:xmpp:time"/><feature var="http://jitsi.org/protocol/colibri"/><feature var="http://jitsi.org/protocol/healthcheck"/><feature var="urn:xmpp:jingle:apps:dtls:0"/><feature var="urn:xmpp:jingle:transports:ice-udp:1"/><feature var="urn:xmpp:jingle:transports:raw-udp:1"/><feature var="jabber:iq:version"/></query></iq>
JVB 2017-11-14 10:10:19.830 FINE: [36] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId 83a76-51613): <iq id="83a76-51613" type="result" to="jitsi-videobridge.meet.guifi.net" from="meet.guifi.net"/>
JVB 2017-11-14 10:10:19.830 FINE: [36] org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq id="83a76-51613" type="result" to="jitsi-videobridge.meet.guifi.net" from="meet.guifi.net"/>
JVB 2017-11-14 10:10:29.830 FINE: [26] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId 83a76-51614): <iq id="83a76-51614" type="result" to="jitsi-videobridge.meet.guifi.net" from="meet.guifi.net"/>
JVB 2017-11-14 10:10:29.830 FINE: [26] org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq id="83a76-51614" type="result" to="jitsi-videobridge.meet.guifi.net" from="meet.guifi.net"/>
JVB 2017-11-14 10:10:39.830 FINE: [613] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId 83a76-51615): <iq id="83a76-51615" type="result" to="jitsi-videobridge.meet.guifi.net" from="meet.guifi.net"/>
JVB 2017-11-14 10:10:39.830 FINE: [613] org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq id="83a76-51615" type="result" to="jitsi-videobridge.meet.guifi.net" from="meet.guifi.net"/>
JVB 2017-11-14 10:10:41.138 FINE: [30] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId AkQL6-236201): <iq type="get" to="jitsi-videobridge.meet.guifi.net" from="focus@auth.meet.guifi.net/focus1071006487923453" id="AkQL6-236201"><query xmlns="http://jabber.org/protocol/disco#info"/></iq>
JVB 2017-11-14 10:10:41.138 FINE: [30] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component 'JitsiVideobridge') Processing IQ request (packetId AkQL6-236201).

meanwhile jvb.log is FINE:

Jicofo 2017-11-14 09:56:40.598 INFO: [86] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Lip-sync enabled in room@conference.meet.guifi.net
Jicofo 2017-11-14 09:56:40.598 INFO: [86] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Joining the room: room@conference.meet.guifi.net
Jicofo 2017-11-14 09:56:40.599 INFO: [55] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberJoined sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@1fced781 member=ChatMember[room@conference.meet.guifi.net/focus, jid: null]@283587152]
Jicofo 2017-11-14 09:56:40.599 WARNING: [55] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-11-14 09:56:40.599 INFO: [55] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Obtained focus role: OWNER
Jicofo 2017-11-14 09:56:40.599 INFO: [55] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member room@conference.meet.guifi.net/focus joined.
Jicofo 2017-11-14 09:56:40.600 INFO: [86] org.jitsi.jicofo.JitsiMeetRecording.log() No recorder service discovered.
Jicofo 2017-11-14 09:56:40.719 INFO: [55] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberJoined sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@1fced781 member=ChatMember[room@conference.meet.guifi.net/8b338772, jid: null]@1031193953]
Jicofo 2017-11-14 09:56:40.720 INFO: [55] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Granted owner to room@conference.meet.guifi.net/8b338772
Jicofo 2017-11-14 09:56:40.720 INFO: [55] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member room@conference.meet.guifi.net/8b338772 joined.
Jicofo 2017-11-14 10:10:36.131 INFO: [63] org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq().396 Focus request for room: room@conference.meet.guifi.net
Jicofo 2017-11-14 10:10:36.172 INFO: [55] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberJoined sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@1fced781 member=ChatMember[room@conference.meet.guifi.net/781016a4, jid: null]@1264931942]
Jicofo 2017-11-14 10:10:36.172 INFO: [55] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member room@conference.meet.guifi.net/781016a4 joined.
Jicofo 2017-11-14 10:10:36.173 SEVERE: [55] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Can not invite participant -- no bridge available.
Jicofo 2017-11-14 10:10:36.173 SEVERE: [55] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Can not invite participant -- no bridge available.
Jicofo 2017-11-14 10:10:36.460 INFO: [55] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberLeft sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@1fced781 member=ChatMember[room@conference.meet.guifi.net/781016a4, jid: null]@1264931942]
Jicofo 2017-11-14 10:10:36.460 INFO: [55] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member room@conference.meet.guifi.net/781016a4 is leaving
Jicofo 2017-11-14 10:10:36.460 INFO: [55] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Removed participant: true, room@conference.meet.guifi.net/781016a4

You can try yourself at: meet.guifi.net

Its nearly vanilla configuration (unchecked third party software like random gravatars). But inside this machine, there is a matrix.org and rocketchat (docker). Perhaps all these applications are fighting with the ports?

This is a stable jitsi installation:

# apt-cache show jitsi
Package: jitsi
Architecture: amd64
Version: 2.10.5550-1

Thanks! Pedro

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 48 (20 by maintainers)

Most upvoted comments

A quick solution to your problem will be to disable health checking from jicofo. Add org.jitsi.jicofo.HEALTH_CHECK_INTERVAL=-1 to /etc/jitsi/jicofo/sip-communicator.properties and restart jicofo.

damencho on Apr 27, 2018

For some reason jicofo thinks there is no jvb instance. It is stopped or something went wrong. Uploading the whole log files may reveal more. Restarting jvb will fix it in short term. The version you had pointed is the jitsi-desktop client and has nothing to do with jitsi-meet.

damencho on Nov 14, 2017

Hi,

I’m facing the same behavior as soon another user is entering in the meeting. Each time jifoco says:

Jicofo 2024-02-26 16:43:37.540 INFO: [64] [room=testconf@conference.jitsi.MYDOMAIN.dev meeting_id=bf29d8e7-7cb5-4034-a9ed-6c44d4c66645] JitsiMeetConferenceImpl.inviteChatMember#800: Creating participant c670aa65 with features=[XMPP_CAPS, JSON_SOURCES, RECEIVE_MULTIPLE_STREAMS, REMB, SOURCE_NAMES, TCC, VISITORS_V1, E2EE, RTX, JINGLE, DTLS, JINGLE_RTP, AUDIO, VIDEO, SCTP, JINGLE_ICE, RAYO]
Jicofo 2024-02-26 16:43:37.540 INFO: [70] [room=testconf@conference.jitsi.MYDOMAIN.dev meeting_id=bf29d8e7-7cb5-4034-a9ed-6c44d4c66645] ColibriV2SessionManager.allocate#278: Allocating for 97861a20
Jicofo 2024-02-26 16:43:37.540 WARNING: [70] BridgeSelector.selectBridge#182: There are no operational bridges.
Jicofo 2024-02-26 16:43:37.540 SEVERE: [70] [room=testconf@conference.jitsi.MYDOMAIN.dev meeting_id=bf29d8e7-7cb5-4034-a9ed-6c44d4c66645 participant=97861a20] ParticipantInviteRunnable.doRun#218: Can not invite participant, no bridge available.
Jicofo 2024-02-26 16:43:37.541 INFO: [74] [room=testconf@conference.jitsi.MYDOMAIN.dev meeting_id=bf29d8e7-7cb5-4034-a9ed-6c44d4c66645] ColibriV2SessionManager.allocate#278: Allocating for c670aa65
Jicofo 2024-02-26 16:43:37.541 WARNING: [74] BridgeSelector.selectBridge#182: There are no operational bridges.
Jicofo 2024-02-26 16:43:37.543 SEVERE: [74] [room=testconf@conference.jitsi.MYDOMAIN.dev meeting_id=bf29d8e7-7cb5-4034-a9ed-6c44d4c66645 participant=c670aa65] ParticipantInviteRunnable.doRun#218: Can not invite participant, no bridge available.
Jicofo 2024-02-26 16:43:37.773 INFO: [72] [room=testconf@conference.jitsi.MYDOMAIN.dev meeting_id=bf29d8e7-7cb5-4034-a9ed-6c44d4c66645] JitsiMeetConferenceImpl.onMemberLeft#942: Member left:c670aa65
Jicofo 2024-02-26 16:43:37.773 INFO: [72] [room=testconf@conference.jitsi.MYDOMAIN.dev meeting_id=bf29d8e7-7cb5-4034-a9ed-6c44d4c66645] JitsiMeetConferenceImpl.terminateParticipant#1021: Terminating c670aa65, reason: gone, send session-terminate: false

Checking the number of files opened:

# lsof | grep jvb | wc -l
9538
# lsof | grep jvb | grep "UDP" |wc -l
102

# dpkg -l | grep jitsi
ii  jitsi-meet                    2.0.9258-1                     all          WebRTC JavaScript video conferences
ii  jitsi-meet-prosody            1.0.7790-1                     all          Prosody configuration for Jitsi Meet
ii  jitsi-meet-turnserver         1.0.7790-1                     all          Configures coturn to be used with Jitsi Meet
ii  jitsi-meet-web                1.0.7790-1                     all          WebRTC JavaScript video conferences
ii  jitsi-meet-web-config         1.0.7790-1                     all          Configuration for web serving of Jitsi Meet
ii  jitsi-videobridge2            2.3-74-ga015be96-1             all          WebRTC compatible Selective Forwarding Unit (SFU)
ii  lua-basexx                    0.4.1-jitsi1                   all          baseXX encoding/decoding library for Lua
ii  lua-cjson:amd64               2.1.0.10-jitsi1                amd64        JSON parser/encoder for Lua

I have no clue where to look for this issue.

EasyNetDev on Feb 26, 2024

I had the exact same issue as @mcr (could not start call, “no bride available”, “Failed to create room: jvbbrewery…”)

I blamed it on the fact that I recently upgraded my debian server to bullseye and haven’t tried to use Jitsi since, but maybe it is unrelated. I edited my /etc/prosody/conf.avail/call.example.com.cfg.lua and added those two lines, restarted jicofo.service and since then everything seems to work again. https://github.com/jitsi/jitsi-meet/blob/e525c2b2ec1abcab6b9233720ba4e1ead3d96a14/doc/debian/jitsi-meet-prosody/prosody.cfg.lua-jvb.example#L73-L74

Findus23 on Feb 22, 2021