Debian amd64, Prosody 0.9 1nightly268-1~sid
Oct 01 11:07:32 general error Top-level error, please report:
/usr/lib/prosody/modules/mod_c2s.lua:161: attempt to concatenate field 'ip' (a nil value)
Oct 01 11:07:32 general error
stack traceback:
/usr/bin/prosody:4: in function 'loop'
/usr/lib/prosody/net/server_event.lua:797: in function </usr/lib/prosody/net/server_event.lua:796>
[C]: in function 'xpcall'
/usr/bin/prosody:376: in function 'loop'
/usr/bin/prosody:407: in main chunk
[C]: ?
Zash
on
Do you by any chance have any logs just before this?
Zash
on
Changes
tags Status-NeedInfo
dgoulet
on
I'm getting this maybe every 3 or 4 weeks on the jabber.otr.im server. A bit different though and unfortunately we don't have any logs on that server except that backtrace:
Feb 08 21:31:46 general error Top-level error, please report:
/usr/lib/prosody/modules/mod_c2s.lua:161: attempt to concatenate field 'ip' (a nil value)
Feb 08 21:31:46 general error
stack traceback:
[C]: in function 'parse'
/usr/lib/prosody/util/xmppstream.lua:255: in function 'feed'
/usr/lib/prosody/modules/mod_c2s.lua:233: in function 'data'
/usr/lib/prosody/modules/mod_c2s.lua:255: in function </usr/lib/prosody/modules/mod_c2s.lua:252>
(tail call): ?
/usr/lib/prosody/net/server_select.lua:868: in function </usr/lib/prosody/net/server_select.lua:850>
[C]: in function 'xpcall'
/usr/bin/prosody:376: in function 'loop'
/usr/bin/prosody:407: in main chunk
[C]: ?
Zash
on
The real stack trace is still obscured by C callback shenanigans. As I said in the earlier comment, debug logs leading up to this would be more helpful.
Zash
on
Fixed in https://hg.prosody.im/0.10/rev/780d728f969f
The missing IP may be caused by really quickly disconnecting before the network stack sees it. Not sure why this happens, but apparently it does, and we get to deal with it.
LuaEvent still does not produce particularly helpful tracebacks.
Debian amd64, Prosody 0.9 1nightly268-1~sid Oct 01 11:07:32 general error Top-level error, please report: /usr/lib/prosody/modules/mod_c2s.lua:161: attempt to concatenate field 'ip' (a nil value) Oct 01 11:07:32 general error stack traceback: /usr/bin/prosody:4: in function 'loop' /usr/lib/prosody/net/server_event.lua:797: in function </usr/lib/prosody/net/server_event.lua:796> [C]: in function 'xpcall' /usr/bin/prosody:376: in function 'loop' /usr/bin/prosody:407: in main chunk [C]: ?
Do you by any chance have any logs just before this?
I'm getting this maybe every 3 or 4 weeks on the jabber.otr.im server. A bit different though and unfortunately we don't have any logs on that server except that backtrace: Feb 08 21:31:46 general error Top-level error, please report: /usr/lib/prosody/modules/mod_c2s.lua:161: attempt to concatenate field 'ip' (a nil value) Feb 08 21:31:46 general error stack traceback: [C]: in function 'parse' /usr/lib/prosody/util/xmppstream.lua:255: in function 'feed' /usr/lib/prosody/modules/mod_c2s.lua:233: in function 'data' /usr/lib/prosody/modules/mod_c2s.lua:255: in function </usr/lib/prosody/modules/mod_c2s.lua:252> (tail call): ? /usr/lib/prosody/net/server_select.lua:868: in function </usr/lib/prosody/net/server_select.lua:850> [C]: in function 'xpcall' /usr/bin/prosody:376: in function 'loop' /usr/bin/prosody:407: in main chunk [C]: ?
The real stack trace is still obscured by C callback shenanigans. As I said in the earlier comment, debug logs leading up to this would be more helpful.
Fixed in https://hg.prosody.im/0.10/rev/780d728f969f The missing IP may be caused by really quickly disconnecting before the network stack sees it. Not sure why this happens, but apparently it does, and we get to deal with it. LuaEvent still does not produce particularly helpful tracebacks.
Changes