<br><br><div class="gmail_quote">On Thu, Sep 13, 2012 at 10:28 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On 09/13/2012 08:26 PM, Matt Emmott wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thursday, September 13, 2012, Joseph Fry wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Try running with '--dd-grab-all'.<br>
<br>
<br>
Nope, same issue. Still no guide data.<br>
</blockquote>
<br>
</blockquote>
Try a reboot. Have seen several similar issues in the past, at least a<br>
few of which were fixed by a reboot.<br>
<br>
One other user had converted his system to static and forgot to set a<br>
DNS server... not sure that is applicable to you.<br>
<br>
______________________________<u></u>_________________<br>
<br>
<br>
Interesting I have the same problem.<br>
When I run it manually from my account it works.<br>
So I created a cronjob to run it nightly but under the mythtv account.<br>
Same problem.<br>
So I removed that cron entry and put it in my account's cron and it all<br>
works.<br>
<br>
I did that as a work around hoping to address the real problem at some<br>
time.<br>
<br>
The reboot did not help me either.<br>
<br>
Good call - I tried su - ing to the mythtv user, then firing up<br>
</blockquote>
/bin/bash and running mythfilldatase. Same issues. I'm open to other ideas,<br>
it stinks coming home with no recordings!<br>
<br>
<br>
</blockquote>
Did anyone get the output of this: mythfilldatabase --dd-grab-all<br>
--nodblog -v file,network --loglevel debug --logpath /tmp<br>
<br>
This is definitely a network or filesystem issue, or an issue with<br>
schedules direct... the logs I have seen so far clearly show failure to<br>
download any listing data.<br>
<br>
</blockquote>
Yes, the output I posted earlier was the result of that. I'll dig into the<br>
results to see if I can web to the addresses in there.<br>
</blockquote>
<br></div></div>
No, that was the output of the "flood the log with useless information in the hope of obscuring any interesting issues" approach using mythfilldatabase -v all.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012-09-13 11:21:10.982153 N Enabled verbose msgs: all<br>
</blockquote>
<br>
Joseph's 2nd request for logs ( <a href="http://www.gossamer-threads.com/lists/mythtv/users/527941#527941" target="_blank">http://www.gossamer-threads.<u></u>com/lists/mythtv/users/527941#<u></u>527941</a> --and, for that matter, his 3rd/the re-request, <a href="http://www.gossamer-threads.com/lists/mythtv/users/527981#527981" target="_blank">http://www.gossamer-threads.<u></u>com/lists/mythtv/users/527981#<u></u>527981</a> ) makes more sense than the first request for -v all logs--because the 2nd approach tries to get specific extra info that may actually be useful (though --nodblog is really unnecessary).<br>
<br>
However, the first log that any user who's having issues should ever post should be a default-verbosity log file--as opposed to excerpts from a log. All we got from you was an excerpt of things you thought might be relevant. Generally, though, a user who doesn't understand why something isn't working is the worst person in the world to decide which information from a log file is relevant. And, since a default-verbosity log file generally has a lot of useful information and isn't too large to post, it's always the best starting point. It's also much better than a log file with too much information that might hide important details and, especially, a log file with so much information that the user cut out some portion of the middle of it, thereby making it hard to figure out what's happening overall. :)<br>
<br>
Mike<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br>Well, the full log was quite a bit of data and it appeared to be pretty redundant. I thought I would post what appeared relevant in the hopes that it would be an easy fix. Further, after posting the much longer logs above, I was notified that it needed to be approved by a mythtv-users moderator before it could be posted. <br>
<br>But back on topic, does anybody have any ideas as to how I could fix this? I'm on day three with no tv listings.<br></div></div>