Hi @AndKe!

It looks like you didn't upload a system info bundle as requested by the template. A bundle is required to further process your issue. It contains important logs and system information to be able to put your issue into context and give pointers as to what has happened.

Please edit your original post above and upload a bundle zip file. Actually upload the file please and do not paste some link to a cloud provider, we want to have everything in one place here. Also do not unpack, repack or otherwise modify the bundle or its name, share it exactly like you get it from OctoPrint.

Without the availability of a bundle, your issue will have to be closed.

Thank you for your collaboration.

dear nagbot - there is no "system info" bundle as the program does not start.

$ ps -ef | grep -i octoprint | grep -i python
$

this information from before the mess is in the forum post
:)

..and the same happens with the 1.9.0 release

Something seems to be seriously wrong with your install. I've gone through a ton of updates from various start versions throughout the whole RC phase, and I'm currently looking at almost 5k successfully upgraded and happily printing instances in the usage tracking.

The question is, what is wrong with your install that makes it completely throw away the whole OctoPrint files so that even the command cannot be found anymore.

At this point I'd honestly suggest to try if recreating the virtual environment helps, as a forced reinstall doesn't seem to do it. Alternative idea is that the SD card is dying or something like that, if that is running on one.

@foosel thanks.
I have upgraded, then returned to 1.8.7 many times now, (two times today, last with safe mode.)
I strongly doubt the high endurance SD to be that particulary corrupt.
I do love that every time I revert -. then things just works (all config/files are there)
Is there a way of doing a supercomplete backup? (with plugins and all?) - then I could reflash the octopi too ? :)

Yes, the built in backup and restore plugin. Doesn't backup the plugin code, but stores what it can about the plugins you have installed and then attempts to reinstall all of them from the plugin repository. Plugin data is included in the backup.

is it possible that my modified menu is to blame?

That should not be related. It's a feature of OctoPrint itself, not some unsuspecting modification (at least I hope you've done it properly).

FWIW: exactly the same happened at work. (which has about the same plugins, but no menu customization.)

• solved by forcing the previous version.
  These are the installed plugins:
  

3rd party:

and systeminfo before upgrade:
octoprint-systeminfo-20230525081621.zip

Bundles:

• octoprint-systeminfo-20230525081621.zip

edited by @github-actions to add bundle viewer links

two plugin errors exist prior to upgrade, bedlevelvisualizer (missing numpy, although that's an old version as numpy dependency was removed) and PrintJobHistory complaining about update checks. nothing out of the ordinary. need to retrieve those logs after upgrade. the UI may not be accessible because it's not starting, but the logs are still obtainable via winscp/filezilla and the file system on the pi.

One system, the one at home, got clean installed using OctoPi image.
I can reproduce one last time the issue with the system at work - please specify exactly which logs you mean by "need to retrieve those logs after upgrade"

I'd first try to see if you can get to the recovery page by going to http://<ip>/recovery and see if it loads. If that doesn't then connecting via SSH to the pi and running the following commands to generate a bundle and then transfer that bundle from the pi with something like winscp/filezilla (if from windows machine).

source ~/oprint/bin/activate
octoprint systeminfo .

More details about the process can be found here.

The job Octopi was the remaining one with this issue. (which was reverted to 1.8.7)
I started with trying full backup. - got an error that required to look into log to find the reason , which was octoprint.plugins.backup.InsufficientSpace

I did 'rm /home/pi/.octoprint/timelapse/*'

• made a backup , (516MB)
  Then started the upgrade to 1.9.0 - and - this time ... it was completed successfully!.
  I doubt the space was the issue, but have no idea what else it could be.

Congrats on the recovery page! - very nice tool! - ..and quite hidden.
Maybe it should be mentioned right in the "server not running" page and other, similar places.