2013-03-10, 01:35
Hi all
I have installed MySQL on Dlink DNS-320 NAS using fun_plug 0.7. All my movies were scanned and added fine, but now when I try to add more movies XBMC seems to lose connection. After logging using SSH to my NAS I get 'mysqld_safe mysqld_restarted' message.
My advancedsettings.xml
Here is MySQL error.log
And here is [mysqld] section of my.cnf file
Obviusly, XBMC crashes (hangs) and the next time I try to start it crashes, creating a dump. For repairing it I have to delete the XBMCMusic database (?).
Also I tried increasing memory to my.cnf but when I do it MySQL daemon doesn't start... perhaps established values were wrong...
I've read in wiki exists mysql performance article but I could not find it.
Can anyone help me? I can't add anything to my DB
Thanks in advanced
I have installed MySQL on Dlink DNS-320 NAS using fun_plug 0.7. All my movies were scanned and added fine, but now when I try to add more movies XBMC seems to lose connection. After logging using SSH to my NAS I get 'mysqld_safe mysqld_restarted' message.
My advancedsettings.xml
Code:
<advancedsettings>
<pathsubstitution>
<substitute>
<from>special://masterprofile/Thumbnails/</from>
<to>smb://xbmc:xbmcxbmc@Sharecenter/xbmc/userdata/Thumbnails/</to>
</substitute>
</pathsubstitution>
<videodatabase>
<type>mysql</type>
<host>192.168.137.120</host>
<port>3306</port>
<user>xbmc</user>
<pass>xbmc</pass>
<name>XBMCVideo</name>
</videodatabase>
<musicdatabase>
<type>mysql</type>
<host>192.168.137.120</host>
<port>3306</port>
<user>xbmc</user>
<pass>xbmc</pass>
<name>XBMCMusic</name>
</musicdatabase>
<videolibrary>
<importwatchedstate>false</importwatchedstate>
</videolibrary>
</advancedsettings>
Here is MySQL error.log
Code:
23:41:29 UTC - mysqld got signal 6 ;
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=262144
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 49437 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
130309 23:41:29 mysqld_safe Number of processes running now: 0
130309 23:41:29 mysqld_safe mysqld restarted
130309 23:41:29 InnoDB: The InnoDB memory heap is disabled
130309 23:41:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130309 23:41:29 InnoDB: Compressed tables use zlib 1.2.6
130309 23:41:29 InnoDB: Initializing buffer pool, size = 16.0M
130309 23:41:29 InnoDB: Completed initialization of buffer pool
130309 23:41:29 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 65604185
130309 23:41:29 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 65604195
130309 23:41:29 InnoDB: Waiting for the background threads to start
130309 23:41:30 InnoDB: 1.1.8 started; log sequence number 65604195
130309 23:41:30 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130309 23:41:30 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130309 23:41:30 [Note] Server socket created on IP: '0.0.0.0'.
130309 23:41:31 [Warning] 'user' entry 'root@ShareCenter' ignored in --skip-name-resolve mode.
130309 23:41:31 [Warning] 'proxies_priv' entry '@ root@ShareCenter' ignored in --skip-name-resolve mode.
130309 23:41:31 [Note] Event Scheduler: Loaded 0 events
130309 23:41:31 [Note] /ffp/bin/mysqld: ready for connections.
Version: '5.5.28' socket: '/ffp/var/run/mysql/mysql.sock' port: 3306 Source distribution
130309 23:41:31 InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 0:484, should be 0:1055!
130309 23:41:31 InnoDB: Assertion failure in thread 1187906752 in file btr0pcur.c line 437
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
And here is [mysqld] section of my.cnf file
Code:
# The MySQL server
[mysqld]
basedir = /ffp
port = 3306
socket = /ffp/var/run/mysql/mysql.sock
log_error = /srv/mysql/log/error.log
pid-file = /ffp/run/mysqld/mysqld.pid
datadir = /srv/mysql/datadir
tmpdir = /srv/mysql/tmp
key_buffer_size = 16K
max_allowed_packet = 1M
table_open_cache = 4
sort_buffer_size = 64K
read_buffer_size = 256K
read_rnd_buffer_size = 256K
net_buffer_length = 2K
thread_stack = 256K
skip-name-resolve
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (using the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
server-id = 1
# Uncomment the following if you want to log updates
#log-bin=/srv/mysql/binlog/mysql-bin.log
# binary logging format - mixed recommended
#binlog_format=mixed
#expire_logs_days = 10
#max_binlog_size = 100M
# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /srv/mysql/innodb/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /srv/mysql/innodblogdir/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
Obviusly, XBMC crashes (hangs) and the next time I try to start it crashes, creating a dump. For repairing it I have to delete the XBMCMusic database (?).
Also I tried increasing memory to my.cnf but when I do it MySQL daemon doesn't start... perhaps established values were wrong...
I've read in wiki exists mysql performance article but I could not find it.
Can anyone help me? I can't add anything to my DB
Thanks in advanced