#592 loggingmanager.lua:262: bad argument #3 to 'format'
Reporter
Roi
Owner
Waqas
Created
Updated
Stars
★ (1)
Tags
Status-Fixed
Milestone-0.10
Weirdness-Very
Type-Defect
Priority-Medium
Roi
on
prosody-0.9 1nightly255-1~sid running on Debian amd64
Jan 14 18:06:43 mod_c2s error Traceback[c2s]: /usr/lib/prosody/core/loggingmanager.lua:262: bad argument #3 to 'format' (string expected, got nil)
stack traceback:
[C]: in function 'format'
/usr/lib/prosody/core/loggingmanager.lua:262: in function '?'
/usr/lib/prosody/util/logger.lua:48: in function </usr/lib/prosody/util/logger.lua:46>
(tail call): ?
/usr/lib/prosody/util/datamanager.lua:272: in function 'list_load'
/usr/lib/prosody/modules/mod_offline.lua:40: in function '?'
/usr/lib/prosody/util/events.lua:67: in function </usr/lib/prosody/util/events.lua:63>
(tail call): ?
/usr/lib/prosody/modules/mod_presence.lua:123: in function 'handle_normal_presence'
/usr/lib/prosody/modules/mod_presence.lua:325: in function '?'
...
/usr/lib/prosody/util/xmppstream.lua:255: in function 'feed'
/usr/lib/prosody/modules/mod_c2s.lua:230: in function 'data'
/usr/lib/prosody/modules/mod_c2s.lua:252: in function 'onincoming'
/usr/lib/prosody/net/server_event.lua:632: in function </usr/lib/prosody/net/server_event.lua:578>
[C]: in function 'loop'
/usr/lib/prosody/net/server_event.lua:793: in function </usr/lib/prosody/net/server_event.lua:792>
[C]: in function 'xpcall'
/usr/bin/prosody:376: in function 'loop'
/usr/bin/prosody:407: in main chunk
[C]: ?
Zash
on
The problem seems to be that the low-level `loadfile` call does not return an error message. That's really weird.
Changes
tagStatus-Accepted
tagha
Zash
on
Changes
tag-ha
tagDifficulty-Easy
tagWeirdness-Very
Zash
on
I think this is most likely related to #593, as seems to happens during loading of offline messages.
prosody-0.9 1nightly255-1~sid running on Debian amd64 Jan 14 18:06:43 mod_c2s error Traceback[c2s]: /usr/lib/prosody/core/loggingmanager.lua:262: bad argument #3 to 'format' (string expected, got nil) stack traceback: [C]: in function 'format' /usr/lib/prosody/core/loggingmanager.lua:262: in function '?' /usr/lib/prosody/util/logger.lua:48: in function </usr/lib/prosody/util/logger.lua:46> (tail call): ? /usr/lib/prosody/util/datamanager.lua:272: in function 'list_load' /usr/lib/prosody/modules/mod_offline.lua:40: in function '?' /usr/lib/prosody/util/events.lua:67: in function </usr/lib/prosody/util/events.lua:63> (tail call): ? /usr/lib/prosody/modules/mod_presence.lua:123: in function 'handle_normal_presence' /usr/lib/prosody/modules/mod_presence.lua:325: in function '?' ... /usr/lib/prosody/util/xmppstream.lua:255: in function 'feed' /usr/lib/prosody/modules/mod_c2s.lua:230: in function 'data' /usr/lib/prosody/modules/mod_c2s.lua:252: in function 'onincoming' /usr/lib/prosody/net/server_event.lua:632: in function </usr/lib/prosody/net/server_event.lua:578> [C]: in function 'loop' /usr/lib/prosody/net/server_event.lua:793: in function </usr/lib/prosody/net/server_event.lua:792> [C]: in function 'xpcall' /usr/bin/prosody:376: in function 'loop' /usr/bin/prosody:407: in main chunk [C]: ?
The problem seems to be that the low-level `loadfile` call does not return an error message. That's really weird.
ChangesI think this is most likely related to #593, as seems to happens during loading of offline messages.
Still happens apparently: #754
ChangesDifficulty-EasyThe traceback should have been fixed by https://hg.prosody.im/trunk/rev/3463d82276de Still unsure about the root cause but I will close this
Changes