epg2vdr: Fatal: Field 'timers._ENDTIME' not defined (missing in dictionary)

  • Habe epgd und epg2vdr aktualisiert und nun Fehler im Log:


    Code
    1. Jan 7 11:00:27 vdr01 vdr[6956]: epg2vdr: Fatal: Missing definition of field 'timers._ENDTIME' in dictionary!
    2. Jan 7 11:00:27 vdr01 vdr[6956]: epg2vdr: Fatal: Field 'timers._ENDTIME' not defined (missing in dictionary)

    Muss ich die Datenbank neui erstellen?


    Die Versionen müssten doch die letzten sein?

    Code
    1. root auf vdr01 am 07.01.2020 11:06
    2. [~] # epgd-tool -show-stats
    3. +---------------------------------------------------+-------+--------+----------------+----------+---------------------------+---------------------------+---------------------------+
    4. | version | dbapi | master | ip | state | last touch | last download | next download |
    5. +---------------------------------------------------+-------+--------+----------------+----------+---------------------------+---------------------------+---------------------------+
    6. | vdr 2.4.0 epg2vdr 1.1.106-GITdddd5c4 (23.12.2019) | 7 | Y | 192.168.178.68 | attached | 7th January 2020 11:06:21 | 7th January 2020 10:42:47 | NULL |
    7. | epgd 1.1.149-GIT71cd459 (15.12.2019) | 7 | - | 192.168.178.68 | standby | 7th January 2020 11:06:21 | 7th January 2020 10:52:53 | 7th January 2020 14:52:53 |
    8. +---------------------------------------------------+-------+--------+----------------+----------+---------------------------+---------------------------+---------------------------+

    Die epg.dat im epgd-Ordenr ist von Heute und das _ENDTIME ist auch drin


    Mit Freiheitsstrafe bis zu fünf Jahren oder mit Geldstrafe wird bestraft, wer eine nukleare Explosion verursacht. [StGB §328 Abs.: 2 Nr.: 3]

    ___

    Gen2VDR V7; VDR 2.4.0; Gehäuse: Antec Fusion V2 Black & iMon LCD (15c2:ffdc); Atric IR-Einschalter Rev. 4; Board: Intel DH77EB, Core i5-3550, Zotac GT630 Zone Edition, 4 GB RAM; DVB: 1x Digital Devices CineS2 Quad V6.5 [VDR-User #1540]

  • Du scheinst eine höhere Version des vdr2epg-Plugins zu benutzen, aber ansonsten schauts bei mir gleich aus und es scheint zu funktionieren - habe jedenfalls keine solchen Meldungen im syslog:

    Code
    1. epgd-tool -show-stats
    2. +--------------------------------------------+-------+--------+-----------------+--------------+---------------------------+---------------------------+---------------------------+
    3. | version | dbapi | master | ip | state | last touch | last download | next download |
    4. +--------------------------------------------+-------+--------+-----------------+--------------+---------------------------+---------------------------+---------------------------+
    5. | vdr 2.4.0 epg2vdr 1.1.105-GIT (17.12.2019) | 7 | y | 192.168.192.150 | attached | 7th January 2020 12:11:25 | 7th January 2020 09:17:48 | NULL |
    6. | epgd 1.1.149-GIT (15.12.2019) | 7 | - | 192.168.192.150 | busy (match) | 7th January 2020 12:10:55 | 7th January 2020 11:57:03 | 7th January 2020 23:57:03 |
    7. +--------------------------------------------+-------+--------+-----------------+--------------+---------------------------+---------------------------+---------------------------+


    Meins kommt (wieder) von Frodo:

    Code: apt-cache policy vdr-plugin-epg2vdr
    1. vdr-plugin-epg2vdr:
    2. Installiert: 3:1.1.105-1frodo0~bionic
    3. Installationskandidat: 3:1.1.105-1frodo0~bionic
    4. Versionstabelle:
    5. *** 3:1.1.105-1frodo0~bionic 500
    6. 500 http://ppa.launchpad.net/frodo-vdr/experimental-vdr-yavdr/ubuntu bionic/main amd64 Packages
    7. 100 /var/lib/dpkg/status
    8. 1.1.106-0yavdr0~bionic 500
    9. 500 http://ppa.launchpad.net/yavdr/experimental-vdr/ubuntu bionic/main amd64 Packages

    MyVDR: yaVDR-Ansible - softhddevice-openglosd (ffmpeg 2.8) - epgd/epg2vdr - skindesigner estuary4vdr (adaptiert) - 1920x1080@50 Hz | kodi 18 - inputstream + amazon vod *broken*
    Aerocube M40 | 300W | ASRock H61M-GE | Intel G530 | Asus ENGT520 | 2 x TT-budget S2-3200 | ASRock Smart Remote (CIR) | 4 GB RAM | 120 GB SSD | 3 TB HDD

  • epgd und epghttpd hast Du bestimmt schon mal neu gestartet?


    Unter yavdr-ansible mit den selben GIT Versionen sehe ich diese Fehler nicht.

    Code
    1. root@vdrserver:~# epgd-tool -show-stats
    2. +--------------------------------------------+-------+--------+----------------+----------+---------------------------+---------------------------+---------------------------+
    3. | version | dbapi | master | ip | state | last touch | last download | next download |
    4. +--------------------------------------------+-------+--------+----------------+----------+---------------------------+---------------------------+---------------------------+
    5. | vdr 2.4.0 epg2vdr 1.1.106-GIT (23.12.2019) | 7 | n | 192.168.64.166 | attached | 8th January 2020 19:56:54 | 8th January 2020 01:18:13 | NULL |
    6. | vdr 2.4.0 epg2vdr 1.1.106-GIT (23.12.2019) | 7 | n | 192.168.64.190 | attached | 8th January 2020 19:56:38 | 8th January 2020 19:02:46 | NULL |
    7. | vdr 2.4.0 epg2vdr 1.1.106-GIT (23.12.2019) | 7 | Y | 192.168.64.191 | attached | 8th January 2020 19:56:39 | 8th January 2020 19:02:46 | NULL |
    8. | epgd 1.1.149-GIT (15.12.2019) | 7 | - | 192.168.64.191 | standby | 8th January 2020 19:46:38 | 8th January 2020 19:06:16 | 9th January 2020 07:06:16 |
    9. +--------------------------------------------+-------+--------+----------------+----------+---------------------------+---------------------------+---------------------------+

    YaVDR-ansible , Case: HFX Classic, Mainboard: ASUS H97M-E, CPU: Intel Celeron CPU G1840T, GPU: GeForce GT 1030, DVB-S: Digital Devices Cine S2 V6

    YaVDR-ansible (24/7), Case: Akasa, Mainboard: NUC D34010WYB, DVB-S: SkyTV Ultimate IV, Miscellaneous: epgd, pihole (DoH)

    YaVDR-ansible (headless), System: HP 260 G2 DM, DVB-S: Sundtek SkyTV Ultimate 6 2016/Q1