Jitsi-Server did not working after update Version (3928)

Install & Config
#1

I’ve set up a Jitsi-server on Ubuntu 18.04.4.

After apt-get upgrade & restart I can’t connect to the server via browser.

I think version is: 3928.

systemctl status jitsi-videobridge2

gives me the following:

jitsi-videobridge2.service - Jitsi Videobridge
Loaded: loaded (/lib/systemd/system/jitsi-videobridge2.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-04-08 13:33:45 UTC; 53min ago
Process: 4678 ExecStartPost=/bin/bash -c echo $MAINPID > /var/run/jitsi-videobridge/jitsi-videobridge.pid (code=exited, status=0/SUCCESS)
Main PID: 4677 (java)
Tasks: 38 (limit: 65000)
CGroup: /system.slice/jitsi-videobridge2.service
└─4677 java -Xmx3072m -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Dnet.java.sip.communicator.SC_HOME_DIR_

Procedure for Debian apt-get upgrade
#2

same here
got this error

#3

This is really strange because it’s NOT the last version.

apt policy jitsi-meet-web
jitsi-meet-web:
Installed: 1.0.3969-1
Candidate: 1.0.3969-1
Version table:
*** 1.0.3969-1 500
500 https://download.jitsi.org stable/ Packages
100 /var/lib/dpkg/status
1.0.3962-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3928-1 500
500 https://download.jitsi.org stable/ Packages

It would be better to test with the last available version (how could you have gotten an old version with apt I wonder)

#4

apt policy jitsi-meet-web gives me the following:

j> itsi-meet-web:

  Installed: 1.0.3928-1
  Candidate: 1.0.3969-1
  Version table:
     1.0.3969-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.3962-1 500
        500 https://download.jitsi.org stable/ Packages
 *** 1.0.3928-1 500
        500 https://download.jitsi.org stable/ Packages
        100 /var/lib/dpkg/status
     1.0.3729-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.3577-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.3387-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.3216-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.3186-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.3081-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.3036-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.2942-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.2866-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.2740-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.2579-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.2441-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.2301-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.1967-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.1592-1 500
        500 https://download.jitsi.org stable/ Packages
     1.0.1575-1 500
        500 https://download.jitsi.org stable/ Packages

and I use this to add jitsi to my repo:

> wget -qO - https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add -
> sudo sh -c "echo 'deb https://download.jitsi.org stable/' > /etc/apt/sources.list.d/jitsi-stable.list"
> sudo apt update -y

and install

> sudo apt install -y jitsi-meet
#5

what says

apt list --upgradable

#6

jicofo/stable 1.0-541-1 all [upgradable from: 1.0-539-1]
jitsi-meet/stable 2.0.4384-1 all [upgradable from: 1.0.4335-1]
jitsi-meet-prosody/stable 1.0.3969-1 all [upgradable from: 1.0.3928-1]
jitsi-meet-turnserver/stable 1.0.3969-1 all [upgradable from: 1.0.3928-1]
jitsi-meet-web/stable 1.0.3969-1 all [upgradable from: 1.0.3928-1]
jitsi-meet-web-config/stable 1.0.3969-1 all [upgradable from: 1.0.3928-1]
jitsi-videobridge2/stable 2.1-164-gfdce823f-1 all [upgradable from: 2.1-157-g389b69ff-1]
libgd3/bionic-updates,bionic-security 2.2.5-4ubuntu0.4 amd64 [upgradable from: 2.2.5-4ubuntu0.3]
linux-generic/bionic-updates,bionic-security 4.15.0.96.87 amd64 [upgradable from: 4.15.0.91.83]
linux-headers-generic/bionic-updates,bionic-security 4.15.0.96.87 amd64 [upgradable from: 4.15.0.91.83]
linux-image-generic/bionic-updates,bionic-security 4.15.0.96.87 amd64 [upgradable from: 4.15.0.91.83]
linux-libc-dev/bionic-updates,bionic-security 4.15.0-96.97 amd64 [upgradable from: 4.15.0-91.92]

#7

Well if you have a software problem it can come of your config or a bug in the software, so it makes sense in my opinion to update to the last version.
Come to think of it as the other updates are security updates, sudo apt full-upgrade chould be done.

#8

I’ve tried sudo apt full-upgrade and after reboot I couldn’t reach the server over the browser.

apt policy jitsi-meet-web

j itsi-meet-web:
Installed: 1.0.3969-1
Candidate: 1.0.3969-1
Version table:
*** 1.0.3969-1 500
500 https://download.jitsi.org stable/ Packages
100 /var/lib/dpkg/status
1.0.3962-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3928-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3729-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3577-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3387-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3216-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3186-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3081-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3036-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2942-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2866-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2740-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2579-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2441-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2301-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1967-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1592-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1575-1 500
500 https://download.jitsi.org stable/ Packages

apt list --upgradable
shows: Listing… Done

I’ve using a standard configuration. Only modified the path to the ssl-cert…

#9

Right, is there anything of interest in
journalctl -e -u jitsi-videobridge2
that is something different of Starting, Started, Stopped, something that looks like an error message ?
if not, what says
sudo tail -n 100 /var/log/jitsi/jvb.log

#10

Hi,
I’ve tested it on a other server and there are the same problems.

journalctl -e -u jitsi-videobridge2

Update started at: Apr 09 09:56:33

Apr 01 22:50:31 ubuntuSrv systemd[1]: Starting Jitsi Videobridge...
Apr 01 22:50:31 ubuntuSrv systemd[1]: Started Jitsi Videobridge.
-- Reboot --
Apr 02 00:47:53 ubuntuSrv systemd[1]: Starting Jitsi Videobridge...
Apr 02 00:47:53 ubuntuSrv systemd[1]: Started Jitsi Videobridge.
-- Reboot --
Apr 02 01:27:45 ubuntuSrv systemd[1]: Starting Jitsi Videobridge...
Apr 02 01:27:45 ubuntuSrv systemd[1]: Started Jitsi Videobridge.
-- Reboot --
Apr 02 01:32:24 ubuntuSrv systemd[1]: Starting Jitsi Videobridge...
Apr 02 01:32:24 ubuntuSrv systemd[1]: Started Jitsi Videobridge.
-- Reboot --
Apr 02 01:35:54 ubuntuSrv systemd[1]: Starting Jitsi Videobridge...
Apr 02 01:35:55 ubuntuSrv systemd[1]: Started Jitsi Videobridge.
-- Reboot --
Apr 02 10:05:12 ubuntuSrv systemd[1]: Stopping Jitsi Videobridge...
Apr 02 10:05:14 ubuntuSrv systemd[1]: Stopped Jitsi Videobridge.
-- Reboot --
Apr 02 10:45:08 ubuntuSrv systemd[1]: Stopping Jitsi Videobridge...
Apr 02 10:45:09 ubuntuSrv systemd[1]: Stopped Jitsi Videobridge.
-- Reboot --
Apr 02 10:49:48 ubuntuSrv systemd[1]: Stopping Jitsi Videobridge...
Apr 02 10:49:48 ubuntuSrv systemd[1]: Stopped Jitsi Videobridge.
-- Reboot --
Apr 02 10:53:17 ubuntuSrv systemd[1]: Stopping Jitsi Videobridge...
Apr 02 10:53:18 ubuntuSrv systemd[1]: Stopped Jitsi Videobridge.
-- Reboot --
Apr 02 18:52:59 ubuntuSrv systemd[1]: Stopping Jitsi Videobridge...
Apr 02 18:52:59 ubuntuSrv systemd[1]: Stopped Jitsi Videobridge.
-- Reboot --
Apr 09 09:56:33 ubuntuSrv systemd[1]: Starting Jitsi Videobridge...
Apr 09 09:56:34 ubuntuSrv systemd[1]: Started Jitsi Videobridge.
Apr 09 10:03:19 ubuntuSrv systemd[1]: Stopping Jitsi Videobridge...
Apr 09 10:03:20 ubuntuSrv systemd[1]: Stopped Jitsi Videobridge.
Apr 09 10:03:20 ubuntuSrv systemd[1]: Starting Jitsi Videobridge...
Apr 09 10:03:20 ubuntuSrv systemd[1]: Started Jitsi Videobridge.
Apr 09 10:15:42 ubuntuSrv systemd[1]: Stopping Jitsi Videobridge...
Apr 09 10:15:42 ubuntuSrv systemd[1]: Stopped Jitsi Videobridge.
-- Reboot --
Apr 09 10:15:57 ubuntuSrv systemd[1]: Starting Jitsi Videobridge...
Apr 09 10:15:58 ubuntuSrv systemd[1]: Started Jitsi Videobridge.

sudo tail -n 100 /var/log/jitsi/jvb.log

2020-04-09 10:15:22.494 INFORMATION: [16] VideobridgeExpireThread.expire#144: Running expire()
2020-04-09 10:15:31.758 INFORMATION: [17] Videobridge.createConference#326: create_conf, id=5dd747a9e386f689 gid=null logging=false
2020-04-09 10:15:31.773 INFORMATION: [17] Health.doRun#294: Performed a successful health check in 15ms. Sticky failure: false
2020-04-09 10:15:41.774 INFORMATION: [17] Videobridge.createConference#326: create_conf, id=516a615b0ba5450a gid=null logging=false
2020-04-09 10:15:41.787 INFORMATION: [17] Health.doRun#294: Performed a successful health check in 14ms. Sticky failure: false
2020-04-09 10:16:06.031 INFORMATION: [1] NewConfig$1.invoke#88: Loaded NewConfig with origin: merge of system properties,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-139-g33e0a49.jar!/reference.conf: 1
2020-04-09 10:16:06.070 INFORMATION: [1] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties
2020-04-09 10:16:06.076 INFORMATION: [1] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties
2020-04-09 10:16:06.080 INFORMATION: [1] JitsiConfig$Companion.reload#40: Reloading.
2020-04-09 10:16:06.121 INFORMATION: [1] NewConfig$1.invoke#88: Loaded NewConfig with origin: merge of system properties,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-139-g33e0a49.jar!/reference.conf: 1
2020-04-09 10:16:06.122 INFORMATION: [1] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties
2020-04-09 10:16:06.122 INFORMATION: [1] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties
2020-04-09 10:16:06.286 INFORMATION: [11] ConfigurationActivator.start#45: Registered the LegacyConfigurationServiceShim in OSGi.
2020-04-09 10:16:06.314 INFORMATION: [11] AbstractVersionActivator.start#91: VersionService registered: JVB 2.1.164-gfdce823f
2020-04-09 10:16:06.396 INFORMATION: [11] AbstractJettyBundleActivator.start#613: Not starting the Jetty service for org.jitsi.videobridge.rest.RESTBundleActivator(port=8080)
2020-04-09 10:16:06.426 INFORMATION: [11] AbstractJettyBundleActivator.start#613: Not starting the Jetty service for org.jitsi.videobridge.rest.PublicRESTBundleActivator(port=-1)
2020-04-09 10:16:06.431 INFORMATION: [11] AbstractJettyBundleActivator.start#613: Not starting the Jetty service for org.jitsi.videobridge.rest.PublicClearPortRedirectBundleActivator(port=8080)
2020-04-09 10:16:06.661 INFORMATION: [11] UlimitCheck.printUlimits#115: Running with open files limit 65000 (hard 65000), thread limit 65000 (hard 65000).
2020-04-09 10:16:06.666 INFORMATION: [11] VideobridgeExpireThread.start#92: Starting with 60 second interval.
2020-04-09 10:16:06.677 WARNUNG: [11] Videobridge.start#918: No authorized source regexp configured. Will accept requests from any source.
2020-04-09 10:16:06.825 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=9e76f9865f47b8bf gid=null logging=false
2020-04-09 10:16:07.032 INFORMATION: [20] TaskPools.<clinit>#81: TaskPools detected 1 processors, creating the CPU pool with that many threads
2020-04-09 10:16:08.371 INFORMATION: [11] JitsiConfig$Companion.reload#40: Reloading.
2020-04-09 10:16:08.441 INFORMATION: [11] NewConfig$1.invoke#88: Loaded NewConfig with origin: merge of system properties,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-139-g33e0a49.jar!/reference.conf: 1
2020-04-09 10:16:08.441 INFORMATION: [11] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties
2020-04-09 10:16:08.442 INFORMATION: [11] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties
2020-04-09 10:16:08.541 INFORMATION: [11] OctoRelayService.start#62: Octo relay is disabled.
2020-04-09 10:16:08.713 INFORMATION: [24] org.ice4j.ice.harvest.StunMappingCandidateHarvester.discover: Discovered public address 93.207.156.230:50788/udp from STUN server 18.156.45.236:443/udp using local address 192.168.1.25:0/udp
2020-04-09 10:16:08.713 INFORMATION: [20] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face=/192.168.1.25, mask=/93.207.156.230
2020-04-09 10:16:08.714 INFORMATION: [20] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=306ms).  stunDiscoveryFailed=false
2020-04-09 10:16:08.716 INFORMATION: [20] org.ice4j.ice.harvest.AbstractUdpListener.<init>: Initialized AbstractUdpListener with address 192.168.1.25:10000/udp. Receive buffer size 10485760 (asked for 10485760)
2020-04-09 10:16:08.720 INFORMATION: [20] org.ice4j.ice.harvest.SinglePortUdpHarvester.<init>: Initialized SinglePortUdpHarvester with address 192.168.1.25:10000/udp
2020-04-09 10:16:12.070 INFORMATION: [25] [hostname=localhost id=shard] MucClient$1.connected#266: Connected.
2020-04-09 10:16:12.070 INFORMATION: [25] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#648: Logging in.
2020-04-09 10:16:12.595 INFORMATION: [25] [hostname=localhost id=shard] MucClient$MucWrapper.join#751: Joined MUC: jvbbrewery@internal.auth.192.168.1.25
SCTP JNI load: Linux OS detected
SCTP lib loaded
=====>: org_jitsi_modified_sctp4j_SctpJni.c calling init
=====>: org_jitsi_modified_sctp4j_SctpJni.c about to set SCTP_DEBUG_ALL
2020-04-09 10:16:13.499 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 6807ms. Sticky failure: false
2020-04-09 10:16:23.501 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=70821f2208fb7579 gid=null logging=false
2020-04-09 10:16:23.533 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 34ms. Sticky failure: false
2020-04-09 10:16:33.534 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=12045a626501fea7 gid=null logging=false
2020-04-09 10:16:33.562 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 29ms. Sticky failure: false
2020-04-09 10:16:43.563 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=29399b9f5ad0c90b gid=null logging=false
2020-04-09 10:16:43.593 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 31ms. Sticky failure: false
2020-04-09 10:16:53.593 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=565327a572ca7cc9 gid=null logging=false
2020-04-09 10:16:53.623 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 30ms. Sticky failure: false
2020-04-09 10:17:03.624 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=a20b61ce552a11e8 gid=null logging=false
2020-04-09 10:17:03.646 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 23ms. Sticky failure: false
2020-04-09 10:17:06.667 INFORMATION: [19] VideobridgeExpireThread.expire#144: Running expire()
2020-04-09 10:17:13.648 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=b4e3a34b383cf724 gid=null logging=false
2020-04-09 10:17:13.673 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 26ms. Sticky failure: false
2020-04-09 10:17:23.675 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=8397b3c48c5260fd gid=null logging=false
2020-04-09 10:17:23.694 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 20ms. Sticky failure: false
2020-04-09 10:17:33.700 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=21f7b724a5a204e2 gid=null logging=false
2020-04-09 10:17:33.725 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 26ms. Sticky failure: false
2020-04-09 10:17:43.727 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=f12a4ad6fccc4cd gid=null logging=false
2020-04-09 10:17:43.749 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 23ms. Sticky failure: false
2020-04-09 10:17:53.751 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=c9a89b51efbe0ef1 gid=null logging=false
2020-04-09 10:17:53.768 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 18ms. Sticky failure: false
2020-04-09 10:18:03.769 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=a37da74517dcf5ca gid=null logging=false
2020-04-09 10:18:03.810 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 42ms. Sticky failure: false
2020-04-09 10:18:06.667 INFORMATION: [19] VideobridgeExpireThread.expire#144: Running expire()
2020-04-09 10:18:13.813 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=429acccd13e84489 gid=null logging=false
2020-04-09 10:18:13.836 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 24ms. Sticky failure: false
2020-04-09 10:18:23.837 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=c2146c5d15c9131a gid=null logging=false
2020-04-09 10:18:23.852 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 16ms. Sticky failure: false
2020-04-09 10:18:33.853 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=fdca53e1f75b9f7f gid=null logging=false
2020-04-09 10:18:33.880 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 28ms. Sticky failure: false
2020-04-09 10:18:43.882 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=e707115bdee66e91 gid=null logging=false
2020-04-09 10:18:43.902 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 21ms. Sticky failure: false
2020-04-09 10:18:53.903 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=40295aafe8f3f928 gid=null logging=false
2020-04-09 10:18:53.936 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 33ms. Sticky failure: false
2020-04-09 10:19:03.938 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=54db9ebb9ac369da gid=null logging=false
2020-04-09 10:19:03.952 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 15ms. Sticky failure: false
2020-04-09 10:19:06.668 INFORMATION: [19] VideobridgeExpireThread.expire#144: Running expire()
2020-04-09 10:19:13.952 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=100b13aa40c92e75 gid=null logging=false
2020-04-09 10:19:13.973 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 21ms. Sticky failure: false
2020-04-09 10:19:23.977 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=a210d68815006267 gid=null logging=false
2020-04-09 10:19:23.998 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 22ms. Sticky failure: false
2020-04-09 10:19:33.999 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=594f018155a54a4 gid=null logging=false
2020-04-09 10:19:34.025 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 27ms. Sticky failure: false
2020-04-09 10:19:44.027 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=71dc52e453a9ae62 gid=null logging=false
2020-04-09 10:19:44.048 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 22ms. Sticky failure: false
2020-04-09 10:19:54.049 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=dab02695823afdbd gid=null logging=false
2020-04-09 10:19:54.075 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 26ms. Sticky failure: false
2020-04-09 10:20:04.077 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=421df485db24a8da gid=null logging=false
2020-04-09 10:20:04.102 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 25ms. Sticky failure: false
2020-04-09 10:20:06.668 INFORMATION: [19] VideobridgeExpireThread.expire#144: Running expire()
2020-04-09 10:20:14.103 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=ec358992c8748d09 gid=null logging=false
2020-04-09 10:20:14.115 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 13ms. Sticky failure: false
2020-04-09 10:20:24.116 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=a1e2a134f901ce59 gid=null logging=false
2020-04-09 10:20:24.135 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 18ms. Sticky failure: false
2020-04-09 10:20:34.136 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=9b4dadd2a50d9b79 gid=null logging=false
2020-04-09 10:20:34.153 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 18ms. Sticky failure: false
2020-04-09 10:20:44.154 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=751052508745e987 gid=null logging=false
2020-04-09 10:20:44.172 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 18ms. Sticky failure: false
2020-04-09 10:20:54.173 INFORMATION: [20] Videobridge.createConference#326: create_conf, id=a33f60ec96696c77 gid=null logging=false
2020-04-09 10:20:54.185 INFORMATION: [20] Health.doRun#294: Performed a successful health check in 12ms. Sticky failure: false
#11

