ejabberd aggregator

Mailing list: Re: Crash on Ubuntu 14.04

Fri, 22 Jul 2016 17:38:43 +0200

Am 21.07.2016 um 03:20 schrieb David Cunningham:

Well, can't say what you did different, but I just tried a freshly
installed Ubuntu 14.04 and ejabberd 2.1.11 started up without problems.

Then I gave ejabberd 15.07 from jabber.at a try, that also worked right
away.

Regards,

Mailing list: Re: Error: REST request is rejected by service

Fri, 22 Jul 2016 13:11:11 +0200


The HTTP response code suggests that the client is not capable of
accepting the server’s response. Is your client perhaps sending an
Accept header such as |Accept: text/plain| where ejabberd is expecting
to send a response of content-type |application/xml|?

JT

Mailing list: Re: Error: REST request is rejected by service

Fri, 22 Jul 2016 11:55:57 +0200

With a similar configuration than you, using ejabberd 16.06 and recent
mod_rest,this call works correctly for me:

$ wget http://localhost:5280/rest/ --server-response --post-data
'<presence to="user1< at >localhost" from="other< at >foo.com"><status>On the
phone</status></presence>'

--2016-07-22 13:51:22--  http://localhost:5280/rest/
S'està resolent localhost (localhost)… 127.0.0.1
S'està connectant a localhost (localhost)|127.0.0.1|:5280…connectat.
HTTP: s'ha enviat la petició, s'està esperant una resposta…
  HTTP/1.1 200 OK
  Content-Type: text/htmread more

Mailing list: Error: REST request is rejected by service

Fri, 22 Jul 2016 05:52:53 +0200

Hi, I'm trying to push presence updates to XMPP clients, and have been working with mod_rest. When an HTTP request is sent it gets an error "REST request is rejected by service". I'm sure the client IP is allowed in the mod_rest configuration so what could be wrong?

Mailing list: Re: External authentication crashed with reason: bad argument in extauth:call_port/2

Fri, 22 Jul 2016 00:54:52 +0200

Hi Holger,

Yes, the external script was running before and was still running
afterwards. It has logging and did not record any request to perform user
authentication. This is only for the /admin/ web page. XMPP clients do
authenticate successfully.


On 22 July 2016 at 01:20, Holger Weiß <holger< at >zedat.fu-berlin.de> wrote:

Mailing list: Re: External authentication crashed with reason: bad argument in extauth:call_port/2

Thu, 21 Jul 2016 15:20:29 +0200

* David Cunningham <dcunningham< at >voisonics.com> [2016-07-21 22:10]:

Is the 'extauth' script still running after that error?  Are you sure it
was running immediately before that error?  Do you see any [error] or
[critical] messages in the log before this happens?

Does the script work for other things (such as authenticating with an
XMPP client) or did you not test that?

Holger

Mailing list: Re: External authentication crashed with reason: bad argument in extauth:call_port/2

Thu, 21 Jul 2016 12:10:18 +0200

Hi Holger, Thanks for the reply.

Mailing list: Re: External authentication crashed with reason: bad argument in extauth:call_port/2

Thu, 21 Jul 2016 12:07:30 +0200

* David Cunningham <dcunningham< at >voisonics.com> [2016-07-21 11:24]:

You should have a full trace in your crash.log file, could you show
that?

What ejabberd version are you using?

Holger

Mailing list: acl database problems in 16.01

Thu, 21 Jul 2016 09:05:33 +0200

Hello! Just installed fresh ubuntu 16.04 and ejabberd 16.01 from it. I configured (yml) ldap authentication and declared myself as admin: acl: ## ## The 'admin' ACL grants administrative privileges to XMPP accounts. ## You can put here as many accounts as you want. ## admin: user: - "dm": "jabber.mydomain" Then started ejabberd and login through web interface. I see that in host config acl database is in RAM (I'm back translating from russian). If I set it to RAM & disk then acl database file appears, but if I restart ejabberd it removes file a

Mailing list: External authentication crashed with reason: badargument in extauth:call_port/2

Thu, 21 Jul 2016 01:24:31 +0200

Hello, I'm using external authentication and have a perl program which is started by ejabberd correctly.

Mailing list: Re: Crash on Ubuntu 14.04

Thu, 21 Jul 2016 01:20:07 +0200

Just to update, I reinstalled using the repository from https://jabber.at
but it had the same issue. Then I installed using the .deb from ejabberd.im
and that worked fine.


On 20 July 2016 at 07:16, David Cunningham <dcunningham< at >voisonics.com>
wrote:

Mailing list: manage

Wed, 20 Jul 2016 12:13:15 +0200

Hi,
How to manage ejabberd cluster?
how to change ejabberd configure without restart ejabberd?
max ejabberd nodes in cluster?


thanks in advance
_______________________________________________
ejabberd mailing list
ejabberd< at >jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

Mailing list: Re: Crash on Ubuntu 14.04

Tue, 19 Jul 2016 21:16:54 +0200

Hi Philipp,

Thanks for the ideas. The process isn't running. I'll try upgrading to a
newer version.


On 19 July 2016 at 22:41, Philipp Huebner <debalance< at >debian.org> wrote:

Mailing list: Re: Crash on Ubuntu 14.04

Tue, 19 Jul 2016 12:41:08 +0200

Hi,

Am 19.07.2016 um 14:09 schrieb David Cunningham:

on Debian/Ubuntu, ejabberd is automatically started upon installation,

I guess your ejabberd is already running, when I call "ejabberdctl live"
in that situation I get a crash as well.

Use "/etc/init.d/ejabberd start|stop|restart" or call
"service ejabberd start|stop|restart" on your system.

As for that version - that is indeed quite old.
I'd suggest to use Debian Jessie with Backports, or a newer Ubuntu
Release, or use the repository from https://jabber.at/en/apt-repository
(preferrably in that order ;) )

Regards,

Mailing list: Crash on Ubuntu 14.04

Tue, 19 Jul 2016 12:09:50 +0200

Hello,

I've installed ejabberd on Ubuntu 14.04 (using the distro package) but from
time of installation it has always immediately crashed.

It seems the error is:
# ejabberdctl live
{error_logger,{{2016,7,19},{4,56,59}},"Protocol: ~tp: register/listen
error: ~tp~n",["inet_tcp",econnrefused]}

I've googled and found suggestions like:
- Check the hostname is resolvable (it is, in /etc/hosts and DNS)
- Check /var/lib/ejabberd/.erlang.cookie is owned by the ejabberd user (it
is)
- Check nothing else is listening on port 4369 (nothing is)

What else could I check?read more