![]() ![]() The strange thing that the logs still mention :1883 after the modifications I've made in ejabberd.yml conf file. To bypass permanently this warning, add to ejabberdctl.cfg the line:Įrlang/OTP 21 Įshell V10.3.4 (abort with 17:21:41.774 Changed loghwm of /opt/ejabberd/logs/error.log to 100ġ7:21:41.774 Changed loghwm of /opt/ejabberd/logs/ejabberd.log to 100ġ7:21:41.851 Loading configuration from /opt/ejabberd/conf/ejabberd.ymlġ7:21:42.456 Failed to open socket at :1883 for mod_mqtt: address family not supported by protocol familyġ7:21:42.456 Supervisor ejabberd_listener had child ` To exit this LIVE mode and stop ejabberd, press: See 'systemctl status rvice' and 'journalctl' for details. I'm disowning so someone else can take over, since I've migrated to using the ejabberd package in community. It fails during package() at make install in the copyfiles step in fastxml/priv/lib. Additional info: package version(s) Name : ejabberd Version : 2.1.11-4 systemctl start info: Job for rvice failed. Updated to build against current master branch. Please be extremely cautious with your actions,Īnd exit immediately if you are not completely sure. systemd service script fails to start ejabberd. ![]() You can interact with the ejabberd node if you know how to use it. So, thinking that everything was grand since live mode worked, I ran 'systemctl enable ejabberd' and rebooted the machine to test the service, but when it came back up, chat was not working, /var/log/ejabberd/ was devoid of new log output, and I didn't see the 'beam' process running. Please be extremely cautious with your actions, and exit immediately if you are not completely sure. You can interact with the ejabberd node if you know how to use it. All log messages will be shown in the command shell. IMPORTANT: ejabberd is going to start in LIVE (interactive) mode.Īll log messages will be shown in the command shell. IMPORTANT: ejabberd is going to start in LIVE (interactive) mode. ![]() And here comes the problem that 3 days now I can't solve, I get this error in the terminal: ![]()
0 Comments
Leave a Reply. |