If I turn off autoscroll to look at something in the terminal, it will keep going until full.
Then the printer just stops. I can't resume the print because it wasn't paused properly, but that's more of a klipper issue.
How can I prevent a terminal buffer overflow from accidentally ruining a print?
Curious if the printer is powered off and @Amplifryer thinks it's on because of backpowering from the Pi? That could cause something like that to happen.
I had autoscroll turned off because occasionally I'll need to read some recent lines in the terminal.
Normally I would turn it on again, but I forgot and so the buffer filled up.
Just seems like a silly way to scrap a print to me. I figured maybe there was a setting that could prevent this from happening.
Where did you find those last lines? I only got to N1399 before it stopped. I didn't export that system info until after I restarted everything and already had another print going.
Edit: scratch that, reviewing the gcode and octoprint log, looks like those were the final lines. Maybe they just didn't show in the terminal because it filled up a while before I even noticed the printer stopped.
I've never seen the hotend cool down unexpectedly, so I'll look into that some more.
I will try to replicate the problem after my print finishes to confirm.
Autoscroll in the terminal is a front-end UI-only feature. It doesn't have any impact on the gcode sent with the OctoPrint server, in the same way that you can close the tab and it carries on printing. It has no impact outside allowing you to look at what was sent without it scrolling down.