[mythtv-users] No EIT data for a channel - "Error: offset>181, pes length & current cannot be queried"

Martin Moores moores.martin at gmail.com
Tue Oct 30 15:40:25 UTC 2012


On 30 October 2012 12:03, Michael T. Dean <mtdean at thirdcontact.com> wrote:

> On 10/30/2012 03:35 AM, Martin Moores wrote:
>
>> Many thanks for that, good to know and thanks for the code!
>>
>> So EIT is now off for all the bad hidden channels, still popping up in
>> the logs (made the changes last night and there was some in the logs at 5am
>> this morning), so must still have a rouge channel.  Will keep looking
>> through them and hopefully find the culprit
>>
>>
> You probably need to restart--as you would have if you set the options in
> mythtv-setup, versus poking data directly into the database.
>
> Mike
>


Thanks Mike, tried a reboot of the backend, seeing the same results at the
moment though.

Starting the think my upgrade to 0.26 didn't go as smoothly as I thought,
as I do have a few issues, which I am not sure if they are database related?

This seems to happen quite frequently, but doesn't effect anything obvious

*Oct 30 12:40:28 MYTHTV1 mythlogserver: mythbackend[15812]: E
ProcessRequest mythsocket.cpp:344 (writeStringList) MythSocket(9d65e90:-1):
writeStringList: Error, socket went unconnected.#012#011#011#011We wrote 0
of 10 bytes with 1 errors#012#011#011#011starts with: 2       OK *

This is quite random, happened in the middle of some recordings before, so
they all restarted.  Have checked the IP in mythtv-setup.  There is the
ongoing thread regarding peoples issues with exiting mythtv-setup, maybe
related

*Oct 30 12:28:20 MYTHTV1 mythlogserver: mythbackend[15405]: E TVRecEvent
mythcorecontext.cpp:299 (ConnectToMasterServer) ERROR: Master backend tried
to connect back to itself!*

I see this when the backend starts, but all tuners work fine, so not sure
what the issue is

*Oct 30 12:07:05 MYTHTV1 mythlogserver: mythbackend[15405]: W CoreContext
dvbchannel.cpp:227 (Open) DVBChan(1:/dev/dvb/adapter0/frontend0): Opening
DVB frontend device failed.#012#011#011#011eno: Device or resource busy (16)
Oct 30 12:07:05  mythlogserver: last message repeated 16 times
Oct 30 12:07:05 MYTHTV1 mythlogserver: mythbackend[15405]: E CoreContext
dvbchannel.cpp:232 (Open) DVBChan(1:/dev/dvb/adapter0/frontend0): Failed to
open DVB frontend device due to fatal error or too many attempts.
Oct 30 12:07:05 MYTHTV1 mythlogserver: mythbackend[15405]: E CoreContext
channelbase.cpp:1227 (CreateChannel) ChannelBase: CreateChannel() Error:
Failed to open device /dev/dvb/adapter0/frontend0
Oct 30 12:07:05 MYTHTV1 mythlogserver: mythbackend[15405]: E CoreContext
main_helpers.cpp:199 (setupTVs) Problem with capture cardsCard 1failed init*

This happens during recordings sometimes and causes skips in the recording
and some glitching.  Am still experimenting with the possibility that this
is signal related?

*Oct 30 08:05:04 MYTHTV1 mythlogserver: mythbackend[6649]: W TFWWrite
ThreadedFileWriter.cpp:500 (DiskLoop)
TFW(/var/lib/mythtv/recordings/1001_20121030055500.mpg:84): write(58092)
cnt 18 total 995084 -- took a long time, 1868 ms*

Maybe all unrelated, if I get a long gap in recordings, I might try going
back to my pre-0.26 database for a bit, see what happens, I should be able
to get back to 0.26 easy enough I guess!

Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20121030/485e98b8/attachment.html>


More information about the mythtv-users mailing list