Bug #101183 Bug in MySQL Role MySQL community 8.0.20.

• Submitted: 15 Oct 2020 9:21
• Modified: 15 Oct 2020 12:30
• Reporter: lokesh singhal
• Status: Not a Bug
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 8.0.20
• OS: Linux
• CPU Architecture: Any
• Tags: mysqldump

[15 Oct 2020 9:21] lokesh singhal

Description:
I am getting error while running my shell script for dump

mysqldump: [Warning] Using a password on the command line interface can be insecure.
mysqldump: [Warning] Using a password on the command line interface can be insecure.
mysqldump: [Warning] Using a password on the command line interface can be insecure.
mysqldump: [Warning] Using a password on the command line interface can be insecure.
mysqldump: Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */ * FROM `filelog`': Lost connection to MySQL server during query (2013)

error  got changed some time with different table.

How to repeat:
Run this 

sh master.sh
=========master.sh=======

mysqldump -u root -pabc123 -h 192.186.0.1 -P 30005 --quick --max_allowed_packet=512M  --single-transaction=TRUE --routines transactiondb  | \gzip  >/db_bkp/$(date +%Y_%m_%d_%H_%M)ramesh.sql.gz
sleep 2m
mysqldump -u root -pabc123 -h 192.186.0.1 -P 30005  --single-transaction=TRUE --routines  panadb  | \gzip  >/db_bkp/$(date +%Y_%m_%d_%H_%M)_panadb.sql.gz
sleep 3m
mysqldump -u root -pabc123 -h 192.186.0.1 -P 30005  --single-transaction=TRUE --routines client_db  | \gzip  >/db_bkp/$(date +%Y_%m_%d_%H_%M)_client_db.sql.gz
sleep 4m
mysqldump -u root -pabc123 -h 192.186.0.1 -P 30005  --single-transaction=TRUE --routines notification_db  | \gzip >/db_bkp/$(date +%Y_%m_%d_%H_%M)_notification_db.sql.gz
sleep 5m
mysqldump -u root -pabc123 -h 192.186.0.1 -P 30005  --single-transaction=TRUE --routines user_db  | \gzip >/db_bkp/$(date +%Y_%m_%d_%H_%M)_user_db.sql.gz

Suggested fix:
take dump one by one  will work fine

[15 Oct 2020 12:30] MySQL Verification Team

Hi Mr. singhal,

Thank you for your bug report.

However, this is not a bug.

First of all, you get warnings for entering password on the command line, which is highly insecure.

Second, you are running into one of the client-related timeouts. That is because you are processing the output with very complicated compression.

You should increase all relevant timeouts.

Not a bug.