Octoprint don't start after new flash 1.11.2

[horodav]

What is the problem?

I flashed my sd card to install Octoprint 1.11.2.
It ran on my rasberry (Model B+ v1.2, I guess raspebby model 1) since months in verison 1.7.x
I wanted to make a full upgrade
On the raspberry, if I log with "pi' , i am having access
The ip adress is responding to a ping
http://octopi.local in my browser is not working
but http://192.68.0.60 (ip adress of octopi.local) is showing The OctoPrint server is currently not running.

What did you already try to solve it?

I tried whats proposed in the web page:

Verify that the process is running: ps -ef | grep -i octoprint | grep -i python should show a python process: => nothing happend

Take a look into ~/.octoprint/logs/octoprint.log : the folder "logs" doesn't exist

I tried this commandpi @octopi:~ $ netstat -lp | grep http
tcp6 0 0 [::]:https [::]:* LISTEN -
tcp6 0 0 [::]:http [::]:* LISTEN -

Have you tried running in safe mode?

No beacuse I don't undestand how to do it

Did running in safe mode solve the problem?

WRITE HERE

Systeminfo Bundle

I tried "octoprint systeminfo." in the command line of "pi" session, but I get "command not found"

I checked the octoprint service staus: it is not running!:
pi@octopi:~ sudo service octoprint status ✗ octoprint.service - The snappy web interface for your 3D printer Loaded: loaded (/etc/systemd/system/octoprint.service; enabled; preset: enabled) Active: failed (Result: signal) since Fri 2025-08-08 21:03:46 BST; 1min 6s ago Duration: 5.507s Process: 2095 ExecStart=/opt/octopi/oprint/bin/octoprint serve --host={HOST} --port=${PORT}
Main PID: 2095 (code=killed, signal=ILL)
CPU: 4.967s

Aug 08 21:03:40 octopi systemd[1]: Started octoprint.service - The snappy web interface for your 3D printer.
Aug 08 21:03:46 octopi systemd[1]: octoprint.service: Main process exited, code=killed, status=4/ILL
Aug 08 21:03:46 octopi systemd[1]: octoprint.service: Failed with result 'signal'.
Aug 08 21:03:46 octopi systemd[1]: octoprint.service: Consumed 4.967s CPU time.
pi@octopi:~ $

Additional information about your setup

Octoprint version 1.11.2
OctoPi version 1.1.0

Update. in the mean time, I asked Chatgpt...

The problem here most likely comes from the fact that your Raspberry Pi 1 is old (ARMv6 processor, low RAM), and the current version of OctoPi/OctoPrint 1.11.2 is no longer officially compatible with this architecture.

Here’s what you need to know:

Since OctoPrint 1.9 or so, Python 3.8+ is required.

However, on a Raspberry Pi 1 (ARMv6), recent OctoPi images no longer provide a compatible build, and recent Raspbian versions don’t support a new enough Python without hacks.

Official OctoPi images are now built for ARMv7 and ARMv8 (Pi 2 and above).

In short:
Recent OctoPi will no longer run natively on a Pi 1 → you have to either:

• Stick with an older version (e.g. OctoPi based on Raspbian Jessie or Stretch, with OctoPrint ≤ 1.7.x).
• Compile OctoPrint yourself on Raspbian Lite (it can run, but very slowly).
• Upgrade to a Pi 3, 4, or Zero 2 W to enjoy the latest versions without headaches.

If you absolutely want to keep your Pi 1:

• Flash an old OctoPi image compatible with Pi 1: for example, OctoPi 0.17.0 (with OctoPrint 1.3.12) or OctoPi 0.18.0 (OctoPrint 1.5.3).
• Then update OctoPrint manually up to the latest version that still works with Python 3.7 (1.7.x).

If you want, I can give you the direct link to download the latest OctoPi image compatible with Raspberry Pi 1 and the procedure to block updates before they break anything.

Thereofore I downloaded version 1.5.3 and now my Octoprint server is back to live

[jneilliii]

@horodav

