ejabberd - Comments for "ejabberd 13.10"

modules need update

searockcliff — Thu, 28 Nov 2013 05:14:24 +0000

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

tixetsal — Sat, 23 Nov 2013 19:16:01 +0000

badlop wrote:

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

Where is this guide?

(edit) Never mind. I found it.

How i can use mod_shit with

Drag7n — Thu, 21 Nov 2013 17:38:23 +0000

How i can use mod_shit with ejabberd-13.10

Stable version?

Azendale — Sun, 10 Nov 2013 03:34:14 +0000

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.

sdfsdf

zinid — Fri, 08 Nov 2013 14:42:37 +0000

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.

Well, I got further by

daff — Thu, 31 Oct 2013 00:08:50 +0000

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?

I have the same problem, but

daff — Wed, 30 Oct 2013 23:42:12 +0000

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?

I guess you are running from

mfoss — Tue, 29 Oct 2013 12:41:00 +0000

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.

convert_to_yaml

MarkT — Mon, 14 Oct 2013 06:42:03 +0000

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