What steps will reproduce the problem? After having upgraded the module mod_mam to the latest version including all updates since changeset 2644 I get stack tracebacks like: Sep 18 12:33:29 general warn Attempt to read a non-existent global 'clone_for_storage' stack traceback: /usr/local/lib/prosody/modules/mod_mam/mod_mam.lua:320: in function </usr/local/lib/prosody/modules/mod_mam/mod_mam.lua:265> (tail call): ? /usr/local/lib/prosody/util/events.lua:67: in function 'fire_event' ... And mod_cloud_notify is "unhappy", too, since the update of the mod_mam module: Sep 18 12:33:29 mod_c2s error Traceback[c2s]: /usr/local/lib/prosody/modules/mod_cloud_notify.lua:376: attempt to index local 'stanza' (a nil value) stack traceback: /usr/local/lib/prosody/modules/mod_cloud_notify.lua:376: in function '?' /usr/local/lib/prosody/util/events.lua:67: in function </usr/local/lib/prosody/util/events.lua:63> (tail call): ? /usr/local/lib/prosody/modules/mod_mam/mod_mam.lua:320: in function </usr/local/lib/prosody/modules/mod_mam/mod_mam.lua:265> ... I think messages to offline users get lost, maybe even to online users, not sure to 100%. What version of the product are you using? On what operating system? 0.9.12 Debian 7.X LTS. Please provide any additional information below. After having reverted the module mod_mam.lua to the version prior to changeset 2644 the server seems to be working as expected again.

Hi. I believe this issue was fixed, but I can't say for sure. Numeric changeset ids are not portable outside of your local machine so I can't know which version or even which repository you got your mod_mam from. Try updating and see if the problem goes away.

• tags Status-NeedInfo
• owner Zash

I think you are right, I missed that patch: https://hg.prosody.im/prosody-modules/rev/1872a9129c2f So the latest version of mod_mam seems to be working fine. You can safely close this issue. Thanks for the speedy response, and keep up the good work, kind regards, Joerg.

Thanks

• tags Status-Fixed