The strange thing that the logs still mention :1883 after the modifications I've made in ejabberd.yml conf file. Open a command prompt and run the following command (taken from the postinstall.bat) in the bin.
Package: ejabberd Maintainer for ejabberd is Ejabberd Packaging Team <> Source for ejabberd is src:ejabberd ( PTS, buildd, popcon ). Run the file manual.vbs and you will get a registry error.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 ` ejabberd: fails to start via systemd service file. Thank you -Ido stativ commented on 20:10 (UTC) ejabberd-svn merged into ejabberd-git (development moved to git). To exit this LIVE mode and stop ejabberd, press: NOTE: To request changes to this package, please submit a pull request to the GitHub repository at Otherwise, open a GitHub issue. Please be extremely cautious with your actions,Īnd exit immediately if you are not completely sure.
#Arch linux ejabberd start of supervisor failed how to
You can interact with the ejabberd node if you know how to use it. /rebates/&252farch-linux-ejabberd-start-of-supervisor-sl-failed. IMPORTANT: ejabberd is going to start in LIVE (interactive) mode.Īll log messages will be shown in the command shell. And here comes the problem that 3 days now I can't solve, I get this error in the terminal:
0 kommentar(er)
