[mythtv-users] Automatically running Mythfilldatabase
gravityhammer at gmail.com
Mon Dec 21 02:28:16 UTC 2009
On Sun, Dec 20, 2009 at 3:41 PM, Michael T. Dean
<mtdean at thirdcontact.com> wrote:
> On 12/20/2009 01:32 PM, Phil Bridges wrote:
>> On Sun, Dec 20, 2009 at 1:26 PM, Phil Bridges wrote:
>>> I do see a mythfilldatabase process still running in ps:
>>> ~ # ps ax|grep myth
>>> 9969 pts/7 S+ 0:00 tail -f /var/log/mythtv/mythbackend.log
>>> 11019 ? Ssl 7:15 /usr/bin/mythbackend --verbose
>>> important,general --logfile /var/log/mythtv/mythbackend.log
>>> 13020 ? SNl 0:13 /usr/bin/mythfilldatabase
>>> 13174 pts/1 R+ 0:00 grep --colour=auto myth
>>> I've had everything shut down over the past few days due to my
>>> firewire problems, and it still doesn't seem to be doing right.
>> Huh. I just noticed this (in my mythbackend log, after the lines I
>> copied above):
>> 2009-12-20 11:57:16.834
>> | Attempting to contact the master backend for rescheduling. |
>> | If the master is not running, rescheduling will happen when |
>> | the master backend is restarted. |
>> 2009-12-20 11:57:16.839 MythContext: Connecting to backend server:
>> 192.168.1.50:6543 (try 1 of 1)
>> 2009-12-20 11:57:16.840 Using protocol version 50
>> 2009-12-20 11:57:16.841 MainServer::ANN Monitor
>> 2009-12-20 11:57:16.842 adding: strongsad as a client (events: 0)
>> 2009-12-20 11:57:16.843 MainServer::ANN Monitor
>> 2009-12-20 11:57:16.843 adding: strongsad as a client (events: 1)
>> 2009-12-20 11:57:16.845 Reschedule requested for id -1.
>> 2009-12-20 11:57:16.845 Received a remote 'Clear Cache' request
>> QMutex::unlock: mutex lock failure:
>> 2009-12-20 11:57:16.850 mythfilldatabase run complete.
>> 2009-12-20 11:57:16.852 DataDirect: Deleting temporary files
>> I'd bet that mutex lock failure has something to do with the issue.
> That's happening late enough that it shouldn't be a problem--it's
> actually happening at exit because we're exiting. It is an issue that
> will be fixed, but it's extremely low priority as it has no adverse effects.
> The hung process is most likely causing issues (and is likely due to
> some known, but not-yet-fixed myth_system() issues).
> mythtv-users mailing list
> mythtv-users at mythtv.org
I also noticed that now, every 10 minutes, I have this in my backend log:
2009-12-20 21:21:59.617 mythfilldatabase still running, skipping checks.
Huh. Killing my mythfilldatabase process causes it to run again.
More information about the mythtv-users