- Migrated from 0.10.2 to 0.11.1 - Local file system (no database) - Debian 9.5 - Prosody Community Modules are up to date I have a lot of these error logs: Dec 05 20:52:14 c2s55576d0d4820 error Traceback[c2s]: /usr/lib/prosody/util/serialization.lua:38: Can't serialize table: table has multiple references stack traceback: [C]: in function 'error' /usr/lib/prosody/util/serialization.lua:38: in function 'fallback' /usr/lib/prosody/util/serialization.lua:135: in function 'serialize_table' /usr/lib/prosody/util/serialization.lua:194: in function 'serialize_table' /usr/lib/prosody/util/serialization.lua:194: in function 'serialize_table' /usr/lib/prosody/util/serialization.lua:194: in function 'serialize_table' /usr/lib/prosody/util/serialization.lua:194: in function 'serialize_table' /usr/lib/prosody/util/serialization.lua:194: in function 'serialize_table' /usr/lib/prosody/util/serialization.lua:220: in function </usr/lib/prosody/util/serialization.lua:218> (...tail calls...) /usr/lib/prosody/util/datamanager.lua:206: in function </usr/lib/prosody/util/datamanager.lua:195> (...tail calls...) ...es/prosody-modules/mod_cloud_notify/mod_cloud_notify.lua:116: in function <...es/prosody-modules/mod_cloud_notify/mod_cloud_notify.lua:114> (...tail calls...) ...es/prosody-modules/mod_cloud_notify/mod_cloud_notify.lua:240: in function '?' /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75> (...tail calls...) /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75> (...tail calls...) /usr/lib/prosody/core/stanza_router.lua:181: in function 'core_post_stanza' /usr/lib/prosody/core/stanza_router.lua:127: in function 'core_process_stanza' /usr/lib/prosody/modules/mod_c2s.lua:276: in function 'func' /usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>

Same here, exactly the same error. Also upgraded from 0.10.2 to 0.11.1. Good to know, Iam not the only one with this.

One more thing to add: Push is broken after this occurs. Restart is required to get it working again. Client is iOS ChatSecure.

Update: Since I updated to Prosody 0.11.2 no such errors occur anymore. Till now :-)

Bug in mod_cloud_notify that I assume has since been fixed. Unearthed by stricter checks in Prosody's data serialization library.

• tags Component-Community Status-Fixed