MCC hangs with Jamu-related error on frontend (new install)

Bug #647367 reported by Tony Sleeckx on 2010-09-25
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mythbuntu-common (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: mythbuntu-control-centre

I have done a clean install of Mythbuntu 10.04 on an Acer Revo, and have selected frontend-only during install.

When I launch MCC I get errors related to Jamu and backend:

tony@myth-front:~$ mythbuntu-control-centre
WARNING: With any -M option Jamu and its MCC plugin must be run on a MythTV backend,
Error(Could not find setting 'BackendServerIP' on host 'myth-front')
CRITICAL: Jamu configuration plugin must be run on a MythTV backend. Local host (myth-front) is not a MythTV backend.

WARNING: Error loading plugin <class 'jamuconfig.JamuconfigPlugin'>
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/MythbuntuControlCentre/plugin.py", line 75, in find_plugin_instances
    self._instances[plugin] = plugin()
  File "/usr/share/mythbuntu/plugins/python/jamuconfig.py", line 100, in __init__
    raise JamuconfigPlugin_error(errormsg)
JamuconfigPlugin_error: Jamu configuration plugin must be run on a MythTV backend. Local host (myth-front) is not a MythTV backend.

Reading package lists... Done
Building dependency tree
Reading state information... Done

When I try to change the SQL pin for remote access to the backend the MCC GUI hangs with these errors in the terminal:

Traceback (most recent call last):
  File "/usr/bin/mythbuntu-control-centre", line 264, in summaryApply
    plugin.user_scripted_changes(self.reconfigure_user[item])
  File "/usr/share/mythbuntu/plugins/python/mysql_configuration.py", line 161, in user_scripted_changes
    if item == "securitypin":
NameError: global name 'item' is not defined

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mythbuntu-control-centre 0.62-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Sep 25 10:39:48 2010
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: mythbuntu-control-centre

Tony Sleeckx (tony-sleeckx) wrote :
Mario Limonciello (superm1) wrote :

Wow this actually looks like a huge oversight that lasted for quite a while.

I think this patch should fix the problem, could you verify?

affects: mythbuntu-control-centre (Ubuntu) → mythbuntu-common (Ubuntu)
Tony Sleeckx (tony-sleeckx) wrote :

Thanks for the very fast reaction.

another error this time:

Traceback (most recent call last):
  File "/usr/bin/mythbuntu-control-centre", line 264, in summaryApply
    plugin.user_scripted_changes(self.reconfigure_user[item])
  File "/usr/share/mythbuntu/plugins/python/mysql_configuration.py", line 165, in user_scripted_changes
    self.mysql.read_xml()
TypeError: read_xml() takes exactly 2 arguments (1 given)

and the errors about Jamu and backend are still there.

doug (r-d-vaughan) wrote :

The Jamu error is solely a configuration issue. Jamu can only be run on a MythTV backend. When Jamu starts it gets the machines IP address and hostname then checks the MythTV database to see if that IP address is included in the "settings" table "BackendServerIP" and the matching "hostname".
So either there is no such record or the "hosts" file does not have a hostname with the machines IP address. In any event the only down side of this error is that the Jamu MCC plugin will not show up in the MCC and Jamu cannot be run on the machine in question.
The MCC will not hang due to this error.

Tony Sleeckx (tony-sleeckx) wrote :

I understand that Jamu can only be run on the backend, and that it is unrelated to the hanging. But:

a) why does does it try to start on a machine that has never been installed as a backend?
b) why does it show up during start of MCC, and complains about an -M option that I have not even added in the command?

Is there somewhere a default option defined for MCC?

tags: added: patch
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mythbuntu-common - 0.55-0ubuntu1

---------------
mythbuntu-common (0.55-0ubuntu1) natty; urgency=low

  * Fix the logic for modifying the security pin (LP: #647367)
  * Fix the security pin check to support 0.24 backends.
  * Rebuild for python 2.7 transition. (LP: #712021)
 -- Mario Limonciello <email address hidden> Wed, 02 Feb 2011 17:55:26 -0600

Changed in mythbuntu-common (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Patches