Fix INNODB Unset message on MariaDB #5637
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Similar to Cacti#5030 The original scripts checks if MariaDB is 11 to not check if INNODB variable doesn't exists, but it was removed on 10.10 and not on 11. This fixes an issue that fixes the UNSET message on Cacti 1.1.25 on Windows All-in-One installer.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Similar to #5030 The original scripts checks if MariaDB is 11 to not check if INNODB variable doesn't exists, but it was removed on 10.10 and not on 11 (as can be seen in #5030 and https://serverfault.com/questions/1128160/removing-innodb-parameter-not-on-error-when-installing-%D0%A1a%D1%81ti). This fixes an issue that fixes the UNSET message on Cacti 1.1.25 on Windows All-in-One Beta installer.