Modify
Warning Please read the Ticket HowTo before creating or commenting on a ticket. Failure to do so may cause your ticket to be rejected or result in a slower response.

Opened 21 months ago

Closed 20 months ago

Last modified 20 months ago

#10986 closed Bug Report - General (fixed)

Submit hardware profile crash

Reported by: pmb@… Owned by: wagnerrp
Priority: trivial Milestone: 0.26
Component: MythTV - General Version: 0.25-fixes
Severity: low Keywords:
Cc: Ticket locked: no

Description

When I try to submit a hardware profile, I get a crash. I am using Fedora 17. In the user interface, I get "Encountered a problem while submitting your profile." In the frontend stdout I just get:
2012-08-10 13:03:23.204730 I Locking input devices
2012-08-10 13:03:29.673206 I Unlocking input devices

The Fedora crash report is attached, and I think it could be useful. For example:

MythDBError: Could not find database login credentials

I am using "mythfrontend version: fixes/0.25 [0.25.1-2.fc17 (c2c276d)] www.mythtv.org"

Attachments (3)

mythtv.txt (5.1 KB) - added by anonymous 21 months ago.
mythtv-log.txt (23 bytes) - added by pmb@… 21 months ago.
Command output after re-initialising config file
mythtv-log.2.txt (1.7 KB) - added by pmb@… 21 months ago.
I made a mistake, here is the correct file.

Download all attachments as: .zip

Change History (10)

Changed 21 months ago by anonymous

comment:1 Changed 21 months ago by wagnerrp

  • Owner set to wagnerrp
  • Status changed from new to accepted

The Python bindings should be searching for your database credentials in all the same places as mythfrontend. What mysql.txt/config.xml does your frontend report it is reading on startup in its logs?

Changed 21 months ago by pmb@…

Command output after re-initialising config file

comment:2 follow-up: Changed 21 months ago by pmb@…

OK I may have found the problem: /home/fa2k/.mythtv/config.xml is completely empty. When I deleted it, it was re-generated, and that error went away.

The next error was: "MythTV.exceptions.MythBEError: Failed to connect to backend at blackhole.lan.fa2k.net:6543". Mythtv only listens on IPv6, but for some reason that address resolves to my IPv4 address as well, and that was used in the submission script. This is arguably a configuration issue on my part, and I set up a proxy to fix this.

With all that in place, I get the attached error.

Changed 21 months ago by pmb@…

I made a mistake, here is the correct file.

comment:3 in reply to: ↑ 2 Changed 21 months ago by wagnerrp

Replying to pmb@…:

The next error was: "MythTV.exceptions.MythBEError: Failed to connect to backend at blackhole.lan.fa2k.net:6543".

When not given a specific address to connect to, the Python bindings will connect to the master backend at the IP address defined for the master backend in the database. The fact that it is complaining about being unable to connect to a hostname means you have incorrectly specified a hostname in mythtv-setup where it asks for an IP.

comment:4 Changed 21 months ago by wagnerrp

The error listed in the attached log merely shows the hardware profiler is not robust against an invalid display profile. I'm not sure how you would have gotten a display profile with no preferred decoder.

comment:5 Changed 21 months ago by pmb@…

Good that it's understood. I have messed with the profiles a lot, but I don't have an empty profile in the UI.

comment:6 Changed 20 months ago by Raymond Wagner <rwagner@…>

  • Resolution set to fixed
  • Status changed from accepted to closed

In b5e154fe816742b18adcc73e409044f06a4b723e/mythtv:

Make hardware profiler ignore errors and continue.

This wraps the various subsets of MythTV data extracted from the
database with a 'try' block, allowing it to ignore and proceed if one of
the subsets fails due to bad data or an unexpected configuration.

Fixes #10986

comment:7 Changed 20 months ago by wagnerrp

  • Milestone set to 0.26
  • Version set to 0.25-fixes

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'new'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.