I have two similar systems which have been running motion for ages. I restarted them both today. One runs motion fine, on the other it fails.
The only difference is one has been upgraded with apt and the other hasn't.
Working:
Pi 3A+
Pi Camera 2 NoIR
Bookworm Lite 32-bit. Updated last weekend.
kernel 6.6.62+rpt-rpi-v7
libcamera-* 0.3.2+tpr20241118-1
motion 4.5.1-2
Not working
Pi 2B (BCM2836)
Pi Camera 2 NoIR
Bookworm Lite 32-bit. Updated today
kernel 6.6.74+rpt-rpi-v7
libcamera-* 0.4.0+rpt20250127-3
motion 4.5.1-2
The motion config files are pretty much identical.
I'm running motion with this service fileLog output from motion isand it just dies at that point.
rpicam-still works correctly.
It may be something I've done, but I can't think of anything I've changed recently that could have affected motion.
Any ideas?
The only difference is one has been upgraded with apt and the other hasn't.
Working:
Pi 3A+
Pi Camera 2 NoIR
Bookworm Lite 32-bit. Updated last weekend.
kernel 6.6.62+rpt-rpi-v7
libcamera-* 0.3.2+tpr20241118-1
motion 4.5.1-2
Not working
Pi 2B (BCM2836)
Pi Camera 2 NoIR
Bookworm Lite 32-bit. Updated today
kernel 6.6.74+rpt-rpi-v7
libcamera-* 0.4.0+rpt20250127-3
motion 4.5.1-2
The motion config files are pretty much identical.
I'm running motion with this service file
Code:
[Unit]Description=Motion detection video capture daemonDocumentation=man:motion(1)#Requires=home-share.mount#After=home-share.mount[Service]Type=simpleUser=motionEnvironment="LIBCAMERA_RPI_TUNING_FILE=/usr/share/libcamera/ipa/rpi/vc4/imx219_noir.json"ExecStart=/usr/bin/libcamerify /usr/bin/motion[Install]WantedBy=multi-user.targetCode:
[0:motion] [NTC] [ALL] [Feb 08 16:35:35] motion_startup: Motion 4.5.1 Started[0:motion] [NTC] [ALL] [Feb 08 16:35:35] motion_startup: Using log type (ALL) log level (NTC)[0:motion] [NTC] [STR] [Feb 08 16:35:35] webu_start_strm: Starting all camera streams on port 8081[0:motion] [NTC] [STR] [Feb 08 16:35:35] webu_strm_ntc: Started camera 0 stream on port 8081[0:motion] [NTC] [STR] [Feb 08 16:35:35] webu_start_ctrl: Starting webcontrol on port 8080[0:motion] [NTC] [STR] [Feb 08 16:35:35] webu_start_ctrl: Started webcontrol on port 8080[0:motion] [NTC] [ENC] [Feb 08 16:35:35] ffmpeg_global_init: ffmpeg libavcodec version 59.37.100 libavformat version 59.27.100[0:motion] [NTC] [ALL] [Feb 08 16:35:35] translate_init: Language: English[0:motion] [NTC] [ALL] [Feb 08 16:35:35] motion_start_thread: Camera ID: 0 is from /etc/motion/motion.conf [0:motion] [NTC] [ALL] [Feb 08 16:35:35] motion_start_thread: Camera ID: 0 Camera Name: (null) Device: /dev/video0[0:motion] [NTC] [ALL] [Feb 08 16:35:35] main: Waiting for threads to finish, pid: 24778[1:ml1] [NTC] [ALL] [Feb 08 16:35:35] motion_init: Camera 0 started: motion detection Enabled[1:ml1] [NTC] [VID] [Feb 08 16:35:35] vid_start: Opening V4L2 device[1:ml1] [NTC] [VID] [Feb 08 16:35:35] v4l2_device_open: Using videodevice /dev/video0 and input -1rpicam-still works correctly.
It may be something I've done, but I can't think of anything I've changed recently that could have affected motion.
Any ideas?
Statistics: Posted by rpdom — Sat Feb 08, 2025 5:33 pm — Replies 1 — Views 20