[mythtv-users] "Filesystem Info cache is empty"
Bob Long
bob at oblong.com.au
Fri Oct 17 01:50:48 UTC 2014
Michael T. Dean wrote on 17/10/14 11:10:
> On 10/16/2014 12:33 PM, Mike Rice wrote:
>> On Thu, Oct 16, 2014 at 4:14 AM, Bob Long wrote:
>>> MythTV 0.25
>>>
>>> The mythbackend.log reports numerous messages like these:
>>>
>>> Oct 16 21:06:08 mythbox2 mythbackend[6680]: E Expire autoexpire.cpp:161
>>> (CalcParams) AutoExpire: Filesystem Info cache is empty, unable to
>>> calculate necessary parameters.
>>>
>>> I've searched and found others ask about this error, but I've not found
>>> an answer.
>>
>> For me this happened when multiple copies of mythbackend were
>> (unintentionally) running. The scripts I was using on a different distro
>> to kill and restart the backend wasn't killing the backend but was
>> starting
>> a new one. If you have more than one mythbackend running kill them
>> all and
>> start one and see if you still get that error.
>
> That could cause it. Similarly, running a tunerless backend could cause
> it.
Definitely not tunerless (1 x HDHomerun + 1 x dual PCI).
So, does this indicate backend is running twice?
-----
mythuser at mythbox2:~$ ps aux|grep -i mythbackend
mythtv 323 6.7 2.1 2856460 86460 ? Sl Oct16 89:24
/usr/bin/mythbackend --syslog local7 --user mythtv
root 6679 0.0 0.0 4400 600 ? Ss Oct13 0:00 sh -c
/usr/bin/mythbackend --syslog local7 --user mythtv
mythtv 6680 0.3 0.8 2207176 35328 ? Sl Oct13 16:32
/usr/bin/mythbackend --syslog local7 --user mythtv
mythuser 10366 0.0 0.0 13592 884 pts/3 S+ 11:42 0:00 grep
--color=auto -i mythbackend
-----
If so, what is likely to cause that?
What else should I look for in the logs?
I know another issue is that on boot, with the frontend in the startup
applications, the frontend says that it can't connect to the backend for
a short while (30 sec or so?).
Could that be related? If so, I guess that has to be investigated first.
Network is wired.
--
Bob Long
More information about the mythtv-users
mailing list