In my logs I see only 2 of these occurrences, and I have a
org.eclipse.jetty.server.Server.doStart: Started
line that you are missing. So it looks like your jetty server (the primary web server running in java that is proxied by nginx) is failing to start, and it indeed preclude any sort of working for jitsi. You can confirm it with something like
sudo ss -tapnu | grep 8080
if it returns nothing, chance is that jetty does not run. If it returns a line with ‘java’ as the software name, I am wrong.

If I am right, take a look at the jvb config file at /etc/jitsi/jvb, that is

  • config
  • sip-communicator.properties

I’d say that a java dev could figure out how to start jetty by hand and get an explicit diagnostic, unfortunately it’s not in my departement, so we could try to guess based on these files. Edit them as appropriate to replace your IPs and domain name if it matters for you.

#12

I think this is the right way to find out why jetty ist not running.
I start
sudo ss -tapnu | grep 8080

In /etc/jitsi I didn’t find ‘jvb’. There are only jicofo,meet, videobridge
But in /etc/jitsi/jicofo I found the files.

In ‘config’ I found

# Jitsi Conference Focus settings
# sets the host name of the XMPP server
JICOFO_HOST=localhost

# sets the XMPP domain (default: none)
JICOFO_HOSTNAME=192.168.1.25

# sets the secret used to authenticate as an XMPP component
JICOFO_SECRET=8ghggggjh

