Hi everybody,
We have an Xamin server which used XMPP and Jabber protocol, but some times, this service (means ejabberd) goes down unexpectedly and "ejabberdctl status" command prints: "Failed RPC connection to the node ejabberd@xamin: nodedown"
[CODE]
root@xamin:~# ejabberdctl status
Failed RPC connection to the node ejabberd@xamin: nodedown
root@xamin:~#
[/CODE]
We look at /var/log/ejabberd/* (* means everything) , but don't any related log has been generated! ( Log level : 10 )
I know when ejabberd service started manually, we have about 14 seconds to ejabberd goes down again!
These codes generated in three different terminal (bash) respectively in order to writing status time line.
[CODE]
root@xamin:~# for ((;;)) do ejabberdctl status; date; echo ""; sleep 1; done >> ejabberdctl_status.log
[/CODE]
[CODE]
root@xamin:~# echo "=================================================" >> $file; /etc/init.d/ejabberd start >> $file; echo "=================================================" >> $file
root@xamin:~#
[/CODE]
[CODE]
root@xamin:~# tail -f ejabberdctl_status.log
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:29:42 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:29:43 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:29:44 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:29:45 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:29:46 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:29:47 UTC 2014
=================================================
Starting jabber server: ejabberd.
=================================================
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:48 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:49 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:50 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:51 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:53 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:54 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:55 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:56 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:57 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:58 UTC 2014
The node ejabberd@xamin is starting with status: started
ejabberd is not running in that node
Check for error messages: ejabberd.log
or other files in that directory.
Mon Aug 11 13:29:59 UTC 2014
The node ejabberd@xamin is starting with status: started
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:30:01 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:30:02 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:30:03 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:30:04 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:30:05 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:30:06 UTC 2014
Failed RPC connection to the node ejabberd@xamin: nodedown
Mon Aug 11 13:30:07 UTC 2014
BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
(v)ersion (k)ill (D)b-tables (d)istribution
Mon Aug 11 13:30:10 UTC 2014
[/CODE]
Our Jabber version :
[CODE]
root@xamin:/usr/lib/ejabberd/ebin# cat ejabberd.app | grep -i vsn
{vsn, "2.1.11"},
root@xamin:/usr/lib/ejabberd/ebin#
[/CODE]
1. What is the maximum log level?
2. What is the newest and latest Jabber version?
3. How we can upgrade to newer versions?
4. Do you have ANY suggestion to overcome this problem?
