[mythtv-users] BE errors

[Bill Meek]

On 09/12/2013 01:59 PM, Daryl McDonald wrote:
...
 > Ok here is the result of the last command:
>
> daryl at daryl-A780L3C:~$  ps ax | grep mythbackend | grep -v grep
>   2986 ?        Ssl    0:05 /usr/bin/mythbackend --syslog local7 --user mythtv
>   3133 pts/3    Sl+    0:03 /usr/bin/mythbackend
>
> and the status command now shows it is "start/running"
>
> The "/usr/bin/mythbackend" command has been showing the errors I've
> been trying to address recently, but you're right I was attempting to
> use it to start the BE, pointers much appreciated. So now do I need to
> keep looking at and addressing those errors? Scheduled recordings have
> been hit and miss at best lately. Sometimes instead of recording it is
> "tuning", and I am concerned about the status of my
> /dev/dvb/adapter0/frontend0 card, it seems there is a failure to open

Clearly two instances of the backend running. The 1st started by
the system, most likely when the machine powered up (or rebooted,)
and the 2nd started by you on the command line. Don't manually start the
backend unless you *know* it's not running!

To look at errors, just look in your backend's log. It's just another
file. Use whatever tool you like to look at it. As suggested last week,
cat, less, nano or a good choice to look at it in real-time: tailf.

If the error on /dev/dvb/adapter0/frontend0 is in the backend's log
(not the log output from your starting a 2nd instance of it,) then
you truly have a problem. To repeat, be sure the error is in the
backend's log before worrying about it.

-- 
Bill