# sets the port to use for the XMPP component connection
JICOFO_PORT=5347

# sets the XMPP domain name to use for XMPP user logins
JICOFO_AUTH_DOMAIN=auth.192.168.1.25

# sets the username to use for XMPP user logins
JICOFO_AUTH_USER=focus

# sets the password to use for XMPP user logins
JICOFO_AUTH_PASSWORD=ggghghgg

# extra options to pass to the jicofo daemon
JICOFO_OPTS=""

# adds java system props that are passed to jicofo (default are for home and logging config file)
JAVA_SYS_PROPS="-Dnet.java.sip.communicator.SC_HOME_DIR_LOCATION=/etc/jitsi -Dnet.java.sip.communicator.SC_HOME_DIR_NAME=jicofo -Dnet.java.sip.communicator.SC_LOG_DIR_LOCATION=/var/log/jitsi -Djava.util.logging.config.file=/etc/jitsi/jicofo/logging.properties"

And in ‘sip-communicator.properties’ I found
org.jitsi.jicofo.BRIDGE_MUC=JvbBrewery@internal.auth.192.168.1.25

#13

Hi,

I’ve updated to the latest version and now I have the same behaviour and problems.

Anyone who can give me a hint where to look into?

1 Like
#14

get it working again with a complete reinstall.

