Depending on what that cord does it might just be cutting power and that is a surefire way to kill the file system. And it looks like something got lost there which should never just get lost on its own. Easiest solution is probably to reimage and make sure to properly shut down the server first through the menu before pressing that button in the future.
1 Like
Is there a way to get a power button that doesn’t have the potential to cause this issue?
Yes, one that measures the current, talks to the pi through the GPIOs, has a client program on the Pi that listens for an GPIO event and issues a proper shutdown first, and then only cuts power when the current indicates that the safe shutdown has been performed.
Off the shelf without some tinkering? Not to my knowledge.
2 Likes
@foosel So i went and bought a new SD card, redid everything from the start. Octroprint server is working now. So not sure if it was bad SD card, or what. But ill reply to this post if the same thing happens again. Thanks for all the info and help. I will make sure I run a shut down though SSH before I flick the switch. Take care all
1 Like
Hi, so i'm having the same issue but my errors are different:
ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:11:35,211 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:11:44,084 - octoprint.plugins.navbartemp - INFO - Checking SoC int ernal temperature
2019-12-30 13:11:45,215 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:11:55,219 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:12:03,175 - backoff - INFO - Backing off __get_dev_settings__(...) for 116.2s (HTTPError: 401 Client Error: Unauthorized for url: http://stream.ge tanywhere.io/api/dev_settings)
2019-12-30 13:12:05,223 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:12:14,138 - octoprint.plugins.navbartemp - INFO - Checking SoC int ernal temperature
2019-12-30 13:12:15,227 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:12:25,231 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:12:35,236 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:12:44,192 - octoprint.plugins.navbartemp - INFO - Checking SoC int ernal temperature
2019-12-30 13:12:45,242 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:12:55,262 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
2019-12-30 13:13:05,271 - octoprint.plugins.opitemp - ERROR - OpiTemp: can't det ermine the temperature, are you sure you're using Armbian?
any idea?
Try it in Safe Mode. It's possible that the OrangePi plugin is the cause but it's good to attempt this without the extra third-party plugins.
when i run the command:
octoprint safemode
i get this:
Error parsing the configuration file, it appears to be invalid YAML.
There was a fatal error initializing the settings manager.
When i run: octoprint serve --safe
i get this:
2019-12-31 11:33:53,098 - octoprint.startup - CRITICAL - Could not initialize se ttings manager: Error parsing the configuration file, it appears to be invalid Y AML.
2019-12-31 11:33:53,099 - octoprint.startup - CRITICAL - There was a fatal error starting up OctoPrint.
Could not initialize settings manager: Error parsing the configuration file, it appears to be invalid YAML.
There was a fatal error starting up OctoPrint.
Well, there you go. The message is pretty clear. I'm guessing that the last manual attempt to edit your ~/.octoprint/config.yaml (or the last plugin added) has somehow managed to make that unhappy.
nano ~/.octoprint/config.yaml
Look in there for anything you think that might have been added by the opitemp plugin. Yaml files are notorious for needing their formatting to be perfect with respect to whitespace at the beginning of a line.
Hi,
I'm having this same issue. I tried to install "Octoprint-PrusaMeshMap' via a "PY" file (https://github.com/PrusaOwners/OctoPrint-PrusaMeshMap) and then Octoprint server stopped. I did the above line in SSH and get this:
pi@octopi:~ $ ~/oprint/bin/octoprint serve --host 127.0.0.1
2020-09-13 10:05:20,057 - octoprint.startup - INFO - ******************************************************************************
2020-09-13 10:05:20,059 - octoprint.startup - INFO - Starting OctoPrint 1.4.2
2020-09-13 10:05:20,060 - octoprint.startup - INFO - ******************************************************************************
2020-09-13 10:05:20,715 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity changed from offline to online
2020-09-13 10:05:20,754 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity state is currently: online
2020-09-13 10:05:20,755 - octoprint.util.connectivity.connectivity_checker - INFO - Connecting to 8.8.8.8:53 is working
2020-09-13 10:05:20,755 - octoprint.util.connectivity.connectivity_checker - INFO - Resolving octoprint.org is working
2020-09-13 10:05:21,972 - octoprint.startup - INFO - Blacklist processing done, adding 10 blacklisted plugin versions: roomtemp (any), GcodeEditor (0.1.1), GcodeEditor (0.2.0), GcodeEditor (0.2.1), GcodeEditor (0.2.2), GcodeEditor (0.2.3), GcodeEditor (0.2.4), GcodeEditor (0.2.5), GcodeEditor (0.2.6), GcodeEditor (0.2.8)
2020-09-13 10:05:22,019 - octoprint.plugin.core - INFO - Loading plugins from /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins, /home/pi/.octoprint/plugins and installed plugin packages...
Found packages: set(['octoprint_PrusaMeshMap'])
usage: octoprint [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: octoprint --help [cmd1 cmd2 ...]
or: octoprint --help-commands
or: octoprint cmd --help
thoughts? thank you!!
also get this:
pi@octopi:~ $ ~/oprint/bin/octoprint --debug
Starting the server via "octoprint" is deprecated, please use "octoprint serve" from now on.
2020-09-13 10:24:41,429 - octoprint.startup - INFO - ******************************************************************************
2020-09-13 10:24:41,436 - octoprint.startup - INFO - Starting OctoPrint 1.4.2
2020-09-13 10:24:41,438 - octoprint.startup - INFO - ******************************************************************************
2020-09-13 10:24:42,190 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity changed from offline to online
2020-09-13 10:24:42,225 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity state is currently: online
2020-09-13 10:24:42,227 - octoprint.util.connectivity.connectivity_checker - INFO - Connecting to 8.8.8.8:53 is working
2020-09-13 10:24:42,227 - octoprint.util.connectivity.connectivity_checker - INFO - Resolving octoprint.org is working
2020-09-13 10:24:43,454 - octoprint.startup - DEBUG - Blacklisted plugin: roomtemp
2020-09-13 10:24:43,464 - octoprint.startup - DEBUG - Blacklisted plugin: GcodeEditor, versions: 0.1.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.2.8
2020-09-13 10:24:43,492 - octoprint.startup - INFO - Blacklist processing done, adding 10 blacklisted plugin versions: roomtemp (any), GcodeEditor (0.1.1), GcodeEditor (0.2.0), GcodeEditor (0.2.1), GcodeEditor (0.2.2), GcodeEditor (0.2.3), GcodeEditor (0.2.4), GcodeEditor (0.2.5), GcodeEditor (0.2.6), GcodeEditor (0.2.8)
2020-09-13 10:24:43,529 - octoprint.plugin.core - INFO - Loading plugins from /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins, /home/pi/.octoprint/plugins and installed plugin packages...
2020-09-13 10:24:43,532 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for pi_support from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/pi_support/init.py
2020-09-13 10:24:43,552 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for discovery from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/discovery/init.py
2020-09-13 10:24:43,708 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for loginui from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/loginui/init.py
2020-09-13 10:24:43,716 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for announcements from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/announcements/init.py
2020-09-13 10:24:44,257 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for virtual_printer from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/virtual_printer/init.py
2020-09-13 10:24:44,266 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for appkeys from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/appkeys/init.py
2020-09-13 10:24:44,290 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for tracking from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/tracking/init.py
2020-09-13 10:24:44,319 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for gcodeviewer from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/gcodeviewer/init.py
2020-09-13 10:24:44,325 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for pluginmanager from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/pluginmanager/init.py
2020-09-13 10:24:44,432 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for backup from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/backup/init.py
2020-09-13 10:24:44,484 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for action_command_notification from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/action_command_notification/init.py
2020-09-13 10:24:44,493 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for errortracking from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/errortracking/init.py
2020-09-13 10:24:44,505 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for softwareupdate from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/softwareupdate/init.py
2020-09-13 10:24:44,593 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for action_command_prompt from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/action_command_prompt/init.py
2020-09-13 10:24:44,608 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for corewizard from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/corewizard/init.py
2020-09-13 10:24:44,619 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for logging from AST of /home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/logging/init.py
2020-09-13 10:24:44,635 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for setup from AST of /home/pi/.octoprint/plugins/setup.py
Found packages: set(['octoprint_PrusaMeshMap'])
usage: octoprint [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: octoprint --help [cmd1 cmd2 ...]
or: octoprint --help-commands
or: octoprint cmd --help
error: option --debug not recognized
From what I can see, you have a completely different issue to the post you are replying to. Please open a 'get help' topic with a full explanation of what you did, and full (not just part) of the logs, as an attachment, not pasted.
2 Likes
Yeah, Charlie's probably right. A new thread would be appreciated. Thanks.
1 Like