<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/29/2013 08:42 PM, Raymond Wagner
wrote:<br>
</div>
<blockquote cite="mid:5248F331.8080809@wagnerrp.com" type="cite">On
9/29/2013 3:58 PM, Raymond Wagner wrote:
<br>
<blockquote type="cite">On 9/29/2013 3:32 PM, Bill Meek wrote:
<br>
<blockquote type="cite">On 09/29/2013 02:13 PM, Raymond Wagner
wrote:
<br>
<blockquote type="cite">On 9/29/2013 3:10 PM, Bill Meek wrote:
<br>
<blockquote type="cite">The backend runs it (by the
housekeeper,) In my logs,
<br>
3 seconds after the BE starts.
<br>
</blockquote>
<br>
If that's too soon, it would be fairly trivial to have the
housekeeper
<br>
delay operation by a few minutes. Additionally, now that it
is being run
<br>
by the housekeeper rather than on frontend startup, it will
eventually
<br>
retry. If I remember correctly, it will attempt once a day
until
<br>
successful, and then wait a month before attempting again.
<br>
</blockquote>
<br>
I'm one of those who's BE shuts down if it's not doing
anything.
<br>
<br>
Even if I run the command manually as the mythtv user:
<br>
<br>
/usr/local/share/mythtv/hardwareprofile/sendProfile.py
--submitOnly -a
<br>
<br>
and: echo $? returns 0.
<br>
<br>
I <assumed> that would reset the 30 day counter, but the
BE still
<br>
tries to run it (and fails) when I restarted it.
<br>
<br>
I'd be glad to test an x minute delay.
<br>
<br>
</blockquote>
<br>
Looking deeper, it seems I configured the hardware profiler to
run
<br>
immediately on startup regardless, and bypassing that to add a
delay
<br>
would be pretty clumsy to implement without an ABI change. There
is also
<br>
no differentiation between a successful and a failed run. It
will always
<br>
take the full 30 day delay.
<br>
<br>
Both of which wouldn't be difficult to implement, just difficult
to fix
<br>
in 0.27. I'll have to think about this a bit more.
<br>
</blockquote>
<br>
This should cause a retry five minutes after startup (of frontend
or backend) if the initial submission failed, although I've not
even tested compiling it, so use at your own risk.
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
</pre>
</blockquote>
Is this likely to fix the crash (not just a failure, a crash) that I
have been getting that tries to initiate a bug report?<br>
</body>
</html>