What steps will reproduce the problem?
1. Don't know
What version of the product are you using? On what operating system?
- Prosody 0.10.2
- Debian 9 (stable)
For some time now I have had the following error message in the error log (one example):
Sep 08 17:22:21 general error Top-level error, please report:
/usr/lib/prosody/modules/mod_bosh.lua:483: attempt to index field '?' (a nil value)
Sep 08 17:22:21 general error
stack traceback:
[C]: in function 'loop'
/usr/lib/prosody/net/server_event.lua:751: in function </usr/lib/prosody/net/server_event.lua:750>
[C]: in function 'xpcall'
/usr/lib/prosody/../../bin/prosody:400: in function 'loop'
/usr/lib/prosody/../../bin/prosody:431: in main chunk
[C]: ?
Zash
on
Thanks for the report!
This looks a bit like #1007, and like in that one, the real stack trace is obscured by libevent, so it is difficult to diagnose from this.
If you can reproduce it, additional debug logs leading up to this would be helpful.
Michael
on
Sorry, but I haven't had this error during the last weeks anymore and I' am not able to reproduce this. Maybe it will occur later on. I will keep an eye on it.
Zash
on
Thanks anyways.
I'm going to mark this as a duplicate. If you find something new relating to this, please post it in #1007.
What steps will reproduce the problem? 1. Don't know What version of the product are you using? On what operating system? - Prosody 0.10.2 - Debian 9 (stable) For some time now I have had the following error message in the error log (one example): Sep 08 17:22:21 general error Top-level error, please report: /usr/lib/prosody/modules/mod_bosh.lua:483: attempt to index field '?' (a nil value) Sep 08 17:22:21 general error stack traceback: [C]: in function 'loop' /usr/lib/prosody/net/server_event.lua:751: in function </usr/lib/prosody/net/server_event.lua:750> [C]: in function 'xpcall' /usr/lib/prosody/../../bin/prosody:400: in function 'loop' /usr/lib/prosody/../../bin/prosody:431: in main chunk [C]: ?
Thanks for the report! This looks a bit like #1007, and like in that one, the real stack trace is obscured by libevent, so it is difficult to diagnose from this. If you can reproduce it, additional debug logs leading up to this would be helpful.
Sorry, but I haven't had this error during the last weeks anymore and I' am not able to reproduce this. Maybe it will occur later on. I will keep an eye on it.
Thanks anyways. I'm going to mark this as a duplicate. If you find something new relating to this, please post it in #1007.
Changes