MYSQL Tuner error 256
Hey guys doing some optimizing and noticed that I am not getting some weird errors on the mysql tuner.
MySQLTuner 1.6.9 Here is my cnf
I have looked around why this code is happening. It means that it cannot connect to the database. I am running the scrip as root. Any ideas guys.
FAIL Execute SQL / return code: 256
[!!] failed to execute: SHOW TABLE STATUS FROMySQLTuner 1.6.9 Here is my cnf
[mysqld]
bind-address=127.0.0.1
max_connections=100
max_user_connections=75
query_cache_size=48M
query_cache_limit=4M
skip-external-locking
key_buffer_size=64M
max_allowed_packet=1073741824
table_open_cache=11k
table_definition_cache=4096
sort_buffer_size=512K
net_buffer_length=8K
read_buffer_size=256K
read_rnd_buffer_size=512K
myisam_sort_buffer_size=16M
wait_timeout=20000
interactive_timeout=22000
query_cache_type=0
innodb_file_per_table=1
innodb_buffer_pool_instances=1
tmp_table_size=160M
max_heap_table_size=160M
thread_pool_size=24
thread_cache_size=4
join_buffer_size=3M
innodb_buffer_pool_size=400M
# This setting ensures that aio limits are not exceeded
# (default is 65536, each instance of mysql takes 2661 with this enabled)
innodb_use_native_aio=0
open_files_limit=15020
default-storage-engine=InnoDB
# LOGGING #
slow_query_log= 1
long_query_time = 1
slow_query_log_file="/var/lib/mysql/slow.log"
# SAFETY #
low_priority_updates=1
concurrent_insert=ALWAYS
local-infile=0
I have looked around why this code is happening. It means that it cannot connect to the database. I am running the scrip as root. Any ideas guys.
-
I have opened a support ticket 8363567 mysqltuner was making the mysql crash. 0 -
Hello, You may find this thread helpful if the MySQL tuning application you are using isn't working and you'd like to try a different one: mysqlmymonlite.sh server stats gathering tool for cPanel Server Thank you. 0 -
Same thing as before, I found the database is crashing when be queried. So not sure, hopefully the ticket can help me figure it out. Thank you though 0 -
Hello, To update, it looks like removing a corrupted database that was no longer required addressed the issue. Thank you. 0
Please sign in to leave a comment.
Comments
4 comments