[mythtv-commits] Ticket #8606: Backend deadlocked after database error when updating program listings from EIT
MythTV
noreply at mythtv.org
Wed Dec 8 21:18:15 UTC 2010
#8606: Backend deadlocked after database error when updating program listings from
EIT
---------------------------------------+----------------------------
Reporter: malcolm.parsons@… | Owner: ijr
Type: defect | Status: closed
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.23-fixes
Severity: high | Resolution: invalid
Keywords: | Ticket locked: 0
---------------------------------------+----------------------------
Comment (by spidersddd@…):
I am having very similar problems as this my mythweb stops responding and
I have had several hard locks on my frontend that require a reboot. If
there is anything I can do to help get this resolved am more then happy
to do it.
Troy K.
email: spidersddd at gmail.com
Replying to [ticket:8606 malcolm.parsons@…]:
> I'm using MythTV 0.23.0+fixes25119-0ubuntu0+mythbuntu2
>
> I've been seeing random backend deadlocks, where the frontend lists no
recorded programmes, the backend doesn't record anything, and the
"Upcoming Recordings" and "Backend Status" pages in MythWeb don't load.
>
> Looking at the logs, there is a database error in the hour before the
deadlock is noticed:
>
> 2010-06-25 12:55:04.036 DB Error (change_program):
> Query was:
> UPDATE program SET starttime = ?, endtime = ? WHERE chanid =
> ? AND starttime = ?
> Bindings were:
> :CHANID=3003, :NEWEND=2010-06-29T02:45:00,
:NEWSTART=2010-06-29T01:08:00,
> :OLDSTART=2010-06-29T00:35:00
> Driver error was [2/1062]:
> QMYSQL3: Unable to execute statement
> Database error was:
> Duplicate entry '3003-2010-06-29 01:08:00-0' for key 'PRIMARY'
>
> Is the EIT collection thread leaving a mutex locked when this error
happens?
--
Ticket URL: <http://code.mythtv.org/trac/ticket/8606#comment:6>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list