[mythtv-users] Run mythfilldatabase if using EIT only sources? (was Re: Performance issue : Number of records in a Table ???)

James Stembridge jstembridge at gmail.com
Wed Mar 29 21:45:01 UTC 2006


Hi Mike,

On 3/29/06, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> would perform the cleanup of old data.  However, at first glance, it
> looks like it might output a warning, "Grabbing XMLTV data using eitonly
> is not verified as working."

Here's the output from running mfdb with a single eit-only source:

$ mythfilldatabase
2006-03-29 22:39:39.087 Using runtime prefix = /usr
2006-03-29 22:39:39.133 New DB connection, total: 1
2006-03-29 22:39:39.138 Connected to database 'mythconverg' at host: localhost
2006-03-29 22:39:39.156 New DB connection, total: 2
2006-03-29 22:39:39.158 Connected to database 'mythconverg' at host: localhost
2006-03-29 22:39:39.952 Updating source #1 (Default) with grabber eitonly
2006-03-29 22:39:39.952 Grabbing XMLTV data using eitonly is not
verified as working.
2006-03-29 22:39:40.038 New DB connection, total: 3
2006-03-29 22:39:40.131 Connected to database 'mythconverg' at host: localhost
2006-03-29 22:39:41.395 New DB connection, total: 4
2006-03-29 22:39:41.396 Connected to database 'mythconverg' at host: localhost
2006-03-29 22:39:41.401 New DB connection, total: 5
2006-03-29 22:39:41.402 Connected to database 'mythconverg' at host: localhost
2006-03-29 22:39:41.411 Data fetching complete.
2006-03-29 22:39:41.411 Adjusting program database end times.
2006-03-29 22:39:41.900     0 replacements made
2006-03-29 22:39:41.900 Marking generic episodes.
2006-03-29 22:39:42.030     Found 0
2006-03-29 22:39:42.030 Marking repeats.
2006-03-29 22:39:42.972     Found 0
2006-03-29 22:39:42.972 Unmarking new episode rebroadcast repeats.
2006-03-29 22:39:44.460     Found 0
2006-03-29 22:39:44.462
===============================================================
| Attempting to contact the master backend for rescheduling.  |
| If the master is not running, rescheduling will happen when |
| the master backend is restarted.                            |
===============================================================
2006-03-29 22:39:44.470 Connecting to backend server: 127.0.0.1:6543
(try 1 of 5)
2006-03-29 22:39:44.479 Using protocol version 26
2006-03-29 22:39:44.625 mythfilldatabase run complete.

All seems to work fine, though as you say the warning about XMLTV is
confusing as I'm not using it. At least I can re-enable my mfdb cron
job, I realised last night that listings had been accumulating since
last April which was starting to make the program guide performance
slightly less that optimal ;-)

Regards,
James.


More information about the mythtv-users mailing list