Procedure for Debian apt-get upgrade

[brmdamon]

I successfully installed Jitsi-meet on a Debian server on 2020/04/01 using the procedure described at https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md . Now I want to upgrade using the latest stable Debian packages.

Common sense tells me that I should stop the daemons, do the upgrade, and then start them again. But, I am not sure how many daemons there and how to stop/start them.

Also, there have been a number of posts by people who have upgraded only to find that the upgraded installation does not work. It would be desirable to be able to upgrade routinely without having to trouble-shoot and hack after each upgrade.

Is this documented somewhere? Failing that, can someone advise? If someone can do that, I would be willing to write a Github wiki page describing the procedure (after testing it!).

Here are links to some reports of upgrade problems:

Jigasi stopped working after upgrading

Hello, I’m using your ubuntu repository on my ubuntu 18.04 server. When upgrading jigasi from 1.0.-244 to 1.1-38-g8f3c241-1, I’m unable to join a conference using a phone. I get fast busy and I get this message in the error logs: 2020-01-07 14:24:30.964 INFOS: [171] org.jitsi.jigasi.SipGateway.incomingCallReceived().188 Incoming call received… 2020-01-07 14:24:30.966 INFOS: [172] org.jitsi.jigasi.SipGatewaySession.run().1281 [ctx=15784250709641827059593] Wait thread cancelled 2020-01-07 14:…

Jitsi broken after Debian upgrade - Could not reserve enough space for 3145728KB object heap

Hi, I previously had a working installation of Jitsi-meet on my Debian 10 32-bit VPS with 1vCPU and 1GB of RAM. I performed a dist-upgrade the other day and installed the latest version of Jitsi-meet and now if you try to start a meet, it just says “Unfortunately, something went wrong”. Looking into the logs I get: jvb.log OpenJDK Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. Error occurred during initialization of…

Apt full-upgrade broke jitsi-meet setup (SSL certificate problem?)

Hi, Yesterday, an unfortunate “apt full-upgrade” broke our Jitsi-meet server running Debian 10 and Apache2. I suspect a SSL certificate issue (see prosody.err, systemctl status prosody and /etc/prosody/conf.avail/meet.example.com.cfg.lua). A user can create a call, but when another user joins, the first user get disconnected and a message “Unfortunately something went wrong we’re trying to fix this” with a reconnect countdown. The second user is unaware of this. He just pops up in a call alone…

Debian upgrade error?

Dear All, Probably in line with other recent reports here, my debian buster install did break upon the following update: jicofo/stable 1.0-508-1 -> 1.0-539-1 amd64 jitsi-meet-prosody/stable 1.0.3729-1 -> 1.0.3928-1 all jitsi-meet-web-config/stable 1.0.3729-1 -> 1.0.3928-1 all jitsi-meet-web/stable 1.0.3729-1 -> 1.0.3928-1 all jitsi-meet/stable 1.0.4101-1 -> 1.0.4335-1 all The log file used by nginx gets filled with entries like this (where 192.168.1.78 is my firewall running HAProxy): 20…

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

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/ji…

[brmdamon]

I got no replies to this post so I just did it!

su
cd ~
apt-get update
apt-get upgrade

(Of course this upgrades everything, not just the Jitsi-related packages. That’s fine in this case since the server is a virtual cloud machine dedicated to the Jitsi server function.)

Then I connected with two different devices. Jitsi appeared to be working.

To be sure that the latest versions were executing I then did

shutdown now -r

After reboot, again connected with two devices. Jitsi appeared to be working.

For reference, the packages downloaded from the Jitsi apt server were:

Get:111 https://download.jitsi.org stable/ jitsi-videobridge2 2.1-183-gdbddd169-1 [33.2 MB]
Get:112 https://download.jitsi.org stable/ jitsi-meet 2.0.4468-1 [2864 B]
Get:113 https://download.jitsi.org stable/ jicofo 1.0-549-1 [49.6 MB]
Get:114 https://download.jitsi.org stable/ jitsi-meet-web 1.0.4025-1 [5926 kB]
Get:115 https://download.jitsi.org stable/ jitsi-meet-web-config 1.0.4025-1 [13.5 kB]
Get:116 https://download.jitsi.org stable/ jitsi-meet-prosody 1.0.4025-1 [34.7 kB]

Hope this is helpful to someone.