mariadb pods failed to start

Bug #1708610 reported by Lan Qi song
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
kolla-kubernetes
New
Undecided
Unassigned

Bug Description

I started mariadb through this commmand from quick start guide:
helm install --debug kolla-kubernetes/helm/service/mariadb --namespace kolla --name mariadb --values ./cloud.yaml

But mariadb failed to start with error logs in /var/log/kolla/mariadb/mariadb.log :
170804 2:57:56 [Note] WSREP: CRC-32C: using hardware acceleration.
  0804 2:57:56 [ERROR] WSREP: Bad value for 'node_address': '0.0.0.0': 22 (Invalid argument)
▽ at galera/src/replicator_smm_params.cpp:InitConfig():85
170804 2:57:56 [ERROR] WSREP: wsrep::init() failed: 7, must shutdown
170804 2:57:56 [ERROR] Aborting

The /etc/my.cnf file:
[client]
default-character-set = utf8

[mysql]
default-character-set = utf8

[mysqld]
bind-address = 0.0.0.0
port = 3306
log-error = /var/log/kolla/mariadb/mariadb.log
log-bin = mysql-bin
binlog_format = ROW
default-storage-engine = innodb
innodb_autoinc_lock_mode = 2
collation-server = utf8_general_ci
init-connect = SET NAMES utf8
character-set-server = utf8
datadir = /var/lib/mysql/
wsrep_cluster_address = gcomm://
wsrep_provider_options = gmcast.listen_addr=tcp://0.0.0.0:4567;ist.recv_addr=0.0.0.0:4568
wsrep_node_address = 0.0.0.0:4567
wsrep_sst_receive_address = 0.0.0.0:4444
wsrep_provider = /usr/lib64/galera/libgalera_smm.so
wsrep_cluster_name = openstack
wsrep_node_name = kolla
wsrep_sst_method = xtrabackup-v2
wsrep_sst_auth = root:8P67A1w9uWURGZXSd9u88W5RimUndOa3RXG2D5FK
wsrep_slave_threads = 4
wsrep_notify_cmd = /usr/local/bin/wsrep-notify.sh
max_connections = 10000
key_buffer_size = 64M
max_heap_table_size = 64M
tmp_table_size = 64M
innodb_buffer_pool_size = 3150M

[server]
pid-file = /var/lib/mysql/mariadb.pid

Lan Qi song (lqslan)
information type: Public → Public Security
information type: Public Security → Public
information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
Maciej (mkasprzyk) wrote :

Hi,
After commenting-out/removing wsrep_node_address everything work's fine.

Revision history for this message
Nikolas Hermanns (nikolas-hermanns) wrote :

I have the same issue:
170929 8:30:13 [Note] /usr/sbin/mysqld (mysqld 10.0.29-MariaDB-wsrep) starting as process 335 ...
170929 8:30:13 [Note] WSREP: wsrep_load(): Galera 25.3.19(r3667) by Codership Oy <email address hidden> loaded successfully.
170929 8:30:13 [Note] WSREP: CRC-32C: using hardware acceleration.
170929 8:30:13 [ERROR] WSREP: Bad value for 'node_address': '0.0.0.0': 22 (Invalid argument)
  at galera/src/replicator_smm_params.cpp:InitConfig():85
170929 8:30:13 [ERROR] WSREP: wsrep::init() failed: 7, must shutdown
170929 8:30:13 [ERROR] Aborting

170929 8:30:13 [Note] /usr/sbin/mysqld: Shutdown complete

170929 08:30:13 mysqld_safe mysqld from pid file /var/lib/mysql/mariadb.pid ended

Revision history for this message
wolf_of_north@sohu.com (wolf-of-north) wrote :

It works run the following command:
$ sed -i 's/wsrep_node_address = 0.0.0.0:4567/#wsrep_node_address = 0.0.0.0:4567/' /etc/kolla/mariadb/galera.cnf

before:
$ kollakube res create configmap \
    mariadb keystone horizon rabbitmq memcached nova-api nova-conductor \
    nova-scheduler glance-api-haproxy glance-registry-haproxy glance-api \
    glance-registry neutron-server neutron-dhcp-agent neutron-l3-agent \
    neutron-metadata-agent neutron-openvswitch-agent openvswitch-db-server \
    openvswitch-vswitchd nova-libvirt nova-compute nova-consoleauth \
    nova-novncproxy nova-novncproxy-haproxy neutron-server-haproxy \
    nova-api-haproxy cinder-api cinder-api-haproxy cinder-backup \
    cinder-scheduler cinder-volume iscsid tgtd keepalived \
    placement-api placement-api-haproxy

Revision history for this message
Kevin Zhao (kevin-zhao) wrote :

could not reproduce with Debian source 5.0.1

Revision history for this message
LYJ (lyj498639133) wrote :

who can you start you mariadb service ,i have a issue: sudo: unable to change to sudoers gid: Operation not permitted. when delopy in openshift.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.