<blockquote>On Wednesday, November 6, 2013 14:01 CET, "Michael T. Dean" <mtdean@thirdcontact.com> wrote:<br /><em>> I think I had the same issue.</em><blockquote>> I found in the backend setup - video sources that there was a blank<br />> entry for schedules direct (which I don't use), of course since there<br />> was no name for it, it did not show on the screen, but you could move<br />> down and select it.<br />> I then deleted it and mythtfilldatabase didn't look for it any more.<br />><br />> Might be worth looking at.<br />><br /><br />Definitely check this. It sounds like you simply have one or more Video<br />Sources configured to use Schedules Direct, even though you didn't<br />intend to (likely because of the confusing UI in setup).<br /><br />Of course, a default-verbosity log of a mythfilldatabase run would tell<br />us exactly what's wrong, rather than forcing us to guess/list all<br />possible mis
configurations you may have...<br /><br />Mike</blockquote>Thanks to both of you. There was indeed a blank source with no channels but using datadirect as a grabber. I deleted it this morning but haven't had time to run mythfilldatabase again since.<br /><br />The run always finishes with error status 1. Could be the blank source, but may also be something else (Unexpected end of file??) My channel tables do (mostly) get filled so I haven't worried too much about it. Here's the log, anyway:<br />http://pastebin.com/pGueTb7M<br />Cheers!<br /> </blockquote><br /><br /><br />