Oct 3 17:21:22 fwmg2 systemd: ejabberd.service: control process exited, code=exited status=1
Oct 3 17:21:22 fwmg2 systemd: Failed to start XMPP Server.
Oct 3 17:21:22 fwmg2 systemd: Unit ejabberd.service entered failed state.
Oct 3 17:21:22 fwmg2 esmith::event[22955]: Job for ejabberd.service failed because the control process exited with error code. See "systemctl status ejabberd.service" and "journalctl -xe" for details.
Oct 3 17:21:22 fwmg2 systemd: ejabberd.service failed.
Oct 3 17:21:22 fwmg2 esmith::event[22955]: [WARNING] restart service ejabberd failed!
Oct 3 17:21:22 fwmg2 systemd: Reloading.
Oct 3 17:21:22 fwmg2 systemd: [/usr/lib/systemd/system/suricata.service:17] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Oct 3 17:21:22 fwmg2 systemd: [/usr/lib/systemd/system/suricata.service:18] Unknown lvalue 'LockPersonality' in section 'Service'
Oct 3 17:21:22 fwmg2 systemd: [/usr/lib/systemd/system/suricata.service:19] Unknown lvalue 'ProtectControlGroups' in section 'Service'
Oct 3 17:21:22 fwmg2 systemd: [/usr/lib/systemd/system/suricata.service:20] Unknown lvalue 'ProtectKernelModules' in section 'Service'
Oct 3 17:21:22 fwmg2 esmith::event[22955]: [INFO] service httpd reload
Oct 3 17:21:22 fwmg2 systemd: Reloading The Apache HTTP Server.
Oct 3 17:21:22 fwmg2 systemd: Reloaded The Apache HTTP Server.
Oct 3 17:21:22 fwmg2 esmith::event[22955]: Action: /etc/e-smith/events/actions/adjust-services FAILED: 1 [78.596805]
Oct 3 17:21:22 fwmg2 esmith::event[22955]: Event: nethserver-ejabberd-save FAILED
Oct 3 17:21:27 fwmg2 systemd: ejabberd.service holdoff time over, scheduling restart.
[root@fwmg2 ~]# journalctl -xe
Oct 03 17:26:03 fwmg2.microgate.local systemd[1]: ejabberd.service: control process exited, code=exited status=1
Oct 03 17:26:03 fwmg2.microgate.local systemd[1]: Failed to start XMPP Server.
-- Subject: Unit ejabberd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ejabberd.service has failed.
--
-- The result is failed.
Oct 03 17:26:03 fwmg2.microgate.local systemd[1]: Unit ejabberd.service entered failed state.
Oct 03 17:26:03 fwmg2.microgate.local systemd[1]: ejabberd.service failed.
Oct 03 17:26:08 fwmg2.microgate.local systemd[1]: ejabberd.service holdoff time over, scheduling restart.
Oct 03 17:26:08 fwmg2.microgate.local systemd[1]: Stopped XMPP Server.
-- Subject: Unit ejabberd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ejabberd.service has finished shutting down.
Oct 03 17:26:08 fwmg2.microgate.local systemd[1]: Starting XMPP Server...
-- Subject: Unit ejabberd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ejabberd.service has begun starting up.
I solved the problem, uninstalled ejebberd, after that used yum erase ejabberd and reinstalled. This issue happens after upgrading from version 7.3 to 7.6.
I had this same issue on another firewall after upgrading, to solve the problem with Ejabberd just remove the active directory firewall and insert again. Everything went back to work.
Whichever may interest you, this above error (@ejabberd_config:get_plain_terms_file:305 Cannot load /etc/ejabberd/ejabberd.yml: unexpected_error) only happens when ejabberd is loaded after the firewall is already joined to the domain. Therefore, ejabberd must be started before joining the domain or remove the firewall from the domain, start ejabberd and join the firewall to the domain again.