<br><div class="gmail_quote">On 4 October 2010 12:14, Richard Morton <span dir="ltr"><<a href="mailto:richard.e.morton@gmail.com">richard.e.morton@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<p>Have you upgraded the master backend or just a slave backend, all systems must be running the same version.</p>
<p>Make sure you have run mythsetup on the master backend to have the db updated, then once that is done make sure all the front ends are run (assuming different plugins are installed on different frontends) to get the rest of the updates done.<br>
</p></blockquote><div><br></div><div>Thanks for the suggestions.</div><div><br></div><div>I only have one backend server and I have run mythtv-setup (several times!). I have also checked for 'wacky' things like whether there could be two different instances of the backend both running somewhere (there aren't!) </div>
<div><br></div><div>I'm totally puzzled by how the same front end binary running on two machines can behave differently. I have removed and re-installed all of the front-end packages on both machines, but to no avail. I can only guess that there must be a configuration file somewhere that is corrupt or that hasn't been updated correctly and that isn't being refreshed by a remove/reinstall of the packages, but I'm really struggling to know where to look - even whether it is likely to be on the backend or the frontend(s).</div>
<div><br></div><div>George</div><div><br></div></div>