Hi all, since I updated "mod_storage_xmlarchive.lua" recently I assume that the following change is causing the error message below (which hits prosody.err quite(!) often): https://hg.prosody.im/prosody-modules/rev/591c643d55b2 This is version 0.11 on Debian Buster using LUA 5.1. Kind regards, Joerg. Apr 17 03:48:12 c2s556b2e10df40 error Traceback[c2s]: attempt to yield across metamethod/C-call boundary stack traceback: [C]: in function 'yield' /usr/local/lib/prosody/util/async.lua:75: in function 'wait' ...es/mod_storage_xmlarchive/mod_storage_xmlarchive.lua:140: in function 'tick' ...es/mod_storage_xmlarchive/mod_storage_xmlarchive.lua:344: in function '(for generator)' /usr/local/lib/prosody/modules/mod_mam/mod_mam.lua:156: in function '?' /usr/local/lib/prosody/util/events.lua:79: in function </usr/local/lib/prosody/util/events.lua:75> (tail call): ? (tail call): ? (tail call): ? /usr/local/lib/prosody/util/events.lua:79: in function </usr/local/lib/prosody/util/events.lua:75> (tail call): ? /usr/local/lib/prosody/core/stanza_router.lua:181: in function 'core_post_stanza' /usr/local/lib/prosody/core/stanza_router.lua:127: in function 'core_process_stanza' /usr/local/lib/prosody/modules/mod_c2s.lua:276: in function 'func' /usr/local/lib/prosody/util/async.lua:127: in function </usr/local/lib/prosody/util/async.lua:1 Apr 17 03:48:12 util.async error unexpected async state: thread not suspended

I can confirm that reverting the change... https://hg.prosody.im/prosody-modules/rev/591c643d55b2 ... let the tracebacks/errors disapper. Kind regards, Joerg.

Thanks for the report. A workaround, not a fix: https://hg.prosody.im/prosody-modules/rev/b92147edd172 Be prepared for the solution involving dropping support for Lua 5.1, as the number of minor problems it causes to maintain support for it is reaching uncomfortable levels.

• tags Status-Accepted Component-Async