In trunk,
I see this:
```
server_epoll error Error in timer: /usr/share/lua/5.2/prosody/core/sessionmanager.lua:156: attempt to index field '?' (a nil value)
stack traceback:
/usr/share/lua/5.2/prosody/core/sessionmanager.lua:156: in function 'destroy_session'
/usr/lib/prosody/modules/mod_smacks.lua:538: in function </usr/lib/prosody/modules/mod_smacks.lua:524>
(...tail calls...)
[C]: in function 'xpcall'
/usr/share/lua/5.2/prosody/net/server_epoll.lua:155: in function 'runtimers'
/usr/share/lua/5.2/prosody/net/server_epoll.lua:1088: in function </usr/share/lua/5.2/prosody/net/server_epoll.lua:1086>
[C]: in function 'xpcall'
/usr/bin/prosody:84: in function 'loop'
/usr/bin/prosody:89: in main chunk
[C]: in ?
```
in logs.
I've no idea what lead to this.
MattJ
on
Hi! Thanks for your patience on this. It would be great if you could upgrade to the latest nightly build (prosody-0.12 or prosody-trunk) and see if this issue still happens. We believe it should be fixed now.
We think it may be the same issue as #1781.
In trunk, I see this: ``` server_epoll error Error in timer: /usr/share/lua/5.2/prosody/core/sessionmanager.lua:156: attempt to index field '?' (a nil value) stack traceback: /usr/share/lua/5.2/prosody/core/sessionmanager.lua:156: in function 'destroy_session' /usr/lib/prosody/modules/mod_smacks.lua:538: in function </usr/lib/prosody/modules/mod_smacks.lua:524> (...tail calls...) [C]: in function 'xpcall' /usr/share/lua/5.2/prosody/net/server_epoll.lua:155: in function 'runtimers' /usr/share/lua/5.2/prosody/net/server_epoll.lua:1088: in function </usr/share/lua/5.2/prosody/net/server_epoll.lua:1086> [C]: in function 'xpcall' /usr/bin/prosody:84: in function 'loop' /usr/bin/prosody:89: in main chunk [C]: in ? ``` in logs. I've no idea what lead to this.
Hi! Thanks for your patience on this. It would be great if you could upgrade to the latest nightly build (prosody-0.12 or prosody-trunk) and see if this issue still happens. We believe it should be fixed now. We think it may be the same issue as #1781.
ChangesIndeed this is fixed. Thanks a lot.