You could try enabling core dumps ("ulimit -c unlimited") and rerunning
rdairplay. The next time it crashes, it will leave a core dump that can be
examined with gdb (e.g. gdb /usr/bin/rdairplay core). You can then use
gdb's bt (backtrace) command to see what rdairplay was doing when it
crashed.

I seem to recall there being something funky with invalid timestamps that
would make qt complain...

On Tue, Jan 5, 2016 at 11:13 AM, Jim Stewart <jstew...@paceaudio.com> wrote:

> I've had this problem since the beginning.  Can't remember if I get the
> exact GP fault error or not.
>
> In my case it crashes about half the time, but in spurts as in it will do
> it 3 or 4 nights in a row, then clear up for a few days, then do it again.
> I haven't determined a pattern to it.
>
> Years ago I configured a silence sense on it so it simply restarts
> rdairplay (and starts it playing) once silence is detected.  Since ripcd
> keeps running, I can do all this with rml commands.  On our main on-air
> machine that has a BT ACS8.2 audio switcher, I use its silence sense to
> trigger the "fix it" macro.
>
> On our backup machine (that lacks the switcher) I use the Jack Audio
> "Silent_Jack" program.  Both work perfectly, typically leaving about 15
> seconds of dead air as opposed to about 5 seconds of dead air normally when
> rdairplay doesn't crash but is simply is being sluggish chaining logs.
>
> Both machines use the same database (or at least snapshots of it), so I'm
> guessing the problem originates from there.  Both machines use Debian Linux
> but typically are on completely different versions, our on-air machine is
> on a fairly old version using the "If it ain't broke, don't fix it"
> concept.  The backup is typically the current Debian version.  So maybe it
> could also be something in Debian that has continued through 3 major
> versions of Debian.
>
> Date: Tue, 5 Jan 2016 06:19:38 -0600
> From: Tim Camp <t...@dotcom1.net>
> To: User discussion about the Rivendell Radio Automation System
>         <rivendell-dev@lists.rivendellaudio.org>
> Subject: [RDD] Rdairplay Crash at midnight after log chain
> Message-ID:
>         <
> cads6wcbbouawtbehvgqwtpkek4ydfew57khfn99_hwq+42m...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Greetings,
>
> The following is the syslog from last night when RdAirplay crashed after
> log load.
>
> Trying to figure out the problem...
>
> Jan  4 23:59:04 zewcon rdairplay: loaded log 'zew0105' in Main Log
> Jan  4 23:59:04 zewcon kernel: [6687443.252425] traps: rdairplay[8606]
> general protection ip:7f127fef45c6 sp:7ffffa10e2d8 error:0 in
> libqt-mt.so.3.3.8[7f127f984000+75b000]
> Jan  4 23:59:09 zewcon caed: alsaStopTimerData(1)
> Jan  4 23:59:25 zewcon caed: alsaStopTimerData(0)
> Jan  5 00:14:48 zewcon ripcd: ran local maintenance routines
> Jan  5 00:17:01 zewcon CRON[6121]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Jan  5 01:00:32 zewcon ripcd: ran local maintenance routines
> Jan  5 01:17:01 zewcon CRON[6313]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Jan  5 01:46:15 zewcon ripcd: ran local maintenance routines
> Jan  5 02:17:01 zewcon CRON[6504]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Jan  5 02:31:59 zewcon ripcd: ran local maintenance routines
> Jan  5 03:17:01 zewcon CRON[6698]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Jan  5 03:17:43 zewcon ripcd: ran local maintenance routines
> Jan  5 04:03:26 zewcon ripcd: ran local maintenance routines
> Jan  5 04:17:01 zewcon CRON[6966]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Jan  5 04:49:10 zewcon ripcd: ran local maintenance routines
> Jan  5 05:17:01 zewcon CRON[7175]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Jan  5 05:34:54 zewcon ripcd: ran local maintenance routines
>
>
> Cheers
>
> Tim Camp
> WZEW-FM
> Mobile, AL.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://caspian.paravelsystems.com/pipermail/rivendell-dev/attachments/20160105/8302e683/attachment-0001.html
> >
>
> ------------------------------
>
> _______________________________________________
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
>
> End of Rivendell-dev Digest, Vol 33, Issue 3
> ********************************************
> _______________________________________________
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
>
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to