Auto-Restart FFmpeg for Continuous Telugu Church Stream
This guide walks you through setting up a watchdog script that automatically restarts FFmpeg whenever it crashes or stops, ensuring your Telugu church sermon stream stays live without manual intervention. You’ll need a Linux server (or any system with bash and systemd/cron), FFmpeg installed, and your streaming credentials (RTMP URL and stream key) ready.
What You’ll Need
- A Linux server or PC (Ubuntu/Debian recommended) with FFmpeg installed (
sudo apt install ffmpeg). - Your streaming platform’s RTMP URL and stream key (e.g., from YouTube Live, Facebook Live, or a custom RTMP server).
- Basic familiarity with the command line and editing text files.
- Optional: systemd (usually pre-installed) or cron for scheduling.
Step-by-Step
- Create a stable FFmpeg command. First, test your FFmpeg command manually to ensure it works. A typical command for streaming a video file or capture device to an RTMP server looks like:
ffmpeg -re -i /path/to/video.mp4 -c:v libx264 -preset veryfast -b:v 2500k -maxrate 2500k -bufsize 5000k -pix_fmt yuv420p -g 50 -c:a aac -b:a 128k -f flv rtmp://a.rtmp.youtube.com/live2/STREAM_KEY
Replace the input path and RTMP URL/key with your own. Test it for a few minutes to confirm it streams without errors.
- Write the watchdog script. Create a new file, e.g.,
stream_watchdog.sh, using a text editor (nano stream_watchdog.sh). The script will run FFmpeg in a loop, restarting it if it exits. Add the following content:#!/bin/bash while true; do ffmpeg -re -i /path/to/video.mp4 -c:v libx264 -preset veryfast -b:v 2500k -maxrate 2500k -bufsize 5000k -pix_fmt yuv420p -g 50 -c:a aac -b:a 128k -f flv rtmp://a.rtmp.youtube.com/live2/STREAM_KEY echo "FFmpeg exited with code $?. Restarting in 5 seconds..." >> /var/log/stream_watchdog.log sleep 5 done
Replace the ffmpeg command with your own. The
while trueloop ensures it restarts indefinitely. Theecholine logs the exit code and a restart message to a log file. - Make the script executable. Run
chmod +x stream_watchdog.shto give it execute permissions. - Test the script. Run the script in the background with
./stream_watchdog.sh &(the ampersand backgrounds it). Check if the stream goes live. Then, manually kill FFmpeg (e.g.,pkill ffmpeg) and watch the log file (tail -f /var/log/stream_watchdog.log) to see if it restarts after 5 seconds. - Set up auto-start on boot (using systemd). To ensure the stream starts automatically after a reboot, create a systemd service. Create a file
/etc/systemd/system/stream-watchdog.servicewith:[Unit] Description=Telugu Church Stream Watchdog After=network-online.target [Service] ExecStart=/path/to/stream_watchdog.sh Restart=always RestartSec=5 User=yourusername [Install] WantedBy=multi-user.target
Replace
/path/to/stream_watchdog.shandyourusernamewith actual values. Then runsudo systemctl daemon-reload,sudo systemctl enable stream-watchdog, andsudo systemctl start stream-watchdog. - Alternative: Use cron for auto-start. If systemd is not available, add a cron job to start the script on boot. Edit crontab with
crontab -eand add:@reboot /path/to/stream_watchdog.sh &. This will start the script every time the server boots.
Common Mistakes
- Incorrect RTMP URL or stream key. Double-check that you’re using the correct server URL and key from your streaming platform. A typo will cause FFmpeg to exit immediately.
- Forgetting to make the script executable. If you get a “Permission denied” error, you forgot
chmod +x. - Using relative paths in the script. Always use absolute paths for input files and log files, because the script may run from a different working directory when started as a service.
- Not logging errors. Without logging, you won’t know why FFmpeg keeps crashing. Always redirect output to a log file for debugging.
- Starting multiple instances. If you run the script manually and also via systemd, you’ll have two competing streams. Ensure only one instance runs at a time.
Tips
- Use a low-latency encoder preset. For live streaming,
-preset veryfastorultrafastreduces CPU load and latency, which is crucial for a smooth sermon stream. - Add a health check. You can extend the script to check if the stream is actually live by querying the RTMP server’s status, but this is advanced. A simple restart loop is often sufficient.
- Monitor the log file. Set up a cron job to email you if the log shows frequent restarts, indicating a persistent problem.
- Keep the input file accessible. If you’re streaming a video file, ensure the file path is correct and the file is readable by the user running the script.
- Consider using a named pipe for live input. If you’re streaming from a live source (like a camera), use a named pipe to avoid re-encoding issues on restart.
Troubleshooting
If the stream still goes down:
- Check the log file. Look at
/var/log/stream_watchdog.logfor error messages from FFmpeg. Common errors include invalid input, codec issues, or network problems. - Test the FFmpeg command manually. Run the exact command from the script in a terminal to see the error output directly. This often reveals the root cause.
- Verify network connectivity. Ensure the server can reach the RTMP server. Use
pingorcurlto test connectivity. - Check system resources. If the server is low on memory or CPU, FFmpeg may crash. Use
htopto monitor resource usage. - Ensure the service is running. If using systemd, check status with
sudo systemctl status stream-watchdog. If it’s not active, start it manually and look for errors.
Frequently Asked Questions
Will this work with any streaming platform?
Yes, as long as you have the correct RTMP URL and stream key. The script is platform-agnostic.
What if my FFmpeg command has different parameters?
Simply replace the ffmpeg command in the script with your own. The watchdog logic remains the same.
How do I stop the automatic restart?
If running manually, kill the script process (e.g., pkill stream_watchdog.sh). If using systemd, run sudo systemctl stop stream-watchdog.
Can I stream from a live camera instead of a file?
Yes, change the input to your capture device, e.g., -f v4l2 -i /dev/video0 for a webcam on Linux. The restart loop will still work.
What if the stream drops due to network issues?
The script will restart FFmpeg, which will attempt to reconnect to the RTMP server. If the network is down, FFmpeg will keep failing and restarting, but the script will keep trying.
Is there a way to get notified if it keeps crashing?
Yes, you can add a mail command inside the loop after a certain number of restarts, or use a monitoring service like UptimeRobot to check your stream URL.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.