mysql does not start on boot post-upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Gregory Haynes |
Bug Description
Attempting to do image based overcloud upgrades. Heat stack is updated, nodes are rebuilt with REBUILD_
140701 00:43:42 mysqld_safe Starting mysqld daemon with databases from /mnt/state/
140701 00:43:42 mysqld_safe WSREP: Running position recovery with --log_error=
140701 00:43:45 mysqld_safe WSREP: Recovered position 9baa9bfc-
140701 0:43:45 [Note] WSREP: wsrep_start_
140701 0:43:45 [Note] WSREP: Read nil XID from storage engines, skipping position init
140701 0:43:45 [Note] WSREP: wsrep_load(): loading provider library '/usr/local/
140701 0:43:45 [Note] WSREP: wsrep_load(): Galera 2.10(r175) by Codership Oy <email address hidden> loaded successfully.
140701 0:43:45 [Note] WSREP: Found saved state: 9baa9bfc-
140701 0:43:45 [Note] WSREP: Reusing existing '/mnt/state/
140701 0:43:45 [Note] WSREP: Passing config to GCS: base_host = 10.22.167.75; base_port = 4567; cert.log_conflicts = no; debug = no; evs.inactive_
140701 0:43:45 [Note] WSREP: Assign initial position for certification: 3853, protocol version: -1
140701 0:43:45 [Note] WSREP: wsrep_sst_grab()
140701 0:43:45 [Note] WSREP: Start replication
140701 0:43:45 [Note] WSREP: Setting initial position to 9baa9bfc-
140701 0:43:45 [Note] WSREP: protonet asio version 0
140701 0:43:45 [Note] WSREP: backend: asio
140701 0:43:45 [Note] WSREP: GMCast version 0
140701 0:43:45 [Note] WSREP: (c1f0d0f7-
140701 0:43:45 [Note] WSREP: (c1f0d0f7-
140701 0:43:45 [Note] WSREP: EVS version 0
140701 0:43:45 [Note] WSREP: PC version 0
140701 0:43:45 [Note] WSREP: gcomm: connecting to group 'tripleo-
140701 0:43:45 [Warning] WSREP: (c1f0d0f7-
140701 0:43:48 [Warning] WSREP: no nodes coming from prim view, prim not possible
140701 0:43:48 [Note] WSREP: view(view_
} joined {
} left {
} partitioned {
})
140701 0:43:49 [Warning] WSREP: last inactive check more than PT1.5S ago (PT3.50629S), skipping check
140701 0:44:18 [Note] WSREP: view((empty))
140701 0:44:18 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)
at gcomm/src/
140701 0:44:18 [ERROR] WSREP: gcs/src/
140701 0:44:18 [ERROR] WSREP: gcs/src/
140701 0:44:18 [ERROR] WSREP: gcs connect failed: Connection timed out
140701 0:44:18 [ERROR] WSREP: wsrep::connect() failed: 7
140701 0:44:18 [ERROR] Aborting
140701 0:44:18 [Note] WSREP: Service disconnected.
140701 0:44:19 [Note] WSREP: Some threads may fail to exit.
140701 0:44:19 [Note] /usr/local/
140701 00:44:19 mysqld_safe mysqld from pid file /var/run/
As Greg explained, this is Galera clustering attempting to boostrap the cluster off of itself. This is in place to enable HA database clustering by default, however, its doing nothing for environments single node controllers. Updating /etc/mysql/
Changed in tripleo: | |
importance: | Undecided → High |
assignee: | nobody → Gregory Haynes (greghaynes) |
Changed in tripleo: | |
status: | New → Confirmed |
Changed in tripleo: | |
status: | Confirmed → Fix Released |
Reviewed: https:/ /review. openstack. org/104455 /git.openstack. org/cgit/ openstack/ tripleo- image-elements/ commit/ ?id=75519a3bc8d 26afb3f8ce0068d 769a0095c66672
Committed: https:/
Submitter: Jenkins
Branch: master
commit 75519a3bc8d26af b3f8ce0068d769a 0095c66672
Author: Gregory Haynes <email address hidden>
Date: Wed Jul 2 22:55:04 2014 -0700
Allow single node mysql clusters to restart
We do not allow automatic restarting for mysql clusters due to possible
data loss issues. This is not a problem for single node clusters.
Related-Bug: #1336110 8b60692d866ee33 737e33f87aa
Change-Id: Id41c2fcf960282