What OctoPi-UpToDate modification is involved?

01-update-octoprint

The problem

While video stream is running, it stops after some period of time either with a full frame or a partial frame. Sometimes refreshing the browser page will get it started again. Browser is Firefox 117.0 (64-bit).

I initially had this problem with a Pi Zero 2 W and a Pi camera 3. Tried a Pi camera 3 wide and same issue. Switched to a Pi 3B with both cameras and same issue. Tried 2 different power supplies and same issue. Tried with an older Pi camera and it took a lot longer to have the video freeze but it did finally fail.

I am now running the Pi 3b with old camera stream and a Pi camera 3 and all is well.

I have not looked at the source code so I don't know if things are interrupt driven. If so, my guess is that an interrupt is being lost and all video stops waiting for the interrupt to be processed.

Please confirm you have understood that you can ONLY report issues with the particular OctoPi-UpToDate build scripts here, not general OctoPrint or OctoPi issues.

• I confirm that my issue is NOT about OctoPrint.
• I confirm that my issue is NOT about OctoPi.
• I confirm that my issue is ONLY about OctoPi-UpToDate.

Additional information & file uploads

I have several logic analyzers (retired IBM Engineer) and have the ability to monitor GPIO(s) pins to help troubleshoot if required.

👉 Latest image & feedback ticket can be found here 👈

This is a ticket to collect feedback on the latest build of the new camera stack (some background on that here) for OctoPi-UpToDate, 20230328122604. Find the image here: https://github.com/OctoPrint/OctoPi-UpToDate/releases/tag/1.0.0-1.8.7-20230328122604

Changes compared to the previous version:

• camera-streamer is now built in another repository, packaged as a deb and then published on https://apt.octoprint.org. The image build now installs from that apt repo and thus makes it possible to update camera-streamer to a later version as necessary, e.g. for bug fixes or if new backwards incompatible libcamera versions are being released.
• latest version of camera-streamer, arguments switched from - to -- accordingly
• workaround for a kernel bug in the latest raspberrypi-kernel package

(Compare view)

Some first config docs are available here: https://faq.octoprint.org/camera-streamer-config

The source tree used for the build is here: https://github.com/OctoPrint/OctoPi-UpToDate/tree/camera-streamer

❗ Please note

This image needs to be flashed to your SD card, wiping it in the process. So if you want to keep anything on there, make a backup first! You can also create an OctoPrint backup, download that, flash, restore from backup. There's no way to update to the contents of this image without a full reflash.

Please provide feedback on your experience with this image in this ticket, whether things work for you or not. Make sure to at least include the following:

• Everything working?
• Pi model
• used cameras
• in case of issues: related logs (journalctl -u camera-streamer\* | pb and share the generated paste.octoprint.org URL)

Known issues:

• --camera-{v,h}flip are currently broken in camera-streamer v0.1-16-gcdb62ef (cdb62ef), see ayufan/camera-streamer#51

Common pitfalls:

• RPiV3 camera not auto-focusing? Make sure any kind of case you've added to it is not interfering with the lens & sensor

👉 Latest image & feedback ticket can be found here 👈

This is a ticket to collect feedback on the latest build of the new camera stack (some background on that here) for OctoPi-UpToDate, 20230504122418. Find the image here: https://github.com/OctoPrint/OctoPi-UpToDate/releases/tag/1.0.0-1.8.7-20230504122418

Changes compared to the previous version:

