<p>Thank you SO much for this message. I was running into the same exact
problem, with schedules through October 8th but no further. I was
pulling my hair out trying to figure out why this would be happening.</p><p>It
didn't help that this was on a Myth box I had built for a relative!</p>Anyway,
I had done the same thing, apparently...run mythfilldatabase as root, and the
mythtv_ddp_data file was sitting there, in /tmp, unwritable. Removed it
and all is well.<br><br>Thanks again!!!<br><br><hr><!-- DRM QUOTE -->
<b>From:</b> R KANNAN <rk111810@gmail.com><br>
<b>Sent:</b> Thu, 4 Oct 2012 21:57:00 -0400 (EDT)<br>
<b>To:</b> mythtv-users@mythtv.org<br>
<b>Subject:</b> Re: [mythtv-users] Schedules Direct Grabbing failure.
[SOLVED]<br>
<p>
<br></p><div class="gmail_quote"><blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
><br>
> Message: 14<br>
> Date: Wed, 03 Oct 2012 20:26:05 -0400<br>
> From: "Michael T. Dean" <<a
href="mailto:mtdean@thirdcontact.com"
target="_blank">mtdean@thirdcontact.com</a><br>
> <mailto:<a href="mailto:mtdean@thirdcontact.com"
target="_blank">mtdean@thirdcontact.com</a>>><br>
> To: Discussion about MythTV <<a
href="mailto:mythtv-users@mythtv.org"
target="_blank">mythtv-users@mythtv.org</a><br>
> <mailto:<a href="mailto:mythtv-users@mythtv.org"
target="_blank">mythtv-users@mythtv.org</a>>><br>
> Subject: Re: [mythtv-users] Schedules Direct Grabbing
failure.<br>
> Message-ID: <<a
href="mailto:506CD79D.6000407@thirdcontact.com"
target="_blank">506CD79D.6000407@thirdcontact.com</a><br>
> <mailto:<a
href="mailto:506CD79D.6000407@thirdcontact.com"
target="_blank">506CD79D.6000407@thirdcontact.com</a>>><br>
> Content-Type: text/plain; charset=ISO-8859-1;
format=flowed<br>
><br>
> On 10/03/2012 06:09 PM, R KANNAN wrote:<br>
> > All,<br>
> ><br>
> > For the past three days, mythfilldatabase is failing
to populate<br>
> data<br>
> > beyond 10/14. Usually SD has data for 14 days.. The
output looks<br>
> like<br>
> > the following..<br>
> ><br>
> ...<br>
> > 2012-10-03 18:05:11.804778 I Grabbing data for
Wed Oct 3 2012<br>
> offset 13<br>
> > 2012-10-03 18:05:11.804808 I From Tue Oct 16
04:00:00 2012 to<br>
> Wed Oct<br>
> > 17 04:00:00 2012 (UTC)<br>
> ><br>
> ...<br>
> > 2012-10-03 18:05:24.065749 I Grab complete.
Actual data from<br>
> Sun Oct<br>
> > 14 04:00:00 2012 to Mon Oct 15 04:00:00 2012 (UTC)<br>
><br>
> We asked for data for the 16th and SD/TMS gave us data for
the<br>
> 14th. If<br>
> the servers don't give us the data we ask for, there's not
much we<br>
> can do.<br>
><br>
> I'd suggest you try the "re-add all lineups" (or whatever
it's called)<br>
> button on the Schedules Direct website and see if it
helps.<br>
><br>
> Mike<br>
><br>
><br>
> I tried readding and also removing & adding line up. I still
don'yt<br>
> seem to be able to grab the data.<br>
><br>
><br>
> 2012-10-04 18:34:35.032289 I DataDirect: Your subscription expires
on<br>
> Mon Dec 17 10:40 AM<br>
> 2012-10-04 18:34:38.875926 I Grab complete. Actual data from
Sun Oct<br>
> 14 04:00:00 2012 to Mon Oct 15 04:00:00 2012 (UTC)<br>
> 2012-10-04 18:34:38.876449 I Main temp tables populated.<br>
> 2012-10-04 18:34:38.949752 I Clearing data for source.<br>
> 2012-10-04 18:34:38.949808 I Clearing from Sun Oct 14 00:00:00
2012<br>
> to Mon Oct 15 00:00:00 2012 (localtime)<br>
><br>
> I think there may be an issue with my database. Is there a way to<br>
> check if my database is corrupted and if so how can I go about<br>
> rebuilding it?<br>
<br>
<a href="http://optimize_mythdb.pl" target="_blank">optimize_mythdb.pl</a>
will fix crashed MySQL tables, but if it's still<br>
asking for one day's data and getting some other day's data, that's<br>
unrelated to your database. At one point I had thought it possible
that<br>
the problem is Qt 4.8's new time format causing problems, but if so, I'd<br>
think other users would be having problems, too (and would think that<br>
you would have started having the problem when you upgraded to Qt 4.8<br>
rather than at some random time--it doesn't seem like you had just<br>
upgraded your system/MythTV when this started happening, right?). I
had<br>
actually done some testing with the date formats that Qt 4.8 is sending<br>
and they seemed to work for me, so I really don't know what could be<br>
causing the problem (but I can almost guarantee that it's outside your<br>
database--just don't know if it's MythTV code (and if so, which code) or<br>
Schedules Direct/TMS code, or your SD/TMS account, or ...)<br>
<br>
Also, please try checking your /tmp directory (or anywhere else) for<br>
mythtv_dd_cache* directory/directories and if you find them, please<br>
delete them all then re-run mfdb.<br>
<br>
Mike<br>
<br>
</blockquote></div><br>I found the problem. I had run mthfilldatabase as
'root' On Oct 1. It filled the data till 10/14 and left a file called
/tmp/mythtv_ddp_data with no write permissions for anyone. After I
deleted the file and ran 'mythfilldatabase', it worked fine. and got data for
5 days.<br>
<br>Thanks for your help. Now I am back to figuring out why my recording stop
after 320 MB when there is plenty of space available. I get messages
like..<br><br>AutoExpire: Filesystem Info cache is empty, unable to determine
what Recordings to expire<br>
<br>and the recording stops.<br>
<pre>_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
</pre>
----