Well, somehow my mythfilldatabase was set to not auto-update in the options. I have no clue how that would happen though. I've running it manually for at least 2 months too

If you check for just 'mythfill' in the settings table, you'll notice MythFillEnabled, likely set to 1... and a hostname. Just one though, apparently this set doesn't like repeating itself.

The following all have a single (wrong) hostname setting on my box:

MythFillEnabled
MythFillPeriod
MythFillMinHour
MythFillMaxHour

I'm going to change them over to the proper name, as this looks to be a promising lead on the culprit, specifically that nasty little MythFillEnabled one. I'll post back after the next fill time comes and goes as to whether or not it fixes our little problem. By the looks of it, that'll be 5am on the 11th... 31 hours or so from now

Charlie

Hi,

Seem to be having the same problem with my database only it won't run manually either, it was updating eratically before i went on holiday and since i came back it has failed completely. If switched of the autofill in settings and rebooted then switched it back on and rebooted taht worked before. Now I can't get the database to to fill at all. It reports error code 512 sometimes but i have no idea what that is. I may have to consider a re install or a restore. Only experienced this with the new upgrade which I had to install when I had a Hard Disk failure. I'll watch you rposts for any clues as I'm a bit of a newbie at this stuff.

thanks

Well, I just checked my box -- Mythfill ran this morning at 5am. So, one of those entries seems to have done it.

Charlie

charlie_D: glad it worked for you. Unfortunately mine was not so successful. I changed those records from "mythtv" to "mbe" and it did not run. However, I had at least two other spurious hostnames that had MythFillEnabled, MythFillPeriod, etc.

I don't have any regex skills at all, so following the MythTV doc instructions on changing hostname the right way, I stopped the backend and used mysqldump to export mythconverg.

I then transferred that exported file to my Mac and used TextWrangler and went through the database and eliminated by hand (ack) extra hostnames records throughout the database. I left entries for my frontend because I'm not sure what should stay and what should go.

I then transferred the file back to my backend, dropped and recreated mythconverg, and restored with the edited MySQL file. I rebooted and all seems to be working, so hopefully I haven't screwed things up too badly. I was hoping that after a reboot, mythtv would detect that the SuggestedRunTime had passed and it would fire off a run, but it didn't.

One question: does your MythFillSuggestedRunTime have a hostname associated with it, or is it NULL?

My MythFillSuggestedRunTime is NULL for a hostname

Hopefully your database surgery worked for ya; I still have to go through and remove all the entries from the other two names and hopefully not break anything I think the Settings table is going to be the only really annoying one.

Charlie

Looks like I didn't kill the patient... mythfilldatabase ran this morning as scheduled. Whew!