Prosody.err (No main room)

Hi,

I noticed in prosody.err file many errors :

Mar 17 09:55:12 (domain):muc_lobby_rooms error No main room(room_name)@lobby.(domain)) for 4iqcuehxc426dfrc@guest.-domain-!

Anybody knows something about it ?

Regards,
noje

What does your prosody config look like?

I attached my prosody cfg :

prosody_cfg.txt (3.3 KB)

Config looks ok. What Prosody version are you running?

My prosody versions :

jitsi-meet-prosody/now 1.0.5675-1
prosody-modules/focal,now 0.0~hg20200128.09e7e880e056+dfsg-1
prosody/focal,now 0.11.4-1

Do you know something about my problem ?

No, sorry. Maybe @damencho can spot something?

Prosody 0.11.4 is rather old. Perhaps get latest prosody-0.11 from prosody package repo?

Make sure not to install 0.12 for now.

Hi,

I’m able to install only 0.12.0-1 version :

root@/etc/apt/sources.list.d# apt list --upgradable | grep prosody

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

prosody/unknown 0.12.0-1~focal1 amd64 [upgradable from: 0.11.4-1]

Regards,
noje

Install prosody-0.11 package

My ubuntu is not able to find and install any 0.11 prosody versions. I don’t know why. I can upgrade only to version 0.12.

You are probably not using prosody package repository.

root@ubuntu:~# echo deb Prosody IM Package Repository $(lsb_release -sc) main | sudo tee -a /etc/apt/sources.list
deb Prosody IM Package Repository focal main
root@ubuntu:~#
root@ubuntu:~# wget https://prosody.im/files/prosody-debian-packages.key -O- | sudo apt-key add -
–2022-03-31 17:00:08-- https://prosody.im/files/prosody-debian-packages.key
Resolving prosody.im (prosody.im)… 46.43.15.35, 2001:41c9:1:424::35
Connecting to prosody.im (prosody.im)|46.43.15.35|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 1686 (1,6K) [application/octet-stream]
Saving to: ‘STDOUT’

  •                                         100%[================================================================================================>]   1,65K  --.-KB/s    in 0s
    

2022-03-31 17:00:08 (152 MB/s) - written to stdout [1686/1686]

OK
root@ubuntu:~#
root@ubuntu:~# sudo apt update
Stary:1 Prosody IM Package Repository focal InRelease
Stary:2 Index of /ubuntu focal InRelease
Pobieranie:3 Index of /ubuntu focal-updates InRelease [114 kB]
Pobieranie:4 Index of /ubuntu focal-backports InRelease [108 kB]
Pobieranie:5 Index of /ubuntu focal-security InRelease [114 kB]
Pobieranie:6 Index of /ubuntu focal-updates/main amd64 Packages [1 701 kB]
Pobieranie:7 Index of /ubuntu focal-backports/universe amd64 c-n-f Metadata [808 B]
Pobieranie:8 Index of /ubuntu focal-security/main amd64 c-n-f Metadata [9 876 B]
Pobieranie:9 Index of /ubuntu focal-security/universe amd64 Packages [695 kB]
Pobrano 2 742 kB w 2s (1 191 kB/s)
12 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
root@ubuntu:~#
root@ubuntu:~# apt-get upgrade prosody=0.11.13
E: Version “0.11.13” for “prosody” has not been found

apt install prosody-0.11.

root@ubuntu:~# apt install prosody-0.11
Reading package list … Done
Building a tree.
Change Status Information … Done
Some packages could not be installed. This could mean
that the first recovery or the distribution of an unstable,
in which some packages have not yet been used or migrated
from the Incoming directory.
Information can help:

The kits have the same features:
prosody-0.11: In conflict with: prosody
E: Could not reach problems, corrupt packages stopped.
root@ubuntu:~#

hum, no idea
you can download this https://packages.prosody.im/debian/pool/main/p/prosody/prosody_0.11.13-1~focal1_amd64.deb
and do dpkg -i prosody_0.11.13-1~focal1_amd64.deb

Yep, It works. I will test a new prosody version. Thanks :slight_smile:

I have the same problem on prosody in 0.11.13-1 version. I noticed that these errors appear when I have more than about 600 simultaneous users connected to conferences.

Have you monitored the server? What is the cpu usage of the prosody process at that time?
Are you using bosh or websockets? You may moving prosody to epoll.
There are a number of threads in the forum for optimizing prosody performance.

  • I have monitored this server, it’s not problem with performance :

  • I use websockets

  • I have epoll configuration : network_backend = “epoll”