G Kazaroth wrote:
> I have a new push for the epg, but will not help with your issue. The error says the *.xml file that was pull from where ever and placed in the data/tmp/xmltv folder disappeared. Obviously, there is something else going on for it to disappear and it has little to do with the databases. It pulls down the file that is compressed and then uncompresses it into the file listed (that was not found). So, the log must have more info on what happened. It got broken before it got here.
I wish the log had more info, but it doesn't. And all the other services (SamsungTV, Pluto, XUMO) have no problem. Also, Cabernet is the only thing running under the hts user account on that system - Tvheadend also runs as the hts user, but on a completely different machine.
So I tried this:
In the plex instance changed the url for the epg data to
https://i.mjh.nz/Plex/us.xml so it would come in uncompressed.
Set the log level to INFO
Went to Data Management and clicked the button to Reset EPG Data, after specifying M3U in the dropdown.
Went to Scheduled Tasks and clicked the icon to Refresh M3U Plex Channels
While that was running this is ALL the log showed for the entire period:
Oct 1 17:47:58 systemname locast[5097]: 2021-10-01 17:47:58,033-INFO:web_handler [127.0.0.1] "GET /api/schedulehtml?task=7A5DF3B8-22ED-11EC-BE39-CA6F026676A3&run=1 HTTP/1.1" 200 -
Oct 1 17:47:58 systemname locast[5097]: 2021-10-01 17:47:58,139-INFO:web_handler [127.0.0.1] "GET /modules/scheduler/scheduler.js HTTP/1.1" 200 -
Oct 1 17:48:03 systemname locast[5097]: 2021-10-01 17:48:03,237-INFO:web_handler [127.0.0.1] "GET /api/schedulehtml HTTP/1.1" 200 -
Oct 1 17:48:03 systemname locast[5097]: 2021-10-01 17:48:03,326-INFO:web_handler [127.0.0.1] "GET /modules/scheduler/scheduler.js HTTP/1.1" 200 -
Oct 1 17:49:04 systemname locast[5097]: 2021-10-01 17:49:04,845-INFO:web_handler [127.0.0.1] "GET /m3u/plex/xmltv.xml HTTP/1.1" 200 -
Just those five lines and that was it! Even several minutes later nothing new had been added, except for a couple lines from systemd about a process that runs under a completely different user account. It wasn't until 18:13:45 that I got another set of those UNEXPECTED EXCEPTION messages, and there was nothing before them. There actually were two setd, one complaining "No such file or directory: '/home/hts/cabernet/data/tmp/xmltv'" and the other "No such file or directory: '/home/hts/cabernet/data/tmp/xmltv/1633126423.0377953'" - the first one makes me wonder if maybe the actual filename is xmltv.xml? I checked that tmp directory a few times and never saw anything in it, and I did check the ownership and permissions to make sure they were okay.
But back to the attempt to get the Plex listings - just out of curiosity I compared a "dummy" program listing that's being produced by Cabernet now to an actual program listing for the same channel:
<programme channel="5e20b730f2f8d5003d739db7-612919784f53e1002c9aa219" start="20211001080000 -0400" stop="20211001090000 -0400">
<title lang="en">Are We There Yet?</title>
<desc lang="en"> Not Available</desc>
<length units="minutes">60</length>
<previously-shown/>
</programme>
<programme channel="5e20b730f2f8d5003d739db7-612919784f53e1002c9aa219" start="20211001184814 +1300" stop="20211001191407 +1300">
<title>The First .45 Episode</title>
<desc>
As Lindsey films a reality show about her family, Kevin comes across a gun in Suzanne's handbag.
</desc>
<icon src="https://db6iftd8li11q.cloudfront.net/MSL1411.jpg"/>
</programme>
I first note the time zone designations are different (-0400 compared to +1300), not sure if that could be an issue. Second, the ' lang="en"' is not used in the actual listings, could something be looking for that?
These are the channel segments at the top of the
http://localhost:6077/m3u/plex/xmltv.xml
file and the real one:
<channel id="5e20b730f2f8d5003d739db7-612919784f53e1002c9aa219">
<display-name>Are We There Yet?</display-name>
<icon src="https://provider-static.plex.tv/epg/images/ott_channels/logos/AreWeThereYet_logo_dark.png"/>
</channel>
<channel id="5e20b730f2f8d5003d739db7-612919784f53e1002c9aa219">
<display-name>AREPX Are We There Yet?</display-name>
<display-name>AREPX Are We There Yet?</display-name>
<display-name>AREPX</display-name>
<display-name>Are We There Yet?</display-name>
<display-name>Are We There Yet?</display-name>
</channel>
In case you are wondering where AREPX came from, I had set it up to use PX as a channel suffix and at that point you hadn't enabled the feature to use channel numbers if none are present, so I used three letter codes derived from the channel name, just so each would be unique. So my next question is, does the logic that extracts the channel listings expect that some of those display-name fields will start with a number? If so that's my fault but I had thought that internally it only used the channel id string for matching.
Let me ask this, suppose I wanted to start over with a mostly fresh install, but not lose my channel edits. If I did a fresh install from scratch and ONLY brought over my config.ini file (with the Plex instance stripped back to the bare minimum, as if I was just installing it) and my current channels.db, would that preserve my channel edits while doing enough of a refresh that it might make these issues go away? Or could the channels.db file be part of the problem?
Anyway I hope I am giving you some useful feedback. Thanks for looking at this, and I really wish I could give you some better clues as to what is going on.
