Unexpected mysql crash after env cold restart

Bug #1606536 reported by Mikhail Samoylov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel Sustaining
Mitaka
Confirmed
High
Fuel Sustaining

Bug Description

Scenario:
            1. Revert from ceph_ha
            2. Waiting up galera and cinder
            3. Check ceph status
            4. Run OSTF
            5. Destroy and remove osd-node
            6. Check ceph status
            7. Run OSTF
            8. Destroy and remove one compute node
            9. Check ceph status
            10. Run OSTF
            11. Cold restart
            12. Waiting up galera and cinder
            13. Run single OSTF - Create volume and attach it to instance
            14. Run OSTF

Actual result:
Failed on step 12

Expected result:
Test passed

Tags: area-library
Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

After short inspection it seems to be either bug in mysql itself:

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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=1
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76505 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f4def5a0800
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f4dec926e88 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x7f4ded160b7c]
/usr/sbin/mysqld(handle_fatal_signal+0x3c2)[0x7f4deceb15c2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f4debba6340]
/usr/sbin/mysqld(thd_get_ha_data+0xc)[0x7f4decefe54c]
/usr/sbin/mysqld(_Z20thd_binlog_trx_resetP3THD+0x2e)[0x7f4ded10b79e]
/usr/sbin/mysqld(_Z17wsrep_post_commitP3THDb+0xcc)[0x7f4decfeb32c]
/usr/sbin/mysqld(_Z12trans_commitP3THD+0x6f)[0x7f4decfd1dcf]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x38d1)[0x7f4decf3f851]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x3c8)[0x7f4decf439d8]
/usr/sbin/mysqld(+0x508c24)[0x7f4decf43c24]
/usr/sbin/mysqld(_Z19do_handle_bootstrapP3THD+0x111)[0x7f4decf43ff1]
/usr/sbin/mysqld(+0x509060)[0x7f4decf44060]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f4debb9e182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4deb2c147d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f4dc40009f0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

or problem in user table sync (just a year ago galera wasn't sync these tables):

2016-07-26T01:29:50.406124+00:00 err: 2016-07-26 01:29:50 15678 [ERROR] /usr/sbin/mysqld: Table './mysql/user' is marked as crashed and should be repaired
2016-07-26T01:29:50.407359+00:00 err: 2016-07-26 01:29:50 15678 [Warning] Checking table: './mysql/user'
2016-07-26T01:29:50.407904+00:00 err: 2016-07-26 01:29:50 15678 [ERROR] 1 client is using or hasn't closed the table properly
2016-07-26T01:29:50.417927+00:00 err: 2016-07-26 01:29:50 15678 [ERROR] /usr/sbin/mysqld: Table './mysql/db' is marked as crashed and should be repaired
2016-07-26T01:29:50.417927+00:00 err: 2016-07-26 01:29:50 15678 [Warning] Checking table: './mysql/db'
2016-07-26T01:29:50.417927+00:00 err: 2016-07-26 01:29:50 15678 [ERROR] 1 client is using or hasn't closed the table properly

Changed in fuel:
status: New → Confirmed
summary: - Failed ceph_ha_restart test
+ Unexpected mysql crash after env cold restart
Revision history for this message
Alex Schultz (alex-schultz) wrote :

Can we have a diagnostic snapshot or link to the failure to research further? I have a feeling the crash log is not related as there is always one at mysql install time.

no longer affects: fuel/newton
Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Mikhail Samoylov (msamoylov) wrote :

Snapshot

Changed in fuel:
status: Incomplete → Confirmed
Revision history for this message
Alex Schultz (alex-schultz) wrote :
Download full text (3.3 KiB)

I tracked down where this environment was in swarm and the actual error was setting NTP. Mysql was fine according to the snapshot.

016-07-26 01:28:27,528 - INFO environment.py:136 -- Please wait while time on nodes: admin, slave-01, slave-02, slave-03, slave-04 will be synchronized
2016-07-26 01:36:46,043 - INFO fuel_web_client.py:1355 -- Wait for task 600 seconds:
 status running
 name dump
 cluster None
 result {}
 progress 0
 message None
 id 8
 uuid 713246d1-1f3e-48dd-a74a-03e93e3b1fe5
2016-07-26 01:39:16,639 - INFO fuel_web_client.py:1370 -- Task finished. Took 150.584681034 seconds.
 status ready
 name dump
 cluster None
 result {}
 progress 100
 message /api/dump/fuel-snapshot-2016-07-26_01-36-46.tar.gz
 id 8
 uuid 713246d1-1f3e-48dd-a74a-03e93e3b1fe5
2016-07-26 01:39:16,651 - INFO decorators.py:51 -- Saving logs to "/home/jenkins/workspace/9.x.system_test.ubuntu.thread_3/logs/fail_error_ceph_ha_restart-fuel-snapshot-2016-07-26_01-36-46.tar.gz" file
2016-07-26 01:42:03,004 - INFO decorators.py:315 -- <<<<<****************************************************************************************************>>>>>
2016-07-26 01:42:03,004 - INFO decorators.py:316 -- Failed in method error_ceph_ha_restart. Make snapshot: error_ceph_ha_restart
2016-07-26 01:42:03,004 - INFO decorators.py:326 -- You could revert and ssh to master node: [source /home/jenkins/venv-nailgun-tests-2.9/bin/activate; dos.py revert-resume 9.x.system_test.ubuntu.thread_3.7 error_ceph_ha_restart && ssh root@10.109.10.2]
2016-07-26 01:42:03,004 - INFO decorators.py:328 -- <<<<<****************************************************************************************************>>>>>
2016-07-26 01:42:03,031 - ERROR decorators.py:126 -- Traceback (most recent call last):
  File "/home/jenkins/workspace/9.x.system_test.ubuntu.thread_3/fuelweb_test/helpers/decorators.py", line 120, in wrapper
    result = func(*args, **kwargs)
  File "/home/jenkins/workspace/9.x.system_test.ubuntu.thread_3/fuelweb_test/tests/tests_strength/test_restart.py", line 164, in ceph_ha_restart
    'slave-04']))
  File "/home/jenkins/workspace/9.x.system_test.ubuntu.thread_3/fuelweb_test/models/fuel_web_client.py", line 2025, in cold_restart_nodes
    self.environment.sync_time()
  File "/home/jenkins/workspace/9.x.system_test.ubuntu.thread_3/fuelweb_test/models/environment.py", line 137, in sync_time
    new_time = sync_time(self.d_env, nodes_names, skip_sync)
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/devops/helpers/retry.py", line 27, in wrapper
    return func(*args, **kwargs)
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/devops/helpers/ntp.py", line 45, in sync_time
    g_ntp.do_sync_time(g_ntp.other_ntps)
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/devops/helpers/ntp.py", line 134, in do_sync_time
    .format(self.report_not_synchronized(ntps)))
TimeoutError: Time on nodes was not set with 'ntpdate':
[(u'slave-04', "Execution of the command 'ntpdate -p 4 -t 0.2 -bu 10.109.11.8\n' failed on ...

Read more...

Revision history for this message
Alex Schultz (alex-schultz) wrote :

So marking this as a duplicate of Bug 1572521

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.