#15

Same problem here. I have Ubuntu 18.04, installed Jitsi-meet with the repository 10 days ago, and it stopped working after an update last Friday (7 jitsi-meet packages were updated) and I restarted the server.

I don’t see either jetty running:
sudo ss -tapnu | grep 8080

When I was advised of the problem, I checked, verified that there was still available upgrades of the seven packages, thought it could solve the problem, execute the update, restarded but same problem.

Here is the content of the last updates in /var/log/apt/history.log:
Start-Date: 2020-04-10 18:03:31
Commandline: apt dist-upgrade
Upgrade: jitsi-meet-turnserver:amd64 (1.0.3928-1, 1.0.3969-1), jitsi-videobridge2:amd64 (2.1-157-g389b69ff-1, 2.1-164-gfdce823f-1), jicofo:amd64 (1.0-539-1, 1.0-541-1), jitsi-meet-web:amd64 (1.0.3928-1, 1.0.3969-1), jitsi-meet:amd64 (1.0.4335-1, 2.0.4384-1), jitsi-meet-web-config:amd64 (1.0.3928-1, 1.0.3969-1), jitsi-meet-prosody:amd64 (1.0.3928-1, 1.0.3969-1)
End-Date: 2020-04-10 18:03:45

Start-Date: 2020-04-12 17:05:04
Commandline: apt dist-upgrade
Upgrade: jitsi-meet-turnserver:amd64 (1.0.3969-1, 1.0.3992-1), jitsi-videobridge2:amd64 (2.1-164-gfdce823f-1, 2.1-169-ga28eb88e-1), jicofo:amd64 (1.0-541-1, 1.0-544-1), jitsi-meet-web:amd64 (1.0.3969-1, 1.0.3992-1), jitsi-meet:amd64 (2.0.4384-1, 2.0.4416-1), jitsi-meet-web-config:amd64 (1.0.3969-1, 1.0.3992-1), jitsi-meet-prosody:amd64 (1.0.3969-1, 1.0.3992-1)
End-Date: 2020-04-12 17:05:16

