<p><br>
On May 13, 2012 5:03 PM, "Bill Meek" <<a href="mailto:keemllib@gmail.com">keemllib@gmail.com</a>> wrote:<br>
><br>
> On 05/13/2012 05:34 PM, Michael T. Dean wrote:<br>
>><br>
>> On 05/13/2012 05:55 PM, Chris Porter wrote:<br>
>>><br>
>>> I am having a strange issue with mythfilldatabase. If I run mythfilldatabase with no arguments it is able to retrieve listing data. However,<br>
>>> if I do mythfilldatabase with the --dd-grab-all option it fails to retrieve data. I made sure I am using a login to Schedules direct without<br>
>>> an @ in the login name and I am only running QT 4.7.0<br>
>>><br>
>>> This suggests to me there is some minor difference between how mythfilldatabase talks to schedules direct when using the --dd-grab-all option<br>
>>> which causes it to fail.<br>
>><br>
>><br>
>> Are you on 0.25+? If so, is it current -fixes? There may be an issue with a timeout which occurs only with --dd-grab-all if it takes the server<br>
>> too long to get the data. I think Gavin fixed this with a better timeout, but am not sure.<br>
><br>
><br>
> Hi;<br>
><br>
> You probably alread read this too, but try:<br>
><br>
> mythfilldatabase --nodblog --loglevel debug --verbose file,network --logpath /tmp --dd-grab-all<br>
><br>
> If its the problem I had with ubuntu 12.04/MySQL 5.5, my log always stalled* here:<br>
><br>
> DataDirect: sourceid 1 has lineup type: LocalBroadcast<br>
><br>
> which was solved with input from one of the IRC channels and involves changing the<br>
> storage engine. But, I did that on my test box and would really like Mike's input<br>
> before broadcasting a solution for production machines.<br>
><br>
> -- <br>
> Bill<br>
><br>
> * I'm now running in 51 seconds where it was taking hours.<br>
><br>
> _______________________________________________<br>
> mythtv-users mailing list<br>
> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
> <a href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br></p>
<p>I am on 0.25 fixes from 20120408-1.</p>
<p>I did do the logging and no problem with mysql. I just see a down load failure with an error code 99.</p>
<p>I guess I can try a more recent version of fixes 0.25.</p>