Problem starting ejabberd

Francenildo · October 3, 2019, 1:50pm

Problem starting ejabberd, does anyone else have this problem?

NethServer release 7.6.1810 (final)
ejabberd
Task completed with errors
Adjust service ejabberd #4 (exit status 1)
restart service ejabberd failed!

Oct 3 10:01:25 fwmg2 systemd: Failed to start XMPP Server.
Oct 3 10:01:25 fwmg2 systemd: Unit ejabberd.service entered failed state.
Oct 3 10:01:25 fwmg2 systemd: ejabberd.service failed.
Oct 3 10:01:30 fwmg2 systemd: ejabberd.service holdoff time over, scheduling restart.
Oct 3 10:01:30 fwmg2 systemd: Stopped XMPP Server.
Oct 3 10:01:30 fwmg2 systemd: Starting XMPP Server…
Oct 3 10:02:22 fwmg2 evebox: 2019-10-03 10:02:22 (purger.go:62) – Deleting events prior to 2019-09-02T10:02:22.238479-0300
Oct 3 10:02:35 fwmg2 systemd: ejabberd.service: control process exited, code=exited status=1
Oct 3 10:02:35 fwmg2 systemd: Failed to start XMPP Server.
Oct 3 10:02:35 fwmg2 systemd: Unit ejabberd.service entered failed state.
Oct 3 10:02:35 fwmg2 systemd: ejabberd.service failed.

stephdl · October 3, 2019, 6:57pm

nothig more related in the ejabberd log ?

Francenildo · October 3, 2019, 8:29pm

When I start the process it shows just that.

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.

stephdl · October 3, 2019, 8:51pm

systemctl cat suricata.service

I do not remenber but you have a specific log for ejabberd, check inside also

EDIT: check /var/log/ejabberd/ejabberd.log and /var/log/messages, try to format your text to ease the reading

Francenildo · October 4, 2019, 2:14pm

In the /var/log/ejabberd/ejabberd.log.

2019-10-04 11:10:43.163 [notice] <0.82.0>@lager_file_backend:146 Changed loghwm of /var/log/ejabberd/ejabberd.log to 100
2019-10-04 11:10:43.164 [info] <0.33.0> Application lager started on node ejabberd@localhost
2019-10-04 11:10:43.172 [info] <0.33.0> Application crypto started on node ejabberd@localhost
2019-10-04 11:10:43.179 [info] <0.33.0> Application sasl started on node ejabberd@localhost
2019-10-04 11:10:43.187 [info] <0.33.0> Application asn1 started on node ejabberd@localhost
2019-10-04 11:10:43.187 [info] <0.33.0> Application public_key started on node ejabberd@localhost
2019-10-04 11:10:43.198 [info] <0.33.0> Application ssl started on node ejabberd@localhost
2019-10-04 11:10:43.202 [info] <0.33.0> Application p1_utils started on node ejabberd@localhost
2019-10-04 11:10:43.213 [info] <0.33.0> Application fast_yaml started on node ejabberd@localhost
2019-10-04 11:10:43.228 [info] <0.33.0> Application fast_tls started on node ejabberd@localhost
2019-10-04 11:10:43.243 [info] <0.33.0> Application fast_xml started on node ejabberd@localhost
2019-10-04 11:10:43.248 [info] <0.33.0> Application stringprep started on node ejabberd@localhost
2019-10-04 11:10:43.262 [info] <0.33.0> Application xmpp started on node ejabberd@localhost
2019-10-04 11:10:43.275 [info] <0.33.0> Application cache_tab started on node ejabberd@localhost
2019-10-04 11:10:43.292 [info] <0.33.0> Application eimp started on node ejabberd@localhost
2019-10-04 11:10:43.330 [info] <0.33.0> Application elixir started on node ejabberd@localhost
2019-10-04 11:10:43.351 [info] <0.65.0>@ejabberd_config:start:68 Loading configuration from /etc/ejabberd/ejabberd.yml
2019-10-04 11:10:43.352 [error] <0.65.0>@ejabberd_config:get_plain_terms_file:305 Cannot load /etc/ejabberd/ejabberd.yml: unexpected_error

stephdl · October 4, 2019, 4:31pm

line 305 of /etc/ejabberd/ejabberd.yml what it is ?

stephdl · October 4, 2019, 6:48pm

Did you triy to expand and restart the service

signal-event nethserver-ejabberd-update

Francenildo · October 6, 2019, 1:17am

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.

Thank you so much for trying to help me.

stephdl · October 6, 2019, 5:51am

The installation of a rpm triggers a specific event, in that case nethserver-ejabberd-update, it could had solved your problem too

Francenildo · October 6, 2019, 9:01pm

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.

Francenildo · October 29, 2019, 6:25pm

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.