prosody-0.9 1nightly255-1~sid running on Debian amd64
Jan 14 18:06:43 mod_c2s error Traceback[c2s]: constant table overflow
stack traceback:
[C]: in function 'loadfile'
/usr/lib/prosody/util/envload.lua:20: in function 'envloadfile'
/usr/lib/prosody/util/datamanager.lua:264: 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/events.lua:67: in function 'fire_event'
/usr/lib/prosody/core/stanza_router.lua:187: in function 'core_post_stanza'
...
/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
This is because there are too many offline messages for prosody to parse them back in one go.
Fixing this would involve changing how 'list' stores are read so that they would read in smaller chunks.
It would be helpful to know exactly how large the offline message store for the user who caused this is.
Also see #577
prosody-0.9 1nightly255-1~sid running on Debian amd64 Jan 14 18:06:43 mod_c2s error Traceback[c2s]: constant table overflow stack traceback: [C]: in function 'loadfile' /usr/lib/prosody/util/envload.lua:20: in function 'envloadfile' /usr/lib/prosody/util/datamanager.lua:264: 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/events.lua:67: in function 'fire_event' /usr/lib/prosody/core/stanza_router.lua:187: in function 'core_post_stanza' ... /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]: ?
This is because there are too many offline messages for prosody to parse them back in one go. Fixing this would involve changing how 'list' stores are read so that they would read in smaller chunks. It would be helpful to know exactly how large the offline message store for the user who caused this is. Also see #577
ChangesDifficulty-Easy