Hi,
My server acts strangely. When started, it crashes in a few minutes with emfile or enfile error. In last log I wathed this records, and it seems to me it establishes s2s connections to itself until crash due to limit exceeded. Why this happens? Why it connects to itself?
=INFO REPORT==== 2008-03-26 10:06:47 ===
I(<0.205.0>:ejabberd_listener:90): (#Port<0.46780>) Accepted connection {{10,0,0,1},39779} -> {{10,0,0,1},5269}
=INFO REPORT==== 2008-03-26 10:06:47 ===
I(<0.3054.0>:ejabberd_s2s_in:104): started: {gen_tcp,#Port<0.46780>}
=INFO REPORT==== 2008-03-26 10:06:48 ===
I(<0.3053.0>:ejabberd_s2s_out:662): terminated: normal
=INFO REPORT==== 2008-03-26 10:07:07 ===
I(<0.615.0>:ejabberd_s2s_in:316): GET KEY: {"ejabberd.root","ejabberd.root",[],
"ad076be92bc4f0d809030907b6835e22650ea764"}
=INFO REPORT==== 2008-03-26 10:07:07 ===
I(<0.3058.0>:ejabberd_s2s_out:106): started: {"ejabberd.root","ejabberd.root",
{verify,<0.615.0>,
"ad076be92bc4f0d809030907b6835e22650ea764",
"2587456236"}}
=INFO REPORT==== 2008-03-26 10:07:07 ===
I(<0.3057.0>:ejabberd_listener:90): (#Port<0.61627>) Accepted connection {{10,0,0,1},39781} -> {{10,0,0,1},5269}
=INFO REPORT==== 2008-03-26 10:07:07 ===
I(<0.3059.0>:ejabberd_s2s_in:104): started: {gen_tcp,#Port<0.61627>}
=INFO REPORT==== 2008-03-26 10:07:07 ===
I(<0.3058.0>:ejabberd_s2s_out:662): terminated: normal
Maybe DNS is bad configured?
Yes, it is very strange.
How did you install ejabberd: binary installer, compiled from source, package from an operating system ...?
What version of ejabberd: 1.1.4, 2.0.0, SVN ...?
When did this strange behaviour start: you updated ejabberd, or Erlang, or modified DNS, modified ejabberd.cfg ...?
Could it be a misconfiguration in the DNS server?
Installed from source.
Installed from source. Version 1.1.4
It starts for no apparent reason...
I've done many things to stop this issue, and in the end I notice that if I block traffic from a neighbor jabber sever and restart ejabberd it works properly. Then a few days after I do unblock that server and now everything is ok. So problem disappeared as suddenly as it appeared.
I think it really could be a DNS issue but I have no actual proof...