#1528 mod_lastlog traceback for nonexistent domain

Reporter Slavko
Owner Nobody
Stars ★ (1)
  • Status-New
  • Type-Defect
  • Priority-Medium
  • Component-Community
  1. Slavko on

    What steps will reproduce the problem? 1. the example.org is not hosted on my prosody 2. run: prosodyctl mod_lastlog someuser@example.com What is the expected output? I expect the same result as for nonexistent user: No record found What do you see instead? I got ugly traceback: Failed to execute command: Error: /usr/lib/prosody/core/storagemanager.lua:65: attempt to index local 'host_session' (a nil value) stack traceback: /usr/lib/prosody/core/storagemanager.lua:65: in function 'initialize_host' /usr/lib/prosody/modules/mod_lastlog/mod_lastlog.lua:78: in function </usr/lib/prosody/modules/mod_lastlog/mod_lastlog.lua:72> [C]: in function 'xpcall' /usr/lib/prosody/core/modulemanager.lua:325: in function 'call_module_method' /usr/bin/prosodyctl:1335: in function 'func' /usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125> What version of the product are you using? On what operating system? It is from Debian's buster-backports -- 0.0~hg20200128.09e7e880e056+dfsg-1~bpo10+1

  2. Zash on

    • tags Component-Community

New comment

Not published. Used for spam prevention and optional update notifications.