I've been using Octoprint on a Raspberry Pi 4 Model B Rev 1.4 for several years now without issue, but silly me, I clicked the update button when I logged into Octoprint today. It fails to start now with an error saying it cannot find GLIBC_2.34.
lld -version shows my system is running 2.28.
Is there a recommended release like bullseye or bookworm?
What did you already try to solve it?
I have only begun researching this error, which seems quite common when apps are compiled against different version of GLIBC. All the fixes look pretty awful. So I'd like to ask the officials in the forum, should I just re-image fresh, or is there a way to dig myself out of this. I have done the apt update/upgrade of course, but remain on buster.
Have you tried running in safe mode?
Not sure how to start the raspberry pi version in safe mode.
Did running in safe mode solve the problem?
Unknown
Systeminfo Bundle
You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
Can't start Octoprint to get this.
Additional information about your setup
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
pi@octopi:~/OctoPrint uname -a
Linux octopi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
pi@octopi:~/OctoPrint ldd --version
ldd (Debian GLIBC 2.28-10+rpt2+rpi1+deb10u2) 2.28
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
pi@octopi:~/OctoPrint cat /sys/firmware/devicetree/base/model
Raspberry Pi 4 Model B Rev 1.4pi@octopi:~/OctoPrint
pi@octopi:~/OctoPrint $ sudo apt update
Hit:1 Index of /debian buster InRelease
Hit:2 Index of /raspbian buster InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Buster version of Pi OS is 2 generations old and could have been utilizing the python 2 codebase. Just a quick test, what do you get when you run the following commands?
Honestly, if you don't have any other custom OS related stuff installed on that image, it's just as easy to use filezilla, winscp, or scp to transfer the ~/.octoprint/folder to get your uploaded gcode (uploads folder) and settings (config.yaml) and flash new image.
This worked for me. After I ran these commands I was back up and running on 1.7.3. For fun, I tried clicking on the upgrade button again, and yet again ended up with not being able to start the service because of the GLIBC error. Re-running these same commands fixed it up again. Thanks for the assistance.
This did not work for me. But I have a different error than the GLIBC error:
2025-09-05 09:32:54,559 - octoprint.startup - INFO - ******************************************************************************
2025-09-05 09:32:54,563 - octoprint.startup - INFO - Starting OctoPrint 1.7.3
2025-09-05 09:32:54,592 - octoprint.startup - INFO - Starting in SAFE MODE. Third party plugins will be disabled!
2025-09-05 09:32:54,593 - octoprint.startup - INFO - Reason for safe mode: setting in config.yaml
2025-09-05 09:32:54,593 - octoprint.startup - INFO - ******************************************************************************
2025-09-05 09:32:55,515 - py.warnings - WARNING - /home/bnosie/oprint/lib/python3.9/site-packages/octoprint/plugin/core.py:35: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
import pkg_resources
2025-09-05 09:32:57,092 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity changed from offline to online
2025-09-05 09:32:57,183 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity state is currently: online
2025-09-05 09:32:57,183 - octoprint.util.connectivity.connectivity_checker - INFO - Connecting to 1.1.1.1:53 is working
2025-09-05 09:32:57,184 - octoprint.util.connectivity.connectivity_checker - INFO - Resolving octoprint.org is working
2025-09-05 09:32:57,201 - octoprint.startup - INFO - Blacklist processing done, adding 3 blacklisted plugin versions: roomtemp (any), GcodeEditor (>=0.1.1,<=0.2.8), gcodeleveling (>=0.1.0,<=0.1.1)
2025-09-05 09:32:57,691 - octoprint.startup - CRITICAL - Could not initialize plugin manager: canonicalize_version() got an unexpected keyword argument 'strip_trailing_zero'
2025-09-05 09:32:57,692 - octoprint.startup - CRITICAL - There was a fatal error starting up OctoPrint.
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.
Sorry I don't have the console output anymore. I think the commands ran fine, only it just didn't solve the root issues. In the end I tried to update the debian version from buster to bullseye, but that crashed the system. So I installed a fresh Bookworm Octopi image and copied over the .octoprint directory from /home/ and I am now installed the plugins again (you can check which plugins you had in the logsfiles also in the .octoprin dir.
