Update problem to latest (2022-06-17)

Hello,

maybe somebody can help me. I’m running a small jitsi server (with JWT) on debian 10 and want to update jitsi. The last version is from May 2022.

When I try that, I got the following message. Why is that?

The following packages have been kept back:
jicofo jitsi-meet jitsi-meet-prosody jitsi-meet-web jitsi-meet-web-config jitsi-videobridge2 linux-image-amd64 prosody

Any hints what I can do?

Thanks in advance
Daniel

Did you set these packages as hold?

apt-mark showhold

Hello emrah,

when I run this command there is no output.

Best, Daniel

In some other threads I read about prosody. My version is ( apt list -a prosody ):

prosody/oldstable 0.12.0-1~buster1 amd64 [upgradable from: 0.11.13-1~buster1]
prosody/now 0.11.13-1~buster1 amd64 [installed,upgradable to: 0.12.0-1~buster1]
prosody/buster-backports 0.11.9-1~bpo10+1 amd64
prosody/oldstable,oldstable 0.11.2-1+deb10u4 amd64

Can you share the whole output of apt-get?

apt-get update ?

Get:1 Index of /debian-security buster/updates InRelease [65.4 kB]
Get:2 Index of /debian buster-backports InRelease [46.7 kB]
Hit:3 Index of /debian buster InRelease
Get:4 Index of /debian buster-updates InRelease [51.9 kB]
Get:5 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B]
Get:6 https://packages.grafana.com/oss/deb stable InRelease [12.1 kB]
Get:7 InfluxDB Repository buster InRelease [4,737 B]
Get:8 Prosody IM Package Repository buster InRelease [7,392 B]
Get:9 Index of /debian buster-updates/main Sources.diff/Index [11.6 kB]
Get:10 Index of /debian buster-updates/main amd64 Packages.diff/Index [11.6 kB]
Get:11 Index of /debian buster-updates/main Sources 2022-05-28-1407.13.pdiff [239 B]
Get:12 Index of /debian buster-updates/main Sources 2022-06-11-2007.01.pdiff [185 B]
Get:13 Index of /debian buster-updates/main amd64 Packages 2022-05-28-1407.13.pdiff [1,094 B]
Get:14 Index of /debian buster-updates/main amd64 Packages 2022-06-11-2007.01.pdiff [169 B]
Get:12 Index of /debian buster-updates/main Sources 2022-06-11-2007.01.pdiff [185 B]
Get:14 Index of /debian buster-updates/main amd64 Packages 2022-06-11-2007.01.pdiff [169 B]
Get:15 Index of /debian-security buster/updates/main Sources [237 kB]
Get:16 Index of /debian-security buster/updates/main amd64 Packages [328 kB]
Get:17 Index of /debian-security buster/updates/main Translation-en [178 kB]
Get:18 Index of /debian buster-backports/main amd64 Packages.diff/Index [27.8 kB]
Get:19 Index of /debian buster-backports/main Translation-en.diff/Index [27.8 kB]
Hit:20 JFrog buster InRelease
Get:21 Index of /debian buster-backports/main amd64 Packages 2022-06-07-1410.28.pdiff [409 B]
Get:22 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,102 B]
Get:23 Index of /debian buster-backports/main amd64 Packages 2022-06-07-2014.25.pdiff [1,072 B]
Get:24 Index of /debian buster-backports/main amd64 Packages 2022-06-09-2008.52.pdiff [825 B]
Get:24 Index of /debian buster-backports/main amd64 Packages 2022-06-09-2008.52.pdiff [825 B]
Get:25 https://packages.grafana.com/oss/deb stable/main amd64 Packages [31.2 kB]
Get:26 Index of /debian buster-backports/main Translation-en 2022-06-07-1410.28.pdiff [374 B]
Get:27 InfluxDB Repository buster/stable amd64 Packages [1,259 B]
Get:28 https://download.jitsi.org stable/ InRelease [1,882 B]
Get:29 Index of /debian buster-backports/main Translation-en 2022-06-09-2008.52.pdiff [778 B]
Get:29 Index of /debian buster-backports/main Translation-en 2022-06-09-2008.52.pdiff [778 B]
Get:30 Prosody IM Package Repository buster/main amd64 Packages [13.8 kB]
Get:31 https://download.jitsi.org stable/ Packages [66.4 kB]
Fetched 1,132 kB in 1s (757 kB/s)
Reading package lists… Done

