EEPG freesat S28E2 funktioniert nicht mit Fehlermeldung: EEPG: Missing table 2 entry

  • Hi, ich bin nach mehr als einem Jahr Abstinenz mal wieder auf S28E und zwar mit einem aktualisierten Setup aus VDR 2.4.0 mit allen Patches hier aus dem Forum und der git-Version vom EEPG-Plugin. Leider funktioniert der 7-Tage-EPG nicht und das Log-File ist voll mit diesen Fehlermeldungen:

    Gibt es irgendein Fix für das Problem?


    Das vollständige Log-File ist angehängt: eepg_missing_table.txt

  • Leider scheint eepg ungepflegt zu sein.


    Ich habe versucht das Plugin bei einem Bekannten zu nutzen und mit aktivem eepg regelmäßig VDR-Crashes gehabt.


    Erstmal habe ich mich damit abgefunden, dass es für die "Englischen" im VDR kein EPG gibt.


    Läuft das Plugin denn bei dir (von den Fehlermeldungen abgesehen) stabil?

  • Also unter vdr 2.2.0 läuft das Plugin stabil.

    Gen2VDR V4 mit VDR 2.0.4 & XBMC 12.2 - Gigabyte MA785GT-UD3H - AMD Athlon II X2 240e - 4 Gb RAM - Ausgabe via MSI N220GT-MD1GZ mit softhddevice & vdpau - 19.2E & 28.2E Empfang via Linux4Media L4M-Twin S2 ver 6.5 - Intel X25-M 80 GB - 3 x Hitachi Deskstar 7K4000 - Medion X10 RF Remote Control 20016398


    LinVDR Mahlzeit-ISO 4.0beta2 - Fujitsu Siemens Computers D1188 - Intel Pentium III EB 1000 Mhz - 256 Mb RAM - Ausgabe via Hauppauge WinTV Nexus-s Rev 2.2 - 19.2E & 28.2E Empfang via TT-Budget - Seagate 7200.10 IDE 750 Gb - PSone-Display - Medion X10 RF Remote Control 20016398

  • Ich habe immer unter 2.4.0 getestet.


    Kann schon sein, dass da irgendwas mit "Locking Order" noch nicht ganz sauber ist.


    Genutzt habe ich auch die letzte GIT-Version.


    Der VDR hat sich immer nach unregelmäßiger Zeit einfach verabschiedet (wenn ich mich richtig erinnere mit "Emergency Exit").

  • Hi,


    habe eben mit vdr-2.4.1 und vdr-plugin-eepg-experimental.tar.bz2

    getestest --> geht



    Gruss

  • Die Crashes waren immer erst nach etwas Laufzeit.

    Ich benutze eine ältere GIT-Version (Dez.2018).
    Da habe ich den "Emergency Exit" so gut wie immer täglich nachts (01 - 05 Uhr)
    Ich dachte das hätte was mit dem "Befüllen" zu tun und achte halt drauf,
    das ich in der Zeit möglichst wenig aufnehme.

    bin ehrlich gesagt nicht auf die Idee gekommen, das es das Plugin selber ist :whatever

    Gruß, jo01

  • Hi,


    I provide a solution in the vdr-2.4.0-eepg-lock.patch attached to this bug report. I use it with VDR 2.4.0 and have no further crashes. The patch thus disables some of the repeated logging.


    https://projects.vdr-developer.org/issues/2586


    The 7-day channel data is up-to-date. VDR to crash with "video data stream broken", presumably due to its being a data stream only nowadays. Forced tuning to the channel for 30 minutes - 1 hour is sufficient.


    I have forked the plugin on github and applied the patches there: https://github.com/nickb937/vdr-plugin-eepg

  • Nice information. I'll definitively try that!


    At least in theory you should be able to get commit access to the repository if the original author does not longer want to maintain the plugin.


    Best way would be if you try to contact the original author about that.


    But forking to github would be OK, too.


    What do you mean with this "7-day" thing? So it is not enough to just have the plugin active and configure VDR to do its regular EPG scan?

  • I thought as a first step, I'd file the bug report and let the author commit the change. I wasn't originally planning to do any more than that until I saw this forum post, then I have been additionally thinking about committing the Genres patch https://projects.vdr-developer.org/issues/1908 and doing some cleanup.


    As for the 7-day EPG issue. The problem is that the EPG data is provided in chunks every 2 (i think) minutes. To get the full EPG you have to listen to the channel for 30 minutes. VDR does not stay tuned to the EEPG plugin to recover all the data, so the EPG contains the now-and-next info only.


    A related discussion I had with the author on similar lines is here, where he suggests that you have to explicitly tune to the channel to get the data: https://projects.vdr-developer.org/issues/1634. I felt that recording the channel was a sufficient hack but maybe now I need to do an explicit tune request on a cron-job to achieve the same effect:



    #!/bin/bash

    # 162 is EPG Background channel in my channels.conf

    $ echo "CHAN 162" >/dev/tcp/<server>/6419


  • Thanks for your answers!


    With VDR 2.4.1 and cheesemonster's current git, the syslog flooding with "missing table entry" stopped.

    However, after tuning for several hours to a BBC transponder, epg is still not working properly (see "Kein Titel" entries in the screenshot below).


    The rotor is not good aligned, so that my next step is to align it better to simply rule out reception problems.

    [IMG:http://schuld.org/BBC_EEPG_KEIN_TITLE.png]

  • To fetch the full EPG, the channel I tune to is:


    EPG Background Audio.;BSkyB:11778:VC23M2S0:S28.2E:27500:0:648=@4:0:0:4152:2:2004:0


    I have used TVheadend in the past and know that it does not need to tune to this channel for long periods of time to get the schedules. I'd like to spend some time figuring out why and see if EEPG can be improved in this respect.

  • When I tune to EPG Background Audio.;BSkyB:11778:VC23M2S0:S28.2E:27500:0:648=@4:0:0:4152:2:2004:0 I get the following error message after a couple a minutes:

    Written 0 titles and 0 summaries does not look so good, does it?

    Does it make sense to patch MAX_TITLES to a higher value?

  • Absolutely fantastic that this plugin in being worked on again! Thank you very much for that!


    I just wanted to let you guys know that the channel carrying the EPG data "EPG Background Audio." is being marked as OBSOLETE since some time now which made me delete it. That was a mistake however since despite being marked as OBSOLETE it still carries the EPG data and there seems to be no substitute channel for it. I've had VDR always configured so that the EPG channel is the channel which is being tuned to on bootup, which makes sure that all the EPG-data can be fetched. It would be awesome of course if manually tuning or setting the EPG channel as the startup channel wouldn't be necessary anymore.


    Btw I wrote in June that the plugin is stable but I also have some random VDR restarts, so I suspect I was a bit premature when writing that. I see absolutely no pattern in the VDR restarts however.

    Gen2VDR V4 mit VDR 2.0.4 & XBMC 12.2 - Gigabyte MA785GT-UD3H - AMD Athlon II X2 240e - 4 Gb RAM - Ausgabe via MSI N220GT-MD1GZ mit softhddevice & vdpau - 19.2E & 28.2E Empfang via Linux4Media L4M-Twin S2 ver 6.5 - Intel X25-M 80 GB - 3 x Hitachi Deskstar 7K4000 - Medion X10 RF Remote Control 20016398


    LinVDR Mahlzeit-ISO 4.0beta2 - Fujitsu Siemens Computers D1188 - Intel Pentium III EB 1000 Mhz - 256 Mb RAM - Ausgabe via Hauppauge WinTV Nexus-s Rev 2.2 - 19.2E & 28.2E Empfang via TT-Budget - Seagate 7200.10 IDE 750 Gb - PSone-Display - Medion X10 RF Remote Control 20016398

  • Now, I've got this invalid lock sequence. Any hints?

  • ; BSkyB: 11778: VC23M2S0: S28.2E: 27500: 0: 648 = @ 4: 0: 0: 4152: 2: 2004: 0 I get the following error message after a couple of minutes :

    Written 0 titles and 0 summaries does not look so good, does it?

    Does it make sense to patch? MAX_TITLES to a higher value?


    The number of titles seems significantly higher than anything I've seen, though I have a similar number of channels and summaries.



    [root @ tv ~] # journalctl --unit = vdr.service --since = "30 minutes ago" | egrep -e 'found [0-9] * titles'

    Oct 11 21:07:38 tv.house vdr [616513]: [616536] EEPG: found 21508 titles

    Oct 11 21:07:57 tv.house vdr [616513]: [616536] EEPG: found 20225 titles

    Oct 11 21:08:17 tv.house vdr [616513]: [616536] EEPG: found 21668 titles

    Oct 11 21:08:38 tv.house vdr [616513]: [616536] EEPG: found 22084 titles

    Oct 11 21:08:59 tv.house vdr [616513]: [616536] EEPG: found 22140 titles

    Oct 11 21:09:19 tv.house vdr [616513]: [616536] EEPG: found 22097 titles

    Oct 11 21:09:39 tv.house vdr [616513]: [616536] EEPG: found 21662 titles

    Oct 11 21:09:52 tv.house vdr [616513]: [616536] EEPG: found 5450 titles

    Oct 11 21:09:52 tv.house vdr [616513]: [616536] EEPG: found 0 titles

    [root @ tv ~] # journalctl --unit = vdr.service --since = "30 minutes ago" | egrep -e 'found [0-9] * channels'

    Oct 11 21:07:38 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    Oct 11 21:07:57 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    Oct 11 21:08:17 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    Oct 11 21:08:38 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    Oct 11 21:08:59 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    Oct 11 21:09:19 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    Oct 11 21:09:39 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    Oct 11 21:09:52 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    Oct 11 21:09:52 tv.house vdr [616513]: [616536] EEPG: found 744 channels

    [root @ tv ~] # journalctl --unit = vdr.service --since = "240 minutes ago" | egrep -e 'found [0-9] * summaries'

    Oct 11 18:07:37 tv.house vdr [616513]: [616536] EEPG: found 21081 summaries

    Oct 11 18:07:58 tv.house vdr [616513]: [616536] EEPG: found 19690 summaries

    Oct 11 18:08:18 tv.house vdr [616513]: [616536] EEPG: found 21076 summaries

    Oct 11 18:08:39 tv.house vdr [616513]: [616536] EEPG: found 21397 summaries

    Oct 11 18:09:00 tv.house vdr [616513]: [616536] EEPG: found 21494 summaries

    Oct 11 18:09:21 tv.house vdr [616513]: [616536] EEPG: found 21559 summaries

    Oct 11 18:09:38 tv.house vdr [616513]: [616536] EEPG: found 15998 summaries

    Oct 11 18:09:55 tv.house vdr [616513]: [616536] EEPG: found 11156 summaries

    Oct 11 18:09:55 tv.house vdr [616513]: [616536] EEPG: found 0 summaries



    I think that 0 titles and 0 summaries is always to be expected as it marks the end of the batch of EPG data.

    Oct 10 00:09:51 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 10 03:09:52 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 10 06:09:52 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 10 09:09:48 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 10 12:09:48 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 10 15:09:50 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 10 18:09:49 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 10 21:09:53 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 11 00:09:54 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 11 03:09:51 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles

    Oct 11 06:09:56 tv.house vdr [3278234]: [3278325] EEPG: found 0 titles