From a323504a32334b9c60dddbdd93acd0888705f5f2 Mon Sep 17 00:00:00 2001 From: Badlop Date: Mon, 28 Jul 2008 16:55:01 +0000 Subject: [PATCH] * doc/guide.tex: Document how to get error message when ejabberd crash dumps at start (EJAB-660) * doc/guide.html: Likewise SVN Revision: 1494 --- ChangeLog | 6 ++++++ doc/guide.html | 15 +++++++++++++-- doc/guide.tex | 15 +++++++++++++++ 3 files changed, 34 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 09efea45e..69a3e3e7e 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2008-07-28 Badlop + + * doc/guide.tex: Document how to get error message when ejabberd + crash dumps at start (EJAB-660) + * doc/guide.html: Likewise + 2008-07-25 Christophe Romain * src/mod_pubsub/mod_pubsub.erl: Speedup startup with many pubsub diff --git a/doc/guide.html b/doc/guide.html index af65e7ea9..4ecd8242a 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -290,7 +290,13 @@ go to the Windows service settings and set ejabberd to be automatically started. Note that the Windows service is a feature still in development, and for example it doesn’t read the file ejabberdctl.cfg.

On a *nix system, if you want ejabberd to be started as daemon at boot time, copy ejabberd.init from the ’bin’ directory to something like /etc/init.d/ejabberd -(depending on your distribution) and call /etc/inid.d/ejabberd start to start it.

The ejabberdctl administration script is included in the bin directory. +(depending on your distribution) and call /etc/inid.d/ejabberd start to start it.

If ejabberd doesn’t start correctly and a crash dump is generated, +there was a severe problem. +You can try starting ejabberd with +the script bin/live.bat in Windows, +or with the command bin/ejabberdctl live in other Operating Systems. +This way you see the error message provided by Erlang +and can identify what is exactly the problem.

The ejabberdctl administration script is included in the bin directory. Please refer to the section 4.1 for details about ejabberdctl, and configurable options to fine tune the Erlang runtime system.

2.2  Installing ejabberd with Operating System specific packages

Some Operating Systems provide a specific ejabberd package adapted to @@ -405,7 +411,12 @@ Node ejabberd@localhost is started. Status: started ejabberd is running ejabberdctl stop -

Please refer to the section 4.1 for details about ejabberdctl, +

If ejabberd doesn’t start correctly and a crash dump is generated, +there was a severe problem. +You can try starting ejabberd with +the command ejabberdctl live +to see the error message provided by Erlang +and can identify what is exactly the problem.

Please refer to the section 4.1 for details about ejabberdctl, and configurable options to fine tune the Erlang runtime system.

2.4.6  Specific Notes for BSD

The command to compile ejabberd in BSD systems is: diff --git a/doc/guide.tex b/doc/guide.tex index bf07f39e5..f01dd9bee 100644 --- a/doc/guide.tex +++ b/doc/guide.tex @@ -241,6 +241,14 @@ On a *nix system, if you want ejabberd to be started as daemon at boot time, copy \term{ejabberd.init} from the 'bin' directory to something like \term{/etc/init.d/ejabberd} (depending on your distribution) and call \term{/etc/inid.d/ejabberd start} to start it. +If \term{ejabberd} doesn't start correctly and a crash dump is generated, +there was a severe problem. +You can try starting \term{ejabberd} with +the script \term{bin/live.bat} in Windows, +or with the command \term{bin/ejabberdctl live} in other Operating Systems. +This way you see the error message provided by Erlang +and can identify what is exactly the problem. + The \term{ejabberdctl} administration script is included in the \term{bin} directory. Please refer to the section~\ref{ejabberdctl} for details about \term{ejabberdctl}, and configurable options to fine tune the Erlang runtime system. @@ -415,6 +423,13 @@ ejabberd is running ejabberdctl stop \end{verbatim} +If \term{ejabberd} doesn't start correctly and a crash dump is generated, +there was a severe problem. +You can try starting \term{ejabberd} with +the command \term{ejabberdctl live} +to see the error message provided by Erlang +and can identify what is exactly the problem. + Please refer to the section~\ref{ejabberdctl} for details about \term{ejabberdctl}, and configurable options to fine tune the Erlang runtime system. -- 2.40.0