- NO CONFIG FILE WITH EJABBERD INSTALLATION DEBIAN JESSIE INSTALL
- NO CONFIG FILE WITH EJABBERD INSTALLATION DEBIAN JESSIE UPDATE
May 03 14:03:46 systemd: Starting A distributed, fault-tolerant Jabber/XMPP server. See "systemctl status rvice" and "journalctl -xeu rvice" for details.
Job for rvice failed because the service did not take the steps required by its unit configuration.
NO CONFIG FILE WITH EJABBERD INSTALLATION DEBIAN JESSIE INSTALL
Thanks! I'm gona try remove and remove ejabberd and install it again. Or a workaround that some people can use to get their ejabberd servers running. I may try this later if I get some free time to mess with it.Īnyway, hopefully this provides some clue that somebody can use to diagnose exactly what is happening with this. The whole "building from source" thing *might* be a red herring. But again, this doesn't explain why it doesn't Just Work right from the jump.Īn interesting experiment would be to just install, uninstall, and then reinstall the distro packaged version and see if that has the same effect. Installing the distro packages is altering some setting (selinux related, maybe?) that affects this. Installing the distro packages installs some transitive dependency that is needed and is otherwise missing when installing from source (but this doesn't explain why the packaged binaries don't just work from the get to)Ģ. My hunch is that one of two things is happening here:ġ. Install and then remove the distro ejabberd packages I've seen this exact pattern play out on both F34 and F35 and it seems completely reproducible so far.ġ. In my case, because I'm using letsencrypt certs for TLS, and not running ejabberd as root, I had to arrange for ejabberd user to be able to read the certs from the /etc/letsencrypt/live/xxx directory tree.Īnyway, after doing all that, ejabberd now starts normally. Go back to your ejabberd build directory and do "make install" Do "rpm -erase ejabberd & rpm -erase ejaberd-selinux"ĩ. Do a "make uninstall" to remove the ejabberd you just installed (I know, this sounds stupid, but it does work for me)Ĩ. Change ownership of the various files and directories that ejabberd needs, so that they are owned by ejabberd:ejabberdĦ. Copy your systemd unit file into place and make any needed tweaks to it, and also configure your ejabberd.yml as needed.ĥ. Clone the upstream git repo, configure, build, and "make install" ejabberd. Create an "ejabberd" group, and an "ejabberd" user (with the user having the group as their sole group)ģ. Spin up the server without the ejabbberd packages from the rpm reposĢ. I'm pretty sure some of these steps aren't strictly *required* and are just artifacts how how I prefer to configure things, but I'll lay it out in detail just in case one of these details does matter.ġ. Here's how I got ejabberd to work on both.
I have NO idea why this works, but it is reproducible on both Fedora 34 and Fedora 35.
NO CONFIG FILE WITH EJABBERD INSTALLATION DEBIAN JESSIE UPDATE
OK, another quick update and a (sort of) workaround.
0 kommentar(er)
