Hi i've got to kill ejabberd and start it again because i've reached the max.
Is there a way to change this "max" value and which one ?
I can't remember which version of ejabberd, is there to find out ? (something like ejabberd -version ?)
Here are my logs:
------------- sasl.log -------------
=SUPERVISOR REPORT==== 26-Jan-2008::19:41:05 ===
Supervisor: {local,mnesia_kernel_sup}
Context: child_terminated
Reason: shutdown
Offender: [{pid,<0.60.0>},
{name,mnesia_monitor},
{mfa,{mnesia_monitor,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=SUPERVISOR REPORT==== 26-Jan-2008::19:41:05 ===
Supervisor: {local,mnesia_kernel_sup}
Context: shutdown
Reason: reached_max_restart_intensity
Offender: [{pid,<0.60.0>},
{name,mnesia_monitor},
{mfa,{mnesia_monitor,start,[]}},
{restart_type,permanent},
{shutdown,3000},
{child_type,worker}]
=SUPERVISOR REPORT==== 26-Jan-2008::19:41:06 ===
Supervisor: {local,mnesia_sup}
Context: child_terminated
Reason: shutdown
Offender: [{pid,<0.59.0>},
{name,mnesia_kernel_sup},
{mfa,{mnesia_kernel_sup,start,[]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=SUPERVISOR REPORT==== 26-Jan-2008::19:41:06 ===
Supervisor: {local,mnesia_sup}
Context: shutdown
Reason: reached_max_restart_intensity
Offender: [{pid,<0.59.0>},
{name,mn
--------------- ejabberd.log ------------
=ERROR REPORT==== 2008-01-26 19:41:06 ===
** Generic server ejabberd_sm terminating
** Last message in was {mnesia_system_event,{mnesia_down,ejabberd@xxxxxxx}}
** When Server state == {state}
** Reason for termination ==
** {node_not_running,ejabberd@xxxxxxx}
=ERROR REPORT==== 2008-01-26 19:41:06 ===
E(<0.2170.1>:ejabberd_router:52): {aborted,
{no_exists,[route,"xxxxxxx.net"]}}
when processing: {{jid,[],
"msn.xxxxxxx.net",
[],
[],
"msn.xxxxxxx.net",
[]},
{jid,"********-1035668-******.com",
"xxxxxxx.net",
"JabberClass",
"********-1035668-******.com",
"xxxxxxx.net",
"JabberClass"},
{xmlelement,"iq",
[{"to",
"********-1035668-******.com@xxxxxxx.net/JabberClass"},
{"from","msn.xxxxxxx.net"},
thanks
MCS
Try to find the origin of the problem
I can't remember which version of ejabberd, is there to find out ? (something like ejabberd -version ?)
A command like that does not exist.
Hi i've got to kill ejabberd and start it again because i've reached the max.
Is there a way to change this "max" value and which one ?
The limit you reached is probably imposed by the Erlang runtime system. Maybe it can be increased, but I think that is not the solution. The solution is to find the reason why your server reached this limit.
You can start ejabberd, and check if it shows any error message in the logs. If nothing strange appears, login with a client, then check again if they show any error message. Things like this doesn't look good:
=SUPERVISOR REPORT==== 26-Jan-2008::19:41:06 === Supervisor: {local,mnesia_sup} Context: shutdown ...