apt-get dist-upgrade -d

Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following package was automatically installed and is no longer required:
libssl-dev
Use ‘apt autoremove’ to remove it.
The following NEW packages will be installed:
libunbound8 linux-image-4.19.0-20-amd64 lua-basexx lua-bit32 lua-cjson lua-luaossl lua-posix lua-readline lua-unbound
The following packages will be upgraded:
dpkg google-chrome-stable grafana jicofo jitsi-meet jitsi-meet-prosody jitsi-meet-tokens jitsi-meet-turnserver jitsi-meet-web
jitsi-meet-web-config jitsi-videobridge2 libcups2 libdpkg-perl libldap-2.4-2 libldap-common libpq5 libssl-dev libssl1.1 libxml2
linux-image-amd64 openssl prosody rsyslog telegraf tzdata
25 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 338 MB of archives.
After this operation, 269 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 Index of /debian-security buster/updates/main amd64 dpkg amd64 1.19.8 [2,210 kB]
Get:2 Index of /debian buster/main amd64 lua-basexx all 0.3-2 [3,870 B]
Get:3 Index of /debian buster/main amd64 lua-cjson amd64 2.1.0+dfsg-2.1 [17.5 kB]
Get:4 Index of /debian buster-updates/main amd64 tzdata all 2021a-0+deb10u5 [266 kB]
Get:5 http://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-stable amd64 102.0.5005.115-1 [84.8 MB]
Get:6 Index of /debian buster/main amd64 libunbound8 amd64 1.9.0-2+deb10u2 [462 kB]
Get:7 Index of /debian buster/main amd64 linux-image-4.19.0-20-amd64 amd64 4.19.235-1 [48.5 MB]
Get:8 InfluxDB Repository buster/stable amd64 telegraf amd64 1.23.0-1 [39.6 MB]
Get:9 Index of /debian-security buster/updates/main amd64 rsyslog amd64 8.1901.0-1+deb10u2 [658 kB]
Get:10 Index of /debian-security buster/updates/main amd64 libcups2 amd64 2.2.10-6+deb10u6 [325 kB]
Get:11 Index of /debian-security buster/updates/main amd64 libssl-dev amd64 1.1.1n-0+deb10u2 [1,807 kB]
Get:12 https://packages.grafana.com/oss/deb stable/main amd64 grafana amd64 9.0.0 [80.0 MB]
Get:13 Index of /debian-security buster/updates/main amd64 libssl1.1 amd64 1.1.1n-0+deb10u2 [1,551 kB]
Get:14 Index of /debian-security buster/updates/main amd64 openssl amd64 1.1.1n-0+deb10u2 [855 kB]
Get:15 Index of /debian-security buster/updates/main amd64 libldap-common all 2.4.47+dfsg-3+deb10u7 [90.1 kB]
Get:16 Index of /debian-security buster/updates/main amd64 libldap-2.4-2 amd64 2.4.47+dfsg-3+deb10u7 [224 kB]
Get:17 Index of /debian-security buster/updates/main amd64 libxml2 amd64 2.9.4+dfsg1-7+deb10u4 [689 kB]
Get:18 Index of /debian-security buster/updates/main amd64 libdpkg-perl all 1.19.8 [1,415 kB]
Get:19 Index of /debian-security buster/updates/main amd64 libpq5 amd64 11.16-0+deb10u1 [172 kB]
Get:20 https://download.jitsi.org stable/ jitsi-videobridge2 2.2-9-g8cded16e-1 [38.1 MB]
Get:21 Prosody IM Package Repository buster/main amd64 prosody amd64 0.12.1-1~buster1 [401 kB]
Get:22 Prosody IM Package Repository buster/main amd64 lua-luaossl amd64 20200709-1prosody1~buster1 [118 kB]
Get:23 Prosody IM Package Repository buster/main amd64 lua-readline amd64 2.9-1prosody1 [14.2 kB]
Get:24 Prosody IM Package Repository buster/main amd64 lua-unbound amd64 0.5-2prosody1 [11.4 kB]
Get:25 Index of /debian buster/main amd64 linux-image-amd64 amd64 4.19+105+deb10u15 [8,648 B]
Get:26 Index of /debian buster/main amd64 lua-bit32 amd64 5.3.0-3 [10.1 kB]
Get:27 Index of /debian buster/main amd64 lua-posix amd64 33.4.0-3 [125 kB]
Get:28 https://download.jitsi.org stable/ jitsi-meet 2.0.7439-1 [3,332 B]
Get:29 https://download.jitsi.org stable/ jicofo 1.0-900-1 [20.6 MB]
Get:30 https://download.jitsi.org stable/ jitsi-meet-web 1.0.6260-1 [14.8 MB]
Get:31 https://download.jitsi.org stable/ jitsi-meet-web-config 1.0.6260-1 [25.0 kB]
Get:32 https://download.jitsi.org stable/ jitsi-meet-prosody 1.0.6260-1 [63.1 kB]
Get:33 https://download.jitsi.org stable/ jitsi-meet-turnserver 1.0.6260-1 [6,128 B]
Get:34 https://download.jitsi.org stable/ jitsi-meet-tokens 1.0.6260-1 [4,288 B]
Fetched 338 MB in 5s (69.5 MB/s)
Download complete and in download only mode

