Mailing List Archive

I ran it again:


2024-02-02 12:55:45.598911 I  Grabber prefers method: allatonce
2024-02-02 12:55:45.600769 I  XMLTV config file is:
/home/mythuser/.mythtv/SD.xmltv
2024-02-02 12:58:04.675701 E  XMLTV grabber returned error code 1
2024-02-02 12:58:04.923745 E  Malformed XML file, missing </tv> element,
at line 1, Premature end of document.
2024-02-02 12:58:05.150067 E  Failed to fetch some program info
2024-02-02 12:58:05.150087 I  Adjusting program database end times.

On 2/2/24 12:44, Jack McGee wrote:
> I don't know when this started. There is nothing in program guide. I
> see mythfilldatabase completed successfully in mythtv frontend. This
> is on
>
> mythbackend --version
> Please attach all output as a file in bug reports.
> MythTV Version : v33.1+fixes.202401260818.512d723c83~ubuntu22.04.1
> MythTV Branch : fixes/33
> Network Protocol : 91
> Library API : 33.20220913-1
> QT Version : 5.15.3
>
>
> This is what I see when I run from command line
>
> 2024-02-02 12:32:11.907976 I  Opening blocking connection to master
> backend
> 2024-02-02 12:32:12.065353 I  Updating source #1 (SD) with grabber
> tv_grab_zz_sdjson_sqlite
> 2024-02-02 12:32:12.066146 I  Found 106 channels for source 1 which
> use grabber
> 2024-02-02 12:32:12.066328 I  Starting process manager
> 2024-02-02 12:32:12.066337 I  Starting process signal handler
> 2024-02-02 12:32:12.066374 I  Starting IO manager (read)
> 2024-02-02 12:32:12.067711 I  Starting IO manager (write)
> 2024-02-02 12:32:12.667497 I  Grabber has capabilities: baseline
> manualconfig preferredmethod lineups apiconfig
> 2024-02-02 12:32:13.168375 I  Grabber prefers method: allatonce
> 2024-02-02 12:32:13.170286 I  XMLTV config file is:
> /home/mythuser/.mythtv/SD.xmltv
> 2024-02-02 12:35:28.645912 I  New static DB connectionChannelCon
>
> ....
>
> 2024-02-02 12:38:50.659211 N  Unknown xmltv channel identifier:
> I95777.json.schedulesdirect.org - Skipping channel.
> 2024-02-02 12:38:50.659532 N  Unknown xmltv channel identifier:
> I95778.json.schedulesdirect.org - Skipping channel.
> 2024-02-02 12:39:05.030288 I  Updated programs: 25652 Unchanged
> programs: 30980
> 2024-02-02 12:39:05.551765 N  Data fetching complete.
> 2024-02-02 12:39:05.551779 I  Adjusting program database end times.
> 2024-02-02 12:39:05.552039 I      0 replacements made
> 2024-02-02 12:39:05.552040 I  Marking generic episodes.
> 2024-02-02 12:39:05.858133 I      Found 11437
> 2024-02-02 12:39:05.858135 I  Extending non-unique programids with
> multiple parts.
> 2024-02-02 12:39:06.051412 I      Found 0
> 2024-02-02 12:39:06.051414 I  Fixing missing original airdates.
> 2024-02-02 12:39:06.571877 I      Found 1023 with programids
> 2024-02-02 12:39:06.572598 I      Found 0 without programids
> 2024-02-02 12:39:06.572599 I  Marking repeats.
> 2024-02-02 12:39:06.605456 I      Found 893
> 2024-02-02 12:39:06.605457 I  Unmarking new episode rebroadcast repeats.
> 2024-02-02 12:39:06.821725 I      Found 1640
> 2024-02-02 12:39:07.316192 I  Marking episode first showings.
> 2024-02-02 12:39:08.070837 I      Found 32928
> 2024-02-02 12:39:08.070840 I  Marking episode last showings.
> 2024-02-02 12:39:08.832214 I      Found 33180
> 2024-02-02 12:39:08.841476 I
> ===============================================================
> | Attempting to contact the master backend for rescheduling.  |
> | If the master is not running, rescheduling will happen when |
> | the master backend is restarted.                            |
> ===============================================================
> 2024-02-02 12:39:08.842283 N  mythfilldatabase run complete.
> 2024-02-02 12:39:08.842372 I  PowerDBus: Closing interfaces
> 2024-02-02 12:39:08.842754 I  Waiting for threads to exit.
> 2024-02-02 12:39:08.843204 I  Exiting
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Fri, Feb 2, 2024 at 6:46?PM Jack McGee <jack@greendesk.net> wrote:
>
> I don't know when this started. There is nothing in program guide. I
> see mythfilldatabase completed successfully in mythtv frontend. This is on
>