Compile OctoPrint yourself on Raspbian Lite (it can run, but very slowly).

Technically wouldn't run any slower than flashing the octopi image I don't think. You can go this approach and use octoprint_deploy to install everything needed.

[David2]

I had the same thing happen tonight and just feel disappointed the app recommended I apply an update that basically bricks my OctoPi. Ultimately I know it's my responsibility to check requirements but I didn't expect OctoPrint to be so high octane and didn't even know something like this could happen. For what its worth, I was also running OctoPrint on a B+. It really might be a good idea to put device compatibility issues up front for users to prevent other people from blundering into the same mistake - like perhaps require users to read and acknowledge what relevant information is available regarding processor or RAM compatibility. Because honestly, I am going to continue using my Pi B+ seeing that it worked fine. Oh well, I now need to learn how to offload my old videos and locate my old OctoPi image.

[jneilliii]

Honestly I'm confused why these issues are happening for you guys with the update. More than likely a change in some upstream dependency that is no longer supported that @foosel might not be aware of.

Upgraded Octoprint, new GLIBC dependency broken

I would use the integrated backup as PrintedWeezl mentioned. Using my backup scheduler plugin in combination with one of the cloud based backup solutions like OneDrive, GoogleDrive, Dropbox (it says timelapse but works with backup events too), or webdav you can achieve resillience in your setup in case the SD card dies or gets corrupted too.

Updated Octoprint today, and now it won't start

Unlike the other issue you are running the latest python 3.9 version in bullseye. What do you get if you run the following command? source ~/oprint/bin/activate pip install --force-reinstall --no-cache-dir octoprint deactivate

[foosel]

For the record, piwheels changed something about their build systems and rebuilt psutil on September 4th, and that probably caused that issue:

Problem with package: psutil

edit The problematic builds have now been pulled from piwheels, so this should no longer happen, at least for now.

[brybalicious]

What is the fix for people with this issue? Install a newer image?

[horodav]

see my update in the initial post:

Update. in the mean time, I asked Chatgpt...

The problem here most likely comes from the fact that your Raspberry Pi 1 is old (ARMv6 processor, low RAM), and the current version of OctoPi/OctoPrint 1.11.2 is no longer officially compatible with this architecture.

Here’s what you need to know:

Since OctoPrint 1.9 or so, Python 3.8+ is required.

However, on a Raspberry Pi 1 (ARMv6), recent OctoPi images no longer provide a compatible build, and recent Raspbian versions don’t support a new enough Python without hacks.

Official OctoPi images are now built for ARMv7 and ARMv8 (Pi 2 and above).

In short:
Recent OctoPi will no longer run natively on a Pi 1 → you have to either:

• Stick with an older version (e.g. OctoPi based on Raspbian Jessie or Stretch, with OctoPrint ≤ 1.7.x).
• Compile OctoPrint yourself on Raspbian Lite (it can run, but very slowly).
• Upgrade to a Pi 3, 4, or Zero 2 W to enjoy the latest versions without headaches.

If you absolutely want to keep your Pi 1:

• Flash an old OctoPi image compatible with Pi 1: for example, OctoPi 0.17.0 (with OctoPrint 1.3.12) or OctoPi 0.18.0 (OctoPrint 1.5.3).
• Then update OctoPrint manually up to the latest version that still works with Python 3.7 (1.7.x).

If you want, I can give you the direct link to download the latest OctoPi image compatible with Raspberry Pi 1 and the procedure to block updates before they break anything.

Thereofore I downloaded version 1.5.3 and now my Octoprint server is back to live

[foosel]

Instead of listening to regurgitations of a genAI that doesn't understand the actual problem at hand here, here's the actual solution for when you already are affected:

Updated Octoprint today, and now it won't start

For me this did the trick: source ~/oprint/bin/activate # activate OctoPrint venv pip uninstall -y psutil pip install --no-binary=:all: "psutil>=6.1.1,<7"

[foosel]

Your stochastic parrot is wrong and you really shouldn't be running ancient software, let alone propagate that as the solution for others to follow.