SOLVED MariaDB upgrade to 10.5 warnings

[greektranslator]

When I try to upgrade to MariaDB 10.5 I get the following warnings, can someone help as to whether it is safe or what I need to do?

Critical
The system detected issues with the current “/etc/my.cnf” file. These issues may interfere with the upgrade to MariaDB 10.5.

Critical
In MariaDB 10.4 and later, the mysql.global_priv table has replaced the mysql.user table. The mysql.user table is converted into a view of the mysql.global_priv table during the database upgrade. The dedicated mariadb.sys user is created as the definer of the new mysql.user view.

Critical
In MariaDB® 10.3, the mysqldump client includes logic for the mysql.transaction_registry table. You cannot use the mysqldump client from an earlier MariaDB release on MariaDB 10.3 and later. For more information about how to upgrade to MariaDB 10.3, read the MariaDB upgrade documentation .

Critical
MariaDB enables "strict mode" by default as of version 10.2. Strict mode controls how MariaDB and MySQL handle invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MariaDB are compatible before upgrading. More information about strict mode is available here .

 

[HostNoc]

HI
Before upgrading it is suggested to take current database backup and then remove database then try to upgrade.

REgards

 

[cPRex]

Hey there!

@HostNoc - You do not need to remove the database before you attempt the upgrade. That would cause a considerable amount of work for all clients.

@greektranslator - there isn't anything you are required to do. Those warnings are just letting you know that if you run into issues, those are the most likely things to check. We require you click the checkbox to at least make people aware of compatibility issues.

 

[greektranslator]

Right, I am most worried about " The system detected issues with the current “/etc/my.cnf” file. These issues may interfere with the upgrade to MariaDB 10.5. "

What is wrong with my cnf file that triggers this? Yes, I did take a backup with mysqldump --all-databases | gzip > alldatabases.sql.gz

Here is my.cnf:

[mysqld]
performance-schema=0
local-infile=0
max_connections = 10000
max_user_connections=9999
key_buffer_size = 1024M
myisam_sort_buffer_size = 256M
read_buffer_size = 16M
table_open_cache = 5000
thread_cache_size = 384
wait_timeout = 28800
interactive_timeout = 28800
connect_timeout = 60
tmp_table_size = 1024M
max_heap_table_size = 1024M
max_allowed_packet = 4G
net_buffer_length = 16384
max_connect_errors = 15
concurrent_insert = 2
read_rnd_buffer_size = 786432
bulk_insert_buffer_size = 64M
query_cache_limit = 32M
query_cache_size = 256M
query_cache_type = 0
query_prealloc_size = 262144
query_alloc_block_size = 65535
transaction_alloc_block_size = 8192
transaction_prealloc_size = 4096
max_write_lock_count = 8
slow_query_log = 1
slow_query_log_file = '/var/lib/mysql/slow.log'
log-error
external-locking=FALSE
open_files_limit=50000

innodb_file_per_table=1
#innodb_buffer_pool_size=128M
default-storage-engine=InnoDB

innodb_buffer_pool_size = 10G
#innodb_additional_mem_pool_size = 512M
innodb_log_file_size = 256M
innodb_log_buffer_size = 256M
innodb_log_files_in_group = 3
innodb_flush_log_at_trx_commit = 2
innodb_lock_wait_timeout = 300
innodb_flush_method=O_DIRECT
innodb_thread_concurrency = 50000
innodb_autoextend_increment = 30
innodb_io_capacity = 10000
#innodb_strict_mode=OFF

# thread_concurrency = 4096
thread_cache_size = 400

[mysqld_safe]

[mysqldump]
quick
max_allowed_packet = 16M

[isamchk]
key-buffer-size=384M
sort_buffer = 384M
read_buffer = 256M
write_buffer = 256M

[myisamchk]
key-buffer-size=384M
sort_buffer = 384M
read_buffer = 256M
write_buffer = 256M

#### Per connection configuration ####
sort_buffer_size = 8M
join_buffer_size = 8M
thread_stack = 512K

 

[cPRex]

At this point the interface isn't letting us know if there is an actual configuration issue or if this is just a warning. I reached out to the developers to see if they can update that page with better information in the future, but I don't have any specific or general answers about that at this time.

I'd recommend reviewing the my.cnf file and making sure none of those values cause a conflict with MariaDB 10.5 before performing the update.

 

[greektranslator]

Which values can conflict? I am really at a loss here, would appreciate any pointers.
In the ticket I was pointed to this cPanel

 

[cPRex]

Correct - as that case says, we're working on changing this warning, but the update will work just fine without you needing to change anything.

 

[greektranslator]

I can confirm safe upgrade.

 

[kodeslogic]

Glad to know the upgrade was successful

 

[cPRex]

I'm glad to hear that went well!

 

[cPRex]

Update - the interface has been adjusted to only present a warning message if there are actual conflicts with the update.

 

[cPRex]

Update - the changes are scheduled to be included in version 98.0.3.