invalida characters

10 views
Skip to first unread message

Damian Minkov

unread,
Nov 3, 2023, 12:42:55 PM11/3/23
to prosody-dev
Hey,

We have been cleaning up our logs lately and we came upon these two errors about invalid characters. Any recommendations, how do we handle those and prevent them?

Jul 05 11:42:58 c2s56224b453640 error   Traceback[c2s]: /usr/share/lua/5.2/prosody/util/stanza.lua:51: invalid tag name: contains invalid characters         stack traceback:         [C]: in function 'error'         /usr/share/lua/5.2/prosody/util/stanza.lua:51: in function 'check_name'         /usr/share/lua/5.2/prosody/util/stanza.lua:82: in function 'new_stanza'         /usr/share/lua/5.2/prosody/util/stanza.lua:105: in function 'tag'         /usr/lib/prosody/modules/mod_saslauth.lua:33: in function 'build_reply'         /usr/lib/prosody/modules/mod_saslauth.lua:82: in function </usr/lib/prosody/modules/mod_saslauth.lua:70>         (...tail calls...)         /usr/share/lua/5.2/prosody/util/events.lua:81: in function </usr/share/lua/5.2/prosody/util/events.lua:77>         (...tail calls...)         /usr/share/lua/5.2/prosody/core/stanza_router.lua:143: in function 'core_process_stanza'         /usr/lib/prosody/modules/mod_c2s.lua:326: in function 'func'         /usr/share/lua/5.2/prosody/util/async.lua:144: in function </usr/share/lua/5.2/prosody/util/async.lua:142>


Aug 01 17:29:54 server_epoll    error   Error in timer: /usr/share/lua/5.2/prosody/util/stanza.lua:65: invalid text value: contains invalid utf8         stack traceback:         [C]: in function 'error'         /usr/share/lua/5.2/prosody/util/stanza.lua:65: in function 'check_text'         /usr/share/lua/5.2/prosody/util/stanza.lua:141: in function 'add_direct_child'         /usr/share/lua/5.2/prosody/util/stanza.lua:116: in function 'text'         /usr/share/jitsi-meet/prosody-plugins/util.lib.lua:218: in function 'update_presence_identity'         ...are/jitsi-meet/prosody-plugins/mod_presence_identity.lua:11: in function '?'         /usr/share/lua/5.2/prosody/util/events.lua:81: in function </usr/share/lua/5.2/prosody/util/events.lua:77>         (...tail calls...)         /usr/share/lua/5.2/prosody/core/stanza_router.lua:184: in function 'core_post_stanza'         /usr/lib/prosody/modules/mod_presence.lua:382: in function '?'         /usr/share/lua/5.2/prosody/util/events.lua:81: in function </usr/share/lua/5.2/prosody/util/events.lua:77>         (...tail calls...)         /usr/share/lua/5.2/prosody/core/sessionmanager.lua:123: in function 'destroy_session'         /usr/lib/prosody/modules/mod_smacks.lua:494: in function </usr/lib/prosody/modules/mod_smacks.lua:477>         (...tail calls...)         [C]: in function 'xpcall'         /usr/share/lua/5.2/prosody/net/server_epoll.lua:148: in function 'runtimers'         /usr/share/lua/5.2/prosody/net/server_epoll.lua:1038: in function </usr/share/lua/5.2/prosody/net/server_epoll.lua:1036>         [C]: in function 'xpcall'         /usr/bin/prosody:78: in function 'loop'         /usr/bin/prosody:83: in main chunk         [C]: in ?

Thank you
damencho

Kim Alvefur

unread,
Nov 13, 2023, 5:01:53 AM11/13/23
to proso...@googlegroups.com
Hi,

On Fri, Nov 03, 2023 at 09:42:55AM -0700, Damian Minkov wrote:
>We have been cleaning up our logs lately and we came upon these two errors
>about invalid characters. Any recommendations, how do we handle those and
>prevent them?

(reduced)
>util/stanza.lua:51: invalid tag name: contains invalid characters
>mod_saslauth.lua:33: in function 'build_reply'

This one suggests that the SASL handler or authentication module
returned an invalid error code, i.e. things like "malformed-request".
Hard to say more than that based on only this traceback.

>Error in timer: util/stanza.lua:65: invalid text value: contains invalid utf8
>...are/jitsi-meet/prosody-plugins/mod_presence_identity.lua:11: in function

Looks like invalid or corrupt UTF-8 got into this module, via a timer.

Hope that's enough to proceed.

--
Regards,
Kim "Zash" Alvefur
Reply all
Reply to author
Forward
0 new messages