[mythtv-users] Suddenly 0byte recordings (James Linder)
James Linder
jam at tigger.ws
Fri Mar 6 01:18:39 UTC 2015
> On 5 Mar 2015, at 8:00 pm, mythtv-users-request at mythtv.org wrote:
>
> Send mythtv-users mailing list submissions to
> mythtv-users at mythtv.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> or, via email, send a message with subject or body 'help' to
> mythtv-users-request at mythtv.org
>
> You can reach the person managing the list at
> mythtv-users-owner at mythtv.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mythtv-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Suddenly 0byte recordings (James Linder)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 4 Mar 2015 21:25:03 +0800
> From: James Linder <jam at tigger.ws>
> To: mythtv-users at mythtv.org
> Subject: Re: [mythtv-users] Suddenly 0byte recordings
> Message-ID: <51EBB3E4-F96F-4516-B788-78EEA898212C at tigger.ws>
> Content-Type: text/plain; charset=us-ascii
>
>
>> On 4 Mar 2015, at 8:00 pm, mythtv-users-request at mythtv.org wrote:
>>
>>> Over ages I???ve occasionally had 0 byte recordings, suddenly I???m getting a truckload.
>>>
>>> I???ve a haupuge USB dual card. I replugged it - no change
>>> During a zero byte recording I stop mythbackend then start it - normal recording
>>>
>>> The log shows:
>>> 2015-03-03 18:37:00.812140 I [13786/13786] CoreContext scheduler.cpp:705 (UpdateRecStatus) - Updatin
>>> g status for Mythbusters on cardid 1 (Tuning => Recorder Failed)
>>> 2015-03-03 18:37:00.925860 I [13786/13836] Scheduler scheduler.cpp:2140 (HandleReschedule) - Resched
>>> ule requested for CHECK -9 7 0 UpdateRecStatus2 | Mythbusters | | Can a ninja slap a bullet out of
>>> the air? Can drivers who hold the steering wheel in the 10-2 position, have their thumbs ripped off
>>> by an airbag? Can an RFID tag explode if placed inside an MRI? |
>>>
>>> I would think ???OK the dongle is broken??? except other channels *do* record and restarting backend ???fixes??? the issue.
>>> I???m using
>>> fixes/0.27 [v0.27.4-27-g40506c2]
>>> which I???ve been using since it came out.
>>>
>>> Can anyone suggest where I might look?
>>>
>>> top - 10:28:45 up 20 days, 20:16, 5 users, load average: 1.00, 1.01, 1.05
>>> Tasks: 208 total, 1 running, 207 sleeping, 0 stopped, 0 zombie
>>> %Cpu(s): 0.2 us, 0.1 sy, 0.0 ni, 99.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
>>> KiB Mem: 3980628 total, 3837272 used, 143356 free, 85952 buffers
>>> KiB Swap: 4193276 total, 393096 used, 3800180 free. 2800716 cached Mem
>>>
>>> [poohcorner] /store/mythlogs [331]% who
>>> jam :0 2015-02-11 14:12 (console)
>>> jam pts/0 2015-02-24 18:28 (:0.0)
>>> jam pts/1 2015-03-03 21:55 (haycorn.home)
>>> jam pts/2 2015-02-24 18:56 (:0.0)
>>> jam pts/3 2015-03-04 10:15 (haycorn.home)
>>>
>>> [poohcorner] /store/mythlogs [332]% df
>>> Filesystem 1K-blocks Used Available Use% Mounted on
>>> /dev/sda2 20510716 7515816 11929944 39% /
>>> devtmpfs 1982424 8 1982416 1% /dev
>>> tmpfs 1990312 0 1990312 0% /dev/shm
>>> tmpfs 1990312 2272 1988040 1% /run
>>> tmpfs 1990312 0 1990312 0% /sys/fs/cgroup
>>> /dev/sda1 103202 4848 98354 5% /boot/efi
>>> /dev/sda6 909101360 577598164 331503196 64% /store
>>> /dev/sda3 20510716 44992 19400768 1% /other
>>> /dev/sda4 20510716 4513288 14932472 24% /home
>>>
>>> Nothing looks dreadfully amiss
>>>
>> If "other channels" - by which I assume you mean using the same device - record
>> successfully, then it looks as if that channel has moved. Try rescanning.
>
> Hika thanks, but a 3 month old dongle in a 3 month old NUC means power supply issues are possible, but not likely.
> Mike the fact that stop then start fixes the issue for hours or 10s hours says channel moved is not an issue.
> Definitly *something* is wrong so I wont discount any suggestion.
> Is any of the debug logging likely to show anything?
One of the obvious suggestions was antenna cable quality:
Year Old F-Type cable to the wall, F-Type from wall to the splitter for the dongle (hauppague accessory)
It is clear I’m dealing with more than 1 issue. Up to now restarting mythbackend without restarting the dongle reset all woes. Here it does not happen. Methinks I’ll get a different dongle and try that.
===============
Card #1 records
===============
2015-03-05 17:00:04.509949 I [30216/30216] CoreContext scheduler.cpp:705 (UpdateRecStatus) - Updating status for
"Ten Eyewitness News First at Five" on cardid 1 (Tuning => Recording)
=============
Card #3 Fails
=============
2015-03-05 18:31:50.700886 I [30216/30216] CoreContext scheduler.cpp:705 (UpdateRecStatus) - Updating status for Mythbusters on cardid 3 (Tuning => Recorder Failed)
==========================
Subsequent Card #1 records
==========================
2015-03-05 19:30:02.438659 I [30216/30216] CoreContext scheduler.cpp:705 (UpdateRecStatus) - Updating status for "Gourmet Farmer Afloat" on cardid 1 (Tuning => Recording)
========================
Subsequent Card #3 fails
========================
2015-03-05 21:03:51.930028 I [30216/30216] CoreContext scheduler.cpp:705 (UpdateRecStatus) - Updating status for "I'm A Celebrity...Get Me Out Of Here!" on cardid 3 (Tuning => Recorder Failed)
*************** Restart backend which usually fixes everything
===============
Card #1 records
===============
2015-03-05 22:25:01.696139 I [6897/6897] CoreContext scheduler.cpp:705 (UpdateRecStatus) - Updating status for "SBS World News" on cardid 1 (Tuning => Recording)
===============
Card #3 FAILS
===============
2015-03-05 23:04:04.569950 I [6897/6897] CoreContext scheduler.cpp:705 (UpdateRecStatus) - Updating status for "Law & Order: S.V.U ." on cardid 3 (Tuning => Recorder Failed)
I think an antenna that is iffy and a dongle that accepts software reset sometimes and sometimes needs a hardware reset create the confusion I been posting. The list and suggestions have been helpful thanks
James
More information about the mythtv-users
mailing list