<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/03/2015 02:46 PM, Ian Evans
wrote:<br>
</div>
<blockquote
cite="mid:CABiY0=ir+rfc8V+XrtUGjwueXVQyF=gRU-drsS3Q56oWgcnCTQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Sat, Jan 3, 2015 at 2:02 PM, Hika
van den Hoven <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:hikavdh@gmail.com" target="_blank">hikavdh@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hoi Ian,<br>
<span><br>
Saturday, January 3, 2015, 7:20:32 PM, you wrote:<br>
<br>
> A real head scratcher though. Had three recordings
from PBS fail<br>
> this morning. All about 4-5 minutes, 440mb into the
recording. If it<br>
> was a flaky power adapter, I wonder if its
flakiness would be so precise. :-)<br>
<br>
</span>Them all failing after about the same time could
suggest that<br>
somewhere on the way a buffer is filling up. Network, disk
or<br>
somewhere else.<br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">Ok...at least I have somewhere else to
potentially look now. Haven't changed a thing except for
regular updates to MythTV 27-fixes.<br>
<br>
</div>
<div class="gmail_extra">I'm not seeing any other warnings
before the fails, except for "(SetStrOption)
RecBase[1](10305A8C-0): SetStrOption(...recordingtype): Option
not in profile." if that's even an error. So I'm not seeing
Myth report any problems besides the unavailable. Any non-myth
logs I should look at?<br>
<br>
Dec 30 23:30:00 buster mythbackend: mythbackend[29647]: I
Scheduler scheduler.cpp:2689 (HandleRecordingStatusChange)
Tuning recording: Nature:"The Himalayas": channel 1172 on
cardid 1, sourceid 1<br>
Dec 30 23:30:00 buster mythbackend: mythbackend[29647]: I
Scheduler scheduler.cpp:2139 (HandleReschedule) Reschedule
requested for PLACE PrepareToRecord<br>
Dec 30 23:30:01 buster mythbackend: mythbackend[29647]: I
TVRecEvent tv_rec.cpp:4130 (TuningNewRecorder) TVRec[1]:
rec->GetPathname():
'/xmas2tb/recordings/1172_20141231043000.mpg'<br>
Dec 30 23:30:01 buster mythbackend: mythbackend[29647]: E
TVRecEvent recorders/recorderbase.cpp:206 (SetStrOption)
RecBase[1](10305A8C-0): SetStrOption(...recordingtype): Option
not in profile.<br>
Dec 30 23:30:02 buster mythbackend: mythbackend[29647]: I
Scheduler scheduler.cpp:2252 (HandleReschedule) Scheduled 285
items in 0.6 = 0.00 match + 0.00 check + 0.61 place<br>
Dec 30 23:30:02 buster mythbackend: mythbackend[29647]: I
CoreContext scheduler.cpp:704 (UpdateRecStatus) Updating
status for Nature:"The Himalayas" on cardid 1 (Tuning =>
Recording)<br>
Dec 30 23:31:41 buster mythbackend: mythbackend[29647]: E
HDHRStreamHandler recorders/hdhrstreamhandler.cpp:419
(TunerSet) HDHRSH(10305A8C-1): Set request
failed#012#011#011#011eno: Resource temporarily unavailable
(11)<br>
Dec 30 23:31:41 buster mythbackend: mythbackend[29647]: E
HDHRStreamHandler recorders/hdhrstreamhandler.cpp:419
(TunerSet) HDHRSH(10305A8C-0): Set request
failed#012#011#011#011eno: Resource temporarily unavailable
(11)<br>
<br>
</div>
<div class="gmail_extra">Thanks!<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
I looked at my logs from when my Homerun Prime failed, and I see the
same message. See log below from a failed recording. The cause at
that time was the infamous "System: reset reason = watchdog". The
homerun prime was completely unresponsive to the config tool or the
web interface for several minutes, and reset itself after some time.
Are you sure the homerun does not have a web interface? I believe
they have some wort of web interface, and it may include a log. Try
entering <a class="moz-txt-link-freetext" href="http://999.999.999.999">http://999.999.999.999</a> on a browser where that is the ip
address of the homerun. <br>
<br>
The problem I had that caused these errors was never resolved, even
after replacing the homerun prime under warranty. The silicon dust
support could not figure out what was wrong. I am no longer using
the homerun prime and have replaced it with a Ceton Infinitv that is
working fine. I am interested in whether others have the same
issues.<br>
<br>
Sep 24 20:59:45 serenity mythbackend: mythbackend[2751]: I
TVRecEvent tv_rec.cpp:1050 (HandleStateChange) TVRec[8]: Changing
from None to RecordingOnly<br>
Sep 24 20:59:45 serenity mythbackend: mythbackend[2751]: I
TVRecEvent tv_rec.cpp:3603 (TuningCheckForHWChange) TVRec[8]: HW
Tuner: 8->8<br>
Sep 24 20:59:47 serenity mythbackend: mythbackend[2751]: E
TVRecEvent recorders/hdhrstreamhandler.cpp:419 (TunerSet)
HDHRSH(13199370-0): Set request failed#012#011#011#011eno: Resource
temporarily unavailable (11)<br>
Sep 24 20:59:47 serenity mythbackend: mythbackend[2751]: E
TVRecEvent tv_rec.cpp:3793 (TuningFrequency) TVRec[8]: Failed to set
channel to 705. Reverting to kState_None<br>
Sep 24 20:59:47 serenity mythbackend: mythbackend[2751]: I
TVRecEvent tv_rec.cpp:1050 (HandleStateChange) TVRec[8]: Changing
from RecordingOnly to None<br>
Sep 24 20:59:47 serenity mythbackend: mythbackend[2751]: I
CoreContext scheduler.cpp:704 (UpdateRecStatus) Updating status for
"Modern Family":"The Long Honeymoon" on cardid 8 (Will Record =>
Recorder Failed)<br>
Sep 24 20:59:48 serenity mythbackend: mythbackend[2751]: E
TVRecEvent recorders/hdhrstreamhandler.cpp:380 (TunerGet)
HDHRSH(13199370-0): Get request failed#012#011#011#011eno: Resource
temporarily unavailable (11)<br>
Sep 24 20:59:48 serenity mythbackend: mythbackend[2751]: E
TVRecEvent recorders/hdhrstreamhandler.cpp:419 (TunerSet) Changing
from None to RecordingOnly<br>
<br>
Peter<br>
</body>
</html>