ZoneMinder Forums

Hello !

My zoneminder v1.32.3 works very well except filters execute command, so for trying/debugging
I made a filter for all cams with alarm frames>250, limit to first 5 results and
Execute command on all matches: usr/bin/zmtest.sh
usr/bin/zmtest.sh (have rights: root:www-data 777) is as follow:

#!/bin/bash
event_path=$1
echo $event_path >>/home/jpd/Dropbox/zmevents/mf

dir zmevents have rights root:www-data 777
zmtest works well on command line (i added a path) but in the filter view if I clic on execute(filter) it doesn't.(the filter just sort the list of matches)

zm log returns for each matches :
.. zmfilter..ERR Command 'usr/bin/zmtest.sh /var/cache/zoneminder/events/2/2019-03-18/2329' exited with status: 72057594037927935

I don't understand why - May somebody help me to solve this issue ?

Thanks in advance

info: zoneminderv1.32.3 is installed according to 'Ubuntu Server 18.04 64-bit with Zoneminder 1.32.x the easy way' & Ubuntu 18.04 LEMP (NGNIX, Mariadb, PHP)

hello !

executing # zmfilter.pl --filter_id=114 from command line , for each matched event it comes for example:

20/03/2019 08:58:02.888270 zmfilter_114[3059].INF [main:970] [Executing 'usr/bin/zmtest.sh /var/cache/zoneminder/events/2/2019-03-19/2502']
Can't exec "usr/bin/zmtest.sh": Aucun fichier ou dossier de ce type at /usr/bin/zmfilter.pl line 971.
Use of uninitialized value $output in scalar chomp at /usr/bin/zmfilter.pl line 974.
Use of uninitialized value $output in concatenation (.) or string at /usr/bin/zmfilter.pl line 975.
20/03/2019 08:58:02.894809 zmfilter_114[3059].ERR [main:978] [Command 'usr/bin/zmtest.sh /var/cache/zoneminder/events/2/2019-03-19/2502' exited with status: 72057594037927935]

can't exec... NO file or dir at /usr/bin/zmfilter.pl line 971 . Why ?

Help !!

What are the permissions of /home /home/jpd and /home/jpd/Dropbox?

You could try changing them to 755 (rwxr-xr-x)...

thanks for your interesr

permissions for Dropbox are jpd(me):www-data rwxrwx-x

I just delete /usr/bin before zmtest.sh in the 'Execute command on all matches' box of the filter.
And now it works fine. This is a bullshit. why is it so delicate ?

Problem solved

It actually looks like you missed the initial / off the command line path...

Execute command on all matches: usr/bin/zmtest.sh

ERR Command 'usr/bin/zmtest.sh