Seems like there is no problem. The following command should work

apt-get dist-upgrade

But an upgrade can break the system. Do you have a recovery plan in case things go wrong?

1 Like

Yes, snapshot is my best friend :slight_smile:

1 Like

Nope, these are the last lines:

Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet-tokens
jitsi-meet-turnserver
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have just tried to upgrade my test machine (Jitsi on Debian Buster), it’s completed without issue. The buster-backports repo is not in my sources.list. It may be related with a package coming from this repo but I’m not sure.

Hello emrah,
I got it working. Thanks for your help.

First I marked prosody:
apt-mark hold prosody

Than I updated the complete system:
sudo apt update && sudo apt upgrade -y

Now it seems to be uptodate:
dpkg -l | grep jitsi

ii jitsi-meet 2.0.7439-1
ii jitsi-meet-prosody 1.0.6260-1
ii jitsi-meet-tokens 1.0.6260-1
ii jitsi-meet-turnserver 1.0.6260-1
ii jitsi-meet-web 1.0.6260-1
ii jitsi-meet-web-config 1.0.6260-1
ii jitsi-videobridge2 2.2-9-g8cded16e-1

1 Like

But something must be wrong with your prosody package and you need to explore that, otherwise, it’s no telling what problems you may encounter. What version of Prosody do you currently run?

dpkg -s prosody | grep Version

Hi Freddie,
it is “Version: 0.11.13-1~buster1”.
Best, Daniel

I see you have a working backup of your system. Maybe take another snapshot now first, then go take a copy of your previous snapshot and try uninstalling all versions of Prosody. Once done, then reinstall latest Prosody version (should be 0.12…). Thereafter, try updating Jitsi. Let’s know how that goes.

Hi Freddie,

I took the snapshot with the working version of May.
After this I uninstalled and installed prosody following this tutorial:

After that I tried to update jitsi and got these errors:


A problem occurred while reading the config file /etc/prosody/prosody.cfg.lua

Error: /usr/share/lua/5.2/prosody/core/configmanager.lua:137: bad argument #2 to ‘format’ (number expected, got nil)

More help on configuring Prosody can be found at Configuring Prosody – Prosody IM
Good luck!


Component “focus.v2202004120448116637.ultrasrv.de” “client_proxy”


A problem occurred while reading the config file /etc/prosody/prosody.cfg.lua

Error: /usr/share/lua/5.2/prosody/core/configmanager.lua:137: bad argument #2 to ‘format’ (number expected, got nil)

More help on configuring Prosody can be found at Configuring Prosody – Prosody IM
Good luck!


dpkg: error processing package jitsi-meet-prosody (–configure):
installed jitsi-meet-prosody package post-installation script subprocess returned error exit status 1
Setting up libldap-2.4-2:amd64 (2.4.47+dfsg-3+deb10u7) …
dpkg: dependency problems prevent configuration of jitsi-meet-tokens:
jitsi-meet-tokens depends on jitsi-meet-prosody; however:
Package jitsi-meet-prosody is not configured yet.

dpkg: error processing package jitsi-meet-tokens (–configure):
dependency problems - leaving unconfigured
Setting up linux-image-amd64 (4.19+105+deb10u15) …
dpkg: dependency problems prevent configuration of jitsi-meet-turnserver:
jitsi-meet-turnserver depends on jitsi-meet-prosody; however:
Package jitsi-meet-prosody is not configured yet.

