[couch potatoe]

Hi Folks, title says it all really...

I've been running Kodi (Helix and Frodo) with a centralised database on my ReadyNAS 1100 for a couple of years now (with media being accessed on the same nas using nfs shares) without any problems from both Windows 7 machines and Pi's.

The ReadyNAS reports its mysql version as: mysql Ver 14.12 Distrib 5.0.24a, for unknown-linux-gnu (sparc) using readline 4.3

I've just upgraded Kodi to 15.0 on my Windows 7 64 bit machine and set up my advancedsettings.xml as used for 14.2.

It would appear that when Kodi starts up it creates the MyVideos93 database and promptly crashes.

A tail of the mysql.log files looks like this: -

Code:

9 Query       CREATE TABLE MyVideos93.directorlinkmovie LIKE directorlinkmovie
9 Query       INSERT INTO MyVideos93.directorlinkmovie SELECT * FROM directorlinkmovie
9 Query       CREATE TABLE MyVideos93.directorlinkmusicvideo LIKE directorlinkmusicvideo
9 Query       INSERT INTO MyVideos93.directorlinkmusicvideo SELECT * FROM directorlinkmusicvideo
9 Query       CREATE TABLE MyVideos93.directorlinktvshow LIKE directorlinktvshow
9 Query       INSERT INTO MyVideos93.directorlinktvshow SELECT * FROM directorlinktvshow
9 Query       CREATE TABLE MyVideos93.episode LIKE episode
9 Query       INSERT INTO MyVideos93.episode SELECT * FROM episode
9 Query       CREATE TABLE MyVideos93.files LIKE files
9 Query       INSERT INTO MyVideos93.files SELECT * FROM files

Full log at http://xbmclogs.com/p1uljmuzq

And the console running the mysql daemon on the nas throws the following...

Code:

Version: '5.0.24a-Debian_3.infrant1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Infrant ReadyNAS distribution mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=16384
read_buffer_size=131072
max_used_connections=2
max_connections=20
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 43535 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Anyone got any bright ideas how to fix this?

TIA

Andy B.