Hi Guys, I’ve previously used Octoprint, but when trying to do a fresh Dietpi install today + Octoprint, I’m running into issues.
It looks like something is causing it to fail on start, but I can’t see an explicit error. It looks like it fails directly after loading plugins (but note that I have not installed any specific plugins or been able to launch Octoprint yet).
I get the following from the log file:
2022-01-07 07:59:16,049 - octoprint.startup - INFO - ******************************************************************************
2022-01-07 07:59:16,067 - octoprint.startup - INFO - Starting OctoPrint 1.7.2
2022-01-07 07:59:16,076 - octoprint.startup - INFO - ******************************************************************************
2022-01-07 07:59:18,967 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity state is currently: online
2022-01-07 07:59:18,970 - octoprint.util.connectivity.connectivity_checker - INFO - Connecting to 1.1.1.1:53 is working
2022-01-07 07:59:18,972 - octoprint.util.connectivity.connectivity_checker - INFO - Resolving octoprint.org is working
2022-01-07 07:59:22,104 - octoprint.plugin.core - INFO - Loading plugins from /mnt/dietpi_userdata/octoprint/.local/lib/python3.9/site-packages/octoprint/plugins, /mnt/dietpi_userdata/octoprint/.octoprint/plugins and installed plugin packages...
2022-01-07 07:59:32,405 - octoprint.plugin.core - INFO - Found 18 plugin(s) providing 18 mixin implementations, 38 hook handlers
If I try run Octoprint manually though I do spot something else.
Right after the line about “Found 18 plugins…” I see “Illegal instruction”
Any pointers or suggestions?
pls can you share some system details
Required Information
- DietPi version | cat /boot/dietpi/.version
- Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
- Kernel version | uname -a
- SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
G_DIETPI_VERSION_CORE=7
G_DIETPI_VERSION_SUB=9
G_DIETPI_VERSION_RC=3
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘applied’
G_LIVE_PATCH_STATUS[1]=‘not applicable’
G_LIVE_PATCH_STATUS[2]=‘not applicable’
G_LIVE_PATCH_STATUS[3]=‘not applicable’
bullseye 1
5.10.63+ #1488 Thu Nov 18 16:14:04 GMT 2021 armv6l GNU/Linux
RPi B (armv6l)
Its an old and probably underpowered Pi for this, but I definitely have had it working previously with Octoprint.
ok I tested on my RPi1 with same negativ result.
root@DietPi1:~# sudo -u octoprint /mnt/dietpi_userdata/octoprint/.local/bin/octoprint serve
2022-01-07 22:54:27,752 - octoprint.startup - INFO - ******************************************************************************
2022-01-07 22:54:27,766 - octoprint.startup - INFO - Starting OctoPrint 1.7.2
2022-01-07 22:54:27,776 - octoprint.startup - INFO - ******************************************************************************
2022-01-07 22:54:30,560 - octoprint.util.connectivity.connectivity_checker - INFO - Connectivity state is currently: online
2022-01-07 22:54:30,562 - octoprint.util.connectivity.connectivity_checker - INFO - Connecting to 1.1.1.1:53 is working
2022-01-07 22:54:30,565 - octoprint.util.connectivity.connectivity_checker - INFO - Resolving octoprint.org is working
2022-01-07 22:54:33,464 - octoprint.plugin.core - INFO - Loading plugins from /mnt/dietpi_userdata/octoprint/.local/lib/python3.9/site-packages/octoprint/plugins, /mnt/dietpi_userdata/octoprint/.octoprint/plugins and installed plugin packages...
2022-01-07 22:54:43,116 - octoprint.plugin.core - INFO - Found 18 plugin(s) providing 18 mixin implementations, 38 hook handlers
Illegal instruction
root@DietPi1:~#
On the other hand side, a test on RPi4B 64bit was successful.
Probably it’s an issue of ARMv6. Maybe these platform is not supportend anymore by newer version of Octoprint.
A question to ask on https://github.com/OctoPrint/OctoPrint/issues
Thank you for having a look. I’ll reach out there too 
Pls share the feedback as it would be interesting for us as well 
Will do. Something interesting though - I tried loading Octopi directly and it works just fine (not ideal as I really prefer using Dietpi for everything). All appeared to be sorted until I loaded a plugin and the same issue started again “Illegal Instruction”.
loading Octopi directly
what do you mean by this?
Anyway our developer had a quick look into to. This was his statement
Looks like OctoPrint loads an ARMv7-only plugin/wheel, I mean Python scripts themselves cannot be incompatible, but the compiled wheels can.
On 32bit system we load all wheels from https://www.piwheels.org/ . If I find time, I will try to install OctoPrint without pre-compiled wheels. That night gonna work as wheels are compiled on SBC directly.
EDIT
Jup it’s one or more of the pre-compiled wheels from piwheels.org. I did a test, installed OctoPrint without using piwheels.org and installation was successful as all wheels compiled on the RPI1 directly.
Ah apologies - I meant I flashed a precompiled OctoPi image on an SD card to test (i.e. No Dietpi). That is probably why there was no issue until I tried to install a plugin and it then probably pulled V7 packages that are not compatible?
All that aside - it also looks like the OctoPi experience is not great on a Pi Model B (they do tell you it’s not recommended due to “performance issues”). It seems to all work, but I can see the machine is not very happy about it 
I’ve also had some layer shift issues and slow prints with it (a conversation for another time and place).
yes, there is no joy to use a Rpi1
The issue definitely seems to be on piwheels.org as it seems they pre-compiled some wheels for ARMv7 only. At the moment we try to find out which one, to be able to report it upstream.