[mythtv-commits] Ticket #2084: Channel table seems to get corrupted either over time or after scan

[MythTV]

#2084: Channel table seems to get corrupted either over time or after scan
-----------------------------------+----------------------------------------
 Reporter:  tim at wheresrover.co.uk  |        Owner:  danielk 
     Type:  defect                 |       Status:  reopened
 Priority:  minor                  |    Milestone:  0.20    
Component:  mythtv                 |      Version:  head    
 Severity:  medium                 |   Resolution:          
-----------------------------------+----------------------------------------
Changes (by tharding at cs.utah.edu):

  * status:  closed => reopened
  * resolution:  invalid =>

Comment:

 Replying to [comment:8 danielk]:
 > No response to questions.

 Sorry, I just got back from vacation :)

 > Tharding, what is your hardware configuration? In the capturecard table
 it looks

 I have two cards, the first card is an analog BT based card. The second
 card is a DVB card (ATSC).

 > like you only have a single analog card defined, but it the logs it
 looks like
 > you have a DVB card with an analog subcard defined. Did you maybe not
 restart
 > the backend after the last time you ran mythtv-setup?

 In mythtv-setup both cards are shown, and at that time I had not done a
 channel scan, I just used the listing from DataDirect. The log is from the
 backend while it was running after having run mythtv-setup.

 I think the problem in my setup was that the dtv_multiplex table had no
 data. I was able to fix my problem by deleting all of the channels for the
 DVB card from the database. Then do a channel scan. After doing the
 channel scan, and importing the schedule data from DataDirect the DVB card
 worked fine.

 There seems to be two problems. Importing the channel list from DataDirect
 does not provide enough information to tune my DVB card (no info in the
 dtv_multiplex table).
 The second problem appears to be if the backend cannot tune to a DVB
 channel, it will still try and add an entry into the recorded table even
 though no data was captured, and this entry appears to have a NULL chanid.
 My guess is chanid is a indexed column, so that is why this is not
 allowed. Then the backend continues in an infinite loop trying to add this
 row.

 Durring all of this, the frontend (running on a seperate machine) has
 dropped back to the main menu, and any attempts to access the backend
 indicate the backend is not responding.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/2084#comment:9>
MythTV <http://www.mythtv.org/>
MythTV