Hi,
I just installed the newest prosody 0.10 version from your Debian Repo on My Ubuntu Server 14.04 machine. When Prosody restarted, I got these error messages:
modulemanager error Error initializing module 'http' on 'trashserver.net': /usr/lib/prosody/core/certmanager.lua:63: bad argument #1 to 'format' (string expected, got nil)
stack traceback:
/usr/lib/prosody/core/modulemanager.lua:30: in function </usr/lib/prosody/core/modulemanager.lua:30>
[C]: in function 'format'
/usr/lib/prosody/core/certmanager.lua:63: in function 'find_cert'
/usr/lib/prosody/core/certmanager.lua:112: in function 'create_context'
/usr/lib/prosody/core/portmanager.lua:113: in function 'activate'
/usr/lib/prosody/core/portmanager.lua:162: in function 'register_service'
/usr/lib/prosody/core/portmanager.lua:221: in function '?'
/usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74>
(tail call): ?
(tail call): ?
/usr/lib/prosody/core/moduleapi.lua:312: in function 'add_item'
...
/usr/lib/prosody/core/modulemanager.lua:75: in function '?'
/usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74>
(tail call): ?
/usr/lib/prosody/core/hostmanager.lua:113: in function 'activate'
/usr/lib/prosody/core/hostmanager.lua:59: in function '?'
/usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74>
(tail call): ?
/usr/bin/prosody:346: in function 'prepare_to_start'
/usr/bin/prosody:414: in main chunk
[C]: ?
... (and more error messages because the http module could not be loaded and different modules depend on mod_http).
Is there any way I can fix this by myself? Or do I have to wait for a bugfix?
Regards,
Thomas
MattJ
on
Hi Thomas, thanks for the report! Sorry you're affected by this issue. We're working on a fix, meanwhile you can use the 209 nightly build: https://prosody.im/nightly/0.10/build209/
Changes
owner MattJ
tags Status-Fixed
MattJ
on
Didn't mean to set the status to fixed back then! However, it is now fixed. The fix will be in the next nightly build (build 211) which is due in about 7 hours from now.
Feel free to reopen this issue if you still see the problem after upgrading tomorrow. If you notice any other issues, please create a new report. Thanks!!
Hi, I just installed the newest prosody 0.10 version from your Debian Repo on My Ubuntu Server 14.04 machine. When Prosody restarted, I got these error messages: modulemanager error Error initializing module 'http' on 'trashserver.net': /usr/lib/prosody/core/certmanager.lua:63: bad argument #1 to 'format' (string expected, got nil) stack traceback: /usr/lib/prosody/core/modulemanager.lua:30: in function </usr/lib/prosody/core/modulemanager.lua:30> [C]: in function 'format' /usr/lib/prosody/core/certmanager.lua:63: in function 'find_cert' /usr/lib/prosody/core/certmanager.lua:112: in function 'create_context' /usr/lib/prosody/core/portmanager.lua:113: in function 'activate' /usr/lib/prosody/core/portmanager.lua:162: in function 'register_service' /usr/lib/prosody/core/portmanager.lua:221: in function '?' /usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74> (tail call): ? (tail call): ? /usr/lib/prosody/core/moduleapi.lua:312: in function 'add_item' ... /usr/lib/prosody/core/modulemanager.lua:75: in function '?' /usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74> (tail call): ? /usr/lib/prosody/core/hostmanager.lua:113: in function 'activate' /usr/lib/prosody/core/hostmanager.lua:59: in function '?' /usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74> (tail call): ? /usr/bin/prosody:346: in function 'prepare_to_start' /usr/bin/prosody:414: in main chunk [C]: ? ... (and more error messages because the http module could not be loaded and different modules depend on mod_http). Is there any way I can fix this by myself? Or do I have to wait for a bugfix? Regards, Thomas
Hi Thomas, thanks for the report! Sorry you're affected by this issue. We're working on a fix, meanwhile you can use the 209 nightly build: https://prosody.im/nightly/0.10/build209/
ChangesDidn't mean to set the status to fixed back then! However, it is now fixed. The fix will be in the next nightly build (build 211) which is due in about 7 hours from now. Feel free to reopen this issue if you still see the problem after upgrading tomorrow. If you notice any other issues, please create a new report. Thanks!!