-
at first had problems with systemd startup, always timed out, fixed by: now have the problem, that motions stops after the first detection (event 1) - here full debug log since: then silence for a minute.. (movie_max_time set to 120) again one minute silence: and then the final shutdown: Why does it restart itself and why does it stop by itself? had issues directly after upgrading debian 10 to 11 and staying on motion 4.3.2, after that i updated manually to 4.4.0. |
Beta Was this translation helpful? Give feedback.
Answered by
Mr-Dave
Mar 8, 2022
Replies: 1 comment 2 replies
-
|
Moved this to a discussion. If there is an associated code problem, it can be reloged/moved back to an issue. From Debian 10 to 11 Motion changed to use systemctl. Looking at the commands issued in the comments, seems like there is a mix of the old service and new systemctl going on. First verify that there are not multiple instances running. Next, disable the systemctl that starts automatically via Once that is set up, then you can re-enable the log, and |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
so the only change i had to do was: i think everything is working as expected now, but please tell me, why daemon has to be set to off, when starting via systemctl ? it is runningas a daemon, but... weird.. sry |
Beta Was this translation helpful? Give feedback.
-
|
It is just one of those things. I think there is an option that can be added to the systemctl service file but when it was packaged on Debian, it wasn't included so this is how it now works.... |
Beta Was this translation helpful? Give feedback.
Answer selected by
kotzer3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Moved this to a discussion. If there is an associated code problem, it can be reloged/moved back to an issue.
From Debian 10 to 11 Motion changed to use systemctl. Looking at the commands issued in the comments, seems like there is a mix of the old service and new systemctl going on.
First verify that there are not multiple instances running. Next, disable the systemctl that starts automatically via
sudo systemctl disable motionNow that all the instances of motion have been shut down, disable the external log anddaemonin the motion.conf file and start motion from a command line so you can validate it all works.Once that is set up, then you can re-enable the log, and
sudo systemctl ena…