SolvedOctoPrint Failure To Resume From Pause

What were you doing?

1. Start Print
2. Click "Pause"

What did you expect to happen?

• The print pauses
• OctoPrint prints "Changing monitoring state from "Printing" to "Paused" in the Terminal tab
• OctoPrint " renames the "Pause" button to "Resume" and enables the button

What happened instead?

• The print pauses
• OctoPrint prints "Changing monitoring state from "Printing" to Pausing in the Terminal tab
• The Pause button is not renamed and remains disabled.
• Can't even cancel print, only option seems to be to restart OctoPrint and lose print

Did the same happen when running OctoPrint in safe mode?

Yes, it also happens in safe mode. In reproducing it I noticed it worked the first two times, but got into the frozen state after the 3rd pause.

Version of OctoPrint

OctoPrint 1.3.8 running on OctoPi 0.14.0

Note: I've been using OctoPrint for a long time (have also been a patreon supporter since 2016 fwiw) and have never had this problem. I only just upgraded, and this seems to have just started.

Operating System running OctoPrint

OctoPi 0.14.0

Printer model & used firmware incl. version

Printrbot Simple Metal. Unsure about Firmware, but purchased 4/22/2015 and have never upgraded firmware afaik.

Browser and version of browser, operating system running browser

Chrome 65.0.3325.181 from Windows 10

Link to octoprint.log

https://pastebin.com/ycpUXe8H

Link to contents of terminal tab or serial.log

https://pastebin.com/g5zWceJA

Link to contents of Javascript console in the browser

https://pastebin.com/NPB8nkyW

Screenshot(s)/video(s) showing the problem:

I have read the FAQ.

Yes

serial.log

log created with standard configuration (I did not change "Log position on pause" option)

I started printing and Paused/Resumed until it was stuck at Pausing. Each time a Octoprint was stuck I added "STUCK" to the serial log with echo "STUCK" > serial.log

As a Workaround for a stuck print the button "Fake Acknowledgement" in the Advanced options of the Terminal` tab kicks the print back into a normal state. I then can Resume the print again.

The log has 4 "STUCK" events and a few more pauses

It could be my imagination, but I've got the feeling that the print gets stuck more frequently if the printer immediately stops after the pause. I think all goes well when the printer finishes a few commands (sometimes even returning a Recv: echo:busy: processing line) and then change from Pausing to Paused

I hope the log helps