since a few days we’ve been expecting problem with out jitsi-meet installation, which has been working fine for several weeks. Yesterday I’ve restarted both Jicofo and Videobridge component and cleaned log files. Up to this morning it came back working normally, but then the problem appeared again. The first “SEVERE” error I see in the jicofo.log is:
Jicofo 2020-07-01 10:31:14.630 SEVERE:  org.jitsi.jicofo.JitsiMeetConferenceImpl.log() One of our bridges failed: jitsi-videobridge.video.opensquare.it
Then, everytime more than one people enters in a conference, I notice:
Jicofo 2020-07-01 10:31:20.541 SEVERE:  org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Can not invite participant -- no bridge available. Jicofo 2020-07-01 10:31:20.541 SEVERE:  org.jitsi.jicofo.JitsiMeetConferenceImpl.log() One of our bridges failed: jitsi-videobridge.video.opensquare.it
and for that timeframe, I’ve seen in the JVB log:
JVB 2020-07-01 10:30:43.762 FINE:  org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component 'JitsiVideobridge') Processing IQ (packetId AXGCD-16154): <iq id="AXGCD-16154" type="result" to="jitsi-videobridge.video.opensquare.it" from="video.opensquare.it"/> JVB 2020-07-01 10:30:45.983 INFO:  org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=b7a488b9a17574b2 conf_name=null,logging=false,conf_count=3,ch_count=18,v_streams=18 JVB 2020-07-01 10:30:46.009 INFO:  org.jitsi.videobridge.health.Health.log() Performed a successful health check in 26ms. Sticky failure: false # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f920178d7a7, pid=30608, tid=0x00007f91fb7fe700 # # 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 [jna8220853435920293971.tmp+0x7a7a7] sctp_timeout_handler+0x444 # # 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_pid30608.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug.
what could be the cause of this?