Re: Upgrade Error
Posted by: Michael Perdue
Date: March 12, 2021 07:44PM

I actually tried to just upgrade to 5.7.33 and this is the log

eginning configuration step: Writing configuration file

Saving installer_config.xml configuration file...
Saved installer_config.xml configuration file.
Ended configuration step: Writing configuration file

Beginning configuration step: Adjusting Windows service

Attempting to grant Network Service require filesystem permissions.
Granted permissions.
Updating existing service
Existing service updated
Ended configuration step: Adjusting Windows service

Beginning configuration step: Backing up MySQL database

Starting MySQL Server in order to run the mysql_upgrade tool.
Warning: There may be some errors thrown by MySQL Server, the mysql_upgrade tool is going to be run next to attempt to fix database incompatibilities.
Starting process for MySQL Server 5.7.33...
Starting process with command: C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.7\my.ini" --console...
Process for mysqld, with ID 2660, has been started successfully and is running.
Successfully started process for MySQL Server 5.7.33.
2021-03-13T01:42:26.431498Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-03-13T01:42:26.431875Z 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.
2021-03-13T01:42:26.458605Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.33-log) starting as process 2660 ...
2021-03-13T01:42:26.496426Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-03-13T01:42:26.496909Z 0 [Note] InnoDB: Uses event mutexes
2021-03-13T01:42:26.497104Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2021-03-13T01:42:26.497277Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-03-13T01:42:26.497478Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2021-03-13T01:42:26.500232Z 0 [Note] InnoDB: Number of pools: 1
2021-03-13T01:42:26.501448Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2021-03-13T01:42:26.511157Z 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M
2021-03-13T01:42:26.515428Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-13T01:42:27.126202Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2021-03-13T01:42:27.150337Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 55688735452
2021-03-13T01:42:27.150730Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 55688735461
2021-03-13T01:42:27.150999Z 0 [Note] InnoDB: Database was not shutdown normally!
2021-03-13T01:42:27.151170Z 0 [Note] InnoDB: Starting crash recovery....
2021-03-13T01:42:44.180701Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2021-03-13T01:42:44.198283Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-03-13T01:42:44.210668Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-03-13T01:42:44.777932Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2021-03-13T01:42:44.833976Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2021-03-13T01:42:44.834360Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2021-03-13T01:42:44.844014Z 0 [Note] InnoDB: Waiting for purge to start
2021-03-13T01:42:44.902033Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 18373ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2021-03-13T01:42:44.904326Z 0 [Note] InnoDB: 5.7.33 started; log sequence number 55688735461
2021-03-13T01:42:44.908042Z 0 [Note] InnoDB: Loading buffer pool(s) from C:\ProgramData\MySQL\MySQL Server 5.7\Data\ib_buffer_pool
2021-03-13T01:42:44.912488Z 0 [Note] Plugin 'FEDERATED' is disabled.
2021-03-13T01:42:45.197043Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2021-03-13T01:42:45.197503Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
2021-03-13T01:42:45.200754Z 0 [Warning] CA certificate ca.pem is self signed.
2021-03-13T01:42:45.201450Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
2021-03-13T01:42:45.202150Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2021-03-13T01:42:45.203437Z 0 [Note] IPv6 is available.
2021-03-13T01:42:45.203771Z 0 [Note] - '::' resolves to '::';
2021-03-13T01:42:45.204176Z 0 [Note] Server socket created on IP: '::'.
2021-03-13T01:42:45.293743Z 0 [Note] InnoDB: Buffer pool(s) load completed at 210312 20:42:45
2021-03-13T01:42:45.379606Z 0 [Note] Failed to start slave threads for channel ''
2021-03-13T01:42:45.416948Z 0 [Note] Event Scheduler: Loaded 0 events
2021-03-13T01:42:45.417978Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: ready for connections.
Version: '5.7.33-log' socket: '' port: 3306 MySQL Community Server (GPL).
Running mysqldump tool to backup the database...
Backup files will be dumped to "C:\ProgramData\MySQL\MySQL Server 5.7\Backup\mysql_dump-2021-03-12T20.42.47.sql".

Starting process with command: C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqldump.exe --defaults-extra-file="C:\Users\Administrator\AppData\Local\Temp\877fd997-1916-4cc2-9983-82dfe2f78fa0.ini" --user=root --host=localhost --port=3306 --default-character-set=utf8 --routines --events --single-transaction=TRUE --all-databases --result-file="C:\ProgramData\MySQL\MySQL Server 5.7\Backup\mysql_dump-2021-03-12T20.42.47.sql"...
2021-03-13T01:42:51.039746Z 2 [Note] Access denied for user 'root'@'localhost' (using password: YES)
mysqldump: Got error: 1045: Access denied for user 'root'@'localhost' (using password: YES) when trying to connect
Process for mysqldump, with ID 5796, was run successfully and exited with code 2.
Ended configuration step: Backing up MySQL database

Options: ReplyQuote

Written By
March 12, 2021 06:11PM
Re: Upgrade Error
March 12, 2021 07:44PM
March 12, 2021 08:12PM
March 12, 2021 08:26PM
March 14, 2021 10:01AM
March 12, 2021 09:24PM
February 09, 2022 09:22PM
February 09, 2022 09:24PM
February 09, 2022 09:31PM
February 10, 2022 01:55PM
February 11, 2022 01:04PM
February 11, 2022 01:06PM
February 11, 2022 01:13PM
February 11, 2022 03:15PM
February 12, 2022 08:16PM
February 12, 2022 09:10PM
February 09, 2022 08:40PM

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.