Ejabberd improvements + ejabberd 20.03

Feature
21

@stephdl: Please revert for introduce: “20.03” to “20.01”.

22

never heard about git cherry-pick ?

23

Do not cache authentication (introduced by 20.03) -> Do not cache authentication (introduced by 20.01)

It was introduced in 20.01 not in 20.03.

24

I cannot cherry-pick your changes some have been rejected until NS 7.8 has been introduced

26

Ready for testing: https://github.com/NethServer/dev/issues/6108

Please also have a look to the logrotate part :wink:

27

Thanks!

Like I have noted previously here: Ejabberd improvements + ejabberd 20.03
-> https://github.com/processone/ejabberd/commit/e4a8afb15d6c995b294a60ed150b86775e2f6805

Have you seen for “loglevel: info”

28

from your link we use the info level

Screenshot (27)

but because we are not humans but developers we prefer the machine language :smiley:

check the /etc/ejabberd/ejabberd.yml

loglevel: 4
log_rotate_count: 0

since it is a default option we could even remove it, or not :stuck_out_tongue:

29

I did some more ejabberd tests on my homeserver, a VPS and a test VM and it’s working as expected.

  • Ejabber service starts and runs without error
  • Logrotate works
  • users can chat and create rooms
  • OMEMO encryption still working
  • LDAP/AD working
  • uploads working

Tested with following clients

  • Gajim
  • Psi+
  • XMPPJabberClient
  • Xabber

I found one warning:

[warning] <0.359.0>@mod_mam:start:98 Mnesia backend for mod_mam is not recommended: it's limited to 2GB and often gets corrupted when reaching this limit. SQL backend is recommended. Namely, for small servers SQLite is a preferred choice because it's very easy to configure.

Can a chat archive reach 2GB when uploads are not stored?
I don’t know if it’s worth the effort but when we have an ejabberd database we may think about storing things from other ejabberd modules too…
It works with postgresql and mariadb102.

nethserver-postgres:

sudo -u postgres psql
CREATE USER ejabberd WITH CREATEDB PASSWORD 'SECRET';
CREATE DATABASE ejabberd OWNER ejabberd;
\q
cat /opt/ejabberd-20.03/lib/ejabberd-20.03/priv/sql/pg.sql | sudo -u ejabberd psql ejabberd

nethserver-mariadb102:

echo "CREATE DATABASE ejabberd;" | mysql102 
echo "GRANT ALL ON ejabberd.* TO 'ejabberd'@'localhost' IDENTIFIED BY 'SECRET';" | mysql102
mysql102 -D ejabberd < /opt/ejabberd-20.03/lib/ejabberd-20.03/priv/sql/mysql.sql

Copy template fragment to edit as template-custom:

mkdir -p /etc/e-smith/templates-custom/etc/ejabberd/ejabberd.yml/
cp /etc/e-smith/templates/etc/ejabberd/ejabberd.yml/85Modules /etc/e-smith/templates-custom/etc/ejabberd/ejabberd.yml/

Edit begin of /etc/e-smith/templates-custom/etc/ejabberd/ejabberd.yml/85Modules to fit to your DB engine:

sql_type: pgsql
sql_port: 5432
#sql_type: mysql
#sql_port: 3312
sql_server: "localhost"
sql_database: "ejabberd"
sql_username: "ejabberd"
sql_password: "SECRET"

and edit the db_type in mod_mam part:

  mod_mam:
    db_type: sql

Apply and there should be no warning anymore.

signal-event nethserver-ejabberd-update

Source:

https://docs.ejabberd.im/admin/configuration/database-ldap/

4 Likes
30

It is a design choice, the upgrade of ejabberd with mariadb it is just a pain, each version brings a lot of sql updates to the db.

If you have a lot of users, go to mysql or use Mnesia

2 Likes
31

Thank you for your test, it’s really appreciated!

3 Likes
32

still brave are needed

1 Like
33

Little question: My changes will be in 7.8?

34

A post was split to a new topic: Upgrade ejabberd to version 22.05