Ben een aantal dagen bezig met het installeren van Mysql (ULI) en ik blijf tegen problemen aanlopen. Heb het (hele?) internet af-ge-googled maar kom er niet uit. Uiteindelijk toch maar hier de vraag gesteld. FFP0.7, ix4-300d, doel van Mysql is het indexeren van beeld en geluid tbv PI met XBMC.
Ik blijf last houden van een mysql.sock issue- deze file nergens te vinden en uiteraard loopt ook mysql hierop vast.
Can't connect to local MySQL server through socket '/ffp/var/run/mysql/mysql.sock
Van alles geprobeerd, oa mysql opnieuw geinstalleerd, met chmod rechten aangepast maar niets helpt.
De errorlog zegt het volgende:
140118 07:41:39 mysqld_safe Starting mysqld daemon with databases from /srv/mysql/datadir
140118 7:41:39 InnoDB: The InnoDB memory heap is disabled
140118 7:41:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140118 7:41:39 InnoDB: Compressed tables use zlib 1.2.6
140118 7:41:40 InnoDB: Initializing buffer pool, size = 16.0M
140118 7:41:40 InnoDB: Completed initialization of buffer pool
140118 7:41:40 InnoDB: highest supported file format is Barracuda.
140118 7:41:40 InnoDB: Assertion failure in thread 1074548736 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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/...cing-innodb-recovery.html
InnoDB: about forcing recovery.
15:41:40 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=0
max_threads=151
thread_count=0
connection_count=0
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.
Hoop dat iemand raad weet!
grt,
Hugo