Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ejabberd won't start #1248

Closed
hebertreis opened this issue Aug 15, 2016 · 2 comments
Closed

Ejabberd won't start #1248

hebertreis opened this issue Aug 15, 2016 · 2 comments

Comments

@hebertreis
Copy link

hebertreis commented Aug 15, 2016

What version of ejabberd are you using?

16.08

What operating system (version) are you using?

Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty

How did you install ejabberd (source, package, distribution)?

Because this issue #1244 "fixed" by @badlop I tried to compile the master branch of this repo that crashed on start up process, then I download the zip file for 16.08 on release page and have the same error after configure->make->make install process

What did not work as expected? Are there error messages in the log? What

ejabberd wont start.

2016-08-15 18:35:35.206 [info] <0.357.0> Application lager started on node ejabberd@localhost
2016-08-15 18:35:35.211 [info] <0.357.0> Application crypto started on node ejabberd@localhost
2016-08-15 18:35:35.215 [info] <0.357.0> Application sasl started on node ejabberd@localhost
2016-08-15 18:35:35.222 [info] <0.357.0> Application asn1 started on node ejabberd@localhost
2016-08-15 18:35:35.222 [info] <0.357.0> Application public_key started on node ejabberd@localhost
2016-08-15 18:35:35.228 [info] <0.357.0> Application ssl started on node ejabberd@localhost
2016-08-15 18:35:35.231 [info] <0.357.0> Application fast_yaml started on node ejabberd@localhost
2016-08-15 18:35:35.237 [info] <0.357.0> Application fast_tls started on node ejabberd@localhost
2016-08-15 18:35:35.241 [info] <0.357.0> Application fast_xml started on node ejabberd@localhost
2016-08-15 18:35:35.243 [info] <0.357.0> Application stringprep started on node ejabberd@localhost
2016-08-15 18:35:35.245 [info] <0.357.0> Application cache_tab started on node ejabberd@localhost
2016-08-15 18:35:35.249 [error] <0.389.0>@ejabberd_app:start_elixir_application:245 Elixir application not started.
2016-08-15 18:35:35.340 [info] <0.357.0> Application mnesia started on node ejabberd@localhost
2016-08-15 18:35:35.760 [error] <0.388.0> CRASH REPORT Process <0.388.0>
 with 0 neighbours exited with reason:
 {aborted,{bad_type,{ejabberd_commands,gen_html_doc_for_commands,[documentation],
"Generates html documentation for ejabberd_commands",[],0,ejabberd_commands_doc,generate_html_output,
[{file,binary},{regexp,binary},{examples,binary}],restricted,[],{res,rescode},
["Path to file where generated documentation should be stored",
"Regexp matching names of commands or modules that will be included inside generated document",
"Comma separated list of languages (choosen from java, perl, xmlrpc, json)that ..."],...}}}
 in application_master:init/4 line 134

2016-08-15 18:35:35.761 [info] <0.357.0> Application ejabberd exited with reason: {aborted,{bad_type,{ejabberd_commands,gen_html_doc_for_commands,[documentation],"Generates html documentation for ejabberd_commands",[],0,ejabberd_commands_doc,generate_html_output,[{file,binary},{regexp,binary},{examples,binary}],restricted,[],{res,rescode},["Path to file where generated documentation should be stored","Regexp matching names of commands or modules that will be included inside generated document","Comma separated list of languages (choosen from java, perl, xmlrpc, json)that ..."],...}}}`

was the unexpected behavior? What was the expected result?

@hebertreis
Copy link
Author

hebertreis commented Aug 16, 2016

I create a new AWS EC2 Instance and did everything from zero and ejabberd it's running now.

@lock
Copy link

lock bot commented Jun 11, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant