Is this expected behavior when using mod_smacks?

[Corn This]

I'm running a private server for a handful of people.  They're reporting occasionally getting "recipient-unavailable" errors despite the person being online.  Looking at the log, it seems like those using Conversations on Android are reconnecting, with consistency, every 10 or every 20 minutes, with the occasional read timeout as shown.  Below is a sample from the log regarding two different users, both using Conversations.  Is this expected?  If not, what should I change to reduce or eliminate it?

Jul 06 02:30:00 info    Client connected
Jul 06 02:30:01 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 02:30:01 info    Authenticated as us...@my.xmpp.server
Jul 06 02:40:18 info    Client connected
Jul 06 02:40:18 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 02:40:18 info    Authenticated as us...@my.xmpp.server
Jul 06 02:50:18 info    Client connected
Jul 06 02:50:19 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 02:50:19 info    Authenticated as us...@my.xmpp.server
Jul 06 03:40:01 info    Client connected
Jul 06 03:40:01 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 03:40:01 info    Authenticated as us...@my.xmpp.server
Jul 06 03:50:17 info    Client connected
Jul 06 03:50:18 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 03:50:18 info    Authenticated as us...@my.xmpp.server
Jul 06 04:04:36 info    Client disconnected: read timeout
Jul 06 04:10:01 info    Client connected
Jul 06 04:10:02 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 04:10:02 info    Authenticated as us...@my.xmpp.server


Jul 06 06:00:18 info    Client connected
Jul 06 06:00:18 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 06:00:18 info    Authenticated as us...@my.xmpp.server
Jul 06 06:20:01 info    Client connected
Jul 06 06:20:01 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 06:20:01 info    Authenticated as us...@my.xmpp.server
Jul 06 06:40:01 info    Client connected
Jul 06 06:40:01 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 06:40:02 info    Authenticated as us...@my.xmpp.server
Jul 06 07:00:01 info    Client connected
Jul 06 07:00:01 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 07:00:01 info    Authenticated as us...@my.xmpp.server
Jul 06 07:02:15 info    Client disconnected: closed
Jul 06 07:21:57 info    Client connected
Jul 06 07:21:57 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 07:21:57 info    Authenticated as us...@my.xmpp.server
Jul 06 07:40:12 info    Client connected
Jul 06 07:40:12 info    Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 06 07:40:13 info    Authenticated as us...@my.xmpp.server

[Тимофей Ёлкин]

Thank you very much, Corn. It's my mistake. Trouble was in jabber-client settings, I forgot set "include room in public lists" in Pidgin

пн, 6 июл. 2020 г. в 16:40, Corn This <cornelius...@gmail.com>:

--
You received this message because you are subscribed to the Google Groups "Prosody IM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prosody-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/prosody-users/01495c91-26e3-4453-b50e-6d7a9cfd2331o%40googlegroups.com.