Package: prosody-modules Version: 0.0~hg20190203.b54e98d5c4a1+dfsg-1+deb10u1 Severity: normal Tags: patch
Dear Maintainer, Module "mam" was enabled using the "memory" storage. Initially it was working fine, after some time clients weren't able to exchange messages any more. Log of Prosody shows: Jan 31 18:40:47 ... error Traceback[c2s]: /usr/lib/prosody/modules/mod_storage_memory.lua:59: attempt to concatenate a nil value stack traceback: /usr/lib/prosody/modules/mod_storage_memory.lua:59: in function 'append' /usr/lib/prosody/modules/mod_mam/mod_mam.lua:303: in function '?' /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75> (...tail calls...) /usr/lib/prosody/core/stanza_router.lua:180: in function 'core_post_stanza' /usr/lib/prosody/core/stanza_router.lua:127: in function 'core_process_stanza' /usr/lib/prosody/modules/mod_c2s.lua:276: in function 'func' /usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125> This is fixed upstream since prosody-0.11.3 https://prosody.im/doc/release/0.11.3 https://issues.prosody.im/1326 Patch: https://hg.prosody.im/trunk/rev/40ed04014b97 Testing patch based on prosody-modules-0.0~hg20190203.b54e98d5c4a1+dfsg-1+deb10u1 and prosody-0.11.2-1. So far all is fine. -- System Information: [removed info from local system] Affected system runs buster with all updates