The Guide is empty

Server Version#: 1.25.4.5487 (Synology)
Player Version#: N/A

The EPG is not populating anymore, no config changed, used to work fine before. Australia with HomeRunHD.

Using: Sydney xmltv.net

Feb 03, 2022 16:45:30.086 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Colombian Emerald' show
Feb 03, 2022 16:45:30.163 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Bolivian Ametrine' show
Feb 03, 2022 16:45:30.538 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Pacific Island Food Revolution' show
Feb 03, 2022 16:45:30.800 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Te Ao with Moana' show
Feb 03, 2022 16:45:30.904 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Country Music' show
Feb 03, 2022 16:45:30.980 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Hunting Aotearoa' show
Feb 03, 2022 16:45:31.064 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'The Fifth Region' show
Feb 03, 2022 16:45:31.343 [0x7f854ddaa8] Debug — Activity: updated activity 1f1b879a-5636-4a4d-9b03-e2c5e19f3a16 - completed 77.0% - Refreshing guide data
Feb 03, 2022 16:45:31.344 [0x7f854ddaa8] Debug — Activity: updated activity 1f1b879a-5636-4a4d-9b03-e2c5e19f3a16 - completed 77.0% - Refreshing guide data
Feb 03, 2022 16:45:31.502 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Racing Live: Ladbrokes Park/Gawler' show
Feb 03, 2022 16:45:31.583 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Autumn Contenders' show
Feb 03, 2022 16:45:31.636 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Champions - So You Think' show
Feb 03, 2022 16:45:31.689 [0x7f854ddaa8] Debug — EPG[xmltv]: Failed to retrieve universal details for 'Racenight Live: Happy Valley' show
Feb 03, 2022 16:45:31.728 [0x7f854ddaa8] Error — Exception inside transaction (inside=1) (/data/jenkins/server/3963556253/MediaProviders/EPG/XMLTV/MediaProviderEpgXmlTv.cpp:702): bad lexical cast: source type value could not be interpreted as target

Feb 03, 2022 16:45:31.735 [0x7f854ddaa8] Error — EPG[xmltv]: Caught exception during data chunk load: bad lexical cast: source type value could not be interpreted as target
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Debug — EPG[xmltv]: Step 1/1 (2022-02-03T00:00Z) (network: 1.0 sec, database: 158.3 sec total: 159.3 sec)
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Debug — Activity: updated activity 1f1b879a-5636-4a4d-9b03-e2c5e19f3a16 - completed 100.0% - Refreshing guide data
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Debug — Activity: updated activity 1f1b879a-5636-4a4d-9b03-e2c5e19f3a16 - completed 100.0% - Refreshing guide data
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Warning — EPG[xmltv]: Failed to load EPG.
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Debug — Database: Shutting down.
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Debug — Captured session 0.
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Debug — Captured session 1.
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Debug — Captured session 2.
Feb 03, 2022 16:45:31.736 [0x7f854ddaa8] Debug — Captured session 3.
Feb 03, 2022 16:45:31.737 [0x7f854ddaa8] Debug — Captured session 4.
Feb 03, 2022 16:45:31.753 [0x7f854ddaa8] Debug — EPG[xmltv]: Total time to load EPG was 159.4 (HTTP details cached 0.0%, CloudFlare grid cached: 0.0%, 0 HTTP errors)

Thanks for reporting this. I will see if i can reproducing it using the xmltv you specified

Appears to be some data Plex Media Server tripped over

Feb 03, 2022 16:45:31.728 [0x7f854ddaa8] Error — Exception inside transaction (inside=1) (/data/jenkins/server/3963556253/MediaProviders/EPG/XMLTV/MediaProviderEpgXmlTv.cpp:702): bad lexical cast: source type value could not be interpreted as target

Feb 03, 2022 16:45:31.735 [0x7f854ddaa8] Error — EPG[xmltv]: Caught exception during data chunk load: bad lexical cast: source type value could not be interpreted as target
1 Like

I have reproduced the error using the xmltv provided. Will put in diagnostics to identify which data was unexpected

1 Like

I have referred this to the development team

Do you know if there was a specific update to the Plex Media Server version that brought this on ?

1 Like

Could have been I did upgrade recently, probably 4 days ago and the guide is empty for the last 2 days. Thanks for looking into this, as it obviously affects all recordings now as there is no guide.

I have looked further into the issue and it appears to be bad xmltv data for a number of channels that you would need to report to the provider of the xmltv data

The start/stop times are wrong syntax for a number of channels having 16 digit instead of 14 digit times

The format used in the xmltv is
yyyymmddhhmmss +hhmm

But 11 channels have extra 2 zeros after the seconds so having a format of
yyyymmddhhmmss00 +hhmm which is incorrect xmltv time format

The channels that have the bad data are
image

Example of correct entry:

        <programme start="20220204030000 +1100" stop="20220204033000 +1100" channel="9.yourtv.com.au">
                <title>TV Shop - Home Shopping</title>
                <sub-title>Fish Seeker</sub-title>
                <desc>Home shopping program.</desc>
                <category>Shopping</category>
                <episode-num system="SxxExx">S2016E218</episode-num>
                <episode-num system="xmltv_ns">2015.217.</episode-num>
                <episode-num system="original-air-date">2022-02-04 03:00:00</episode-num>
                <previously-shown />
                <video>
                        <quality>SDTV</quality>
                </video>
                <rating>
                        <value>G</value>
                </rating>
                <premiere />
        </programme>

and Example of bad invalid entry

        <programme start="2022020400000000 +1100" stop="2022020406000000 +1100" channel="301.yourtv.com.au">
                <title>BBC</title>
                <desc></desc>
                <category>Radio</category>
        </programme>

This is wrong 2022020400000000 +1100 and should be 20220204000000 +1100

What you could do until your xmltv provider fixes the problem:

  • remove the affected channels
  • download the xmltv periodically from Manifest to a file and edit the file to remove the extra 2 zeros and setup the dvr using an xmltv file rather than a url

e.g.

curl -o Sydneyxmltv.xml  http://xmltv.net/xml_files/Sydney.xml

You would need to identify the programme lines for the affected channels and remove the extra 2 zeros

I am linking spec for time for xmltv data
xmltv/xmltv.dtd at master · XMLTV/xmltv (github.com)
See line 91

1 Like

Hi, Thanks I removed those offending channels from my PVR Guide and it’s now working… I have advised the guide provider… thank you for you prompt help :slight_smile:

36 SBS Arabic24 37 SBS Radio 1 38 SBS Radio 2 39 SBS Chill 301 SBS Radio 1 302 SBS Radio 2 303 SBS Radio 3 304 SBS Arabic24 305 SBS PopDesi 306 SBS Chill 307 SBS PopAsia

Sorry, that was an error as SBS changed their time format. This should have been fixed from about a week ago…

For Info - as from Plex Media Server 1.25.7 we will be resilient to this non standard syntax

@mbedwani Beta 1.25.7 which came out this week allows for the non-standard variations in the start / end times

See release notice for Plex Media Server 1.25.7.5604

  • (EPG) Fix parsing XMLTV time including milliseconds (#13353)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.