scriptorron
commented
7 months ago Hi Markus,
the first error message comes from libcamera:
2024-02-21T21:47:10.599487+01:00 haustuer indiserver[667]: 2024-02-21T20:47:10: Driver indi_pylibcamera: [5:28:24.978519301] [788] #33[1;31mERROR # 33[1;37mCamera #33[1;34mcamera.cpp:675 #33[0mCamera in Configured state trying queueRequest() requiring state RunningThat leaded to a RuntimeError in a thread started and hosted by the picamera2 library. It seems this exception is not raised up to the indi_pylibcamera driver (your log looks like the driver continues to start exposures). I will try to find a way to detect the exception. Than I can implement something to recover from the error.
Which version of the python-picamera2 library do you use? Please forward me the output of
apt list --installed | grep picamera2Do you know a way to reproduce the error without waiting for hours?
Thank you, Ronald
gmke
I'm running indi_pylibcamera on a RPi Zero 2 W with Raspbian bookworm 64bit and a RPI HQ camera. Intended use is as an Allsky camera with indi-allsky. For various reasons, indi-allsky runs on a different server, the Zero 2 W only runs indiserver (v2.0.6) with the indi_pylibcamera driver. The driver was installed using pip but without a venv. Since about a week, this setup runs on my desk for test purposes. Unfortunately, the driver frequently crashes. Usually I get a run time of a few hours, the current record was about 24h. The error condition in the syslog looks always like this:
CS, Markus