Nginx-rtmp-module: exec_* directives don't work with Nginx 1.10.0

[hongquan]

I compiled _nginx-rtmp-module_ with Nginx 1.10.0 on Ubuntu 16.04, as deb files.

I'm testing _nginx-rtmp-module_ by streaming my webcam and view with JWPlayer in /test folder.

The problem is that exec, exec_push, exec_pull don't work. I always have to run ffpmpeg separately to feed video to nginx.

This is how I config nginx:

• I add these lines to _/etc/nginx/nginx.conf_

rtmp {
        # error_log /var/log/nginx/rtmp-error.log debug;
        include /etc/nginx/sites-streaming/*;
}

• I create _/etc/nginx/sites-streaming/video_ file with this content: http://hastebin.com/piwegevune.nginx

As you can see, I tried to debug those directives by make them create log file in _/tmp/_ if they are called. But after I restarted Nginx and visited the streaming URL, no file is created.

Nginx's error log gives nothing.

[ThalysonR]

Same problem, no logs. Please help

[levifig]

Same here, no logs (macOS 10.12).

[jeby6372]

same problem with Nginx 1.10.2 on debian 8 / raspbian Jessie

[ghost]

Same with 1.10.3 on Ubuntu Trusty

[sassyn]

same with 1.11.9

[aleohl]

Do we have any idea if this will be solved or is the repo doomed?

[sassyn]

It seems to be working.
I have compile it again, and using a bash script instead of putting the command in the nginx configuration.

Put something like exec_static/ exec_pull/ exec_push and call to the bash script.
ex:

exec_pull /tmp/test.sh

in test.sh put

touch /tmp/simpletest

This should be working just fine.

[romainlq]

hi, same with Nginx 1.12.0 even with a bash script

[MrLiuzhu]

@all
in nginx.conf, please config root to run this file,ex:
`user root;
worker_processes 1;

error_log logs/error.log;

error_log logs/error.log notice;

error_log logs/error.log info;

error_log logs/error.log debug;`

maybe exec need root to run

[levifig]

@MrLiuzhu Well, that is for sure not happening. I certainly hope you're not responsible for production servers…

[crlshn]

thanks matte... user matters... root no way jos'e .. but create user and add privileges... no brainier.

[mkrn]

Had the same issue. renaming exec => exec_push in nginx.conf helped. Works in nginx 1.15.1