-
benk
Does anyone know what causes: > Stream closed by local host: Idle connection (connection-timeout)
-
MattJ
benk, some servers close idle connections, so I assume it's that
-
benk
But I can't send messages to this federated contact. I don't know whether to blame his server or mine
-
MattJ
That message, alone, doesn't sound like the culprit
-
MattJ
Closing idle connections happens all the time
-
benk
I would assume so, but it's unusual that messages are failing to send because of this
-
MattJ
I agree it's unusual, so I would suspect a different cause
-
benk
the last time I had a federation issue the other admin simply had to restart ejabberd, so maybe one of our servers has gotten into a state
-
Zash
Closing idle connections wouldn't be the cause, but it would mean that the connection has to be reestablished, which could run into trouble that only the initiating side sees.
-
MattJ
That doesn't sound normal. There are ejabberd servers with plenty of uptime, and I doubt a restart is the least disruptive way to solve 99% of issues.
-
MattJ
Yeah, this is the kind of thing I'd expect to see more of if bidi was widely deployed :)
- benk starts looking into logs
-
MattJ
afaik ejabberd doesn't support that yet
-
benk
> 2022-07-27 20:09:32.352413+05:00 [warning] <0.15150.0>@ejabberd_s2s_out:process_closed/2:157 Failed to establish outbound s2s connection kwiecien.us -> chiajlingvoj.ynh.fr: Stream closed by local host: Idle connection (connection-timeout); bouncing for 37 seconds
-
benk
this is what I'm seeing a few times in the last case
-
MattJ
Okay, that is a bit strange
-
MattJ
I'd maybe take that to the ejabberd support MUC, maybe they know what could be going on
-
benk
will do