Update to 85.2 Unresponsive Issues
After about 1hr running the server it would no longer show my printers or even the dashboard anymore. The log shows the following error msg numerous times:
2017-07-08 13:13:06: LUA error calling sendEvent:...iles (x86)\Repetier-Server\modules\server\lua\render.lua:100: attempt to index a nil value (local 'manager')
I have several printers sharing the same gcodes, thanks for the new feature btw! The server is running on windows 10.
Any help in remedying this would be much appreciated.
2017-07-08 13:13:06: LUA error calling sendEvent:...iles (x86)\Repetier-Server\modules\server\lua\render.lua:100: attempt to index a nil value (local 'manager')
I have several printers sharing the same gcodes, thanks for the new feature btw! The server is running on windows 10.
Any help in remedying this would be much appreciated.
Comments
Can you show the complete log (dropbox/googledrive) and tell me when the problem occured. Your error would come if no model manager exists for a file to update. Since every printer has one I wonder how you got the error. One thing might be if it tries to render a model in the "old" storage, but uploading new files should not trigger that problem.
Did you do anything else while printing like preparing new models that could lead to the problem? And also quite important did the printer continue to print with ui not responding? These are different threads so it might work or not depending on what exactly happened.
You can also fix the error just to be sure it is not causing the ui hang. In INSTALL_DIR/modules/server/lua/render.lua replace around line 98 the function with this version:
In windows that directory is not writeable so you need to copy, edit and copy back. Then restart server.
You said the hang happens after these messages, which is correct as these come after the file is uploaded and analysed. Can you be more precise as my tests just start the print leaving ui intact (I guess like with your first 200 prints). Sometimes I see this in your log:
Which indicates in deed a disconnect but normally it will reconnect directly afterwards. So do you have any errors in javascript console if you check it (in chrome right click and investigate or however this is called in your language then to console).
But without knowing how to reproduce or more informations I can not find it. I guess something has changed for you so it started happening, just now we need to know what the difference to the first 200 prints is.