[ejabberd] ejabberd 2.0.1 - problems with RPC (amd64)

Michael Flaig mflaig at pro-linux.de
Mon Jul 28 17:10:41 MSD 2008


Hi there,

I'm currently in the process of migrating from openfire to ejabberd and
ran into a quite annoying problem I didn't get solved, yet.

My System is Debian lenny. Installing ejabberd from debian of course.
--- snip ---
srv-2000:~# apt-cache show ejabberd
Package: ejabberd
Priority: optional
Architecture: amd64
Version: 2.0.1-2
--- snap ---

I do set the hostname to localhost (or the hostname -s, tried both) 
Enter the user and password to be created for admin

--- snip ---
Creating config file /etc/ejabberd/ejabberd.cfg with new version
Starting jabber server: ejabberd.
Waiting for ejabberd to register admin
user..............................................................
Can't register admin user "admin at localhost".
Probably ejabberd is configured for serving another hostname.
--- snap ---

After installing there are plenty of epmd processes, no beam process
So I killed all epmd processes and did start ejabberd again

Now it looks better:
--- snip ---
15973 ?        S      0:00 /usr/lib/erlang/erts-5.6.3/bin/epmd -daemon
15988 ?        S      0:00 /usr/lib/erlang/erts-5.6.3/bin/epmd -daemon
15990 pts/1    Sl     0:00 /usr/lib/erlang/erts-5.6.3/bin/beam -K false
-P 250000 -- -root /usr/lib/erlang -progname erl --
-home /var/lib/ejabberd -sname ejabberd -pa /usr/lib/ejabberd/ebin -s
ejabberd -kernel inetrc "/etc/ejabberd/inetrc" -ejabberd config
"/etc/ejabberd/ejabberd.cfg" log_path "/var/log/ejabberd/ejabberd.log"
-sasl sasl_error_logger {file,"/var/log/ejabberd/sasl.log"} -mnesia dir
"/var/lib/ejabberd" -smp disable -noshell -noshell -noinput
--- snap ---

--- ejabberd.log ---
=INFO REPORT==== 2008-07-28 13:19:00 ===
I(<0.314.0>:mod_pubsub:152) : pubsub init
"localhost" [{access_createnode,

pubsub_createnode},
                                                       {plugins,

["default","pep"]}]

=INFO REPORT==== 2008-07-28 13:19:00 ===
I(<0.314.0>:mod_pubsub:207) : ** tree plugin is nodetree_default

=INFO REPORT==== 2008-07-28 13:19:00 ===
I(<0.314.0>:mod_pubsub:211) : ** init default plugin

=INFO REPORT==== 2008-07-28 13:19:00 ===
I(<0.314.0>:mod_pubsub:211) : ** init pep plugin

=INFO REPORT==== 2008-07-28 13:29:15 ===
I(<0.322.0>:mod_pubsub:152) : pubsub init
"localhost" [{access_createnode,

pubsub_createnode},
                                                       {plugins,

["default","pep"]}]

=INFO REPORT==== 2008-07-28 13:29:15 ===
I(<0.322.0>:mod_pubsub:207) : ** tree plugin is nodetree_default

=INFO REPORT==== 2008-07-28 13:29:15 ===
I(<0.322.0>:mod_pubsub:211) : ** init default plugin

=INFO REPORT==== 2008-07-28 13:29:15 ===
I(<0.322.0>:mod_pubsub:211) : ** init pep plugin
--- snap ---

srv-2000:/var/log/ejabberd# ejabberdctl 
RPC failed on the node ejabberd at localhost: nodedown

Ejabberd seems to be running. When I configure ldap I can log on and use
it, however ejabberdctl does not work and everytime ejabberdctl is
invoked I see new epmd processes ...

This may be amd64 related. On a i386 installation ejabberdctl works
right.

However logging shows no problems so how would I want to proceed from
here to find the actual problem?

Seen this problem before?

Thanks for your help

Regards,

	Michael


PS. I'm opening a bug report on bugs.debian.org, too.

-- 
Michael Flaig <mflaig at pro-linux.de>
PROLinux.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.jabber.ru/pipermail/ejabberd/attachments/20080728/d7fc12ab/attachment.pgp 


More information about the ejabberd mailing list