ejabberd 13.10

We are pleased to announce a new stable release of ejabberd, ejabberd Community 13.10.

It has some changes, several improvements and many bugfixes over the previous (not officially announced) 13.06. It is also the first official stable release of ejabberd Community after ejabberd 2.1.13. You are now pleased to use ejabberd community as reference for stable releases of ejabberd, from the master branch. ejabberd 2.1.x support is discontinued.

The most noticeable changes since 13.03-beta and 13.06 are:

  • in the configuration file: it is now written using YAML syntax instead of Erlang syntax. So, after installing ejabberd, search for a file called ejabberd.yml. If you have an old ejabberd.cfg, you can convert it to yml using the “ejabberdctl convert_to_yaml” command. The ejabberd Guide is fully updated to describe the new syntax.
  • in logging system: it now uses Lager to produce cleaner logs, with a “one line per element” scheme.
  • in build process: now Rebar is used for simpler dependency handling, so code is modular among several repositories, putting out of ejabberd general purpose libraries.

Changes since 2.1.13 are even more noticeable:

  • huge improvements regarding performances
  • optimized memory consumption
  • clean code representation of xmlel records

As usual, the release is tagged in the Git source code repository on github

The source package and binary installers are available at ProcessOne

If you suspect you found a bug, search or fill a bug report in Jira

Please note this branch requires at least Erlang/OTP R15, and works correctly with R16B02.

Comment viewing options

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

modules need update

I tried the 13.10, it works.
But none of the extra modules works, the extra modules like mod_archive need update. Google finds them too old and no update.
Maybe you need buy a commercial one OR try other alternates like OpenFire and waiting for the modules to be updated.

Mystical guide

badlop wrote:

The ejabberd Guide is fully updated to describe the new syntax.

Where is this guide?

(edit) Never mind. I found it.

Stable version?

It seems that this post is saying 13.10 is a stable version.

But the sidebar on the site says 13.10 is testing and 2.1.13 is the stable branch.

I assume this post is correct, but it is a little confusing.

convert_to_yaml

Hi,
Just doing an run-up of a test install.
How should I rub the convert_to_yaml command?
As it appears the command is only present in the new bin/ejabberdctl.
Which I've not got running yet.
Possibly because I've not converted my config?

The attempt to start gets a fair way, then stops at:
'p1_stun': {error,
{"no such file or directory",
"p1_stun.app"}}

I cannot find p1_stun mentioned anywhere.

Thanks for any clues and good luck with this new release!

Best, MarkT

I guess you are running from

I guess you are running from source apckage or Git repo. For the missing dependency, try running:
$ ./rebar get-deps
Then recompile, it should try to get the missing packages in deps/, compile and install them automatically.

I have the same problem, but

I have the same problem, but I installed using the official Linux 64-bit installer from http://www.process-one.net/en/ejabberd/downloads/.

I upgraded from 2.1.9 by copying over the ejabberd.cfg configuration file as well as the database (in database/ejabberd@localhost). Then starting ejabberd using "/opt/ejabberd-13.10/bin/ejabberdctl start". The logfile shows various warnings (which I hope will go away once I convert ejabberd.cfg to ejabberd.yml) and this error:

2013-10-31 00:30:55.843 [critical] <0.415.0>@ejabberd:exit_or_halt:124 failed to start application 'p1_stun': {error,
                                        {"no such file or directory",
                                         "p1_stun.app"}}

What is missing here?

Well, I got further by

Well, I got further by disabling 'ejabberd_stun'. Now ejabberd starts and I was able to convert ejabberd.cfg to ejabberd.yml. Now where does ejabberd expect to find the ejabberd.yml configuration file? Apparently not in /opt/ejabberd-13.10/conf/ejabberd.yml, because once I moved ejabberd.cfg out of the way all I get in the logs is this:

2013-10-31 00:54:31.690 [error] <0.37.0>@ejabberd_config:get_plain_terms_file:170 Problem loading ejabberd config file /opt/ejabberd-13.10/conf/ejabberd.cfg : no such file or directory

So how do I get ejabberd to use the Yaml configuration file?

sdfsdf

daff wrote:

Well, I got further by disabling 'ejabberd_stun'. Now ejabberd starts and I was able to convert ejabberd.cfg to ejabberd.yml. Now where does ejabberd expect to find the ejabberd.yml configuration file? Apparently not in /opt/ejabberd-13.10/conf/ejabberd.yml, because once I moved ejabberd.cfg out of the way all I get in the logs is this:

2013-10-31 00:54:31.690 [error] <0.37.0>@ejabberd_config:get_plain_terms_file:170 Problem loading ejabberd config file /opt/ejabberd-13.10/conf/ejabberd.cfg : no such file or directory

So how do I get ejabberd to use the Yaml configuration file?

It's created in ejabberd's $HOME if the command is called with relative paths as arguments.

How i can use mod_shit with

How i can use mod_shit with ejabberd-13.10

Syndicate content