Mythtv v31 running on Ubuntu 20.04.1 LTS 64bit
FE status shows:
Last mythfilldatabase Guide Update:
Started: Fri Jul 24 2020, 4:52 PM
Finished: Fri Jul 24 2020, 4:53 PM
Result: Succesful
Suggested next: yesterday, 4:52 PM
(16 days)
If I log into the mythtv use and run "sudo -H -u mythtv bash -c "mythfilldatabase -v system"" it runs correctly other than some skipped channels. The FE status is updated to
Last mythfilldatabase Guide Update:
Started: Today, 4:16 PM
Finished: Today, 4:17 PM
Result: Successful
Suggested next: Tomorrow, 4:16 PM
(18 days)
However after tomorrow it will return to the above situations with the number of days counting down until I manually run it again.
Daily mythfilldatabase update not running.
Moderator: Forum Moderators
Re: Daily mythfilldatabase update not running.
Is the grabber set to the one you choose? Check the path to mythfilldatabase. These commands will print out what you've got or
use mythtv-setup to check:
The password is from the <Password> line in config.xml
If that doesn't pan out, then pastebin the above commands, their output and the last run in mythfilldatabase.log please.
use mythtv-setup to check:
Code: Select all
mysql --user=mythtv --password --execute="SELECT sourceid,name,xmltvgrabber FROM videosource" mythconverg
mysql --user=mythtv --password --execute="SELECT * FROM settings WHERE value IN ('MythFillDatabasePath','MythFillDatabaseArgs')" mythconverg
If that doesn't pan out, then pastebin the above commands, their output and the last run in mythfilldatabase.log please.
Re: Daily mythfilldatabase update not running.
| sourceid | name | xmltvgrabber |
+----------+------+-------------------+
| 1 | SD | tv_grab_zz_sdjson |
+----------+------+-------------------+
| value | data | hostname |
+----------------------+------------------+----------+
| MythFillDatabaseArgs | --dd-grab-all | NULL |
| MythFillDatabasePath | mythfilldatabase | NULL |
mythtv-setup shows Schedules Direct JSON API (xmltv) is in use.
nano $HOME/.mythtv/SD.xmltv shows:
cache=/home/mythtv/.xmltv/tv_grab_zz_sdjson.cache
channel-id-format=default
previously-shown-format=date
username=xxxxxx
password=xxxxxx
mode=lineup
lineup=USA-OTA-76078
Where exactly do I find the mythfilldatabase log
+----------+------+-------------------+
| 1 | SD | tv_grab_zz_sdjson |
+----------+------+-------------------+
| value | data | hostname |
+----------------------+------------------+----------+
| MythFillDatabaseArgs | --dd-grab-all | NULL |
| MythFillDatabasePath | mythfilldatabase | NULL |
mythtv-setup shows Schedules Direct JSON API (xmltv) is in use.
nano $HOME/.mythtv/SD.xmltv shows:
cache=/home/mythtv/.xmltv/tv_grab_zz_sdjson.cache
channel-id-format=default
previously-shown-format=date
username=xxxxxx
password=xxxxxx
mode=lineup
lineup=USA-OTA-76078
Where exactly do I find the mythfilldatabase log
Re: Daily mythfilldatabase update not running.
Use mythtv-setup to remove the --dd-grab-all argument. It isn't a valid option
in v31. It causes mythfilldatabase to exit with error code 132.
mythtv-setup: General -> Program Schedule Downloading Options -> Guide Data Arguements
MythTV logs are typically in /var/log/mythtv
in v31. It causes mythfilldatabase to exit with error code 132.
mythtv-setup: General -> Program Schedule Downloading Options -> Guide Data Arguements
MythTV logs are typically in /var/log/mythtv
Re: Daily mythfilldatabase update not running.
Looks like removing the "--dd-grab-all " did the trick. So if it is no longer valid for v31 why was it added during a clean install of OS and v31?
Re: Daily mythfilldatabase update not running.
Really good question. None of the packaging repos add it and the
MythTV repo itself doesn't add it.
I know you said: "clean install of OS and v31", but did you restore the DB from
an existing backup after the install?
MythTV repo itself doesn't add it.
I know you said: "clean install of OS and v31", but did you restore the DB from
an existing backup after the install?
Re: Daily mythfilldatabase update not running.
Nope it was a completely new install. Attempted upgrade from v30 failed completely and I forgot to take a backup first! Anyway decided to upgrade Ubuntu at that time to 20.04 and chose delete option so system wasn't dragging any old mythbuntu baggage forward.