Description
The current version being used is SRS 2.0 with http-flv. After running the command "./objs/srs -c conf/http.flv.live.conf" for a while, it will unexpectedly exit (this situation occurs frequently). There are no relevant logs in the srs.log file.
To compile, use the command "./configure --with-ssl --with-hls --with-ssl --with-nginx --with-http-server --with-http-api --with-http-callback && make".
Configuration file:
listen 1935;
max_connections 1000;
srs_log_tank file;
srs_log_file ./objs/srs.log;
http_server {
enabled on;
listen 8080;
dir ./objs/nginx/html;
}
vhost defaultVhost {
http_remux {
enabled on;
mount [vhost]/[app]/[stream].flv;
hstrs on;
}
}
In the srs.log file, it can be seen that a few minutes ago the streaming was being pushed normally. When the streaming cannot be pushed, it is found that srs has already exited. Checking the srs.log file, there are no relevant logs indicating the exit of srs.
You can try running the command "ulimit -c unlimited" and then running srs. After srs exits, switch to the root directory and execute "find / -name core.*" to check if there is a core file for srs.
Is there any way to determine the cause of the automatic exit?
(It has been tested that when not using http-flv and using the configuration "./configure --with-ssl --with-hls --with-nginx --with-http-callback && make" with the hls.conf configuration to start srs, srs runs very stable and the above problem has not occurred.)
TRANS_BY_GPT3