ejabberd - Comments for "ejabberd running but RPC failed"

use sudo. solved my problem.

lilprogramer — Fri, 22 Aug 2014 15:00:24 +0000

use sudo. solved my problem.

erlang

Anonymous — Wed, 06 Feb 2008 12:17:34 +0000

/ets/init.d/ejabberd status ????

Did you install corect version of erlang?
I have same trouble a week ago with ejabberd 1.1.4(Fedora7) and it didn't work with erlang 12 - i had to install erlang 11B-5

How can start ejabberd

yllsuarez — Mon, 24 Sep 2007 19:27:12 +0000

I use Ubuntu, where and how can get some script to start the ejabberd automatically.

thanks

hostname -s ...

icomes — Sat, 03 Feb 2007 04:30:25 +0000

I encountered the same problem,
and It seems that the hostname is the key to solve it.

If you start ejabberd with "-sname ejabberd" in the /etc/init.d/ejabberd script,
then the corresponding line should be "NODE=ejabberd@`hostname -s`" in /usr/sbin/ejabberdctl(in my case).

ps.
If the command "hostname -s" returns "Unknow host",
just edit(vi?) the /etc/hosts file.

Hmmm

SpaceHobo — Mon, 15 Jan 2007 12:09:28 +0000

I have the same problem, and have verified that the -sname matches (the script enforces this) and that the nodename matches $( hostname -s ) (the scripts enforce this as well). Any ideas?

Wrong hostname in node?

aszlig — Thu, 24 Aug 2006 07:19:08 +0000

hullo,

please check if the hostname of your node matches the short hostname
(hostname -s). if not please either fix your dns configuration or
/etc/hosts ;-)

c'ya

Re: 1) Firewall on localhost?

sander — Wed, 02 Aug 2006 22:49:42 +0000

SunB wrote:

teo wrote:

2) Erlang cookie issue? From which user did you run ejabberdctl?

root

And what is the user that owns the beam process of ejabberd?

Nope, the Node and hostname

SunB — Mon, 17 Jul 2006 13:44:29 +0000

Nope, the Node and hostname settings are correct (in /etc/init.d/ejabberd.cfg and /usr/sbin/ejabberdctl)

Thank you, any other ideas?

In the file ejabberdctl two

ikss — Mon, 17 Jul 2006 13:02:01 +0000

Where is the file ejabberdctl which is called when you ask the status of your server ?
In this file (ejabberdctl which is a sh script), two variables are defined : $NODE and $HOST.
When i read you, i think that : NODE=ejabberd and HOST=srv ?!

Maybe the values for these variables are different from the values which are used in your script /etc/init.d/ejabberd ?

Re: 1) Firewall on localhost?

SunB — Mon, 17 Jul 2006 12:52:31 +0000

teo wrote:

1) Firewall on localhost?

No!

teo wrote:

2) Erlang cookie issue? From which user did you run ejabberdctl?

root

teo wrote:

3) Some application has bound port 4369 and doesn't allow epmd to listen on it?

epmd only listens at 127.0.0.1

teo wrote:

4) Some more?

hope so ...

Thx 4 help

1) Firewall on localhost? 2)

teo — Thu, 13 Jul 2006 05:49:34 +0000

1) Firewall on localhost?

2) Erlang cookie issue? From which user did you run ejabberdctl?

3) Some application has bound port 4369 and doesn't allow epmd to listen on it?

4) Some more?