#1261 ssl.lua:123: attempt to call method 'setfd' (a nil value)
Reporter
MattJ
Owner
Nobody
Created
Updated
Stars
★ (1)
Tags
Type-Defect
Status-NeedInfo
Milestone-0.11
Priority-Medium
MattJ
on
What steps will reproduce the problem?
Unknown
What do you see?
/usr/share/lua/5.2/ssl.lua:123: attempt to call method 'setfd' (a nil value)
stack traceback:
/usr/share/lua/5.2/ssl.lua:123: in function 'wrap'
/usr/lib/prosody/net/server_event.lua:156: in function '_start_ssl'
/usr/lib/prosody/net/server_event.lua:396: in function </usr/lib/prosody/net/server_event.lua:394>
[C]: in function 'loop'
/usr/lib/prosody/net/server_event.lua:763: in function </usr/lib/prosody/net/server_event.lua:762>
[C]: in function 'xpcall'
/usr/bin/prosody:80: in function 'loop'
/usr/bin/prosody:90: in main chunk
[C]: in ?
Dec 09 03:05:25 general error
stack traceback:
[C]: in function 'loop'
/usr/lib/prosody/net/server_event.lua:763: in function </usr/lib/prosody/net/server_event.lua:762>
[C]: in function 'xpcall'
/usr/bin/prosody:80: in function 'loop'
/usr/bin/prosody:90: in main chunk
[C]: in ?
What version of the product are you using? On what operating system?
0.11 nightly build 16 (2018-12-01, 6f97acc4583b) on Debian stretch.
Zash
on
What versions of LuaSocket and LuaSec?
Any clues as to what it's trying to start TLS on?
Changes
tags Status-NeedInfo
Zash
on
Perhaps it tried to start TLS twice? LuaSec-wrapped connections don't have the :setfd method that LuaSockets connections have, which would explain this.
What steps will reproduce the problem? Unknown What do you see? /usr/share/lua/5.2/ssl.lua:123: attempt to call method 'setfd' (a nil value) stack traceback: /usr/share/lua/5.2/ssl.lua:123: in function 'wrap' /usr/lib/prosody/net/server_event.lua:156: in function '_start_ssl' /usr/lib/prosody/net/server_event.lua:396: in function </usr/lib/prosody/net/server_event.lua:394> [C]: in function 'loop' /usr/lib/prosody/net/server_event.lua:763: in function </usr/lib/prosody/net/server_event.lua:762> [C]: in function 'xpcall' /usr/bin/prosody:80: in function 'loop' /usr/bin/prosody:90: in main chunk [C]: in ? Dec 09 03:05:25 general error stack traceback: [C]: in function 'loop' /usr/lib/prosody/net/server_event.lua:763: in function </usr/lib/prosody/net/server_event.lua:762> [C]: in function 'xpcall' /usr/bin/prosody:80: in function 'loop' /usr/bin/prosody:90: in main chunk [C]: in ? What version of the product are you using? On what operating system? 0.11 nightly build 16 (2018-12-01, 6f97acc4583b) on Debian stretch.
What versions of LuaSocket and LuaSec? Any clues as to what it's trying to start TLS on?
ChangesPerhaps it tried to start TLS twice? LuaSec-wrapped connections don't have the :setfd method that LuaSockets connections have, which would explain this.