installed ejabberd package post-installation script subprocess returned error exit status 1

Asked by joergsorge on 2018-09-07

I'm trying to install ejabberd on ubuntu server 18.
It fails with the error message in the summary.

The status after install:

ejabberd.service - A distributed, fault-tolerant Jabber/XMPP server
   Loaded: loaded (/lib/systemd/system/ejabberd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2018-09-07 16:41:21 CEST; 7ms ago
     Docs: https://www.process-one.net/en/ejabberd/docs/
  Process: 18985 ExecStart=/bin/sh -c /usr/sbin/ejabberdctl start && /usr/sbin/ejabberdctl started (code=exited, status=1/FAILURE)

Additionally I get this after a while checking the status again

Sep 07 17:05:45 myserver[15994]: Failed to create dirty io scheduler thread 0

The ejabberd crash and error logs are empty.
The ejabberd.log also give me no hints:

2018-09-07 17:05:18.097 [info] <0.33.0> Application ejabberd started on node ejabberd@localhost
2018-09-07 17:06:38.717 [info] <0.33.0> Application lager started on node ejabberd@localhost
2018-09-07 17:06:38.717 [notice] <0.81.0>@lager_file_backend:146 Changed loghwm of /var/log/ejabberd/error.log to 100
2018-09-07 17:06:38.717 [notice] <0.81.0>@lager_file_backend:146 Changed loghwm of /var/log/ejabberd/ejabberd.log to 100
2018-09-07 17:06:38.728 [info] <0.33.0> Application crypto started on node ejabberd@localhost
2018-09-07 17:06:38.737 [info] <0.33.0> Application sasl started on node ejabberd@localhost
2018-09-07 17:06:38.747 [info] <0.33.0> Application asn1 started on node ejabberd@localhost
2018-09-07 17:06:38.747 [info] <0.33.0> Application public_key started on node ejabberd@localhost
2018-09-07 17:06:38.760 [info] <0.33.0> Application ssl started on node ejabberd@localhost
2018-09-07 17:06:38.766 [info] <0.33.0> Application p1_utils started on node ejabberd@localhost
2018-09-07 17:06:38.778 [info] <0.33.0> Application fast_yaml started on node ejabberd@localhost
2018-09-07 17:06:38.794 [info] <0.33.0> Application fast_tls started on node ejabberd@localhost
2018-09-07 17:06:38.814 [info] <0.33.0> Application fast_xml started on node ejabberd@localhost
2018-09-07 17:06:38.826 [info] <0.33.0> Application stringprep started on node ejabberd@localhost
2018-09-07 17:06:38.834 [info] <0.33.0> Application xmpp started on node ejabberd@localhost
2018-09-07 17:06:38.845 [info] <0.33.0> Application cache_tab started on node ejabberd@localhost
2018-09-07 17:06:38.980 [info] <0.33.0> Application eimp started on node ejabberd@localhost
2018-09-07 17:06:38.980 [info] <0.64.0>@ejabberd_config:start:73 Loading configuration from /etc/ejabberd/ejabberd.yml
2018-09-07 17:06:39.725 [info] <0.33.0> Application mnesia started on node ejabberd@localhost
2018-09-07 17:06:39.771 [info] <0.33.0> Application os_mon started on node ejabberd@localhost
2018-09-07 17:06:39.775 [info] <0.372.0>@cyrsasl_digest:start:62 FQDN used to check DIGEST-MD5 SASL authentication: myserver
2018-09-07 17:06:39.776 [warning] <0.110.0> More than 80% of OS memory is allocated, starting OOM watchdog
2018-09-07 17:06:39.822 [info] <0.33.0> Application fs started on node ejabberd@localhost
2018-09-07 17:06:39.900 [warning] <0.391.0>@ejabberd_pkix:build_chain_and_check:426 Failed to validate certificate from /etc/ejabberd/ejabberd.pem: self-signed certificate
2018-09-07 17:06:39.925 [warning] <0.391.0>@ejabberd_pkix:handle_call:255 No certificate found matching 'localhost': strictly configured clients or servers will reject connections with this host; obtain a certificate for this (sub)domain from any trusted CA such as Let's Encrypt (www.letsencrypt.org)
2018-09-07 17:06:39.970 [info] <0.33.0> Application inets started on node ejabberd@localhost
2018-09-07 17:06:39.970 [warning] <0.369.0>@gen_mod:sort_modules:146 module 'mod_mam' is recommended for module 'mod_muc' but is not found in the config
2018-09-07 17:06:39.973 [warning] <0.391.0>@ejabberd_pkix:handle_call:255 No certificate found matching 'conference.localhost': strictly configured clients or servers will reject connections with this host; obtain a certificate for this (sub)domain from any trusted CA such as Let's Encrypt (www.letsencrypt.org)
2018-09-07 17:06:40.120 [warning] <0.391.0>@ejabberd_pkix:handle_call:255 No certificate found matching 'echo.localhost': strictly configured clients or servers will reject connections with this host; obtain a certificate for this (sub)domain from any trusted CA such as Let's Encrypt (www.letsencrypt.org)
2018-09-07 17:06:40.150 [warning] <0.391.0>@ejabberd_pkix:handle_call:255 No certificate found matching 'pubsub.localhost': strictly configured clients or servers will reject connections with this host; obtain a certificate for this (sub)domain from any trusted CA such as Let's Encrypt (www.letsencrypt.org)
2018-09-07 17:06:40.165 [info] <0.33.0> Application iconv started on node ejabberd@localhost
2018-09-07 17:06:40.166 [warning] <0.391.0>@ejabberd_pkix:handle_call:255 No certificate found matching 'irc.localhost': strictly configured clients or servers will reject connections with this host; obtain a certificate for this (sub)domain from any trusted CA such as Let's Encrypt (www.letsencrypt.org)
2018-09-07 17:06:40.198 [info] <0.64.0>@ejabberd_cluster_mnesia:wait_for_sync:124 Waiting for Mnesia synchronization to complete
2018-09-07 17:06:40.199 [info] <0.64.0>@ejabberd_app:start:59 ejabberd 18.01 is started in the node ejabberd@localhost in 1.73s
2018-09-07 17:06:40.201 [info] <0.33.0> Application ejabberd started on node ejabberd@localhost
2018-09-07 17:06:40.201 [info] <0.406.0>@ejabberd_listener:init_tcp:140 Start accepting TCP connections at [::]:5280 for ejabberd_http
2018-09-07 17:06:40.201 [info] <0.405.0>@ejabberd_listener:init_tcp:140 Start accepting TCP connections at [::]:5269 for ejabberd_s2s_in
2018-09-07 17:06:40.201 [info] <0.404.0>@ejabberd_listener:init_tcp:140 Start accepting TCP connections at [::]:5222 for ejabberd_c2s

What can I do?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2018-09-07
Last reply:
2018-09-23
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.