[mythtv-users] Database upgrading failed after update to .27

[Captain Hook]

Looks like I've broken mysql now.  Based on this thread:
http://www.mythtvtalk.com/i-really-need-help-mysql-4553/ I ran the
following:

ALTER TABLE `program` DROP INDEX `title_subtitle_start`

Now I cannot seem to get mysql to start at all.

aaron at MythTV:~$ service mysql status
mysql stop/waiting
aaron at MythTV:~$

aaron at MythTV:~$ sudo service mysql start
start: Job failed to start

I see an "error.log" file in /var/log/mysql but it doesn't seem to have any
information for me as to when I am attempting to start the service, just
upon boot.

Version: '5.5.29-0ubuntu0.12.04.2'  socket: '/var/run/mysqld/mysqld.sock'
 port: 3306  (Ubuntu)
130908 14:54:49 [Note] /usr/sbin/mysqld: Normal shutdown

130908 14:54:49 [Note] Event Scheduler: Purging the queue. 0 events
130908 14:54:51 [Warning] /usr/sbin/mysqld: Forcing close of thread 302
 user: 'mythtv'

130908 14:54:51  InnoDB: Starting shutdown...
130908 14:54:53  InnoDB: Shutdown completed; log sequence number 21793990
130908 14:54:53 [Note] /usr/sbin/mysqld: Shutdown complete




On Sun, Sep 8, 2013 at 2:34 PM, Captain Hook <captainhookzero at gmail.com>wrote:

> I attempted to update to .27 from .26.  It seems to have updated, however,
> I could not access any recordings from a frontend (complaining about
> database version) and then I noticed that Mythweb wasn't working either
> (blank screen).
>
> I then logged into my backend and tried to open MythTV Backend Setup, only
> to receive a white screen for 5-10 seconds, followed by a message that says
> MythTV needs to upgrade database for my TV schema, from 1315 to 1317.  If I
> select upgrade, it tells me a location of a backup file if the system
> becomes unstable, and then quickly closes, then asks me if I want to start
> the backend.  I enter my password, it then asks about mythfilldatabase.
>
> It still doesn't work, and upon subsequent launches of MythTV Backend
> Setup, I am prompted with the same questions, so it isn't upgrading.
>
> When I look at mythsetup.log, I have this:
>
> Sep  8 14:20:43 MythTV mythtv-setup.real: mythtv-setup[4299]: I
> CoreContext schemawizard.cpp:118 (Compare) Current MythTV Schema Version
> (DBSchemaVer): 1315
> Sep  8 14:20:43 MythTV mythtv-setup.real: mythtv-setup[4299]: E
> CoreContext dbutil.cpp:604 (DoBackup) Backing up database with script:
> '/usr/share/mythtv/mythconverg_backup.pl'
> Sep  8 14:20:49 MythTV mythtv-setup.real: mythtv-setup[4299]: C
> CoreContext dbutil.cpp:625 (DoBackup) Database Backup complete.
> Sep  8 14:20:49 MythTV mythtv-setup.real: mythtv-setup[4299]: C
> CoreContext dbutil.cpp:656 (DoBackup) Backed up database to file:
> '/var/lib/mythtv/db_backups/mythconverg-1315-20130908182043.sql.gz'
> Sep  8 14:20:57 MythTV mythtv-setup.real: mythtv-setup[4299]: C
> CoreContext dbcheck.cpp:402 (performActualUpdate) Upgrading to MythTV
> schema version 1316
> Sep  8 14:20:57 MythTV mythtv-setup.real: mythtv-setup[4299]: E
> CoreContext dbcheck.cpp:417 (performActualUpdate) DB Error (Performing
> database upgrade): #012Query was: ALTER TABLE program ADD INDEX
> title_subtitle_start (title, subtitle, starttime); #012Error was: Driver
> error was [2/1061]:#012QMYSQL: Unable to execute query#012Database error
> was:#012Duplicate key name 'title_subtitle_start'#012 #012new version: 1316
> Sep  8 14:20:57 MythTV mythtv-setup.real: mythtv-setup[4299]: E
> CoreContext dbcheck.cpp:502 (UpgradeTVDatabaseSchema) Database schema
> upgrade failed.
> Sep  8 14:20:57 MythTV mythtv-setup.real: mythtv-setup[4299]: E
> CoreContext main.cpp:553 (main) Couldn't upgrade database to new schema.
>
>
> Before I restore my snapshot of my backend, any thoughts on a quick fix?
>  Fall TV season is around the corner and I don't want to mess with this too
> much.
>
> Thanks for any assistance provided.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130908/c51c80c4/attachment.html>