MySQL Forums
Forum List  »  General

Re: mysqld got signal 6 ; / [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files.
Posted by: NOT_FOUND NULL !
Date: May 08, 2019 05:31AM

Additional info:

[root@mysql01 mysql]# cat /etc/my.cnf
[mysqld]
# skip-grant-table
# innodb_force_recovery=6
# innodb_purge_threads=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
transaction-isolation=READ-COMMITTED
user=mysql
# binlog_format=ROW
binlog_format=mixed
symbolic-links = 0
innodb_log_checksums=on

key_buffer_size = 8M
max_allowed_packet = 32M
thread_stack = 256K
thread_cache_size = 64
query_cache_limit = 8M
query_cache_size = 64M
query_cache_type = 1

max_connections = 550
# expire_logs_days = 10
# max_binlog_size = 100M

# log_bin should be on a disk with enough free space.
# Replace '/var/lib/mysql/mysql_binary_log' with an appropriate path for your
# system and chown the specified folder to the mysql user.
log_bin=/var/lib/mysql/mysql_binary_log

# In later versions of MySQL, if you enable the binary log and do not set
# a server_id, MySQL will not start. The server_id must be unique within
# the replicating group.
server_id=1

read_buffer_size = 2M
sort_buffer_size = 8M
read_rnd_buffer_size = 8M
sort_buffer_size = 8M
join_buffer_size = 8M

# InnoDB settings
innodb_autoinc_lock_mode=2
# innodb_flush_log_at_trx_commit=0
innodb_flush_log_at_trx_commit=2

innodb_file_per_table = 1
innodb_log_buffer_size = 64M
# innodb_buffer_pool_size=122M
# innodb_buffer_pool_size = 1G
innodb_buffer_pool_size = 128M
innodb_thread_concurrency = 8
innodb_flush_method = O_DIRECT
innodb_log_file_size = 512M

# Cluster Specific Changes
bind-address=192.168.0.126
default_storage_engine=innodb

# Replication Specifics
wsrep_provider=/usr/lib64/galera-3/libgalera_smm.so
wsrep_provider_options="gcache.size=300M; gcache.page_size=300M"
wsrep_cluster_name="galera_cluster1"
wsrep_cluster_address="gcomm://192.168.0.126,192.168.0.107,192.168.0.114"
wsrep_sst_method=rsync
wsrep_node_address="192.168.0.126"
wsrep_node_name="mysql01"

# https://stackoverflow.com/questions/25852239/collation-utf8-general-ci-is-not-valid-for-character-set-latin1
character-set-server = utf8
collation-server = utf8_general_ci

[mysql_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

sql_mode=STRICT_ALL_TABLES

[root@mysql01 mysql]# rpm -aq|grep -Ei mysql
mysql-wsrep-devel-5.7-5.7.25-25.17.el7.x86_64
mysql-wsrep-libs-compat-5.7-5.7.25-25.17.el7.x86_64
mysql-wsrep-libs-5.7-5.7.25-25.17.el7.x86_64
mysql-wsrep-5.7-5.7.25-25.17.el7.x86_64
mysql-connector-java-5.1.25-3.el7.noarch
mysql-wsrep-client-5.7-5.7.25-25.17.el7.x86_64
mysql80-community-release-el7-3.noarch
mysql-wsrep-common-5.7-5.7.25-25.17.el7.x86_64
mysql-wsrep-server-5.7-5.7.25-25.17.el7.x86_64
[root@mysql01 mysql]#

Options: ReplyQuote


Subject
Written By
Posted
Re: mysqld got signal 6 ; / [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files.
May 08, 2019 05:31AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.