Hello,
So I've had this audio monitor to listen in on the baby room. It's a pogoplug with a USB webcam attached to it, and uses ffmpeg to stream the audio from the USB webcam to another Pogoplug which runs ffmpeg to play the audio. It works great most of the time. Out of a few days, I get a couple of times when ffmpeg stops running for some reason. I kind of bandaid the issue by creating a cron job to do "systemctl stop babymonitor.service" and then "systemctl start babymonitor.service" every hour. It works ok, but sometimes one of them crashes and it stops working until the next time the cron job runs at the top of the hour.
Is there a better way to do this? Can I have a cron job run every 2 minutes and look to see whether or not the ffmpeg process is running?
Here's the "systemctl status" output when things stop working. I don't know if this help anyone?
baby monitor in the baby room:
$this->bbcode_second_pass_quote('', '
')[root@alarm ~]# systemctl status baby.service
baby.service - baby monitor
Loaded: loaded (/etc/systemd/system/baby.service; enabled)
Active: failed (Result: exit-code) since Sat 2014-01-18 05:17:43 CST; 23min ago
Process: 5252 ExecStart=/usr/bin/ffmpeg -re -f alsa -i plughw:0 -acodec mp2 -ab 128000 -ar 48000 -ac 1 -filter bandpass=f=600:csg=0:width_type=q:w=.806 -f rtp rtp://224.1.2.3:1234 (code=exited, status=1/FAILURE)
Main PID: 5252 (code=exited, status=1/FAILURE)
[solved] ways to keep program running
5 posts
• Page 1 of 1
[solved] ways to keep program running
by permitivity » Sat Jan 18, 2014 11:45 pm
Here's the speaker portion:
$this->bbcode_second_pass_quote('', '
')[root@alarm ~]# systemctl status parent.service
parent.service - baby monitor
Loaded: loaded (/etc/systemd/system/parent.service; enabled)
Active: inactive (dead) since Sat 2014-01-18 05:17:53 CST; 14min ago
Process: 29259 ExecStart=/usr/bin/ffmpeg -i rtp://224.1.2.3:1234 -f alsa plughw:1 (code=exited, status=0/SUCCESS)
Process: 29256 ExecStartPre=/bin/sleep 45 (code=exited, status=0/SUCCESS)
Main PID: 29259 (code=exited, status=0/SUCCESS)
You can see how I'm forming the ffmpeg command on the baby portion as well as the parent portion of the service. If I'm doing something wrong, please let me know. Ideally, I'd like to find the root cause of these crashes, but it also makes me feel better if there's a better cron job that more frequently looks to see if the monitors are working. My current method is kind of blunt - just stopping and starting the services every hour.
Last edited by permitivity on Thu Jan 23, 2014 6:27 am, edited 1 time in total.
- permitivity
- Posts: 141
- Joined: Mon Feb 18, 2013 3:08 am