-
Hi everyone, I had motion running great on my server when it was on Ubuntu 18.04. Now that I have reinstalled my server to a most recent version and kernel, I can't start motion anymore. Once started, the service status is turning on "deactivating" mode then is being killed. System configuration:
Motion configuration:I got the motion.conf file which is calling two additionnal camera files (camera1-dist.conf and camera2-dist.conf). This worked well on my old system, now it seems that motion tries to open a device from motion.conf, where there none. motion.conf:
Camera conf:
Motion service status just after starting:
The most odd thing is that it actually capture and write pictures on disk until it is being killed. Final status (killed):
I spend hours on this... anyone knows what I'm doing wrong? Thank you for your help |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
It seems that the problem occurs only when running motion with systemd service, cause when I run motion in daemon mode with:
Everything seems to work fine. Any idea? |
Beta Was this translation helpful? Give feedback.
It seems that the problem occurs only when running motion with systemd service, cause when I run motion in daemon mode with:
motion -c /etc/motion/motion.conf -b -d 3 -k ALL
Everything seems to work fine.
Any idea?