[mythtv-users] What is commflag "exit status 140"?
Michael T. Dean
mtdean at thirdcontact.com
Thu Sep 6 22:14:53 UTC 2012
On 09/06/2012 04:47 PM, Phil Bridges wrote:
> Since upgrading to .25-fixes, my slave backend has decided to error on
> commercial detection. If I look at my backend log, I see:
> 2012-09-06 16:32:26.352429 I [6825/10080] Commflag_6848
> jobqueue.cpp:2276 (DoFlagCommercialsThread) - JobQueue: Commercial
> Detection Starting for "Blah" recorded from channel 1051 at
> 2012-09-06 16:32:26.450483 E [6825/10080] Commflag_6848
> jobqueue.cpp:2362 (DoFlagCommercialsThread) - JobQueue: Commercial
> Detection Errored: "Blah" recorded from channel 1051 at
> 2012-09-06T16:00:00 (Failed with exit status 140)
> Restarting the backend will fix the problem - for a while. What is
> "exit status 140", and how do I fix it?
> I've also noticed that when this happens, the backend stops generating
> the preview image for MythWeb:
> 2012-09-06 16:37:00.095873 E [6825/10083] HttpServer50
> previewgenerator.cpp:254 (Run) - Preview: Encountered problems running
> '/usr/bin/mythpreviewgen --size 100x56 --chanid 1301 --starttime
> 20120906060000 --outfile
> --verbose general --logpath /var/log/mythtv --loglevel info --quiet'
> If I run the command manually, I don't get the error, and the preview
> works fine.
#define GENERIC_EXIT_KILLED 140 ///< Process killed or stopped
which means that something is killing the process. If you're not the one
doing the killing and it keeps happening--especially if it's most common
after the backend has been running for a while--I would guess that
you're getting hit by the OOM killer (the kernel is killing off
processes because you're out of memory and don't have enough swap space).
More information about the mythtv-users