There are three common cases (and
none of them are considered fatal,
just informational).

The first is that there is a new channel
in your location, with a new XMLTVID
(if it is an OTA source maybe a new
diginet, or if it is a cable source maybe
a new channel).

The second is that a channel has
changed XMLTVID due to upstream
changes (it happens more often with
cable changes, such as a change
for timezone sources (east to west),
or sometimes the channel just
changes it's sources entirely).

The last is an artifact for (especially)
OTA locations with translators.
For "reasons" the upstream
sometimes (and the sometimes
is the annoying part) uses a
different XMLTVID for a translator
transmitter even though it is
providing 100% the same schedule.

In some cases you can rerun the
channel setup, or ask mythfilldatabase
to refresh your channels.

There is also a 3rd party application
that can try to identify the details
and offer to (in some cases) fix
things for you. It is documented
on the MythTV wiki.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

I tried this:

mythuser@amethi:~$ tv_grab_zz_sdjson_sqlite --manage-lineups
Unable to authenticate to Schedules Direct: HTTP response code was 500
Enter your username at Schedules Direct: jack@greendesk.net
Enter your password for jack@greendesk.net at Schedules Direct:
Unable to authenticate to Schedules Direct: HTTP response code was 500


Why does this fail?

username and password work to log into schedules direct.


On 2/2/24 13:05, Gary Buhrmaster wrote:
> On Fri, Feb 2, 2024 at 6:46?PM Jack McGee <jack@greendesk.net> wrote:
>> I don't know when this started. There is nothing in program guide. I
>> see mythfilldatabase completed successfully in mythtv frontend. This is on
>>
> There are three common cases (and
> none of them are considered fatal,
> just informational).
>
> The first is that there is a new channel
> in your location, with a new XMLTVID
> (if it is an OTA source maybe a new
> diginet, or if it is a cable source maybe
> a new channel).
>
> The second is that a channel has
> changed XMLTVID due to upstream
> changes (it happens more often with
> cable changes, such as a change
> for timezone sources (east to west),
> or sometimes the channel just
> changes it's sources entirely).
>
> The last is an artifact for (especially)
> OTA locations with translators.
> For "reasons" the upstream
> sometimes (and the sometimes
> is the annoying part) uses a
> different XMLTVID for a translator
> transmitter even though it is
> providing 100% the same schedule.
>
> In some cases you can rerun the
> channel setup, or ask mythfilldatabase
> to refresh your channels.
>
> There is also a 3rd party application
> that can try to identify the details
> and offer to (in some cases) fix
> things for you. It is documented
> on the MythTV wiki.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Ignore this. I was not connected to internet when I tried that.


On 2/2/24 13:20, Jack McGee wrote:
> I tried this:
>
> mythuser@amethi:~$ tv_grab_zz_sdjson_sqlite --manage-lineups
> Unable to authenticate to Schedules Direct: HTTP response code was 500
> Enter your username at Schedules Direct: jack@greendesk.net
> Enter your password for jack@greendesk.net at Schedules Direct:
> Unable to authenticate to Schedules Direct: HTTP response code was 500
>
>
> Why does this fail?
>
> username and password work to log into schedules direct.
>
>
> On 2/2/24 13:05, Gary Buhrmaster wrote:
>> On Fri, Feb 2, 2024 at 6:46?PM Jack McGee <jack@greendesk.net> wrote:
>>> I don't know when this started. There is nothing in program guide.   I
>>> see mythfilldatabase completed successfully in mythtv frontend. 
>>> This is on
>>>
>> There are three common cases (and
>> none of them are considered fatal,
>> just informational).
>>
>> The first is that there is a new channel
>> in your location, with a new XMLTVID
>> (if it is an OTA source maybe a new
>> diginet, or if it is a cable source maybe
>> a new channel).
>>
>> The second is that a channel has
>> changed XMLTVID due to upstream
>> changes (it happens more often with
>> cable changes, such as a change
>> for timezone sources (east to west),
>> or sometimes the channel just
>> changes it's sources entirely).
>>
>> The last is an artifact for (especially)
>> OTA locations with translators.
>> For "reasons" the upstream
>> sometimes (and the sometimes
>> is the annoying part) uses a
>> different XMLTVID for a translator
>> transmitter even though it is
>> providing 100% the same schedule.
>>
>> In some cases you can rerun the
>> channel setup, or ask mythfilldatabase
>> to refresh your channels.
>>
>> There is also a 3rd party application
>> that can try to identify the details
>> and offer to (in some cases) fix
>> things for you.  It is documented
>> on the MythTV wiki.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users@mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Thanks Gary, I took the python script from

https://www.mythtv.org/wiki/XMLTV#Channel_selection_shortcut_2


and ran it:

mythuser@amethi:~/.mythtv$ python3 sdjson-sqlite-select
Traceback (most recent call last):
  File "/home/mythuser/.mythtv/sdjson-sqlite-select", line 23, in <module>
    import pymysql
ModuleNotFoundError: No module named 'pymysql'


On 2/2/24 13:05, Gary Buhrmaster wrote:
> On Fri, Feb 2, 2024 at 6:46?PM Jack McGee <jack@greendesk.net> wrote:
>> I don't know when this started. There is nothing in program guide. I
>> see mythfilldatabase completed successfully in mythtv frontend. This is on
>>
> There are three common cases (and
> none of them are considered fatal,
> just informational).
>
> The first is that there is a new channel
> in your location, with a new XMLTVID
> (if it is an OTA source maybe a new
> diginet, or if it is a cable source maybe
> a new channel).
>
> The second is that a channel has
> changed XMLTVID due to upstream
> changes (it happens more often with
> cable changes, such as a change
> for timezone sources (east to west),
> or sometimes the channel just
> changes it's sources entirely).
>
> The last is an artifact for (especially)
> OTA locations with translators.
> For "reasons" the upstream
> sometimes (and the sometimes
> is the annoying part) uses a
> different XMLTVID for a translator
> transmitter even though it is
> providing 100% the same schedule.
>
> In some cases you can rerun the
> channel setup, or ask mythfilldatabase
> to refresh your channels.
>
> There is also a 3rd party application
> that can try to identify the details
> and offer to (in some cases) fix
> things for you. It is documented
> on the MythTV wiki.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

And I will add, for sometime, I have had several (not any stations I
care about), move and had no listings.  It was on my list to fix this.

This must have happened last night, as I usually check new shows daily,
and did so yesterday.  Now there is no guide data. I think I have pretty
good backups of the backend, if there is any value to restoring anything
to fix this to how it was yesterday I would be interested.

Today, I have nothing for any station.


On 2/2/24 13:52, Jack McGee wrote:
> Thanks Gary, I took the python script from
>
> https://www.mythtv.org/wiki/XMLTV#Channel_selection_shortcut_2
>
>
> and ran it:
>
> mythuser@amethi:~/.mythtv$ python3 sdjson-sqlite-select
> Traceback (most recent call last):
>   File "/home/mythuser/.mythtv/sdjson-sqlite-select", line 23, in
> <module>
>     import pymysql
> ModuleNotFoundError: No module named 'pymysql'
>
>
> On 2/2/24 13:05, Gary Buhrmaster wrote:
>> On Fri, Feb 2, 2024 at 6:46?PM Jack McGee <jack@greendesk.net> wrote:
>>> I don't know when this started. There is nothing in program guide.   I
>>> see mythfilldatabase completed successfully in mythtv frontend. 
>>> This is on
>>>
>> There are three common cases (and
>> none of them are considered fatal,
>> just informational).
>>
>> The first is that there is a new channel
>> in your location, with a new XMLTVID
>> (if it is an OTA source maybe a new
>> diginet, or if it is a cable source maybe
>> a new channel).
>>
>> The second is that a channel has
>> changed XMLTVID due to upstream
>> changes (it happens more often with
>> cable changes, such as a change
>> for timezone sources (east to west),
>> or sometimes the channel just
>> changes it's sources entirely).
>>
>> The last is an artifact for (especially)
>> OTA locations with translators.
>> For "reasons" the upstream
>> sometimes (and the sometimes
>> is the annoying part) uses a
>> different XMLTVID for a translator
>> transmitter even though it is
>> providing 100% the same schedule.
>>
>> In some cases you can rerun the
>> channel setup, or ask mythfilldatabase
>> to refresh your channels.
>>
>> There is also a 3rd party application
>> that can try to identify the details
>> and offer to (in some cases) fix
>> things for you.  It is documented
>> on the MythTV wiki.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users@mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

One other datapoint. The user running mythtv is mythtv.

I am logged into the backend as another user. I see SD.XMLTV in home
directories of both mythuser and mythtv.  I don't know password for
mythtv, only database password for that user.

mythuser@amethi:~$ sudo ps -U mythtv
    PID TTY          TIME CMD
   2962 ?        00:01:28 mythbackend

On 2/2/24 14:15, Jack McGee wrote:
> And I will add, for sometime, I have had several (not any stations I
> care about), move and had no listings.  It was on my list to fix this.
>
> This must have happened last night, as I usually check new shows
> daily, and did so yesterday.  Now there is no guide data. I think I
> have pretty good backups of the backend, if there is any value to
> restoring anything to fix this to how it was yesterday I would be
> interested.
>
> Today, I have nothing for any station.
>
>
> On 2/2/24 13:52, Jack McGee wrote:
>> Thanks Gary, I took the python script from
>>
>> https://www.mythtv.org/wiki/XMLTV#Channel_selection_shortcut_2
>>
>>
>> and ran it:
>>
>> mythuser@amethi:~/.mythtv$ python3 sdjson-sqlite-select
>> Traceback (most recent call last):
>>   File "/home/mythuser/.mythtv/sdjson-sqlite-select", line 23, in
>> <module>
>>     import pymysql
>> ModuleNotFoundError: No module named 'pymysql'
>>
>>
>> On 2/2/24 13:05, Gary Buhrmaster wrote:
>>> On Fri, Feb 2, 2024 at 6:46?PM Jack McGee <jack@greendesk.net> wrote:
>>>> I don't know when this started. There is nothing in program guide.   I
>>>> see mythfilldatabase completed successfully in mythtv frontend. 
>>>> This is on
>>>>
>>> There are three common cases (and
>>> none of them are considered fatal,
>>> just informational).
>>>
>>> The first is that there is a new channel
>>> in your location, with a new XMLTVID
>>> (if it is an OTA source maybe a new
>>> diginet, or if it is a cable source maybe
>>> a new channel).
>>>
>>> The second is that a channel has
>>> changed XMLTVID due to upstream
>>> changes (it happens more often with
>>> cable changes, such as a change
>>> for timezone sources (east to west),
>>> or sometimes the channel just
>>> changes it's sources entirely).
>>>
>>> The last is an artifact for (especially)
>>> OTA locations with translators.
>>> For "reasons" the upstream
>>> sometimes (and the sometimes
>>> is the annoying part) uses a
>>> different XMLTVID for a translator
>>> transmitter even though it is
>>> providing 100% the same schedule.
>>>
>>> In some cases you can rerun the
>>> channel setup, or ask mythfilldatabase
>>> to refresh your channels.
>>>
>>> There is also a 3rd party application
>>> that can try to identify the details
>>> and offer to (in some cases) fix
>>> things for you.  It is documented
>>> on the MythTV wiki.
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users@mythtv.org
>>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>> http://wiki.mythtv.org/Mailing_List_etiquette
>>> MythTV Forums: https://forum.mythtv.org
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users@mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Fri, 2 Feb 2024 13:52:49 -0600, you wrote:

>Thanks Gary, I took the python script from
>
>https://www.mythtv.org/wiki/XMLTV#Channel_selection_shortcut_2
>
>
>and ran it:
>
>mythuser@amethi:~/.mythtv$ python3 sdjson-sqlite-select
>Traceback (most recent call last):
> ? File "/home/mythuser/.mythtv/sdjson-sqlite-select", line 23, in <module>
> ??? import pymysql
>ModuleNotFoundError: No module named 'pymysql'

If you are running Ubuntu, then you can fix that error by:

sudo apt install python3-mysql
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 2/2/24 16:03, Stephen Worthington wrote:
> sudo apt install python3-mysql


mythuser@amethi:~$ sudo apt install python3-mysql
[sudo] password for mythuser:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package python3-mysql

On Fri, 2 Feb 2024 20:49:14 -0600, you wrote:

>
>On 2/2/24 16:03, Stephen Worthington wrote:
>> sudo apt install python3-mysql
>
>
>mythuser@amethi:~$ sudo apt install python3-mysql
>[sudo] password for mythuser:
>Reading package lists... Done
>Building dependency tree... Done
>Reading state information... Done
>E: Unable to locate package python3-mysql

Sorry, typo. Try this:

sudo apt install pythton3-pymysql

There is also an alternative:

sudo apt install python3-mysqldb

I have both installed.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Thanks.


Unpacking python3-pymysql (1.0.2-1ubuntu1) ...
Setting up python3-pymysql (1.0.2-1ubuntu1) ...
mythuser@amethi:~$ sudo python3
/home/mythtv/.mythtv/tv_grab_az_sdjson_sqlite
  File "/home/mythtv/.mythtv/tv_grab_az_sdjson_sqlite", line 112
    eval 'exec /usr/bin/perl -w -S $0 ${1+"$@"}' if 0; # not running
under some shell
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: expected 'else' after 'if' expression
mythuser@amethi:~$ /home/mythtv/.mythtv/tv_grab_az_sdjson_sqlite
-bash: /home/mythtv/.mythtv/tv_grab_az_sdjson_sqlite: Permission denied
mythuser@amethi:~$ sudo /home/mythtv/.mythtv/tv_grab_az_sdjson_sqlite
sudo: /home/mythtv/.mythtv/tv_grab_az_sdjson_sqlite: command not found
mythuser@amethi:~$ python3 /home/mythtv/.mythtv/tv_grab_az_sdjson_sqlite
  File "/home/mythtv/.mythtv/tv_grab_az_sdjson_sqlite", line 112
    eval 'exec /usr/bin/perl -w -S $0 ${1+"$@"}' if 0; # not running
under some shell
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: expected 'else' after 'if' expression

On 2/2/24 23:21, Stephen Worthington wrote:
> On Fri, 2 Feb 2024 20:49:14 -0600, you wrote:
>
>> On 2/2/24 16:03, Stephen Worthington wrote:
>>> sudo apt install python3-mysql
>>
>> mythuser@amethi:~$ sudo apt install python3-mysql
>> [sudo] password for mythuser:
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> E: Unable to locate package python3-mysql
> Sorry, typo. Try this:
>
> sudo apt install pythton3-pymysql
>
> There is also an alternative:
>
> sudo apt install python3-mysqldb
>
> I have both installed.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

OK, I now have guide data in mythtv Frontend, can schedule recordings
which I couldn't do yesterday. I have a lot more channels (maybe they
were hidden before) and only two with no guide data.


But mythfilldatabase doesn't look any different.


mythuser@amethi:~$ mythfilldatabase -v
2024-02-03 07:29:54.571279 C  mythfilldatabase version: fixes/33
[v33.1+fixes.202401260818.512d723c83~ubuntu22.04.1] www.mythtv.org
2024-02-03 07:29:54.571286 C  Qt version: compile: 5.15.3, runtime: 5.15.3
2024-02-03 07:29:54.571307 I  Ubuntu 22.04.3 LTS (x86_64)
2024-02-03 07:29:54.571308 N  Enabled verbose msgs:  general
2024-02-03 07:29:54.571314 N  Setting Log Level to LOG_INFO
2024-02-03 07:29:54.581580 I  Added logging to the console
2024-02-03 07:29:54.581824 I  Setup Interrupt handler
2024-02-03 07:29:54.581828 I  Setup Terminated handler
2024-02-03 07:29:54.581831 I  Setup Segmentation fault handler
2024-02-03 07:29:54.581833 I  Setup Aborted handler
2024-02-03 07:29:54.581837 I  Setup Floating point exception handler
2024-02-03 07:29:54.581840 I  Setup Illegal instruction handler
2024-02-03 07:29:54.581842 I  Setup Bus error handler
2024-02-03 07:29:54.581852 I  Setup Real-time signal 0 handler
2024-02-03 07:29:54.581854 I  Setup Hangup handler
2024-02-03 07:29:54.581929 N  Using runtime prefix = /usr
2024-02-03 07:29:54.581931 N  Using configuration directory =
/home/mythuser/.mythtv
2024-02-03 07:29:54.581950 I  Assumed character encoding: en_US.UTF-8
2024-02-03 07:29:54.582135 I  Empty LocalHostName. This is typical.
2024-02-03 07:29:54.582143 I  Using a profile name of: 'amethi' (Usually
the same as this host's name.)
2024-02-03 07:29:54.582222 I  Start up testing connections. DB
192.168.1.105, BE , attempt 0, status dbAwake, Delay: 2000
2024-02-03 07:29:55.117394 N  Setting QT default locale to EN_US
2024-02-03 07:29:55.117401 I  Current locale EN_US
2024-02-03 07:29:55.117434 N  Reading locale defaults from
/usr/share/mythtv//locales/en_us.xml
2024-02-03 07:29:55.140760 I  PowerDBus: Failed to delay sleep,shutdown:
Permission denied
2024-02-03 07:29:55.143226 I  PowerDBus: Added UPower.Device
'/org/freedesktop/UPower/devices/ups_hiddev0'
2024-02-03 07:29:55.143452 I  Power: On AC power
2024-02-03 07:29:55.190598 I  Power: Supported actions: None
2024-02-03 07:29:55.192417 I  Loading en_us translation for module
mythfrontend
2024-02-03 07:29:55.194739 I  Current MythTV Schema Version
(DBSchemaVer): 1376
2024-02-03 07:29:55.199195 I MythCoreContext::ConnectCommandSocket():
Connecting to backend server: 192.168.1.105:6543 (try 1 of 1)
2024-02-03 07:29:55.200083 I MythCoreContext::CheckProtoVersion(): Using
protocol version 91 BuzzOff
2024-02-03 07:29:55.200316 I  Opening blocking connection to master backend
2024-02-03 07:29:55.416249 I  Updating source #1 (SD) with grabber
tv_grab_zz_sdjson_sqlite
2024-02-03 07:29:55.417016 I  Found 106 channels for source 1 which use
grabber
2024-02-03 07:29:55.417217 I  Starting process manager
2024-02-03 07:29:55.417223 I  Starting process signal handler
2024-02-03 07:29:55.417245 I  Starting IO manager (read)
2024-02-03 07:29:55.418605 I  Starting IO manager (write)
2024-02-03 07:29:56.018365 I  Grabber has capabilities: baseline
manualconfig preferredmethod lineups apiconfig
2024-02-03 07:29:56.569192 I  Grabber prefers method: allatonce
2024-02-03 07:29:56.570844 I  XMLTV config file is:
/home/mythuser/.mythtv/SD.xmltv
2024-02-03 07:30:50.763360 I  New static DB connectionChannelCon
2024-02-03 07:30:51.837875 N  Unknown xmltv channel identifier:
I100561.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:52.521970 N  Unknown xmltv channel identifier:
I103658.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:52.522436 N  Unknown xmltv channel identifier:
I103662.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:52.522864 N  Unknown xmltv channel identifier:
I103664.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:52.523314 N  Unknown xmltv channel identifier:
I103666.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:52.523752 N  Unknown xmltv channel identifier:
I103786.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:52.524173 N  Unknown xmltv channel identifier:
I103787.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:52.524645 N  Unknown xmltv channel identifier:
I103809.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:54.338500 N  Unknown xmltv channel identifier:
I106816.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:55.516281 N  Unknown xmltv channel identifier:
I106915.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:57.173332 N  Unknown xmltv channel identifier:
I110605.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:57.173675 N  Unknown xmltv channel identifier:
I112045.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:57.173972 N  Unknown xmltv channel identifier:
I112046.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:58.836525 N  Unknown xmltv channel identifier:
I112553.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:30:58.836863 N  Unknown xmltv channel identifier:
I112554.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:31:11.886224 N  Unknown xmltv channel identifier:
I115703.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:31:16.744238 N  Unknown xmltv channel identifier:
I116614.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:31:20.111903 N  Unknown xmltv channel identifier:
I119445.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:31:25.161433 N  Unknown xmltv channel identifier:
I121280.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:31:25.161785 N  Unknown xmltv channel identifier:
I121353.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:31:25.162159 N  Unknown xmltv channel identifier:
I121918.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:31:25.162491 N  Unknown xmltv channel identifier:
I123118.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:31:25.162813 N  Unknown xmltv channel identifier:
I124210.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:17.493375 N  Unknown xmltv channel identifier:
I72157.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:17.493836 N  Unknown xmltv channel identifier:
I72159.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:17.494327 N  Unknown xmltv channel identifier:
I72161.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:17.494777 N  Unknown xmltv channel identifier:
I72162.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:17.495184 N  Unknown xmltv channel identifier:
I72290.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:19.668445 N  Unknown xmltv channel identifier:
I74344.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:19.668821 N  Unknown xmltv channel identifier:
I74345.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:20.505453 N  Unknown xmltv channel identifier:
I74927.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:24.580189 N  Unknown xmltv channel identifier:
I78761.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:29.510916 N  Unknown xmltv channel identifier:
I88584.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:29.511218 N  Unknown xmltv channel identifier:
I88585.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:40.310545 N  Unknown xmltv channel identifier:
I95776.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:40.310832 N  Unknown xmltv channel identifier:
I95777.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:40.311095 N  Unknown xmltv channel identifier:
I95778.json.schedulesdirect.org - Skipping channel.
2024-02-03 07:32:46.785501 I  Updated programs: 7761 Unchanged programs:
49222
2024-02-03 07:32:47.343566 N  Data fetching complete.
2024-02-03 07:32:47.343580 I  Adjusting program database end times.
2024-02-03 07:32:47.343815 I      0 replacements made
2024-02-03 07:32:47.343815 I  Marking generic episodes.
2024-02-03 07:32:47.630320 I      Found 2418
2024-02-03 07:32:47.630322 I  Extending non-unique programids with
multiple parts.
2024-02-03 07:32:47.829279 I      Found 0
2024-02-03 07:32:47.829283 I  Fixing missing original airdates.
2024-02-03 07:32:48.378433 I      Found 947 with programids
2024-02-03 07:32:48.379154 I      Found 0 without programids
2024-02-03 07:32:48.379155 I  Marking repeats.
2024-02-03 07:32:48.413233 I      Found 914
2024-02-03 07:32:48.413235 I  Unmarking new episode rebroadcast repeats.
2024-02-03 07:32:48.642152 I      Found 2038
2024-02-03 07:32:49.177320 I  Marking episode first showings.
2024-02-03 07:32:49.977454 I      Found 33155
2024-02-03 07:32:49.977458 I  Marking episode last showings.
2024-02-03 07:32:50.784473 I      Found 33418
2024-02-03 07:32:50.793606 I
===============================================================
| Attempting to contact the master backend for rescheduling.  |
| If the master is not running, rescheduling will happen when |
| the master backend is restarted.                            |
===============================================================
2024-02-03 07:32:50.794194 N  mythfilldatabase run complete.
2024-02-03 07:32:50.794273 I  PowerDBus: Closing interfaces
2024-02-03 07:32:50.794629 I  Waiting for threads to exit.
2024-02-03 07:32:50.795057 I  Exiting



_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 03/02/2024 13:38, Jack McGee wrote:
>
(snip)
>
> 2024-02-03 07:30:51.837875 N  Unknown xmltv channel identifier: I100561.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:52.521970 N  Unknown xmltv channel identifier: I103658.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:52.522436 N  Unknown xmltv channel identifier: I103662.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:52.522864 N  Unknown xmltv channel identifier: I103664.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:52.523314 N  Unknown xmltv channel identifier: I103666.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:52.523752 N  Unknown xmltv channel identifier: I103786.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:52.524173 N  Unknown xmltv channel identifier: I103787.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:52.524645 N  Unknown xmltv channel identifier: I103809.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:54.338500 N  Unknown xmltv channel identifier: I106816.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:55.516281 N  Unknown xmltv channel identifier: I106915.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:57.173332 N  Unknown xmltv channel identifier: I110605.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:57.173675 N  Unknown xmltv channel identifier: I112045.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:57.173972 N  Unknown xmltv channel identifier: I112046.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:58.836525 N  Unknown xmltv channel identifier: I112553.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:30:58.836863 N  Unknown xmltv channel identifier: I112554.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:31:11.886224 N  Unknown xmltv channel identifier: I115703.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:31:16.744238 N  Unknown xmltv channel identifier: I116614.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:31:20.111903 N  Unknown xmltv channel identifier: I119445.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:31:25.161433 N  Unknown xmltv channel identifier: I121280.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:31:25.161785 N  Unknown xmltv channel identifier: I121353.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:31:25.162159 N  Unknown xmltv channel identifier: I121918.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:31:25.162491 N  Unknown xmltv channel identifier: I123118.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:31:25.162813 N  Unknown xmltv channel identifier: I124210.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:17.493375 N  Unknown xmltv channel identifier: I72157.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:17.493836 N  Unknown xmltv channel identifier: I72159.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:17.494327 N  Unknown xmltv channel identifier: I72161.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:17.494777 N  Unknown xmltv channel identifier: I72162.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:17.495184 N  Unknown xmltv channel identifier: I72290.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:19.668445 N  Unknown xmltv channel identifier: I74344.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:19.668821 N  Unknown xmltv channel identifier: I74345.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:20.505453 N  Unknown xmltv channel identifier: I74927.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:24.580189 N  Unknown xmltv channel identifier: I78761.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:29.510916 N  Unknown xmltv channel identifier: I88584.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:29.511218 N  Unknown xmltv channel identifier: I88585.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:40.310545 N  Unknown xmltv channel identifier: I95776.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:40.310832 N  Unknown xmltv channel identifier: I95777.json.schedulesdirect.org -
> Skipping channel.
> 2024-02-03 07:32:40.311095 N  Unknown xmltv channel identifier: I95778.json.schedulesdirect.org -
> Skipping channel.
>
(snip)
>
I can't remember which way round this is, but it is either channels you subscribe to that are not in
your <sourceid>.xmltv file, or channels that are in your <sourceid>.xmltv file but that aren't in
your subscription (lineup).

These are basically just warnings. If you care to take the time and follow each one up, you can fix
them (ie remove the messages) by hand editing your .xmltv files so that your lineup, your .xmltv
file and your channel list all match.

--

Mike Perkins


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org