MySQL Forums
Forum List  »  MySQL Query Browser

mysqldump command failing with crash
Posted by: shamik de
Date: June 28, 2016 05:51AM

Hi Experts,
I need advice for following issue. I am using following version of MySQL on Linux.

mysql> show variables like 'version';
| Variable_name | Value |
| version | 5.7.10-log |
1 row in set (0.00 sec)

LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 6.6 (Final)
Release: 6.6
Codename: Final

I have databases with BLOBS, when trying for mysqldump the server is Crashing.

InnoDB: End of page dump
2016-06-28T11:33:12.672588Z 5 [Note] InnoDB: Uncompressed page, stored checksum in field1 1838029964, calculated checksums for field1: crc32 1644617659/1342938682, innodb 641883149, none 3735928559, stored checksum in field2 0, calculated checksums for field2: crc32 1644617659/1342938682, innodb 2495212955, none 3735928559, page LSN 105 1573641333, low 4 bytes of LSN at page end 0, page number (if stored to page already) 137430, space id (if created with >= MySQL-4.1.1 and stored already) 164
InnoDB: Page may be a BLOB page
2016-06-28T11:33:12.672600Z 5 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to for information about forcing recovery.
2016-06-28T11:33:12.672609Z 5 [ERROR] [FATAL] InnoDB: Unable to read page [page id: space=164, page number=137430] into the buffer pool after 100 attempts. The most probable cause of this error may be that the table has been corrupted. Or, the table was compressed with with an algorithm that is not supported by this instance. If it is not a decompress failure, you can try to fix this problem by using innodb_force_recovery. Please see for more details. Aborting...
2016-06-28 17:03:12 0x7fa5c1fa2700 InnoDB: Assertion failure in thread 140349900728064 in file line 923
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
11:33:12 UTC - mysqld got signal 6 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 197937113 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fa57810ec20
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 = 7fa5c1fa1e28 thread_stack 0x40000

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

The manual page at contains
information that should help you find out what is causing the crash.
160628 17:03:12 mysqld_safe Number of processes running now: 0
160628 17:03:12 mysqld_safe mysqld restarted
2016-06-28T11:33:12.899570Z 0 [Warning] option 'net_buffer_length': unsigned value 8388608 adjusted to 1048576
2016-06-28T11:33:12.899638Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-06-28T11:33:12.899644Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2016-06-28T11:33:12.899647Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2016-06-28T11:33:12.900092Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.10-log) starting as process 19939 ...
2016-06-28T11:33:12.903771Z 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See
2016-06-28T11:33:12.903848Z 0 [Note] InnoDB: PUNCH HOLE support available
2016-06-28T11:33:12.903862Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-06-28T11:33:12.903869Z 0 [Note] InnoDB: Uses event mutexes
2016-06-28T11:33:12.903874Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2016-06-28T11:33:12.903881Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-06-28T11:33:12.903887Z 0 [Note] InnoDB: Using Linux native AIO
2016-06-28T11:33:12.904124Z 0 [Note] InnoDB: Number of pools: 1
2016-06-28T11:33:12.904212Z 0 [Note] InnoDB: Using CPU crc32 instructions
2016-06-28T11:33:12.911844Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2016-06-28T11:33:12.976873Z 0 [Note] InnoDB: Completed initialization of buffer pool
2016-06-28T11:33:12.985720Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2016-06-28T11:33:12.997548Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2016-06-28T11:33:13.002733Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 452615676178
2016-06-28T11:33:13.002750Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 452615676187
2016-06-28T11:33:13.005349Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 452615676187
2016-06-28T11:33:13.005372Z 0 [Note] InnoDB: Database was not shutdown normally!
2016-06-28T11:33:13.005386Z 0 [Note] InnoDB: Starting crash recovery.
2016-06-28T11:33:13.022296Z 0 [Note] InnoDB: Last MySQL binlog file position 0 5109368, file name master-mysql-bin.000341
2016-06-28T11:33:13.126969Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

2016-06-28T11:33:13.126994Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2016-06-28T11:33:13.127053Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2016-06-28T11:33:13.169697Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2016-06-28T11:33:13.170457Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2016-06-28T11:33:13.170471Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2016-06-28T11:33:13.170799Z 0 [Note] InnoDB: Waiting for purge to start
2016-06-28T11:33:13.220946Z 0 [Note] InnoDB: 5.7.10 started; log sequence number 452615676187
2016-06-28T11:33:13.221268Z 0 [Note] InnoDB: Loading buffer pool(s) from /opt/simpana/MediaAgent64/SnapVolumeMounts/SnapMnt_1_2_372808_12_14158/ib_buffer_pool
2016-06-28T11:33:13.221349Z 0 [Note] InnoDB: not started
2016-06-28T11:33:13.221483Z 0 [Note] Plugin 'FEDERATED' is disabled.
2016-06-28T11:33:13.222169Z 0 [Note] Recovering after a crash using master-mysql-bin
2016-06-28T11:33:13.227107Z 0 [Note] InnoDB: Buffer pool(s) load completed at 160628 17:03:13
2016-06-28T11:33:13.242701Z 0 [Note] Starting crash recovery...
2016-06-28T11:33:13.242769Z 0 [Note] Crash recovery finished.
2016-06-28T11:33:13.566847Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2016-06-28T11:33:13.566869Z 0 [Note] Server hostname (bind-address): '*'; port: 23428
2016-06-28T11:33:13.566938Z 0 [Note] IPv6 is available.
2016-06-28T11:33:13.566952Z 0 [Note] - '::' resolves to '::';
2016-06-28T11:33:13.566962Z 0 [Note] Server socket created on IP: '::'.
2016-06-28T11:33:13.636143Z 0 [Note] Event Scheduler: Loaded 0 events
2016-06-28T11:33:13.636252Z 1 [Note] Event Scheduler: scheduler thread started with id 1
2016-06-28T11:33:13.636323Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.10-log' socket: '/snap_LVM//mysql.sock' port: 23428 MySQL Community Server (GPL)

Options: ReplyQuote

Written By
mysqldump command failing with crash
June 28, 2016 05:51AM

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.