Your message dated Mon, 20 Apr 2009 22:44:34 +0400
with message-id <[email protected]>
and subject line Re: Bug#492722: RPC fails, package unable to create admin 
user,after  install ejabberdctl not working - Found word(s) list error in the 
Text body
has caused the Debian Bug report #492722,
regarding erlang-base: multiple epmd processes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
492722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492722
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ejabberd
Version: 2.0.1-2
Severity: grave
Justification: renders package unusable

I am seeing a problem with ejabberd rpc on lenny.
First problem comes up on install (tried with real machine name "srv-2000" and 
localhost)

--- 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 "ad...@localhost".
Probably ejabberd is configured for serving another hostname.
--- snap ---

Package installs however ignoring this error

After installing there are plenty of epmd processes, no beam process however
As I understand it, without beam no rpc, so I did killall epmd and started 
ejabberd with the init script.
beam is now there.
--- 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 ---

This is the only part, that also applies to i386:
On i386 ejabberdctl does not work after installing, but works after killing 
empd and starting again. 

On amd64 killing and starting doesn't fix the problem. Error persists.
On i386 there is only one beam and one epmd process on amd64 there is one beam 
and two epmd processes.

--- snip ---
srv-2000:/var/log/ejabberd# ejabberdctl 
RPC failed on the node ejabb...@localhost: nodedown
--- snap ---

However the log does not give any clue to what is wrong:
--- 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 ---

Anyway, Ejabberd seems to be running. When I configure ldap I can log on and 
use it, however ejabberdctl does not work
When ejabberdctl is invoked another epmd process turns up. Init script does not 
work because it depends on ejabberdctl to work

So I am pretty much out of idea what the problem could be or where to look to 
see what's wrong with RPC.


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.16-weiti
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ejabberd depends on:
ii  adduser                3.108             add and remove users and groups
ii  debconf [debconf-2.0]  1.5.22            Debian configuration management sy
ii  erlang-base [erlang-ab 1:12.b.3-dfsg-1   Concurrent, real-time, distributed
ii  erlang-nox             1:12.b.3-dfsg-1   Concurrent, real-time, distributed
ii  libc6                  2.7-10            GNU C Library: Shared libraries
ii  libexpat1              2.0.1-4           XML parsing C library - runtime li
ii  libpam0g               0.99.7.1-6+b1     Pluggable Authentication Modules l
ii  libssl0.9.8            0.9.8g-10.1       SSL shared libraries
ii  openssl                0.9.8g-10.1       Secure Socket Layer (SSL) binary a
ii  ucf                    3.007             Update Configuration File: preserv
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

ejabberd recommends no packages.

Versions of packages ejabberd suggests:
ii  libunix-syslog-perl           1.1-2      Perl interface to the UNIX syslog(

-- debconf information:
* ejabberd/password: (password omitted)
* ejabberd/verify: (password omitted)
  ejabberd/nomatch:
* ejabberd/user: admin
* ejabberd/hostname: srv-2000



--- End Message ---
--- Begin Message ---
The bug is gone, so I'm closing it.

-- 
Sergei Golovan


--- End Message ---

Reply via email to