What is the problem?
The LCD screen on my Prusa i3MK3S, while running Octoprint but just having completed a successful print, showed an impossible temperature of -1874 (C). Can Octoprint "push" information to the LCD? If that's possible, then that would give me confidence that the bug was software, in Octoprint, and not some hardware bug in the printer.
What did you already try to solve it?
I rebooted the printer and rebooted the Octopi, and the issue has not (yet) reappeared.
Have you tried running in safe mode and if so did it solve the issue?
No (see above).
Complete Logs
octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support! Not log excerpts, complete logs.)
Excerpt below. Picture was taken at 11:17am (and should correlate with the log time).
2020-11-27 10:15:02,575 - octoprint.access.users - INFO - Logged in user: octopi
2020-11-27 10:15:06,487 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.141
2020-11-27 10:15:06,580 - octoprint.server.util.flask - INFO - Passively logging in user octopi from 2601:446:c300:2686:314f:eb1:e75d:8ee5
2020-11-27 10:15:06,582 - octoprint.access.users - INFO - Logged in user: octopi
2020-11-27 10:15:12,702 - octoprint.server.util.sockjs - INFO - User octopi logged in on the socket from client ::ffff:192.168.1.141
2020-11-27 10:15:14,184 - octoprint.plugins.softwareupdate - INFO - Saved version cache to disk
2020-11-27 10:15:15,522 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from https://plugins.octoprint.org/plugins.json
2020-11-27 10:15:16,944 - octoprint.plugins.pluginmanager - INFO - Loaded plugin notices data from https://plugins.octoprint.org/notices.json
2020-11-27 10:21:35,499 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.141
2020-11-27 10:26:44,866 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-11-27 10:26:46,195 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 184527}
2020-11-27 10:29:16,280 - octoprint.server.util.flask - INFO - Passively logging in user octopi from 2601:446:c300:2686:314f:eb1:e75d:8ee5
2020-11-27 10:29:16,282 - octoprint.access.users - INFO - Logged in user: octopi
2020-11-27 10:29:18,216 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.141
2020-11-27 10:29:18,414 - octoprint.server.util.flask - INFO - Passively logging in user octopi from 2601:446:c300:2686:314f:eb1:e75d:8ee5
2020-11-27 10:29:18,415 - octoprint.access.users - INFO - Logged in user: octopi
2020-11-27 10:29:19,029 - octoprint.server.util.sockjs - INFO - User octopi logged in on the socket from client ::ffff:192.168.1.141
2020-11-27 10:29:39,474 - octoprint.plugins.DisplayLayerProgress - INFO - FilePreProcessor. Checking LayerExpressions.
2020-11-27 10:29:39,475 - octoprint.plugins.DisplayLayerProgress - INFO - FilePreProcessor. LayerExpression valid. Start processing...
2020-11-27 10:29:40,761 - octoprint.filemanager.analysis - INFO - Starting analysis of local:AmongUs/bone_0.15mm_PETG_MK3S_32m.gcode
2020-11-27 10:29:40,850 - octoprint.plugins.DisplayLayerProgress - INFO - Store layer count in MetaFile
2020-11-27 10:29:40,886 - octoprint.plugins.DisplayLayerProgress - INFO - Read total height from MetaFile
2020-11-27 10:29:40,899 - octoprint.plugins.DisplayLayerProgress - INFO - Total height not found in MetaFile
2020-11-27 10:29:42,389 - octoprint.plugins.DisplayLayerProgress - INFO - Store layer count in MetaFile
2020-11-27 10:29:42,450 - octoprint.plugins.DisplayLayerProgress - INFO - Read total height from MetaFile
2020-11-27 10:29:42,458 - octoprint.filemanager.analysis - INFO - Analysis of entry local:AmongUs/bone_0.15mm_PETG_MK3S_32m.gcode finished, needed 1.70s
2020-11-27 10:29:42,469 - octoprint.plugins.DisplayLayerProgress - INFO - Store layer count in MetaFile
2020-11-27 10:29:42,485 - octoprint.plugins.DisplayLayerProgress - INFO - Read total height from MetaFile
2020-11-27 10:29:43,005 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2020-11-27 10:29:43,045 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 7 port/baudrate candidates: /dev/ttyACM0@115200, /dev/ttyACM0@250000, /dev/ttyACM0@230400, /dev/ttyACM0@57600, /dev/ttyACM0@38400, /dev/ttyACM0@19200, /dev/ttyACM0@9600
2020-11-27 10:29:43,048 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyACM0, baudrate 115200
2020-11-27 10:29:43,051 - octoprint.util.comm - INFO - Connecting to port /dev/ttyACM0, baudrate 115200
2020-11-27 10:29:43,068 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2020-11-27 10:29:43,077 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-11-27 10:29:44,122 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"
2020-11-27 10:29:44,137 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-11-27 10:29:46,961 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2020-11-27 10:29:48,202 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: AmongUs/bone_0.15mm_PETG_MK3S_32m.gcode, owner: octopi, user: octopi
2020-11-27 10:29:48,236 - octoprint.plugins.DisplayLayerProgress - INFO - File '/home/pi/.octoprint/uploads/AmongUs/bone_0.15mm_PETG_MK3S_32m.gcode' selected. Determining number of layers.
2020-11-27 10:29:48,239 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2020-11-27 10:29:48,244 - octoprint.plugins.DisplayLayerProgress - INFO - Read total height from MetaFile
2020-11-27 10:29:48,249 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: AmongUs/bone_0.15mm_PETG_MK3S_32m.gcode, owner: octopi, user: octopi
2020-11-27 10:29:48,687 - octoprint.plugins.DisplayLayerProgress - INFO - Store layer count in MetaFile
2020-11-27 10:29:48,698 - octoprint.plugins.DisplayLayerProgress - INFO - File select-event processing done!'
2020-11-27 10:29:48,756 - octoprint.plugins.DisplayLayerProgress - INFO - Printing started. Detailed progress started.{'origin': u'local', 'name': u'bone_0.15mm_PETG_MK3S_32m.gcode', u'user': 'octopi', u'owner': 'octopi', 'path': u'AmongUs/bone_0.15mm_PETG_MK3S_32m.gcode', 'size': 1914884L}
2020-11-27 10:29:49,864 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {'origin': u'local', 'file': '99ce806b59785c6f8beebe2076021d55dd1ffd7d'}
2020-11-27 10:29:50,485 - octoprint.util.comm - INFO - Printer reports firmware name "Prusa-Firmware 3.9.1 based on Marlin"
2020-11-27 10:29:51,125 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {u'printer_baudrate': 0, u'printer_port': u'AUTO', 'firmware_name': u'Prusa-Firmware 3.9.1 based on Marlin'}
2020-11-27 10:29:55,074 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2020-11-27 10:29:55,101 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-11-27 10:29:55,165 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2020-11-27 10:41:44,869 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-11-27 10:41:46,268 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 185427}
2020-11-27 10:55:43,073 - octoprint.plugins.DisplayLayerProgress - INFO - FilePreProcessor. Checking LayerExpressions.
2020-11-27 10:55:43,075 - octoprint.plugins.DisplayLayerProgress - INFO - FilePreProcessor. LayerExpression valid. Start processing...
2020-11-27 10:56:44,872 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-11-27 10:56:46,286 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 186327}
2020-11-27 11:06:32,171 - octoprint.util.comm - INFO - Finished in 2203.933 s.
2020-11-27 11:06:32,173 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Finishing"
2020-11-27 11:06:32,180 - octoprint.printer.standard.job - INFO - Print job done - origin: local, path: AmongUs/bone_0.15mm_PETG_MK3S_32m.gcode, owner: octopi
2020-11-27 11:06:32,225 - octoprint.plugins.DisplayLayerProgress - INFO - Printing stopped. Detailed progress stopped.
2020-11-27 11:06:32,323 - octoprint.plugin - ERROR - Error while calling plugin enclosure
Traceback (most recent call last):
File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint/plugin/__init__.py", line 230, in call_plugin
result = getattr(plugin, method)(*args, **kwargs)
File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint_enclosure/__init__.py", line 1573, in on_event
file_name = os.path.basename(payload["file"])
KeyError: 'file'
2020-11-27 11:06:32,887 - octoprint.plugins.tracking - INFO - Sent tracking event print_done, payload: {'origin': u'local', 'file': '99ce806b59785c6f8beebe2076021d55dd1ffd7d', u'elapsed': 2203}
2020-11-27 11:06:37,814 - octoprint.util.comm - INFO - Changing monitoring state from "Finishing" to "Operational"
2020-11-27 11:11:44,873 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-11-27 11:11:46,262 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 187227}
2020-11-27 11:14:28,028 - octoprint.plugins.DisplayLayerProgress - INFO - FilePreProcessor. Checking LayerExpressions.
2020-11-27 11:14:28,032 - octoprint.plugins.DisplayLayerProgress - INFO - FilePreProcessor. LayerExpression valid. Start processing...
2020-11-27 11:14:29,017 - octoprint.filemanager.analysis - INFO - Starting analysis of local:AmongUs/Visor_1_0.15mm_PETG_MK3S_33m.gcode
2020-11-27 11:14:29,095 - octoprint.plugins.DisplayLayerProgress - INFO - Store layer count in MetaFile
2020-11-27 11:14:29,117 - octoprint.plugins.DisplayLayerProgress - INFO - Read total height from MetaFile
2020-11-27 11:14:30,006 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-11-27 11:14:30,249 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Sending file to SD"
2020-11-27 11:14:30,645 - octoprint.plugins.DisplayLayerProgress - INFO - Store layer count in MetaFile
2020-11-27 11:14:30,677 - octoprint.plugins.DisplayLayerProgress - INFO - Read total height from MetaFile
2020-11-27 11:14:30,720 - octoprint.filemanager.analysis - INFO - Analysis of entry local:AmongUs/Visor_1_0.15mm_PETG_MK3S_33m.gcode finished, needed 1.70s
2020-11-27 11:14:30,734 - octoprint.plugins.DisplayLayerProgress - INFO - Store layer count in MetaFile
2020-11-27 11:14:30,746 - octoprint.plugins.DisplayLayerProgress - INFO - Read total height from MetaFile
2020-11-27 11:14:36,877 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-11-27 11:14:42,883 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-11-27 11:14:48,893 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-11-27 11:14:54,900 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-11-27 11:15:00,909 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2020-11-27 11:15:06,925 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2020-11-27 11:15:07,006 - octoprint.util.comm - INFO - Changing monitoring state from "Sending file to SD" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2020-11-27 11:15:07,093 - octoprint.plugins.DisplayLayerProgress - INFO - Printing stopped. Detailed progress stopped.
2020-11-27 11:15:07,103 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2020-11-27 11:15:07,646 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_timeout, payload: {'commerror_text': u'Too many consecutive timeouts, printer still connected and alive?'}
2020-11-27 11:15:08,976 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {'origin': u'sdcard', u'reason': u'error', u'commerror_text': u'Too many consecutive timeouts, printer still connected and alive?', 'file': 'ccb7468adf530cebc19811b993c9187ad491e95c', u'elapsed': 37}
2020-11-27 11:20:40,763 - octoprint.server.api.system - INFO - Performing command for core:reboot: sudo shutdown -r now
2020-11-27 11:20:41,015 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.141
2020-11-27 11:20:41,236 - octoprint.server - INFO - Shutting down...
2020-11-27 11:20:42,201 - octoprint.server - INFO - Calling on_shutdown on plugins
2020-11-27 11:20:42,202 - octoprint.events - INFO - Processing shutdown event, this will be our last event
2020-11-27 11:20:42,206 - octoprint.events - INFO - Event loop shut down
2020-11-27 11:20:42,242 - octoprint.server - INFO - Goodbye!
2020-11-27 11:20:48,294 - octoprint.startup - INFO - ******************************************************************************
2020-11-27 11:20:48,296 - octoprint.startup - INFO - Starting OctoPrint 1.4.2
2020-11-27 11:20:48,296 - octoprint.startup - INFO - ******************************************************************************
Can attach full 15,000 line log if you really, absolutely need it.
Additional information about your setup
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
Prusa i3MK3S on latest firmware, latest (non-release-candidate) build of Octoprint. Plugins include Bed Visualizer, Dashboard, DisplayLayerProgress, Enclosure, OctoPrint-WideScreen, PrintTimeGenius, Printer Dialogs, Printer Notifications, Virtual Printer.