What steps will reproduce the problem?
1. Install mod vjud
2. Define it in config:
Component("search." .. domain) "vjud"
server_user_role = "prosody:registered"
parent_host = "xmpp." .. domain
vjud_mode = "all"
3. See logs:
prosody | modulemanager error Error initializing module 'vjud' on 'search.example.org': /usr/share/lua/5.4/prosody/core/moduleapi.lua:135: Failed to load plugin library 'vcard', error: /usr/lib/prosody/modules/share/lua/5.4/mod_vcard/vcard.lib.lua: No such file or directory
prosody | stack traceback:
prosody | [C]: in function 'error'
prosody | /usr/share/lua/5.4/prosody/core/moduleapi.lua:135: in function 'prosody.core.moduleapi.require'
prosody | /var/lib/prosody/custom_plugins/share/lua/5.4/mod_vjud.lua:7: in main chunk
prosody | [C]: in function 'xpcall'
prosody | /usr/share/lua/5.4/prosody/core/modulemanager.lua:291: in upvalue 'do_load_module'
prosody | /usr/share/lua/5.4/prosody/core/modulemanager.lua:378: in function 'prosody.core.modulemanager.load'
prosody | /usr/share/lua/5.4/prosody/core/modulemanager.lua:149: in function 'prosody.core.modulemanager.load_modules_for_host'
prosody | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77>
prosody | (...tail calls...)
prosody | /usr/share/lua/5.4/prosody/core/hostmanager.lua:108: in function 'prosody.core.hostmanager.activate'
prosody | /usr/share/lua/5.4/prosody/core/hostmanager.lua:58: in field '?'
prosody | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77>
prosody | (...tail calls...)
prosody | /usr/share/lua/5.4/prosody/util/startup.lua:468: in field '?'
prosody | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77>
prosody | (...tail calls...)
prosody | /usr/share/lua/5.4/prosody/util/fsm.lua:25: in upvalue 'notify_transitioned'
prosody | /usr/share/lua/5.4/prosody/util/fsm.lua:58: in method 'begin_startup'
prosody | /usr/share/lua/5.4/prosody/util/startup.lua:494: in function 'prosody.util.startup.prepare_to_start'
prosody | /usr/share/lua/5.4/prosody/util/startup.lua:953: in function 'prosody.util.startup.prosody'
prosody | /usr/share/lua/5.4/prosody/util/async.lua:161: in function 'prosody.util.async.default_runner_func'
prosody | /usr/share/lua/5.4/prosody/util/async.lua:149: in function </usr/share/lua/5.4/prosody/util/async.lua:147>
What is the expected output?
Working mod vjud
What do you see instead?
Not working vjud
What version of the product are you using? On what operating system?
Prosody 13.0.2 in docker container (https://github.com/prosody/prosody-docker/blob/master/Dockerfile), but a bit customised
Zash
on
Thanks for the report. This is a community module, feel free to help improve this.
This specific error is because the module is not maintained and its metadata has not been updated to include the additional library in the plugin installer package.
Compare to other multi-file modules, e.g. https://hg.prosody.im/prosody-modules/file/cc665f343690/mod_firewall/README.md
However since mod_vjud is based on vcard-temp instead of vcard4, it still will not work right with modern Prosody anyway, and that is the larger task if someone wants to pick up maintenance.
What steps will reproduce the problem? 1. Install mod vjud 2. Define it in config: Component("search." .. domain) "vjud" server_user_role = "prosody:registered" parent_host = "xmpp." .. domain vjud_mode = "all" 3. See logs: prosody | modulemanager error Error initializing module 'vjud' on 'search.example.org': /usr/share/lua/5.4/prosody/core/moduleapi.lua:135: Failed to load plugin library 'vcard', error: /usr/lib/prosody/modules/share/lua/5.4/mod_vcard/vcard.lib.lua: No such file or directory prosody | stack traceback: prosody | [C]: in function 'error' prosody | /usr/share/lua/5.4/prosody/core/moduleapi.lua:135: in function 'prosody.core.moduleapi.require' prosody | /var/lib/prosody/custom_plugins/share/lua/5.4/mod_vjud.lua:7: in main chunk prosody | [C]: in function 'xpcall' prosody | /usr/share/lua/5.4/prosody/core/modulemanager.lua:291: in upvalue 'do_load_module' prosody | /usr/share/lua/5.4/prosody/core/modulemanager.lua:378: in function 'prosody.core.modulemanager.load' prosody | /usr/share/lua/5.4/prosody/core/modulemanager.lua:149: in function 'prosody.core.modulemanager.load_modules_for_host' prosody | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77> prosody | (...tail calls...) prosody | /usr/share/lua/5.4/prosody/core/hostmanager.lua:108: in function 'prosody.core.hostmanager.activate' prosody | /usr/share/lua/5.4/prosody/core/hostmanager.lua:58: in field '?' prosody | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77> prosody | (...tail calls...) prosody | /usr/share/lua/5.4/prosody/util/startup.lua:468: in field '?' prosody | /usr/share/lua/5.4/prosody/util/events.lua:81: in function </usr/share/lua/5.4/prosody/util/events.lua:77> prosody | (...tail calls...) prosody | /usr/share/lua/5.4/prosody/util/fsm.lua:25: in upvalue 'notify_transitioned' prosody | /usr/share/lua/5.4/prosody/util/fsm.lua:58: in method 'begin_startup' prosody | /usr/share/lua/5.4/prosody/util/startup.lua:494: in function 'prosody.util.startup.prepare_to_start' prosody | /usr/share/lua/5.4/prosody/util/startup.lua:953: in function 'prosody.util.startup.prosody' prosody | /usr/share/lua/5.4/prosody/util/async.lua:161: in function 'prosody.util.async.default_runner_func' prosody | /usr/share/lua/5.4/prosody/util/async.lua:149: in function </usr/share/lua/5.4/prosody/util/async.lua:147> What is the expected output? Working mod vjud What do you see instead? Not working vjud What version of the product are you using? On what operating system? Prosody 13.0.2 in docker container (https://github.com/prosody/prosody-docker/blob/master/Dockerfile), but a bit customised
Thanks for the report. This is a community module, feel free to help improve this. This specific error is because the module is not maintained and its metadata has not been updated to include the additional library in the plugin installer package. Compare to other multi-file modules, e.g. https://hg.prosody.im/prosody-modules/file/cc665f343690/mod_firewall/README.md However since mod_vjud is based on vcard-temp instead of vcard4, it still will not work right with modern Prosody anyway, and that is the larger task if someone wants to pick up maintenance.
Changes