just updated to: dev-erlang/p1_mysql-1.0.22 dev-erlang/xmpp-1.7.0 dev-erlang/stun-1.2.10 net-im/ejabberd-23.10 After update, ejabberd will not start: minbar:root:~:11 # ejabberdctl foreground {{bad_heart_flag,log_rotate_size},{heart,check_start_heart,[]}} System process <0.0.0> terminated: {badarg,[{erlang,exit,[false,kill],[{error_info,#{module=>erl_erts_errors}}]},{init,kill_em,1,[]},{init,clear_system,3,[]},{init,new_kernelpid,3,[]},{init,boot_loop,2,[]}]} (no logger present) unexpected logger message: {log,error,"Error in process ~p with exit value:~n~p~n",[<0.0.0>,{badarg,[{erlang,exit,[false,kill],[{error_info,#{module=>erl_erts_errors}}]},{init,kill_em,1,[]},{init,clear_system,3,[]},{init,new_kernelpid,3,[]},{init,boot_loop,2,[]}]}],#{error_logger=>#{emulator=>true,tag=>error},pid=><0.0.0>,time=>1702306230595497,gl=><0.0.0>}} Crash dump is being written to: /var/log/ejabberd/erl_crash_20231211-095030.dump...done I had to roll back to: =dev-erlang/xmpp-1.6.2 =dev-erlang/stun-1.2.7 =net-im/ejabberd-23.04 p1-mysql seems to be fine.
This is apparently an upstream bug in ejabberdctl and can be fixed by commenting out `EJABBERD_OPTS` in `ejabberdctl.cfg`
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2f272ce2acf66bb2471cd5ce9fd4756336b36864 commit 2f272ce2acf66bb2471cd5ce9fd4756336b36864 Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2023-12-11 15:42:44 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2023-12-11 15:43:50 +0000 net-im/ejabberd: backport fixes for ejabberdctl Thanks to Holger Weiß for mentioning the patches to backport. Closes: https://bugs.gentoo.org/919711 Signed-off-by: Florian Schmaus <flow@gentoo.org> net-im/ejabberd/Manifest | 2 ++ .../ejabberd/{ejabberd-23.10.ebuild => ejabberd-23.10-r1.ebuild} | 7 +++++++ 2 files changed, 9 insertions(+)
