Today i saw the announcement for update to Octoprint 1.4.1 and I started the update unintentionally.
In the end the update failed and now i cannot get Octoprint running again.
How can I get the Server running again without loosing all my setting etc.?
What did you already try to solve it?
WinSCP into the pi to get the Log files but dont know how to continue.
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.)
I don't see any difference either, but they also still look truncated/incomplete.
octoprint.log doesn't show you starting the update, let alone an attempt to restart after. plugin_softwareupdate_console.log just ends in the middle of a sentence:
2020-08-04 16:04:03,363 > Looking in ind
but shows that OctoPrint itself should have been update just fine.
What happens if you do the following:
ssh into OctoPi
sudo service octoprint stop
~/oprint/bin/octoprint serve --debug
The latter should start OctoPrint manually. I would expect it to print some error. In any case, share what gets printed to the screen.
Since your logs are borked I have no idea WHAT happened here (if you are in the habit of pulling power from your Pi without proper shutdown first - stop doing that, it can cause file system corruption that can lead to issues like this one), but we can try one last thing:
Hello,
I'm new to the community but I wanted to jump in here. Thank you for everything that you do.
I am having the same problems as @reipet, and the issues started immediately after I updated by agreeing to the auto-update notification. I see nothing in the Octoprint.log file from today's date, and I have deleted the octoprint.log file to see if anything is added on a restart. Nothing even gets written to the log file when I try to launch Octoprint.
The service status shows a status of "exited", and I also used your suggestion above of ~/oprint/bin/octoprint serve --debug, but that returns nothing at the prompt.
pi@octopi:~ $ sudo service octoprint status
? octoprint.service - LSB: OctoPrint daemon
Loaded: loaded (/etc/init.d/octoprint; generated; vendor preset: enabled)
Active: active (exited) since Wed 2020-08-05 15:54:54 BST; 3s ago
Docs: man:systemd-sysv-generator(8)
Process: 10955 ExecStop=/etc/init.d/octoprint stop (code=exited, status=0/SUCCESS)
Process: 11099 ExecStart=/etc/init.d/octoprint start (code=exited, status=0/SUCCESS)
Aug 05 15:54:54 octopi systemd[1]: Starting LSB: OctoPrint daemon...
Aug 05 15:54:54 octopi octoprint[11099]: Starting OctoPrint Daemon: OctoPrint.
Aug 05 15:54:54 octopi systemd[1]: Started LSB: OctoPrint daemon.
The webpage on the pi, after a very long wait, shows the following:
Reporting back at promised... Something VERY odd is going on.
I tried running ~/oprint/bin/pip install --force-reinstall OctoPrint==1.4.1 and it reports as follows:
pi@octopi:~ $ ~/oprint/bin/pip install --force-reinstall OctoPrint==1.4.1
Requirement already satisfied: OctoPrint==1.4.1 in ./oprint/lib/python2.7/site-packages
You are using pip version 9.0.3, however version 20.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
I thought it was a bit odd that pip was so out of date, so I tried to update it only to find that pip was not installed. That seemed very unlikely, so I reinstalled it, but sadly I still can't start Octoprint.
Please let me know if I can capture any more information that will help.
As note, I had the same issues and came to see if there were other posts. Would have provided near-carbon-copy info as Q-Branch above.
However, performing the SSH update method and restarting the server worked and everything looks good. It booted in safe mood first, but now all seems well.
Well that was a bit of a mess, but I got there in the end.
I had to resort to nuking octoprint completely, deleting its installation directory, and then re-installing everything octoprint-related on the Raspberry Pi from scratch. If anyone is in a similar position, then I suggest following the "Basic Setup" and "Automatic start up" sections of the following page:
I have lost all of my recent configuration, which is obviously my own fault for not having a backup that was more recent than January 2019. I'm starting again, with my head hanging in shame.
Thank you to @reipet and others for their quick responses, and of course to @foosel for her magnificent software. I strongly recommend that more people contribute to the development effort on Patreon - https://www.patreon.com/foosel/ (and no, I'm not getting anything in return to endorse Gina's stuff. I just like it!)
For future reference, that's the pip of the venv. You would have to use ~/oprint/bin/pip install --update pip to update it, pip is not installed globally on OctoPi.
