[SOLVED] Zentyal 3.3.4, Jabber 3.3 - Jabber fails to start - won't bind to LDAP

[RAB]

I seem to hit this bug
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1241632

I can not find a way to start jabber (despite the webadmin interface sayin that the module started correctly, the module status says "stopped". "/etc/init.d/zentyal jabber status" shows "stopped". a commandline restart takes forever to no avail.

The credentials in /etc/ejabberd/ejabberd.cgf match the ones provided in the webinterface. External ldap explorer works fine with the same credentials.

Any help would be appreciated!

From /var/log/ejabberd/ejabberd.log.1 (this is repeated many many many times):


=INFO REPORT==== 2014-02-11 20:28:42 ===
I(<0.291.0>:eldap:983) : LDAP connection on 127.0.0.1:390

=INFO REPORT==== 2014-02-11 20:28:42 ===
I(<0.281.0>:eldap:983) : LDAP connection on 127.0.0.1:390

=INFO REPORT==== 2014-02-11 20:28:42 ===
I(<0.373.0>:eldap:983) : LDAP connection on 127.0.0.1:390

=INFO REPORT==== 2014-02-11 20:28:42 ===
I(<0.347.0>:eldap:983) : LDAP connection on 127.0.0.1:390

=WARNING REPORT==== 2014-02-11 20:28:42 ===
W(<0.347.0>:eldap:931) : LDAP bind failed on 127.0.0.1:390
Reason: invalidCredentials

=WARNING REPORT==== 2014-02-11 20:28:42 ===
W(<0.373.0>:eldap:931) : LDAP bind failed on 127.0.0.1:390
Reason: invalidCredentials

=WARNING REPORT==== 2014-02-11 20:28:42 ===
W(<0.281.0>:eldap:931) : LDAP bind failed on 127.0.0.1:390
Reason: invalidCredentials

=WARNING REPORT==== 2014-02-11 20:28:42 ===
W(<0.291.0>:eldap:931) : LDAP bind failed on 127.0.0.1:390
Reason: invalidCredentials

[RAB]

the used ejabberd version is indeed 2.1.10.

ejabberd 2.1.12 has an erlang related ldap fix on board ...

http://redir.process-one.net/ejabberd-2.1.12

[RAB]

So - wanted to try and install ejabberd 2.1.13 to see if this solves the issue.

http://www.process-one.net/en/ejabberd/archive/

However the installer wants to configure from scratch so not sure if it is wise to proceed.

Any hints on how to just upgrade ejabberd within the Zentyal setting?

[RAB]

solved - not sure which steps were necessary.

did a

apt-get remove -purge zentyal-jabber
apt-get autoremove -purge

Then reinstalled jabber through zentyal webadmin

Still not running, only a crash report in /var/log/ejabberd

Then ran into this post: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516718

Which led me to kill some processes:

Rebooting the server isn't necessary, just make sure there's no beam, beam.smp and epmd processes running.
You can find them like this:
# ps axc|grep beam
# ps axc|grep epmd

Note that the epmd process comes up again after killing it.


And - tada - jabber can be started (I used "service zentyal jabber start" but I presume the webinterface would have worked as well ....