dpkg: error processing package jitsi-meet-turnserver (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody (= 1.0.6260-1); however:
Package jitsi-meet-prosody is not configured yet.

dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
Setting up libpq5:amd64 (11.16-0+deb10u1) …
Processing triggers for man-db (2.8.5-2) …
Processing triggers for menu (2.1.47+b1) …
Processing triggers for mime-support (3.62) …
Processing triggers for libc-bin (2.28-10+deb10u1) …
Processing triggers for systemd (241-7~deb10u8) …
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet-tokens
jitsi-meet-turnserver
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)

It looks like there’s something wrong with your main prosody config file. The log specifies the location of the error too.

Did you ever install the unstable package (prosody)?

Do you have this as the last line in your prosody.cfg.lua file?

Include "conf.d/*.cfg.lua"

Actually, why don’t you just share your prosody.cfg.lua file?

I don’t know if I ever installed an unstable version. If yes, not intentionally.

Here’s my prosody.cfg.lua or do you want the one in conf.avail ?

– Prosody XMPP Server Configuration

– Information on configuring Prosody can be found on our
– website at Configuring Prosody – Prosody IM

– Tip: You can check that the syntax of this file is correct
– when you have finished by running this command:
– prosodyctl check config
– If there are any errors, it will let you know what and where
– they are, otherwise it will keep quiet.

– Good luck, and happy Jabbering!

---------- Server-wide settings ----------
– Settings in this section apply to the whole server and are the default settings
– for any virtual hosts

– This is a (by default, empty) list of accounts that are admins
– for the server. Note that you must create the accounts separately
– (see Creating accounts – Prosody IM for info)
– Example: admins = { “user1@example.com”, “user2@example.net” }
admins = { }

– Enable use of libevent for better performance under high load
– For more information see: libevent – Prosody IM
–use_libevent = true

– Prosody will always look in its source directory for modules, but
– this option allows you to specify additional locations where Prosody
– will look for modules first. For community modules, see https://modules.prosody.im/
–plugin_paths = {}

– This is the list of modules Prosody will load on startup.
– It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
– Documentation for bundled modules can be found at: Prosody Modules – Prosody IM
modules_enabled = {

– Generally required
“roster”; – Allow users to have a roster. Recommended :wink:
“saslauth”; – Authentication for clients and servers. Recommended if you want to log in.
“tls”; – Add support for secure TLS on c2s/s2s connections
“dialback”; – s2s dialback support
“disco”; – Service discovery

– Not essential, but recommended
“carbons”; – Keep multiple clients in sync
“pep”; – Enables users to publish their avatar, mood, activity, playing music and more
“private”; – Private XML storage (for room bookmarks, etc.)
“blocklist”; – Allow users to block communications with other users
“vcard4”; – User profiles (stored in PEP)
“vcard_legacy”; – Conversion between legacy vCard and PEP Avatar, vcard
“limits”; – Enable bandwidth limiting for XMPP connections

– Nice to have
“version”; – Replies to server version requests
“uptime”; – Report how long server has been running
“time”; – Let others know the time here on this server
“ping”; – Replies to XMPP pings with pongs
“register”; – Allow users to register on this server using a client and change passwords
–“mam”; – Store messages in an archive and allow users to access it
–“csi_simple”; – Simple Mobile optimizations

– Admin interfaces
“admin_adhoc”; – Allows administration via an XMPP client that supports ad-hoc commands
–“admin_telnet”; – Opens telnet console interface on localhost port 5582

– HTTP modules
–“bosh”; – Enable BOSH clients, aka “Jabber over HTTP”
–“websocket”; – XMPP over WebSockets
–“http_files”; – Serve static files from a directory over HTTP

– Other specific functionality
–“groups”; – Shared roster support
–“server_contact_info”; – Publish contact information for this service
–“announce”; – Send announcement to all online users
–“welcome”; – Welcome users who register accounts
–“watchregistrations”; – Alert admins of registrations
–“motd”; – Send a message to users when they log in
–“legacyauth”; – Legacy authentication. Only used by some old clients and bots.
–“proxy65”; – Enables a file transfer proxy service which clients behind NAT can use
}

– These modules are auto-loaded, but should you want
– to disable them then uncomment them here:
modules_disabled = {
– “offline”; – Store offline messages
– “c2s”; – Handle client connections
– “s2s”; – Handle server-to-server connections
– “posix”; – POSIX functionality, sends server to background, enables syslog, etc.
}

