+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Discussion (https://forum.cuberite.org/forum-5.html)
+--- Thread: Lua Engine - failure? (/thread-1649.html)
Lua Engine - failure? - hoatzer - 11-14-2014
I'm wathing the log of my server on my second screen.
I realized that everytime I using the workbench I get this message:
[13:25:33] Lua engine: attempting to push a plain pointer, pushing nil instead.
[13:25:33] This indicates an unimplemented part of MCS bindings
[13:25:33] Stack trace:
[13:25:33] Stack trace end
Now I just saw that:
cEvent: waiting for the event failed: -1, err = 110: Connection timed out. Continuing, but server may be unstable.
Do I have to worry?
RE: Lua Engine - failure? - xoft - 11-15-2014
The first part is a legitimate issue, best reported on GitHub.
The cEvent part is interesting. What OS are you using? It could be a serious issue, and it could be nothing. Could you compile from sources and run under a debugger, to pinpoint where this happens?
RE: Lua Engine - failure? - hoatzer - 11-15-2014
It's Raspian on a Banana Pi. Latest Version.
I'd like to help you but could you please give me more detailed oders?
RE: Lua Engine - failure? - xoft - 11-15-2014
I'm not good enough with Linux to guide you here, perhaps someone with more Linux experience can chime in? @worktycho? @Howaner?
Basically, you need to download the sources using git, then compile them in debug mode using cmake and g++, and finally use gdb to set a breakpoint on that specific line in the Event.cpp source and wait for it to be hit, to see at least the stacktrace. You can find the compiling instructions in the COMPILING.md file: https://github.com/mc-server/MCServer/blob/master/COMPILING.md but setting gdb breakpoints is beyond my current expertise level.