ejabberd 2.0.0-rc1 released

ejabberd 2.0.0 has been in the works since more than a year ago. This release will include an impressive amount of new features, improvements and bug fixes. Just to name two: more clustering features and updated Pub-Sub service with PEP support.

Please read with detail the Release Notes for a list of changes and important notes.

But the final release of ejabberd 2.0.0 is not ready yet. Right now it's time for Release Candidate 1.

Three weeks ago 2.0.0-beta1 was published. Several people reported important bugs that are now fixed in RC1. You can check the tickets concerning Beta1 that are fixed in RC1 and the SVN log since Beta1 was released until RC1.

Source code and binary installers are available as usual in the ejabberd downloads page.

To formally report bugs please use the ejabberd bug tracker. Alternatively, you can start a discussion in the ejabberd mailing list or in the ejabberd forums. If you just want to report a small bug, you can also add a comment here.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

LDAP ssl and/or TLS

Hi,

In the release notes under ldap improvements, LDAPS and TLS support are not listed explicitly. Is there information somewhere about whether 2.0 supports this?

Thanks,

ak

LDAPS: not in 2.0.0

Not in 2.0.0. Here is the feature request in the bug tracker: LDAPS support.

Post Install Script Fails

I am brand new to this, but I would like to set up a version of ejabberd with an http-bind interface on my debian etch system at home as part of a wider plan for chat on another web site I run (which can't support services on other ports because because its a shared host - so I would like to redirect chat my server as an interim measure before we upgrade). Because of the http-bind requirement, I can't use the stable release which is bundled with Debian.

So I downloaded the linux_86 installer for the 2.0.0-rc1 version and ran it to install the software. Once the installation process had shown ### up to 100%, there was a long delay (~ 1 minute) and then eventually the script reported an error in the post-install script.

There is a crash dump in the logs directory of the installation. Its quite long (so at the moment I haven't posted it here) but it seems to give no indication of why

Debian Etch Erlang is R11b2.4. I have the nox version installed.

The domain name I entered during installation is www.chandlerfamily.org.uk - I already have apache2 supporting port 80 on this machine. I opened port 5280 in my firewall for eventual connection from outside.

I am not sure where I go from here in terms of what I might be doing wrong, or what information I could provide you to help me figure out what is wrong. Can you help please.

Are there log files?

akc42 wrote:

Debian Etch Erlang is R11b2.4. I have the nox version installed.

Note that the Process-one binary installers already include Erlang/OTP: 'The installers contain all the libraries and dependencies needed to run ejabberd.'

Of course, it isn't any problem to have already Erlang installed. Just note that the system erlang will not be used.

akc42 wrote:

The domain name I entered during installation is www.chandlerfamily.org.uk - I already have apache2 supporting port 80 on this machine. I opened port 5280 in my firewall for eventual connection from outside.

I tried the 2.0.0-rc1 linux 32 bits installer in my Ubuntu Hardy, and it completed the installation correctly. I had put the same domain that you.

akc42 wrote:

So I downloaded the linux_86 installer for the 2.0.0-rc1 version and ran it to install the software. Once the installation process had shown ### up to 100%, there was a long delay (~ 1 minute) and then eventually the script reported an error in the post-install script.

There is a crash dump in the logs directory of the installation.

Once the copying of files finished, the installer started ejabberd, then tried to create the admin account and finally stop ejabberd. Quite probably the delay you saw is about the installer waiting ejabberd to start, but ejabberd didn't start correctly and was not responding.

The crash dump was probably generated by ejabberd when trying to start. Do you also have log files ejabberd.log and sasl.log? Maybe they provide some meaningful information to the reason of the problem.

I found same probem as you

I found same probem as you

Syndicate content