– Disable account creation by default, for security
– For more information see Creating accounts – Prosody IM
allow_registration = false

– Force clients to use encrypted connections? This option will
– prevent clients from authenticating unless they are using encryption.

c2s_require_encryption = false

– Force servers to use encrypted connections? This option will
– prevent servers from authenticating unless they are using encryption.

s2s_require_encryption = true

– Force certificate authentication for server-to-server connections?

s2s_secure_auth = false

– Some servers have invalid or self-signed certificates. You can list
– remote domains here that will not be required to authenticate using
– certificates. They will be authenticated using DNS instead, even
– when s2s_secure_auth is enabled.

–s2s_insecure_domains = { “insecure.example” }

– Even if you disable s2s_secure_auth, you can still require valid
– certificates for some domains by specifying a list here.

–s2s_secure_domains = { “jabber.org” }

– Enable rate limits for incoming client and server connections

limits = {
c2s = {
rate = “10kb/s”;
};
s2sin = {
rate = “30kb/s”;
};
}

– Required for init scripts and prosodyctl
pidfile = “/var/run/prosody/prosody.pid”

– Select the authentication backend to use. The ‘internal’ providers
– use Prosody’s configured data storage to store the authentication data.

authentication = “internal_hashed”

– Select the storage backend to use. By default Prosody uses flat files
– in its configured data directory, but it also supports more backends
– through modules. An “sql” backend is included by default, but requires
– additional dependencies. See Data storage – Prosody IM for more info.

–storage = “sql” – Default is “internal”

– For the “sql” backend, you can uncomment one of the below to configure:
–sql = { driver = “SQLite3”, database = “prosody.sqlite” } – Default. ‘database’ is the filename.
–sql = { driver = “MySQL”, database = “prosody”, username = “prosody”, password = “secret”, host = “localhost” }
–sql = { driver = “PostgreSQL”, database = “prosody”, username = “prosody”, password = “secret”, host = “localhost” }

– Archiving configuration
– If mod_mam is enabled, Prosody will store a copy of every message. This
– is used to synchronize conversations between multiple clients, even if
– they are offline. This setting controls how long Prosody will keep
– messages in the archive before removing them.

archive_expires_after = “1w” – Remove archived messages after 1 week

– You can also configure messages to be stored in-memory only. For more
– archiving options, see mod_mam – Prosody IM

– Logging configuration
– For advanced logging see Logging – Prosody IM
log = {
info = “/var/log/prosody/prosody.log”; – Change ‘info’ to ‘debug’ for verbose logging
error = “/var/log/prosody/prosody.err”;
– “*syslog”; – Uncomment this for logging to syslog
– “*console”; – Log to the console, useful for debugging with daemonize=false
}

– Uncomment to enable statistics
– For more info see Statistics – Prosody IM
– statistics = “internal”

– Certificates
– Every virtual host and component needs a certificate so that clients and
– servers can securely verify its identity. Prosody will automatically load
– certificates/keys from the directory specified here.
– For more information, including how to use ‘prosodyctl’ to auto-import certificates
– (from e.g. Let’s Encrypt) see Certificates – Prosody IM

– Location of directory to find certificates in (relative to main config file):
certificates = “certs”

– HTTPS currently only supports a single certificate, specify it here:
–https_certificate = “/etc/prosody/certs/localhost.crt”

----------- Virtual hosts -----------
– You need to add a VirtualHost entry for each domain you wish Prosody to serve.
– Settings under each VirtualHost entry apply only to that host.

–VirtualHost “localhost”

–VirtualHost “example.com
– certificate = “/path/to/example.crt”

------ Components ------
– You can specify components to add hosts that provide special services,
– like multi-user conferences, and transports.
– For more information on components, see Components in Prosody – Prosody IM

—Set up a MUC (multi-user chat) room server on conference.example.com:
–Component “conference.example.com” “muc”
— Store MUC messages in an archive and allow users to access it
–modules_enabled = { “muc_mam” }

—Set up an external component (default component port is 5347)

– External components allow adding various services, such as gateways/
– transports to other networks like ICQ, MSN and Yahoo. For more info
– see: Components in Prosody – Prosody IM

–Component “gateway.example.com
– component_secret = “password”

Include “conf.d/*.cfg.lua”

# prosodyctl check config

Checking config…
Done.

All checks passed, congratulations!