Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Not a Bug
-
10.5.11
-
None
-
Ubuntu 18.04 64bit
Description
command:
mysqldump -v -f --max_allowed_packet=1G --skip-log-queries --add-locks --single-transaction --dump-date --events --flush-logs --quick --opt --routines --triggers --log-error=/tmp/log.txt --result_file=/tmp/zgx.sql zgx
Last part of log output
– Sending SELECT query...
– Retrieving rows...
– Rolling back to savepoint sp...
– Retrieving table structure for table zgx_zorgovereenkomsten_documenten_audit...
– Sending SELECT query...
– Retrieving rows...
– Rolling back to savepoint sp...
– Retrieving table structure for table zgx_zorgprofielen_wlz...
– Sending SELECT query...
– Retrieving rows...
– Rolling back to savepoint sp...
– Retrieving table structure for table zgx_zorgverzekeraars...
– Sending SELECT query...
– Retrieving rows...
– Rolling back to savepoint sp...
– Retrieving table structure for table zgx_zorgverzekeraars_audit...
– Sending SELECT query...
– Retrieving rows...
– Rolling back to savepoint sp...
– Releasing savepoint...
CPU is now 100% and runs forever
Attachments
Activity
mysqldump -v --dump-date --events --routines --triggers --result-file=/tmp/zgx.sql zgx
with --events causes 100% cpu and freezes
last part of log:
– Sending SELECT query...
– Retrieving rows...
– Retrieving table structure for table zgx_zorgverzekeraars_audit...
– Sending SELECT query...
– Retrieving rows...
^C
mysqldump -v --dump-date --routines --triggers --result-file=/tmp/zgx.sql zgx
without --events runs ok
last part of log:
– Retrieving view structure for table zgx_zorgprofielen_wlz...
– It's base table, skipped
– Retrieving view structure for table zgx_zorgverzekeraars...
– It's base table, skipped
– Retrieving view structure for table zgx_zorgverzekeraars_audit...
– It's base table, skipped
– Disconnecting from 127.0.0.1...
mysqldump -v -d -R --events --triggers --result_file=/backup/zgx_ddl.sql zgx
running mysqldump without data (DDL only) with --events also freezes
mysqldump -v -d --events --result_file=/backup/zgx_ddl.sql zgx
dumping --events only causes freeze and 100% cpu
after updating the last modified event and rerun
mysqldump -v -d --events --result_file=/tmp/events.sql zgx, the mysqldump runs ok.
So it seemed the problem is caused by an incorrectly
saved event.
dump data only works
mysqldump -v --no-create-info --single-transaction zgx > /backup/zgx_data.sql
dump create info without data also works
mysqldump -v -d -R --triggers --result_file=/backup/zgx_ddl.sql zgx