JVB Connection refused on localhost:2222 after upgrade


At first, I could not upgrade

# apt update && apt upgrade -y && apt autoremove -y
Hit:1 http://ru.archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://ru.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:3 http://ru.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Get:4 http://ru.archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:5 http://packages.prosody.im/debian focal InRelease [7275 B]
Get:6 http://packages.prosody.im/debian focal/main amd64 Packages [1830 B]
Hit:7 https://download.jitsi.org stable/ InRelease
Fetched 345 kB in 1s (337 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
7 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  jicofo jitsi-meet jitsi-meet-prosody jitsi-meet-web jitsi-meet-web-config jitsi-videobridge2 prosody
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.

I upgraded the prosody by running apt install prosody and it installed prosody-0.12 which turned out incompatible. Then I ran apt install prosody-0.11 and now I have

prosodyctl about
Prosody 0.11 nightly build 182 (2022-12-14, c4b1b5cbc20b)

but now I have repeating errors in the JVB log:

JVB 2022-12-30 07:40:27.928 WARNING: [17] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$9#632: Error connecting:
org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [localhost:5222] (localhost/' failed because: java.net.ConnectException: Connection refused
        at org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:664)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:849)
        at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526)
        at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$9(MucClient.java:627)
        at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:833)
JVB 2022-12-30 07:40:32.103 WARNING: [23] [hostname=localhost id=shard] MucClient.setPresenceExtensions#459: Cannot set presence extension: not connected.

I read about it shows that prosody doesn’t work, however when I try to kick it off it indicates

# systemctl start prosody
Failed to start prosody.service: Unit prosody.service is masked.

How can I solve it? Thanks in advance.

What is the output for

dpkg -l "prosody*"
1 Like
# dpkg -l "prosody*"

| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                Version             Architecture Description
rc  prosody             0.12.2-1~focal1     amd64        Lightweight Jabber/XMPP server
ii  prosody-0.11        1nightly182-1~focal amd64        Lightweight Jabber/XMPP server
un  prosody-0.12        <none>              <none>       (no description available)
un  prosody-modules     <none>              <none>       (no description available)
un  prosody-trunk       <none>              <none>       (no description available)
un  prosody-xmpp-server <none>              <none>       (no description available)

Sorry for buzz, it resolved by

systemctl unmask prosody
systemctl start prosody