You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I actually tried this on a VM recently, going from 2.3 - 2.4 and things worked okay.
Unfortunately, on my production machine MySQL is failing to start. /opt/so/log/mysql/mysqld.log shows:
2024-03-07T20:43:13.374312Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
2024-03-07T20:43:13.374450Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-03-07T20:43:13.694532Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 5.7.41, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
2024-03-07T20:43:13.694591Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2024-03-07T20:43:14.073914Z 1 [ERROR] [MY-011013] [Server] Failed to initialize DD Storage Engine.
2024-03-07T20:43:14.109444Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-03-07T20:43:14.109604Z 0 [ERROR] [MY-010119] [Server] Aborting
It seems the container is trying to upgrade from the 5.7.41 database files to the newer version. First, I will say there was no reason why the old database had crashed. The machine had been properly shutdown.
Any help is greatly appreciate.
Guidelines
I have read the discussion guidelines at Read before posting! #1720 and assert that I have followed the guidelines.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Version
2.4.50
Installation Method
Security Onion ISO image
Description
installation
Installation Type
Standalone
Location
on-prem with Internet access
Hardware Specs
Exceeds minimum requirements
CPU
20
RAM
18GB
Storage for /
166G
Storage for /nsm
3.4TB
Network Traffic Collection
span port
Network Traffic Speeds
Less than 1Gbps
Status
No, one or more services are failed (please provide detail below)
Salt Status
Yes, there are salt failures (please provide detail below)
Logs
Yes, there are additional clues in /opt/so/log/ (please provide detail below)
Detail
I upgraded from 2.3 to 2.4. following the instructions at https://docs.securityonion.net/en/2.4/appendix.html
I actually tried this on a VM recently, going from 2.3 - 2.4 and things worked okay.
Unfortunately, on my production machine MySQL is failing to start. /opt/so/log/mysql/mysqld.log shows:
It seems the container is trying to upgrade from the 5.7.41 database files to the newer version. First, I will say there was no reason why the old database had crashed. The machine had been properly shutdown.
Any help is greatly appreciate.
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions