The OctoPrint server is currently not running


#1

The server shutdown for no reason and not for first time. Cut down my 18 hours print around last few layers.

I ran the code on error page to check if Octoprint server is running, No output. ps -ef | grep -i octoprint | grep -i python
Checked log, no error log in the file, looks like the whole Octoprint shut down including logging.
Use sudo service octoprint restart is able to bring it up again.

Octoprint Version 1.3.8, OctoPi Version 0.14.0, printer CR-10, firmware Marlin 1.1.8

octoprint.log (178.5 KB)


#2

The last thing to write to the log was octoprint.plugins.DisplayLayerProgress. Any chance this is the culprit? Looking at what it was writing, it was obviously confused.

2018-05-19 21:23:25,539 - octoprint.plugins.DisplayLayerProgress - INFO - ** GCODE:M117 0% L=-/-
2018-05-19 21:23:25,555 - octoprint.plugins.DisplayLayerProgress - INFO - ** NavBar:Progress: 0% Layer: - of - Height: - of -mm
2018-05-19 21:23:27,955 - octoprint.plugins.DisplayLayerProgress - INFO - ** GCODE:M117 0% L=-/-
2018-05-19 21:23:27,960 - octoprint.plugins.DisplayLayerProgress - INFO - ** NavBar:Progress: 0% Layer: - of - Height: - of -mm
2018-05-19 21:23:39,682 - octoprint.plugins.DisplayLayerProgress - INFO - ** NavBar:Progress: 0% Layer: - of - Height: 10.00 of -mm

#3

Oh, that's after restart the Octoprint server. The last log right before this happens I believe is
2018-05-19 17:58:53,215 - octoprint.plugins.DisplayLayerProgress - INFO - ** NavBar:Progress: 99% Layer: 891 of 899 Height: 178.40 of 180.00mm
Search 178.40 in the file, you will get to this line. After this is the restart information, as you can see is hours later when I found something went wrong.


#4

Wow. There's really nothing suggestive, just the restart and a mere 8 layers from the top.

So what about all this chatter:

2018-05-19 12:18:57,790 - backoff - ERROR - Backing off __forward_ws__(...) for 0.4s (WebSocketConnectionClosedException: socket is already closed.)
2018-05-19 12:18:58,205 - octoprint.plugins.anywhere - WARNING - Not connected to server ws or connection lost
2018-05-19 12:18:58,206 - backoff - ERROR - Backing off __forward_ws__(...) for 1.0s (WebSocketConnectionClosedException: socket is already closed.)
2018-05-19 12:18:59,202 - octoprint.plugins.anywhere - WARNING - Not connected to server ws or connection lost
2018-05-19 12:18:59,204 - backoff - ERROR - Backing off __forward_ws__(...) for 0.1s (WebSocketConnectionClosedException: socket is already closed.)
2018-05-19 12:18:59,351 - octoprint.plugins.anywhere - WARNING - Not connected to server ws or connection lost
2018-05-19 12:18:59,352 - backoff - ERROR - Backing off __forward_ws__(...) for 0.5s (WebSocketConnectionClosedException: socket is already closed.)
2018-05-19 12:18:59,854 - octoprint.plugins.anywhere - WARNING - Not connected to server ws or connection lost
2018-05-19 12:18:59,855 - backoff - ERROR - Backing off __forward_ws__(...) for 2.8s (WebSocketConnectionClosedException: socket is already closed.)
2018-05-19 12:19:01,425 - octoprint.plugins.DisplayLayerProgress - INFO - ** GCODE:M117 66% L=529/899

Is it this? From that issue, it sounds like the GPX plugin is the biggest suspect.