On 16/09/13 07:42, Warren Mead wrote:
> Sep 16 06:24:58 playout-desktop caed: FadeLevel: -42
> Sep 16 06:24:59 playout-desktop caed: FadeLevel: -84
> Sep 16 06:24:59 playout-desktop caed: FadeLevel: -126
> Sep 16 06:24:59 playout-desktop caed: FadeLevel: -168
> Sep 16 06:24:59 playout-desktop caed: FadeLevel: -210
> Sep 16 06:24:59 playout-desktop kernel: [3003854.320272] __ratelimit: 34
> callbacks suppressed
> Sep 16 06:24:59 playout-desktop kernel: [3003854.320276]
> rdairplay[2448]: segfault at e0 ip 001f46f7 sp bf9b84dc error 4 in
> librd-1.7.1.so[110000+25b000]
Hi Warren,
I suspect there isn't enough there to be useful. One tip I found which
may help. I run rdairplay inside a screen process and inside a while
loop logging to a file. That way if rdairplay crashes the output of the
command/crash is logged and it automatically restarts with todays log
and lets automation or the presenter carry on.
The script is as simple as:
#!/bin/bash
while [ /bin/true ]; do
echo "starting `date`"
echo "START: `date`" >> /home/logs/airplay.log
/usr/bin/rdairplay --log1=`date +%Y_%m_%d`:+ >> /home/logs/airplay.log
2>&1
echo "END: `date`" >> /home/logs/airplay.log
DATEID=`date`
ALERT=`echo -e "\nAlert: WARNING $DATEIS\nrdairplay
restarting\n\n\n\nGoodbye" | mail -s "rdairplay restarted" [email protected]`
echo "RESTARTING `date`"
sleep 5
done
So that script keeps a log of output from rdairplay (i.e. crash data)
and also emails me when it happens.
Hope that helps for future.
--
Andy
e: andy @ thebmwz3.co.uk
w: http://www.thebmwz3.co.uk
g: https://github.com/andyb2000/
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
