how use start a ffmpeg via pm2?anyone can help?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
i want use pm2 to run this cmd ffmpeg -i rtsp://XX:XXX@192.168.1.21:554/Streaming/Channels/101?transportmode=unicast -rtsp_transport tcp -f rtsp rtsp://127.0.0.1:554/01 the following is my script:
module.exports = {
apps : [{
name:'ffmpeg',
exec_interpreter:'ffmpeg',
args: '-i rtsp://xxx:xxxx@192.168.2.47:554/Streaming/Channels/101?transportmode=unicast -rtsp_transport tcp -f rtsp rtsp://127.0.0.1:554/01',
watch: 'flase',
autorestart:true,
error_file:'./ffmpeg-err.log',
out_file:'./ffmpeg-out.log',
pid_file:'./ffmpeg-pid.log'
}],
}
and the console give me:
[PM2][WARN] Applications ffmpeg not running, starting...
[PM2][ERROR] Error: No script path - aborting
but i just want to run a cmd not a script, so i dont have an script file.
need help,thx.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue includes a PM2 ecosystem configuration and an ffmpeg command, but names no repository file or test. Start with PM2's command and ecosystem-configuration documentation, then verify how a non-script command is represented; done means the supported usage is clearly documented and avoids the reported "No script path" error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cli
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100