[mythtv-users] Trunk Broken? MainServer: HandleRemoteEncoder(cmd GET_STATE) Unknown encoder: 1

[Christopher Kerr]

Hi all,

So, I've been running trunk for a while (from the JYA repos) and its
generally been pretty good. However, since I updated on Sunday (and
again today, in an effort to fix it), everything has gone rather
wrong.

I'm now running trunk 24692. However, I'm having some trouble with the
tuners on my remote backend - basically, if I try to watch LiveTV, the
frontend gives me the usual error about all inputs being used despite
there being no recordings.

Examination of the master backend logs shows up these errors:

2010-05-18 01:54:52.491 MainServer: HandleRemoteEncoder(cmd GET_STATE)
Unknown encoder: 1
2010-05-18 01:54:52.522 MainServer: HandleRemoteEncoder(cmd
GET_SLEEPSTATUS) Unknown encoder: 1
2010-05-18 01:54:52.572 MainServer: HandleRemoteEncoder(cmd GET_STATE)
Unknown encoder: 2
2010-05-18 01:54:52.623 MainServer: HandleRemoteEncoder(cmd
GET_SLEEPSTATUS) Unknown encoder: 2
2010-05-18 01:54:52.714 MainServer: HandleRemoteEncoder(cmd GET_STATE)
Unknown encoder: 3
2010-05-18 01:54:52.756 MainServer: HandleRemoteEncoder(cmd
GET_SLEEPSTATUS) Unknown encoder: 3

Logs on the slave backend show no issues, and monitoring the slave
backend on port 6544 indicates that the tuners are fine on that end.

In short, for some reason, my slave backend seems unable to properly
inform the master of its available tuners.

Things I've tried:

Dumping the whole database and setting up from scratch - didn't help
Rebooting - didn't help
Checked version numbers - all frontend and backend packages are version 24692.

If anyone can shed some light on this, it'd be greatly appreciated.

- Chris

BTW, what is the correct method for setting up a dummy tuner under
0.23+? I have a tunerless master backend, and at the moment the fake
tuner attached to it is fairly hack-ish.