Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can not invite participant -- no bridge available.

See original GitHub issue

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

Issue Analytics

State:
Created 6 years ago
Comments:46 (20 by maintainers)

Top GitHub Comments

2reactions

damenchocommented, Apr 27, 2018

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.

2reactions

damenchocommented, Nov 14, 2017

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.