[doug]

Everyone can ignore this...through mucking around in MySQL Workbench, creating and dropping databases, changing permissions on the database files in WinSCP , it finally worked it's way through to creating a new database when upgrading. Ugh! I have no idea what really fixed it.


-----------------------------

I thought I would take 16.0RC3 for a spin and it looks good. This may be a bug or just a result of trying to run two databases, but here is what happens:

I have a MariaDB running on an unRaid docker which has my shared databases. When I upgraded to 16.0, the database upgrade starts, but the databases are not fully created. So when I restart Kodi I get a crash. It happens when I try to start the upgrade from a Windows based box or an RPi2. Is this just a function of using MariaDB and I'll have to export or recreate my databases to upgrade?

In searching the forum I see a previous thread where someone has a similar problem. Unfortunately, I don't know enough about sql to investigate if this is what is happening to me.

The details:

This is the log from the upgrade. You can see the database upgrade for Music and Videos has failed:
http://pastebin.com/72jVifPm

Here is my mysqlsafe.log from during the upgrade:

Code:

160211 14:39:03  InnoDB: Warning: trying to init to the tablespace memory cache
InnoDB: a tablespace 482 of name './MyMusic56/album.ibd',
InnoDB: but a tablespace 480 of the same name
InnoDB: already exists in the tablespace memory cache!
InnoDB: We assume that InnoDB did a crash recovery, and you had
InnoDB: an .ibd file for which the table did not exist in the
InnoDB: InnoDB internal data dictionary in the ibdata files.
InnoDB: We assume that you later removed the .ibd and .frm files,
InnoDB: and are now trying to recreate the table. We now remove the
InnoDB: conflicting tablespace object from the memory cache and try
InnoDB: the init again.
160211 14:39:03  InnoDB: Warning: trying to init to the tablespace memory cache
InnoDB: a tablespace 483 of name './MyVideos99/actor.ibd',
InnoDB: but a tablespace 481 of the same name
InnoDB: already exists in the tablespace memory cache!
InnoDB: We assume that InnoDB did a crash recovery, and you had
InnoDB: an .ibd file for which the table did not exist in the
InnoDB: InnoDB internal data dictionary in the ibdata files.
InnoDB: We assume that you later removed the .ibd and .frm files,
InnoDB: and are now trying to recreate the table. We now remove the
InnoDB: conflicting tablespace object from the memory cache and try
InnoDB: the init again.