Jo, habe den Root mal neu aufgesetzt.
Versuche nun Mysql 5.6 auf FreeBSD 10 zu installieren x.x
Ich editiert's dann rein.
Wenn ich mich in
Navicat einloggen will:
[Only registered and activated users can see links. Click Here To Register...]
Wenn ich mich in Putty mit
mysql -p einloggen will:
Code:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
Mysql ist gestartet & in der rc.conf eingetragen
Wenn ich den
Server starten will kommt folgendes:
Code:
mysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
cannot open direct sql connection to host: localhost user: mt2 db: common
cannot start server while no common sql connected
Die
.err Datei sagt:
Code:
141116 14:18:56 mysqld_safe mysqld restarted
2014-11-16 14:18:56 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-11-16 14:18:56 5374 [Note] Plugin 'FEDERATED' is disabled.
2014-11-16 14:18:56 5374 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-16 14:18:56 5374 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-16 14:18:56 5374 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-11-16 14:18:56 5374 [Note] InnoDB: Memory barrier is not used
2014-11-16 14:18:56 5374 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-16 14:18:56 5374 [Note] InnoDB: Using CPU crc32 instructions
2014-11-16 14:18:56 5374 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-11-16 14:18:56 5374 [Note] InnoDB: Completed initialization of buffer pool
2014-11-16 14:18:56 5374 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-16 14:18:56 5374 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1589260
2014-11-16 14:18:56 5374 [Note] InnoDB: Database was not shutdown normally!
2014-11-16 14:18:56 5374 [Note] InnoDB: Starting crash recovery.
2014-11-16 14:18:56 5374 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-11-16 14:18:56 5374 [Note] InnoDB: Restoring possible half-written data pages
2014-11-16 14:18:56 5374 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1593653
2014-11-16 14:18:56 5374 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-11-16 14:18:57 5374 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-16 14:18:57 5374 [Note] InnoDB: Waiting for purge to start
2014-11-16 14:18:57 5374 [Note] InnoDB: 5.6.21 started; log sequence number 1593653
2014-11-16 14:18:57 5374 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-16 14:18:57 5374 [Note] IPv6 is available.
2014-11-16 14:18:57 5374 [Note] - '::' resolves to '::';
2014-11-16 14:18:57 5374 [Note] Server socket created on IP: '::'.
13:18:57 UTC - mysqld got signal 11 ;
[B]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.[/B]
key_buffer_size=8388608
read_buffer_size=131072
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 = 68194 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
141116 14:18:57 mysqld_safe mysqld restarted
Kann es eventuell an den Libs liegen?!
Sehet: "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."
