ejabberd - Comments for "doesn't establish connections anymore"

Got it running again. :-) I

Shakademus — Sun, 02 May 2010 07:20:15 +0000

Got it running again. :-)

I made a backup and then ran 'aptitude reinstall'. Since that flushed the hostname and admin user out auf the configuration file, I then used dpkg-reconfigure to set those settings. Then everything worked fine and I didn't even have to import the backup - all the data got preserved.

Sadly, I don't know whether the reinstall or the reconfiguration did the trick (should have tried the reconf first...)

It is, no intrusion happened;

Shakademus — Sat, 24 Apr 2010 23:16:39 +0000

It is, no intrusion happened; so it'll be the reinstallation... Hope it helps.

Random port: typical in erlang

mfoss — Sat, 24 Apr 2010 19:22:48 +0000

Shakademus wrote:

What I just mentioned when looking for the webadmin: Besides c2s, s2s, http and a locally listening port 7777, there's a port 34188 beam is listening on. May it be the daemon got hacked? Could be a remote shell I guess...

That random-looking port number is typical in erlang, see
http://www.process-one.net/en/ejabberd/guide_en#firewall

How to reproduce:
1. In a shell execute:

erl -sname aaa

2. In another shell execute:

$ epmd -names
epmd: up and running on port 4369 with data:
name aaa at port 44399

3. Then verify this is the port number that you found intriguing:

$ netstat -nlp | grep beam
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 0.0.0.0:44399           0.0.0.0:*               LISTEN      11513/beam.smp

No, s2s connection do not

Shakademus — Sat, 24 Apr 2010 17:29:45 +0000

No, s2s connection do not work as well. As I said the logs only show an 'Accepted connection' message, no 'Connection established' or anything else following.

What I said about authentication was wrong. I mixed that up, sorry. In fact I _do_ use the standard internal method.

Connecting to webadmin, I get a 404 Not Found page. I don't know whether that's normal or not, since I've never used it before. But the good news: Calling webadmin, the connection does not terminate abnormally, just normal responses. Log shows:

=INFO REPORT==== 2010-04-24 19:03:27 ===
I(<0.248.0>:ejabberd_listener:112) : (#Port<0.744>) Accepted connection {{92,226
,110,251},50207} -> {{89,238,65,243},5280}
=INFO REPORT==== 2010-04-24 19:03:27 ===
I(<0.241.0>:ejabberd_http:123) : started: {gen_tcp,#Port<0.744>}

So it seems the problem is bound to just xmpp connections.

I think I'll try to reinstall these days, although I would really like to know what's wrong / what happened.

Try to use "Service

mfoss — Sat, 24 Apr 2010 14:58:18 +0000

Try to use "Service Discovery" from a remote server (like jabber.org) to your ejabberd. If you can see your MUC service, Pubsub, Vjud... then the problem is only in client connections.

You say that in ejabberd.cfg you don't use the internal auth_method. In that case, configure auth_method to use internal, register some dummy account "dummy123", and try to login to it. If that works, it means the problem is only in your specific auth method.

You can also check if ejabberd WebAdmin works or not.