No script start on_movie_end und on_picture_save #1816
Replies: 11 comments 23 replies
-
|
I have checked |
Beta Was this translation helpful? Give feedback.
-
|
It definitely doesn't work. |
Beta Was this translation helpful? Give feedback.
-
|
Try to put something simple that is not restricted by user rights, ex, |
Beta Was this translation helpful? Give feedback.
-
|
I too see these being triggered on my test machine but do not see it happening in your log.
(Just searching for possible clues as to why it isn't working anymore) |
Beta Was this translation helpful? Give feedback.
-
|
I'm particularly curious about this message: It appears right where exec_command should go |
Beta Was this translation helpful? Give feedback.
-
|
Looks like execution failed and the child process reached Line 99 in 1ae0438 |
Beta Was this translation helpful? Give feedback.
-
|
I tried to put whatever nonsense into command but it gets executed every time |
Beta Was this translation helpful? Give feedback.
-
|
I also checked two cameras setup and the command is executed: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the quick reply. The most important settings are now:
Additionally I have activated...
There are still no entries in the log... After triggering 3 events, motion.log looks like this:
It still doesn't work.
Alternatively I could use inotify to monitor the directory with the mp4 and jpg files and perform actions.... |
Beta Was this translation helpful? Give feedback.
-
Remove duplicate strings from config, run again and upload new log |
Beta Was this translation helpful? Give feedback.
-
|
Oh, I made a mistake with the copy-paste. I added the logger to a few on_xxxx events. Here is the new log file:
Regards, |
Beta Was this translation helpful? Give feedback.
-
|
After upgrading motion 4.3.2 with version 4.7.0, some libraries were no longer needed and were removed by apt-autoremove.
As I see from the deb package of motion 4.7, these libraries are now used:
Maybe there is an incompatibility there ? |
Beta Was this translation helpful? Give feedback.
-
|
How comfortable are you in building motion from sources? |
Beta Was this translation helpful? Give feedback.
-
|
I only have basic knowledge and have so far created from sources when everything was already prepared. If you give me some guidance, I'm sure I can add additional logging around the exec_command function. |
Beta Was this translation helpful? Give feedback.
-
|
This is a mystery... Is everything completely up to date with For building and adding logging, you can follow the guide for Debian . The only thing is to just not do the Once it is built, you would start it with the command The specific logging to add is inside the exec_command function which is in the Add the following using a text editor: Save the file, go back and execute |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for the instructions. After building I started There were no outputs in the log file with "Test log ..." I then searched event.c for the first function that calls exec_command(). I added a line MOTION_LOG() to this function so that it now looks like this: After rebuilding, I started motion again. Even if ERR, TYPE_EVENTS and SHOW_ERRNO may not be assigned when the call is made (I don't know much about this), you can see that on_xxxx... commandos are called, but exec_command() is probably never called there. I hope this helps to find the error. |
Beta Was this translation helpful? Give feedback.
-
|
...I just noticed that on_picture_save is disabled... But on_event_start is enabled, so I added the line to on_event_start. The following entries are now present in the log file (excerpt): |
Beta Was this translation helpful? Give feedback.
-
|
Then I deactivated if(...) in on_movie_end. Now the entries in the log look like this: There is no output of the command I hope it helps. |
Beta Was this translation helpful? Give feedback.
-
|
I forgot to describe this: |
Beta Was this translation helpful? Give feedback.
-
|
This seems to indicate that the configuration item for the Try to specify the |
Beta Was this translation helpful? Give feedback.
-
Try to specify the on only in the camera.conf file rather than the motion.conf file.This is the solution !!!. Up to version 4.3.2 it worked if the on_ entries were in the motion.conf file. In the versions after that the entries must be in the configuration files of the cameras. Please point out in documentation that the configuration of the on_ events belongs in the camera configuration files. Thank you very much for your good support and help!!! The thread can now be closed. Jörg |
Beta Was this translation helpful? Give feedback.
-
|
I have checked one of my 4.6.0 cameras, and I don't see such behavior. |
Beta Was this translation helpful? Give feedback.
-
|
That is possible, I carried out the tests with on_movie_end. |
Beta Was this translation helpful? Give feedback.
-
|
can you zip and upload the original configs? |
Beta Was this translation helpful? Give feedback.
-
|
The configs do not need to be zipped, there is not much contained if I leave out all unused options: motion.conf: camera....conf In the configuration for the other two cameras only other camera_name, camera_id, picture_filename, movie_filename and of course a changed netcam_url are used. All other options not mentioned here are commented out or do not exist. |
Beta Was this translation helpful? Give feedback.
-
|
@Joerg12345 I know, that you kinda found a workaround, but would you mind helping us to identify the root cause? Could you please comment out all Also edit This will comment out few lines and always print config values with quotes. Then edit This will print all config params again at event, like it does on start. This way we could see if values somehow changed at runtime. Recompile, then set Thanks 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
I have applied all changes and am using only one camera again: In conf.c And in motion.c In motion.conf is set Now only these lines appear in motion.log: It seems that none of the on_ events are processed. |
Beta Was this translation helpful? Give feedback.
-
|
@Joerg12345 from the top of the main config to the bottom and check if that resolves the issue? |
Beta Was this translation helpful? Give feedback.
-
|
Ok, so now the issue is clear. Camera params must come the last: |
Beta Was this translation helpful? Give feedback.
-
|
Shared params must stay in the main config. Camera files only contain params that you override, like camera_name, netcam_url etc |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the help and the great motion project ! |
Beta Was this translation helpful? Give feedback.
-
|
I have to apologize, I made a mistake in the last test!!! When "cleaning up" the configurations, I noticed that the settings for the on_events and loading the camera configuration were included twice in the So I tested them all again and got the following results: Only So no events are recorded ! If I change the order of the lines (camera configuration is loaded after the events are defined): This records events, which This means that when defining on_ events in It does not matter whether the lines are at the end, in the middle or at the beginning of the motion.conf file, only the order is important. In case the camera configurations do not contain on_ events, the events contained in If events are defined in the configuration for one of the two camera, the setting in motion.conf is overwritten for this camera and this event is used for this camera. This means...if the same event is used for all cameras, it is sufficient to enter it in ...or it is "mixed" if motion.conf contains on_ event entries and some camera configurations have their own on_ events for their camera. Please excuse the mistake I made, after testing intensively for another 3 hours, the description is now correct. |
Beta Was this translation helpful? Give feedback.
-
|
To make configuration easier when setting up for the first time, I have created templates for the first configuration. I noticed that in a camera configuration from an old installation there was an entry |
Beta Was this translation helpful? Give feedback.
-
Did you read the guide?
Yes
What is the base version number of Motion being used?
4.3.x
What was the install method?
Installed via package tool
What is base architecture?
ARM-64bit
What is the distro being used?
Raspbian
Disto version number
12 bookworm
Camera type(s) being used?
Network camera with RTSP
Describe the issue/problem and steps to reproduce
For all motion versions greater than 4.3.2, no script is started for on_movie_end and on_picture_save.
After updating from 4.3.2 to 4.7.0 I noticed this.
Then I tried some versions >4.3.2 and <4.7.0, but no script was started in any of them.
I'm doing something wrong or is this a bug in the software ?
Many thanks for your support!
Jörg
Motion log output at log_level 8
Beta Was this translation helpful? Give feedback.
All reactions