prosody trunk hg:867ac771fb6e prosodyctl about general warn Attempt to read a non-existent global 'once' stack traceback: /home/md85/lib/prosody/util/async.lua:236: in main chunk [C]: in function 'require' /home/md85/lib/prosody/core/storagemanager.lua:12: in main chunk [C]: in function 'require' /home/md85/lib/prosody/core/usermanager.lua:18: in main chunk [C]: in function 'require' /home/md85/lib/prosody/util/startup.lua:469: in function 'make_host' /home/md85/lib/prosody/util/startup.lua:481: in function 'make_dummy_hosts' /home/md85/lib/prosody/util/startup.lua:499: in function 'prosodyctl' /home/md85/bin/prosodyctl:49: in main chunk [C]: in ? Prosody (unknown version) # Prosody directories Data directory: /home/md85/var/lib/prosody Config directory: /home/md85/etc/prosody Source directory: /home/md85/lib/prosody Plugin directories: /home/md85/opt/prosody-modules/ /home/md85/lib/prosody/modules/ # Lua environment Lua version: Lua 5.2 Lua module search paths: /home/md85/lib/prosody/?.lua /home/md85/.luarocks/share/lua/5.2/?.lua /home/md85/.luarocks/share/lua/5.2/?/init.lua /home/md85/share/lua/5.2/?.lua /home/md85/share/lua/5.2/?/init.lua Lua C module search paths: /home/md85/lib/prosody/?.so /home/md85/.luarocks/lib/lua/5.2/?.so /home/md85/lib/lua/5.2/?.so LuaRocks: Installed (2.4.3) # Lua module versions lfs: LuaFileSystem 1.7.0 libevent: 2.1.8-stable luaevent: 0.4.4 lxp: LuaExpat 1.3.0 socket: LuaSocket 3.0-rc1 ssl: 0.7 After updating my prosody trunk I got the following traceback: Mar 23 15:34:26 storagemanager warn ASYNC-01: Attempt to access storage outside async context, see https://prosody.im/doc/developers/async - stack traceback: /home/md85/lib/prosody/core/storagemanager.lua:53: in function 'delete' /home/md85/lib/prosody/modules/mod_mam/mod_mam.lua:373: in function </home/md85/lib/prosody/modules/mod_mam/mod_mam.lua:369> (...tail calls...) [C]: in function 'xpcall' /home/md85/lib/prosody/util/timer.lua:42: in function 'callback' /home/md85/lib/prosody/net/server_select.lua:872: in function '?' /home/md85/lib/prosody/net/server_select.lua:903: in function </home/md85/lib/prosody/net/server_select.lua:895> [C]: in function 'xpcall' /home/md85/bin/prosody:79: in function 'loop' /home/md85/bin/prosody:89: in main chunk [C]: in ?

Thanks for the report!

• title Storagemanager ASYNC-01 warning Storagemanager ASYNC-01 warning in prosodyctl
• tags Milestone-0.11 Status-Accepted

I was confused by the two different tracebacks.

• title Storagemanager ASYNC-01 warning in prosodyctl Storagemanager ASYNC-01 warning in timers

Bumping async to 0.12

• tags Milestone-0.11 Milestone-0.12

mod_mam now runs its cleanup job in an async runner since https://hg.prosody.im/trunk/rev/ddc07fb8dcd4 so this particular issue has been fixed. The question remains whether we should have some generic central solution that covers all timers, or if it's enough to do it like mod_mam in the cases that need it?