I think there was a problem in the last upgrades, and hope there is a mean to solve the problem without reinstalling.

Cheers !

#16

yes jetty (jvb) does not seem to run. I’d say that checking the videobridge config files that are indeed under /etc/jitsi/videobridge and the jvb log in /var/log/jitsi/jvb.log are the first things to do.

#17

Hi gpatel-fr,

Thanks for your answer. In jvblog, I don’t see something special, it even created a meeting room:

2020-04-13 18:31:16.493 INFO: [17] Videobridge.createConference#326: create_conf, id=1f7ac37fca3f7a9c gid=null logging=false
2020-04-13 18:31:16.512 INFO: [17] Health.doRun#294: Performed a successful health check in 19ms. Sticky failure: false
2020-04-13 18:31:26.513 INFO: [17] Videobridge.createConference#326: create_conf, id=116dfa3fb946e5d8 gid=null logging=false
2020-04-13 18:31:26.518 INFO: [17] Health.doRun#294: Performed a successful health check in 6ms. Sticky failure: false
2020-04-13 18:31:36.518 INFO: [17] Videobridge.createConference#326: create_conf, id=f7bd295a3fb266cb gid=null logging=false
2020-04-13 18:31:36.524 INFO: [17] Health.doRun#294: Performed a successful health check in 6ms. Sticky failure: false
2020-04-13 18:31:46.524 INFO: [17] Videobridge.createConference#326: create_conf, id=c7c1bf56a108875e gid=null logging=false
2020-04-13 18:31:46.530 INFO: [17] Health.doRun#294: Performed a successful health check in 6ms. Sticky failure: false