• camera-streamer upgraded to v0.1-21-g54f538e (fixes --camera-{v,h}flip, see ayufan/camera-streamer#51)
• kernel pinned to 32bit (see raspberrypi/linux#5402)
• "no webcam available" error page adjusted for new camera-stack (#4, thanks @cp2004!)

This should hopefully now cover all pain points reported on past iterations.

(Compare view)

Some first config docs are available here: https://faq.octoprint.org/camera-streamer-config

The source tree used for the build is here: https://github.com/OctoPrint/OctoPi-UpToDate/tree/camera-streamer

❗ Please note

This image needs to be flashed to your SD card, wiping it in the process. So if you want to keep anything on there, make a backup first! You can also create an OctoPrint backup, download that, flash, restore from backup. There's no way to update to the contents of this image without a full reflash.

Please provide feedback on your experience with this image in this ticket, whether things work for you or not. Make sure to at least include the following:

• Everything working?
• Pi model
• used cameras
• in case of issues: related logs (journalctl -u camera-streamer\* | pb and share the generated paste.octoprint.org URL)

Known issues:

Currently none.

Common pitfalls:

• RPiV3 camera not auto-focusing? Make sure any kind of case you've added to it is not interfering with the lens & sensor

👉 Latest image & feedback ticket can be found here 👈

OctoPi 1.0.0 is out, and I also have a new camera stack for you all to test!

Over the course of the past two weeks I've been setting up a CustoPiZer build script to swap the mjpg-streamer/webcamd combo on OctoPi that currently only supports the old legacy camera stack with a new camera-streamer and systemd based setup that supports libcamera (think RPiCam v3 as well as newer Arducams on top of the old ones). Some systemd magic takes care of camera detection, hotplug and even multicam support (successfully tested with two USB cameras and one RPiv3cam).

You can find the image here: https://github.com/OctoPrint/OctoPi-UpToDate/releases/tag/1.0.0-1.8.7-20230309160428. Image last updated on 2023-03-09 @ 16:50UTC!

Some first config docs are available here: https://faq.octoprint.org/camera-streamer-config

And finally, this is the source tree used for the build: https://github.com/OctoPrint/OctoPi-UpToDate/tree/camera-streamer

❗ Please note

This image needs to be flashed to your SD card, wiping it in the process. So if you want to keep anything on there, make a backup first! You can also create an OctoPrint backup, download that, flash, restore from backup. There's no way to update to the contents of this image without a full reflash.

I hope to be able to merge this into the OctoPi-UpToDate main branch ASAP, after which it will become part of the OctoPi image distributed on the download page and RPi Imager, but some testing from others would certainly help here 🙂

Please provide feedback on your experience with this image in this ticket, whether things work for you or not. Make sure to at least include the following:

• Everything working?
• Pi model
• used cameras
• in case of issues: related logs (journalctl -u camera-streamer\* | pb and share the generated paste.octoprint.org URL)

The current signing key will go invalid on March 15th. It has thus been rotated to a new one. Sadly this requires a re-import of the public key for apt to recognize the new key (something not on my radar when I created the old key and set it to only one year of runtime).

This manifests in an error like this:

W: GPG error: https://apt.octoprint.org/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 418208F07AD011A2
E: The repository 'https://apt.octoprint.org/debian bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

If you run into this, please enter these commands to re-import the updated public key:

curl -s --compressed "https://foosel.github.io/apt.octoprint.org/octoprint.gpg.key" | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/octoprint.gpg > /dev/null
sudo apt update

The updated key will be valid until March 10th 2034.

Future builds will recognize the updated key out-of-the-box.

👉 Latest image & feedback ticket can be found here 👈

This is a ticket to collect feedback on the latest build of the new camera stack (some background on that here) for OctoPi-UpToDate.

Currently, that is 20230718115729. Find the image here: https://github.com/OctoPrint/OctoPi-UpToDate/releases/tag/1.0.0-1.9.2-20230718115729

Config docs are available here: https://faq.octoprint.org/camera-streamer-config

The source tree used for the build is here: https://github.com/OctoPrint/OctoPi-UpToDate/tree/camera-streamer

Changelog

Changes in build 20230718115729 from 2023-07-18

• OctoPrint updated to 1.9.2

Changes in build 20230627083607 from 2023-06-27

• OctoPrint updated to 1.9.1

Changes in build 20230523124648 from 2023-05-23

• OctoPrint updated to 1.9.0

❗ Please note

This image needs to be flashed to your SD card, wiping it in the process. So if you want to keep anything on there, make a backup first! You can also create an OctoPrint backup, download that, flash, restore from backup. There's no way to update to the contents of this image without a full reflash.

Please provide feedback on your experience with this image in this ticket, whether things work for you or not. Make sure to at least include the following:

• Everything working?
• Pi model
• used cameras
• in case of issues: related logs (journalctl -u camera-streamer\* | pb and share the generated paste.octoprint.org URL)

Known issues:

Currently none.

Common pitfalls:

• RPiV3 camera not auto-focusing? Make sure any kind of case you've added to it is not interfering with the lens & sensor

What OctoPi-UpToDate modification is involved?

01-update-octoprint

The problem

1. camera stream does not load on SLA-Control tab
2. going through settings>Webacm and Timelapse>MJPEG stream [/webcam/?action=stream], the camera is present and viewable

Please confirm you have understood that you can ONLY report issues with the particular OctoPi-UpToDate build scripts here, not general OctoPrint or OctoPi issues.

• I confirm that my issue is NOT about OctoPrint.
• I confirm that my issue is NOT about OctoPi.
• I confirm that my issue is ONLY about OctoPi-UpToDate.

Additional information & file uploads

It looks like we have a behaviour change in that regard from from OctoPi < 1.0.0 to OctoPi >= 1.0.0.

Example:

OctoPi 0.18.0:

2023-11-28 17:52:47,473 - octoprint.server - INFO - Shutting down...
2023-11-28 17:52:47,485 - octoprint.server - INFO - Calling on_shutdown on plugins
2023-11-28 17:52:47,489 - octoprint.events - INFO - Processing shutdown event, this will be our last event
2023-11-28 17:52:47,672 - octoprint.events - INFO - Event loop shut down
2023-11-28 17:52:47,921 - octoprint.plugins.tracking - INFO - Sent tracking event shutdown, payload: {}
2023-11-28 17:52:48,111 - octoprint.server - INFO - Goodbye!
2023-11-28 17:52:55,660 - octoprint.startup - INFO - ******************************************************************************
2023-11-28 17:52:55,663 - octoprint.startup - INFO - Starting OctoPrint 1.9.3
2023-11-28 17:52:55,665 - octoprint.startup - INFO - ******************************************************************************

OctoPi 1.0:

2023-11-28 17:58:10,696 - octoprint.plugins.github_release_patcher - INFO - Started dummy release server on http://127.0.0.1:50672
2023-11-28 17:58:10,696 - octoprint.plugins.github_release_patcher - INFO - Set Github release URL to http://127.0.0.1:50672/releases/{user}/{repo}
2023-11-28 18:01:21,363 - octoprint.startup - INFO - ******************************************************************************
2023-11-28 18:01:21,366 - octoprint.startup - INFO - Starting OctoPrint 1.9.3
2023-11-28 18:01:21,367 - octoprint.startup - INFO - ******************************************************************************

No shutdown events triggered. It looks like the systemd unit on 1.0 simply nukes away the server directly, whereas on OctoPi < 1.0 it still got a chance to cleanly shut down. That's something that needs to get looked at, but that's rather something for OctoPrint/OctoPi-UpToDate or guysoft/OctoPi.

Originally posted by @foosel in OctoPrint/OctoPrint#4882 (comment)

This is a ticket to collect feedback on the latest build of the new camera stack (some background on that here) for OctoPi-UpToDate.

Currently, that is 2023.10.09.154319. Find the image here: https://github.com/OctoPrint/OctoPi-UpToDate/releases/tag/1.0.0-1.9.3-20231009154319

Config docs are available here: https://faq.octoprint.org/camera-streamer-config

The source tree used for the build is here: https://github.com/OctoPrint/OctoPi-UpToDate/tree/camera-streamer

Changelog

Changes in build 2023.10.09.154319 from 2023-10-09

• OctoPrint updated to 1.9.3

Changes in build 2023.07.20.144556 from 2023-07-20

• camera-streamer updated to 0.2.5
  • Heads-up: camera-streamer 0.2.5 added a new parameter --http-listen to define which network interfaces to listen on, and by default only listens on localhost. If you have cameras configured that are currently not behind haproxy on the same device, you'll need to add --http-listen=0.0.0.0 to the OPTIONS of your camera config. The docs have been updated accordingly.
• user-fix fixed #8

❗ Please note

This image needs to be flashed to your SD card, wiping it in the process. So if you want to keep anything on there, make a backup first! You can also create an OctoPrint backup, download that, flash, restore from backup. There's no way to update to the contents of this image without a full reflash.

Please provide feedback on your experience with this image in this ticket, whether things work for you or not. Make sure to at least include the following:

• Everything working?
• Pi model
• used cameras
• in case of issues: related logs (journalctl -u camera-streamer\* | pb and share the generated paste.octoprint.org URL)

Known issues:

• ayufan/camera-streamer#94 (this is currently considered a blocker for general roll-out of this camera stack, as it causes the camera stream to crash)

Common pitfalls:

• RPiV3 camera not auto-focusing? Make sure any kind of case you've added to it is not interfering with the lens & sensor

What OctoPi-UpToDate modification is involved?

80-install-user-fix

The problem

1.0.0-1.9.2 new stack is having an issue with non default username.
After installing the Image with the "new camera stack" there is an issue with executing the octoprint executable:
-- Journal begins at Thu 2022-09-22 01:23:40 BST, ends at Wed 2023-07-19 22:29:42 BST. -- Sep 22 01:23:59 octopi systemd[1]: Started The snappy web interface for your 3D printer. Sep 22 01:23:59 octopi systemd[429]: octoprint.service: Failed to execute /home/zaid/oprint/bin/octoprint: No such file or directory Sep 22 01:23:59 octopi systemd[429]: octoprint.service: Failed at step EXEC spawning /home/zaid/oprint/bin/octoprint: No such file or directory Sep 22 01:24:00 octopi systemd[1]: octoprint.service: Main process exited, code=exited, status=203/EXEC Sep 22 01:24:00 octopi systemd[1]: octoprint.service: Failed with result 'exit-code'.

I checked if the file was there:
`zaid@octopi:~/oprint $ ls -lah
total 24K
drwxr-xr-x 4 zaid zaid 4.0K Oct 27 2022 .
drwxr-xr-x 8 zaid zaid 4.0K Sep 22 2022 ..
drwxr-xr-x 2 zaid zaid 4.0K Jul 18 13:03 bin
-rw-r--r-- 1 zaid zaid 40 Oct 27 2022 .gitignore
drwxr-xr-x 3 zaid zaid 4.0K Oct 27 2022 lib
-rw-r--r-- 1 zaid zaid 204 Oct 27 2022 pyvenv.cfg

zaid@octopi:~/oprint/bin $ ls -lah| grep octo
-rwxr-xr-x 1 zaid zaid 218 Jul 18 13:03 octoprint`

It just didn't want to start up. I had a custom user with a password set up. Not sure, if that is an issue here.

Please confirm you have understood that you can ONLY report issues with the particular OctoPi-UpToDate build scripts here, not general OctoPrint or OctoPi issues.

• I confirm that my issue is NOT about OctoPrint.
• I confirm that my issue is NOT about OctoPi.
• I confirm that my issue is ONLY about OctoPi-UpToDate.

Additional information & file uploads

XXXX@octopi:~ $ cat /etc/octopi_version
1.0.0