I also verified videobridge config, and it seems correct, it is something like that, with JVB_HOSTNAME being the FDQN of my server and JVB_HOST empty:

# Jitsi Videobridge settings

# sets the XMPP domain (default: none)
JVB_HOSTNAME=jitsi.example.com

# sets the hostname of the XMPP server (default: domain if set, localhost otherwise)
JVB_HOST=
#18

I just revewed the install process on the Youtube Jitsi web page, and they clearly states that yu have three chioces, uses Jetty, or install nginx or apache which will act as reverse proxy pour Jitsi-Meet.
I Installed nginx in the install process, as other documentations on the web suggestts (and it is my normal web server), so perhaps it is normal that I don’t hace Jetty listening on port 80, and the problem is elsewhere ?

In jcofo.log, I do see some warning and severe lines:

Jicofo 2020-04-13 17:56:15.522 WARNING: [27] org.jitsi.jicofo.bridge.BridgeSelector.log() No pub-sub node mapped for jvbbrewery@internal.auth.rendez-vous.c2n.u-psud.fr/5e41855a-f9
Jicofo 2020-04-13 17:56:15.523 INFO: [27] org.jitsi.jicofo.bridge.Bridge.log() Setting max total packet rate of 50800.0
Jicofo 2020-04-13 17:56:15.523 INFO: [27] org.jitsi.jicofo.bridge.Bridge.log() Setting average participant packet rate of 500
Jicofo 2020-04-13 17:56:15.529 INFO: [27] org.jitsi.jicofo.bridge.BridgeSelector.log() Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.rendez-vous.c2n.u-psud.fr/5e41855
Jicofo 2020-04-13 17:56:15.548 INFO: [41] org.jitsi.jicofo.bridge.JvbDoctor.log() Scheduled health-check task for: jvbbrewery@internal.auth.rendez-vous.c2n.u-psud.fr/5e41855a-f97c
Jicofo 2020-04-13 17:56:43.152 INFO: [31] org.jitsi.jicofo.ComponentsDiscovery.log() New component discovered: focus.rendez-vous.c2n.u-psud.fr, null
Jicofo 2020-04-14 00:01:19.650 SEVERE: [40] org.jitsi.xmpp.component.ComponentBase.log() Ping timeout for ID: ckzxP-21950
Jicofo 2020-04-14 00:02:26.269 WARNING: [57] org.jitsi.xmpp.component.ComponentBase.log() PROCESSING TIME LIMIT EXCEEDED - it took 3337ms to process: <iq id="ckzxP-22009" type="re

For information, I removed the jitsi-meet packages, and reinstall them afterwards, but to no avail, the problem is still present, no web connexion “connexion failed”.

#19

maybe this threads helps:

#20

I think that with recent versions it is not longer true that you can use jetty as only web server; jetty still exists and runs but it is mandatory to proxy it with nginx. Jetty should certainly NOT listen on port 80, but it listens on port 8080 on my config. I think this port 8080 is only used for REST api…

You can check more precisely the presence of jitsi components by

ps fauxww | grep prosody → PID of prosody (the XMPP / Jabber server)

sudo ss -tapnu | grep PID-of-prosody

you should get 3 lines,
1 for the port 5222 → jvb
1 for the port 5347 → jicofo
1 for the port 5222 → jicofo

I think that in your case /var/log/jitsi/jvb.log is more relevant than jicofo.log