Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-27517

mariadb-upgrade from MySQL 5.7 pollutes stdout on some sys schema views

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6
    • 10.6
    • Upgrades
    • None

    Description

      • Use data from MySQL 5.7 and run mariadb-upgrade (10.6 tested)

        $ docker stop mariadb-server-2
        $ # cd </path/of/mysql-data> 
        $ sudo cp -r mysql-data /tmp/mysql-data
        $ sudo chown -R 999:docker /tmp/mysql-data
         
        $ docker container run --rm --name mariadb-server-2  -v /tmp/mysql-data:/var/lib/mysql \
        -e MARIADB_ROOT_PASSWORD=secret -d mariadb:latest 
        

        Start upgrade

        $ docker exec -it mariadb-server-2 mariadb-upgrade test1 books -uroot -psecret
        

      In attachment is the example.

      Attachments

        Issue Links

          Activity

            danblack Daniel Black added a comment -

            Is running "mysql_fix_privilege_tables" before "Fixing views from mysql" a sufficient and acceptable solution?

            danblack Daniel Black added a comment - Is running "mysql_fix_privilege_tables" before "Fixing views from mysql" a sufficient and acceptable solution?

            Tried but still the same.

            anel Anel Husakovic added a comment - Tried but still the same.
            danblack Daniel Black added a comment -

            mysql-5.7 init

            $ podman run --rm -v m57:/var/lib/mysql:Z -e MYSQL_ALLOW_EMPTY_PASSWORD=1 --name m57 mysql:5.7 
            2022-02-01 02:25:05+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.37-1debian10 started.
            ..
            

            mariadb:10.2-a1f630ccfe33a14ee3c535a78b645d384c82876d upgrade

            $ podman run --rm -v m57:/var/lib/mysql:Z -e MARIADB_AUTO_UPGRADE=1 --name m102 m102_upstream
            2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.2.42+maria~bionic started.
            2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
            2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.2.42+maria~bionic started.
            2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
            2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Starting temporary server
            2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Waiting for server startup
            2022-02-01  2:26:23 140328960284352 [Note] mysqld (mysqld 10.2.42-MariaDB-1:10.2.42+maria~bionic) starting as process 44 ...
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Uses event mutexes
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Compressed tables use zlib 1.2.11
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Using Linux native AIO
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Number of pools: 1
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Using SSE2 crc32 instructions
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Completed initialization of buffer pool
            2022-02-01  2:26:23 140328238257920 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Highest supported file format is Barracuda.
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Upgrading redo log: 2*50331648 bytes; LSN=12660085
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Starting to delete and rewrite log files.
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes
            2022-02-01  2:26:23 140328960284352 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes
            2022-02-01  2:26:24 140328960284352 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
            2022-02-01  2:26:24 140328960284352 [Note] InnoDB: New log files created, LSN=12660085
            2022-02-01  2:26:24 140328960284352 [Note] InnoDB: 128 out of 128 rollback segments are active.
            2022-02-01  2:26:24 140328960284352 [Note] InnoDB: Creating shared tablespace for temporary tables
            2022-02-01  2:26:24 140328960284352 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
            2022-02-01  2:26:24 140328960284352 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
            2022-02-01  2:26:24 140328960284352 [Note] InnoDB: 5.7.37 started; log sequence number 12660085
            2022-02-01  2:26:24 140328073926400 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
            2022-02-01  2:26:24 140328960284352 [Note] Plugin 'FEEDBACK' is disabled.
            2022-02-01  2:26:24 140328799098624 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
            2022-02-01  2:26:24 140328960284352 [Note] Reading of all Master_info entries succeeded
            2022-02-01  2:26:24 140328960284352 [Note] Added new Master_info '' to hash table
            2022-02-01  2:26:24 140328960284352 [Note] mysqld: ready for connections.
            Version: '10.2.42-MariaDB-1:10.2.42+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
            2022-02-01  2:26:24 140328073926400 [Note] InnoDB: Buffer pool(s) load completed at 220201  2:26:24
            2022-02-01 02:26:24+00:00 [Note] [Entrypoint]: Temporary server started.
            2022-02-01 02:26:24+00:00 [Note] [Entrypoint]: Backing up system database to system_mysql_backup_unknown_version.sql.zst
            2022-02-01  2:26:24 140328798791424 [ERROR] InnoDB: Column last_update in table `mysql`.`innodb_table_stats` is BINARY(4) NOT NULL but should be INT UNSIGNED NOT NULL (flags mismatch).
            2022-02-01  2:26:24 140328798791424 [ERROR] InnoDB: Fetch of persistent statistics requested for table `mysql`.`gtid_executed` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
            2022-02-01 02:26:24+00:00 [Note] [Entrypoint]: Backing up complete
            2022-02-01 02:26:24+00:00 [Note] [Entrypoint]: Starting mariadb-upgrade
            The --upgrade-system-tables option was used, user tables won't be touched.
            MariaDB upgrade detected
            Phase 1/7: Checking and upgrading mysql database
            Processing databases
            mysql
            mysql.columns_priv                                 OK
            mysql.db                                           OK
            mysql.engine_cost                                  OK
            mysql.event                                        OK
            mysql.func                                         OK
            mysql.gtid_executed                                OK
            mysql.help_category                                OK
            mysql.help_keyword                                 OK
            mysql.help_relation                                OK
            mysql.help_topic                                   OK
            mysql.innodb_index_stats                           OK
            mysql.innodb_table_stats                           OK
            mysql.ndb_binlog_index                             OK
            mysql.plugin                                       OK
            mysql.proc                                         OK
            mysql.procs_priv                                   OK
            mysql.proxies_priv                                 OK
            mysql.server_cost                                  OK
            mysql.servers                                      OK
            mysql.slave_master_info                            OK
            mysql.slave_relay_log_info                         OK
            mysql.slave_worker_info                            OK
            mysql.tables_priv                                  OK
            mysql.time_zone                                    OK
            mysql.time_zone_leap_second                        OK
            mysql.time_zone_name                               OK
            mysql.time_zone_transition                         OK
            mysql.time_zone_transition_type                    OK
            mysql.user                                         OK
            Phase 2/7: Installing used storage engines... Skipped
            Phase 3/7: Fixing views from mysql
            2022-02-01  2:26:24 140328798791424 [ERROR] Incorrect definition of table mysql.proc: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVA
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`schema_auto_increment_columns`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`schema_object_overview`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`schema_redundant_indexes`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`schema_unused_indexes`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`version`: the version is set to 100242
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_file_io`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_file_io_type`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_stages`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_statement_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_statement_type`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$innodb_buffer_stats_by_schema`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$innodb_buffer_stats_by_table`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$innodb_lock_waits`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$io_by_thread_by_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$io_global_by_file_by_bytes`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$io_global_by_file_by_latency`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$io_global_by_wait_by_bytes`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$io_global_by_wait_by_latency`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$latest_file_io`: the version is set to 100242, algorithm restored to be MERGE
            sys.host_summary
            Error    : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist
            status   : Operation failed
            sys.host_summary_by_file_io
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.host_summary_by_file_io_type
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.host_summary_by_stages
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.host_summary_by_statement_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.host_summary_by_statement_type
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.innodb_buffer_stats_by_schema
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.innodb_buffer_stats_by_table
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.innodb_lock_waits
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.io_by_thread_by_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.io_global_by_file_by_bytes
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.io_global_by_file_by_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.io_global_by_wait_by_bytes
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.io_global_by_wait_by_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.latest_file_io
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.memory_by_host_by_current_bytes
            Error    : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist
            Error    : View 'sys.memory_by_host_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.memory_by_thread_by_current_bytes
            Error    : Table 'performance_schema.memory_summary_by_thread_by_event_name' doesn't exist
            status   : Operation failed
            sys.memory_by_user_by_current_bytes
            Error    : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist
            status   : Operation failed
            sys.memory_global_by_current_bytes
            Error    : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist
            status   : Operation failed
            sys.memory_global_total
            Error    : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist
            Error    : View 'sys.memory_global_total' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.metrics
            Error    : Table 'performance_schema.global_status' doesn't exist
            status   : Operation failed
            sys.processlist
            Error    : Table 'performance_schema.events_transactions_current' doesn't exist
            status   : Operation failed
            sys.ps_check_lost_instrumentation
            Error    : Table 'performance_schema.global_status' doesn't exist
            Error    : View 'sys.ps_check_lost_instrumentation' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.schema_auto_increment_columns                  OK
            sys.schema_index_statistics
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.schema_object_overview                         OK
            sys.schema_redundant_indexes                       OK
            sys.schema_table_lock_waits
            Error    : Table 'performance_schema.metadata_locks' doesn't exist
            status   : Operation failed
            sys.schema_table_statistics
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.schema_table_statistics_with_buffer
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.schema_tables_with_full_table_scans
            Error    : Cann2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$ps_digest_95th_percentile_by_avg_us`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$ps_digest_avg_latency_distribution`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$schema_flattened_keys`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$schema_index_statistics`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$schema_tables_with_full_table_scans`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$statement_analysis`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_errors_or_warnings`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_full_table_scans`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_runtimes_in_95th_percentile`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_sorting`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_temp_tables`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_file_io`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_file_io_type`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_stages`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_statement_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_statement_type`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$wait_classes_global_by_avg_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$wait_classes_global_by_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$waits_by_host_by_latency`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$waits_by_user_by_latency`: the version is set to 100242, algorithm restored to be MERGE
            2022-02-01  2:26:25 140328798791424 [Note] View `sys`.`x$waits_global_by_latency`: the version is set to 100242, algorithm restored to be MERGE
            ot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.schema_unused_indexes                          OK
            sys.session
            Error    : Table 'performance_schema.events_transactions_current' doesn't exist
            Error    : View 'sys.session' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.session_ssl_status
            Error    : Table 'performance_schema.status_by_thread' doesn't exist
            status   : Operation failed
            sys.statement_analysis
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.statements_with_errors_or_warnings
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.statements_with_full_table_scans
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.statements_with_runtimes_in_95th_percentile
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.statements_with_sorting
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.statements_with_temp_tables
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.user_summary
            Error    : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist
            Error    : View 'sys.user_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.user_summary_by_file_io
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.user_summary_by_file_io_type
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.user_summary_by_stages
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.user_summary_by_statement_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.user_summary_by_statement_type
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.version                                        OK
            sys.wait_classes_global_by_avg_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.wait_classes_global_by_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.waits_by_host_by_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.waits_by_user_by_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.waits_global_by_latency
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.x$host_summary
            Error    : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist
            Error    : View 'sys.x$host_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$host_summary_by_file_io                      OK
            sys.x$host_summary_by_file_io_type                 OK
            sys.x$host_summary_by_stages                       OK
            sys.x$host_summary_by_statement_latency            OK
            sys.x$host_summary_by_statement_type               OK
            sys.x$innodb_buffer_stats_by_schema                OK
            sys.x$innodb_buffer_stats_by_table                 OK
            sys.x$innodb_lock_waits                            OK
            sys.x$io_by_thread_by_latency                      OK
            sys.x$io_global_by_file_by_bytes                   OK
            sys.x$io_global_by_file_by_latency                 OK
            sys.x$io_global_by_wait_by_bytes                   OK
            sys.x$io_global_by_wait_by_latency                 OK
            sys.x$latest_file_io                               OK
            sys.x$memory_by_host_by_current_bytes
            Error    : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist
            Error    : View 'sys.x$memory_by_host_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$memory_by_thread_by_current_bytes
            Error    : Table 'performance_schema.memory_summary_by_thread_by_event_name' doesn't exist
            Error    : View 'sys.x$memory_by_thread_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$memory_by_user_by_current_bytes
            Error    : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist
            Error    : View 'sys.x$memory_by_user_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$memory_global_by_current_bytes
            Error    : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist
            Error    : View 'sys.x$memory_global_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$memory_global_total
            Error    : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist
            Error    : View 'sys.x$memory_global_total' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$processlist
            Error    : Table 'performance_schema.events_transactions_current' doesn't exist
            Error    : View 'sys.x$processlist' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$ps_digest_95th_percentile_by_avg_us          OK
            sys.x$ps_digest_avg_latency_distribution           OK
            sys.x$ps_schema_table_statistics_io
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.x$schema_flattened_keys                        OK
            sys.x$schema_index_statistics                      OK
            sys.x$schema_table_lock_waits
            Error    : Table 'performance_schema.metadata_locks' doesn't exist
            Error    : View 'sys.x$schema_table_lock_waits' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$schema_table_statistics
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.x$schema_table_statistics_with_buffer
            Error    : Cannot load from mysql.proc. The table is probably corrupted
            error    : Corrupt
            sys.x$schema_tables_with_full_table_scans          OK
            sys.x$session
            Error    : Table 'performance_schema.events_transactions_current' doesn't exist
            Error    : View 'sys.x$session' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$statement_analysis                           OK
            sys.x$statements_with_errors_or_warnings           OK
            sys.x$statements_with_full_table_scans             OK
            sys.x$statements_with_runtimes_in_95th_percentile  OK
            sys.x$statements_with_sorting                      OK
            sys.x$statements_with_temp_tables                  OK
            sys.x$user_summary
            Error    : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist
            Error    : View 'sys.x$user_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.x$user_summary_by_file_io                      OK
            sys.x$user_summary_by_file_io_type                 OK
            sys.x$user_summary_by_stages                       OK
            sys.x$user_summary_by_statement_latency            OK
            sys.x$user_summary_by_statement_type               OK
            sys.x$wait_classes_global_by_avg_latency           OK
            sys.x$wait_classes_global_by_latency               OK
            sys.x$waits_by_host_by_latency                     OK
            sys.x$waits_by_user_by_latency                     OK
            sys.x$waits_global_by_latency                      OK
            Phase 4/7: Running 'mysql_fix_privilege_tables'
            2022-02-01  2:26:25 140328798791424 [ERROR] InnoDB: Column last_update in table `mysql`.`innodb_table_stats` is BINARY(4) NOT NULL but should be INT UNSIGNED NOT NULL (flags mismatch).
            2022-02-01  2:26:25 140328798791424 [ERROR] InnoDB: Column last_update in table `mysql`.`innodb_table_stats` is BINARY(4) NOT NULL but should be INT UNSIGNED NOT NULL (flags mismatch).
            2022-02-01  2:26:25 140328798791424 [ERROR] InnoDB: Column last_update in table `mysql`.`innodb_table_stats` is BINARY(4) NOT NULL but should be INT UNSIGNED NOT NULL (flags mismatch).
            Phase 5/7: Fixing table and database names ... Skipped
            Phase 6/7: Checking and upgrading tables... Skipped
            Phase 7/7: Running 'FLUSH PRIVILEGES'
            OK
            2022-02-01 02:26:25+00:00 [Note] [Entrypoint]: Finished mariadb-upgrade
            2022-02-01 02:26:25+00:00 [Note] [Entrypoint]: Stopping temporary server
            

            Looking at mysql:5.7

            mysql> select db,name from mysql.proc;
            +-----+-------------------------------------+
            | db  | name                                |
            +-----+-------------------------------------+
            | sys | create_synonym_db                   |
            | sys | diagnostics                         |
            | sys | execute_prepared_stmt               |
            | sys | extract_schema_from_file_name       |
            | sys | extract_table_from_file_name        |
            | sys | format_bytes                        |
            | sys | format_path                         |
            | sys | format_statement                    |
            | sys | format_time                         |
            | sys | list_add                            |
            | sys | list_drop                           |
            | sys | ps_is_account_enabled               |
            | sys | ps_is_consumer_enabled              |
            | sys | ps_is_instrument_default_enabled    |
            | sys | ps_is_instrument_default_timed      |
            | sys | ps_is_thread_instrumented           |
            | sys | ps_setup_disable_background_threads |
            | sys | ps_setup_disable_consumer           |
            | sys | ps_setup_disable_instrument         |
            | sys | ps_setup_disable_thread             |
            | sys | ps_setup_enable_background_threads  |
            | sys | ps_setup_enable_consumer            |
            | sys | ps_setup_enable_instrument          |
            | sys | ps_setup_enable_thread              |
            | sys | ps_setup_reload_saved               |
            | sys | ps_setup_reset_to_default           |
            | sys | ps_setup_save                       |
            | sys | ps_setup_show_disabled              |
            | sys | ps_setup_show_disabled_consumers    |
            | sys | ps_setup_show_disabled_instruments  |
            | sys | ps_setup_show_enabled               |
            | sys | ps_setup_show_enabled_consumers     |
            | sys | ps_setup_show_enabled_instruments   |
            | sys | ps_statement_avg_latency_histogram  |
            | sys | ps_thread_account                   |
            | sys | ps_thread_id                        |
            | sys | ps_thread_stack                     |
            | sys | ps_thread_trx_info                  |
            | sys | ps_trace_statement_digest           |
            | sys | ps_trace_thread                     |
            | sys | ps_truncate_all_tables              |
            | sys | quote_identifier                    |
            | sys | statement_performance_analyzer      |
            | sys | sys_get_config                      |
            | sys | table_exists                        |
            | sys | version_major                       |
            | sys | version_minor                       |
            | sys | version_patch                       |
            +-----+-------------------------------------+
            48 rows in set (0.00 sec)
             
            mysql> show create view sys.host_summary\G
            *************************** 1. row ***************************
                            View: host_summary
                     Create View: CREATE ALGORITHM=TEMPTABLE DEFINER=`mysql.sys`@`localhost` SQL SECURITY INVOKER VIEW `sys`.`host_summary` AS select if(isnull(`performance_schema`.`accounts`.`HOST`),'background',`performance_schema`.`accounts`.`HOST`) AS `host`,sum(`stmt`.`total`) AS `statements`,`sys`.`format_time`(sum(`stmt`.`total_latency`)) AS `statement_latency`,`sys`.`format_time`(ifnull((sum(`stmt`.`total_latency`) / nullif(sum(`stmt`.`total`),0)),0)) AS `statement_avg_latency`,sum(`stmt`.`full_scans`) AS `table_scans`,sum(`io`.`ios`) AS `file_ios`,`sys`.`format_time`(sum(`io`.`io_latency`)) AS `file_io_latency`,sum(`performance_schema`.`accounts`.`CURRENT_CONNECTIONS`) AS `current_connections`,sum(`performance_schema`.`accounts`.`TOTAL_CONNECTIONS`) AS `total_connections`,count(distinct `performance_schema`.`accounts`.`USER`) AS `unique_users`,`sys`.`format_bytes`(sum(`mem`.`current_allocated`)) AS `current_memory`,`sys`.`format_bytes`(sum(`mem`.`total_allocated`)) AS `total_memory_allocated` from (((`performance_schema`.`accounts` join `sys`.`x$host_summary_by_statement_latency` `stmt` on((`performance_schema`.`accounts`.`HOST` = `stmt`.`host`))) join `sys`.`x$host_summary_by_file_io` `io` on((`performance_schema`.`accounts`.`HOST` = `io`.`host`))) join `sys`.`x$memory_by_host_by_current_bytes` `mem` on((`performance_schema`.`accounts`.`HOST` = `mem`.`host`))) group by if(isnull(`performance_schema`.`accounts`.`HOST`),'background',`performance_schema`.`accounts`.`HOST`)
            character_set_client: utf8
            collation_connection: utf8_general_ci
            1 row in set (0.00 sec)
             
            mysql> show create function sys.format_time\G
            *************************** 1. row ***************************
                        Function: format_time
                        sql_mode: 
                 Create Function: CREATE DEFINER=`mysql.sys`@`localhost` FUNCTION `format_time`( picoseconds TEXT ) RETURNS text CHARSET utf8
                NO SQL
                DETERMINISTIC
                SQL SECURITY INVOKER
                COMMENT '\n Description\n \n Takes a raw picoseconds value, and converts it to a human readable form.\n \n Picoseconds are the precision that all latency values are printed in\n within Performance Schema, however are not user friendly when wanting\n to scan output from the command line.\n \n Parameters\n \n picoseconds (TEXT):\n The raw picoseconds value to convert.\n \n Returns\n \n TEXT\n \n Example\n \n mysql> select format_time(342342342342345);\n +------------------------------+\n | format_time(342342342342345) |\n +------------------------------+\n | 00:05:42                     |\n +------------------------------+\n 1 row in set (0.00 sec)\n \n mysql> select format_time(342342342);\n +------------------------+\n | format_time(342342342) |\n +------------------------+\n | 342.34 us              |\n +------------------------+\n 1 row in set (0.00 sec)\n \n mysql> select format_time(34234);\n +--------------------+\n | format_time(34234) |\n +--------------------+\n | 34.23 ns           |\n +--------------------+\n 1 row in set (0.00 sec)\n '
            BEGIN IF picoseconds IS NULL THEN RETURN NULL; ELSEIF picoseconds >= 604800000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 604800000000000000, 2), ' w'); ELSEIF picoseconds >= 86400000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 86400000000000000, 2), ' d'); ELSEIF picoseconds >= 3600000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 3600000000000000, 2), ' h'); ELSEIF picoseconds >= 60000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 60000000000000, 2), ' m'); ELSEIF picoseconds >= 1000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 1000000000000, 2), ' s'); ELSEIF picoseconds >= 1000000000 THEN RETURN CONCAT(ROUND(picoseconds / 1000000000, 2), ' ms'); ELSEIF picoseconds >= 1000000 THEN RETURN CONCAT(ROUND(picoseconds / 1000000, 2), ' us'); ELSEIF picoseconds >= 1000 THEN RETURN CONCAT(ROUND(picoseconds / 1000, 2), ' ns'); ELSE RETURN CONCAT(picoseconds, ' ps'); END IF; END
            character_set_client: utf8
            collation_connection: utf8_general_ci
              Database Collation: utf8_general_ci
            1 row in set (0.00 sec)
             
            mysql> select version();
            +-----------+
            | version() |
            +-----------+
            | 5.7.37    |
            +-----------+
            1 row in set (0.00 sec)
            

            So MySQL's sys schema views depend on stored functions.

            1. fixing views does a mysqlcheck on all views
            2. the aspect of CHECK/REPAIR TABLE cause mariadb to open the view and validate the resolution of these functions.
            3. Its not until Phase 4/7: Running 'mysql_fix_privilege_tables' when the mysql.proc gets updated (sql_mode, aggregate functions column etc), where mariadb will recognise it without error

            So technically this can happen to any mysql view that has a reference to a stored function.

            danblack Daniel Black added a comment - mysql-5.7 init $ podman run --rm -v m57:/var/lib/mysql:Z -e MYSQL_ALLOW_EMPTY_PASSWORD=1 --name m57 mysql:5.7 2022-02-01 02:25:05+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.37-1debian10 started. .. mariadb:10.2-a1f630ccfe33a14ee3c535a78b645d384c82876d upgrade $ podman run --rm -v m57:/var/lib/mysql:Z -e MARIADB_AUTO_UPGRADE=1 --name m102 m102_upstream 2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.2.42+maria~bionic started. 2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.2.42+maria~bionic started. 2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required 2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Starting temporary server 2022-02-01 02:26:23+00:00 [Note] [Entrypoint]: Waiting for server startup 2022-02-01 2:26:23 140328960284352 [Note] mysqld (mysqld 10.2.42-MariaDB-1:10.2.42+maria~bionic) starting as process 44 ... 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Uses event mutexes 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Using Linux native AIO 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Number of pools: 1 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Using SSE2 crc32 instructions 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Completed initialization of buffer pool 2022-02-01 2:26:23 140328238257920 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Highest supported file format is Barracuda. 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Upgrading redo log: 2*50331648 bytes; LSN=12660085 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Starting to delete and rewrite log files. 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes 2022-02-01 2:26:23 140328960284352 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes 2022-02-01 2:26:24 140328960284352 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2022-02-01 2:26:24 140328960284352 [Note] InnoDB: New log files created, LSN=12660085 2022-02-01 2:26:24 140328960284352 [Note] InnoDB: 128 out of 128 rollback segments are active. 2022-02-01 2:26:24 140328960284352 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-02-01 2:26:24 140328960284352 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-02-01 2:26:24 140328960284352 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-02-01 2:26:24 140328960284352 [Note] InnoDB: 5.7.37 started; log sequence number 12660085 2022-02-01 2:26:24 140328073926400 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2022-02-01 2:26:24 140328960284352 [Note] Plugin 'FEEDBACK' is disabled. 2022-02-01 2:26:24 140328799098624 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist 2022-02-01 2:26:24 140328960284352 [Note] Reading of all Master_info entries succeeded 2022-02-01 2:26:24 140328960284352 [Note] Added new Master_info '' to hash table 2022-02-01 2:26:24 140328960284352 [Note] mysqld: ready for connections. Version: '10.2.42-MariaDB-1:10.2.42+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: 0 mariadb.org binary distribution 2022-02-01 2:26:24 140328073926400 [Note] InnoDB: Buffer pool(s) load completed at 220201 2:26:24 2022-02-01 02:26:24+00:00 [Note] [Entrypoint]: Temporary server started. 2022-02-01 02:26:24+00:00 [Note] [Entrypoint]: Backing up system database to system_mysql_backup_unknown_version.sql.zst 2022-02-01 2:26:24 140328798791424 [ERROR] InnoDB: Column last_update in table `mysql`.`innodb_table_stats` is BINARY(4) NOT NULL but should be INT UNSIGNED NOT NULL (flags mismatch). 2022-02-01 2:26:24 140328798791424 [ERROR] InnoDB: Fetch of persistent statistics requested for table `mysql`.`gtid_executed` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead. 2022-02-01 02:26:24+00:00 [Note] [Entrypoint]: Backing up complete 2022-02-01 02:26:24+00:00 [Note] [Entrypoint]: Starting mariadb-upgrade The --upgrade-system-tables option was used, user tables won't be touched. MariaDB upgrade detected Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.columns_priv OK mysql.db OK mysql.engine_cost OK mysql.event OK mysql.func OK mysql.gtid_executed OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.innodb_index_stats OK mysql.innodb_table_stats OK mysql.ndb_binlog_index OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.server_cost OK mysql.servers OK mysql.slave_master_info OK mysql.slave_relay_log_info OK mysql.slave_worker_info OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Phase 2/7: Installing used storage engines... Skipped Phase 3/7: Fixing views from mysql 2022-02-01 2:26:24 140328798791424 [ERROR] Incorrect definition of table mysql.proc: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVA 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`schema_auto_increment_columns`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`schema_object_overview`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`schema_redundant_indexes`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`schema_unused_indexes`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`version`: the version is set to 100242 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_file_io`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_file_io_type`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_stages`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_statement_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$host_summary_by_statement_type`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$innodb_buffer_stats_by_schema`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$innodb_buffer_stats_by_table`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$innodb_lock_waits`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$io_by_thread_by_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$io_global_by_file_by_bytes`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$io_global_by_file_by_latency`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$io_global_by_wait_by_bytes`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$io_global_by_wait_by_latency`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$latest_file_io`: the version is set to 100242, algorithm restored to be MERGE sys.host_summary Error : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist status : Operation failed sys.host_summary_by_file_io Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.host_summary_by_file_io_type Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.host_summary_by_stages Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.host_summary_by_statement_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.host_summary_by_statement_type Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.innodb_buffer_stats_by_schema Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.innodb_buffer_stats_by_table Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.innodb_lock_waits Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.io_by_thread_by_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.io_global_by_file_by_bytes Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.io_global_by_file_by_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.io_global_by_wait_by_bytes Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.io_global_by_wait_by_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.latest_file_io Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.memory_by_host_by_current_bytes Error : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist Error : View 'sys.memory_by_host_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.memory_by_thread_by_current_bytes Error : Table 'performance_schema.memory_summary_by_thread_by_event_name' doesn't exist status : Operation failed sys.memory_by_user_by_current_bytes Error : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist status : Operation failed sys.memory_global_by_current_bytes Error : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist status : Operation failed sys.memory_global_total Error : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist Error : View 'sys.memory_global_total' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.metrics Error : Table 'performance_schema.global_status' doesn't exist status : Operation failed sys.processlist Error : Table 'performance_schema.events_transactions_current' doesn't exist status : Operation failed sys.ps_check_lost_instrumentation Error : Table 'performance_schema.global_status' doesn't exist Error : View 'sys.ps_check_lost_instrumentation' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.schema_auto_increment_columns OK sys.schema_index_statistics Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.schema_object_overview OK sys.schema_redundant_indexes OK sys.schema_table_lock_waits Error : Table 'performance_schema.metadata_locks' doesn't exist status : Operation failed sys.schema_table_statistics Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.schema_table_statistics_with_buffer Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.schema_tables_with_full_table_scans Error : Cann2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$ps_digest_95th_percentile_by_avg_us`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$ps_digest_avg_latency_distribution`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$schema_flattened_keys`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$schema_index_statistics`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$schema_tables_with_full_table_scans`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$statement_analysis`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_errors_or_warnings`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_full_table_scans`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_runtimes_in_95th_percentile`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_sorting`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$statements_with_temp_tables`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_file_io`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_file_io_type`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_stages`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_statement_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$user_summary_by_statement_type`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$wait_classes_global_by_avg_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$wait_classes_global_by_latency`: the version is set to 100242, algorithm restored to be TEMPTABLE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$waits_by_host_by_latency`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$waits_by_user_by_latency`: the version is set to 100242, algorithm restored to be MERGE 2022-02-01 2:26:25 140328798791424 [Note] View `sys`.`x$waits_global_by_latency`: the version is set to 100242, algorithm restored to be MERGE ot load from mysql.proc. The table is probably corrupted error : Corrupt sys.schema_unused_indexes OK sys.session Error : Table 'performance_schema.events_transactions_current' doesn't exist Error : View 'sys.session' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.session_ssl_status Error : Table 'performance_schema.status_by_thread' doesn't exist status : Operation failed sys.statement_analysis Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.statements_with_errors_or_warnings Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.statements_with_full_table_scans Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.statements_with_runtimes_in_95th_percentile Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.statements_with_sorting Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.statements_with_temp_tables Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.user_summary Error : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist Error : View 'sys.user_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.user_summary_by_file_io Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.user_summary_by_file_io_type Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.user_summary_by_stages Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.user_summary_by_statement_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.user_summary_by_statement_type Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.version OK sys.wait_classes_global_by_avg_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.wait_classes_global_by_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.waits_by_host_by_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.waits_by_user_by_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.waits_global_by_latency Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.x$host_summary Error : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist Error : View 'sys.x$host_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$host_summary_by_file_io OK sys.x$host_summary_by_file_io_type OK sys.x$host_summary_by_stages OK sys.x$host_summary_by_statement_latency OK sys.x$host_summary_by_statement_type OK sys.x$innodb_buffer_stats_by_schema OK sys.x$innodb_buffer_stats_by_table OK sys.x$innodb_lock_waits OK sys.x$io_by_thread_by_latency OK sys.x$io_global_by_file_by_bytes OK sys.x$io_global_by_file_by_latency OK sys.x$io_global_by_wait_by_bytes OK sys.x$io_global_by_wait_by_latency OK sys.x$latest_file_io OK sys.x$memory_by_host_by_current_bytes Error : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist Error : View 'sys.x$memory_by_host_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$memory_by_thread_by_current_bytes Error : Table 'performance_schema.memory_summary_by_thread_by_event_name' doesn't exist Error : View 'sys.x$memory_by_thread_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$memory_by_user_by_current_bytes Error : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist Error : View 'sys.x$memory_by_user_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$memory_global_by_current_bytes Error : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist Error : View 'sys.x$memory_global_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$memory_global_total Error : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist Error : View 'sys.x$memory_global_total' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$processlist Error : Table 'performance_schema.events_transactions_current' doesn't exist Error : View 'sys.x$processlist' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$ps_digest_95th_percentile_by_avg_us OK sys.x$ps_digest_avg_latency_distribution OK sys.x$ps_schema_table_statistics_io Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.x$schema_flattened_keys OK sys.x$schema_index_statistics OK sys.x$schema_table_lock_waits Error : Table 'performance_schema.metadata_locks' doesn't exist Error : View 'sys.x$schema_table_lock_waits' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$schema_table_statistics Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.x$schema_table_statistics_with_buffer Error : Cannot load from mysql.proc. The table is probably corrupted error : Corrupt sys.x$schema_tables_with_full_table_scans OK sys.x$session Error : Table 'performance_schema.events_transactions_current' doesn't exist Error : View 'sys.x$session' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$statement_analysis OK sys.x$statements_with_errors_or_warnings OK sys.x$statements_with_full_table_scans OK sys.x$statements_with_runtimes_in_95th_percentile OK sys.x$statements_with_sorting OK sys.x$statements_with_temp_tables OK sys.x$user_summary Error : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist Error : View 'sys.x$user_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$user_summary_by_file_io OK sys.x$user_summary_by_file_io_type OK sys.x$user_summary_by_stages OK sys.x$user_summary_by_statement_latency OK sys.x$user_summary_by_statement_type OK sys.x$wait_classes_global_by_avg_latency OK sys.x$wait_classes_global_by_latency OK sys.x$waits_by_host_by_latency OK sys.x$waits_by_user_by_latency OK sys.x$waits_global_by_latency OK Phase 4/7: Running 'mysql_fix_privilege_tables' 2022-02-01 2:26:25 140328798791424 [ERROR] InnoDB: Column last_update in table `mysql`.`innodb_table_stats` is BINARY(4) NOT NULL but should be INT UNSIGNED NOT NULL (flags mismatch). 2022-02-01 2:26:25 140328798791424 [ERROR] InnoDB: Column last_update in table `mysql`.`innodb_table_stats` is BINARY(4) NOT NULL but should be INT UNSIGNED NOT NULL (flags mismatch). 2022-02-01 2:26:25 140328798791424 [ERROR] InnoDB: Column last_update in table `mysql`.`innodb_table_stats` is BINARY(4) NOT NULL but should be INT UNSIGNED NOT NULL (flags mismatch). Phase 5/7: Fixing table and database names ... Skipped Phase 6/7: Checking and upgrading tables... Skipped Phase 7/7: Running 'FLUSH PRIVILEGES' OK 2022-02-01 02:26:25+00:00 [Note] [Entrypoint]: Finished mariadb-upgrade 2022-02-01 02:26:25+00:00 [Note] [Entrypoint]: Stopping temporary server Looking at mysql:5.7 mysql> select db,name from mysql.proc; +-----+-------------------------------------+ | db | name | +-----+-------------------------------------+ | sys | create_synonym_db | | sys | diagnostics | | sys | execute_prepared_stmt | | sys | extract_schema_from_file_name | | sys | extract_table_from_file_name | | sys | format_bytes | | sys | format_path | | sys | format_statement | | sys | format_time | | sys | list_add | | sys | list_drop | | sys | ps_is_account_enabled | | sys | ps_is_consumer_enabled | | sys | ps_is_instrument_default_enabled | | sys | ps_is_instrument_default_timed | | sys | ps_is_thread_instrumented | | sys | ps_setup_disable_background_threads | | sys | ps_setup_disable_consumer | | sys | ps_setup_disable_instrument | | sys | ps_setup_disable_thread | | sys | ps_setup_enable_background_threads | | sys | ps_setup_enable_consumer | | sys | ps_setup_enable_instrument | | sys | ps_setup_enable_thread | | sys | ps_setup_reload_saved | | sys | ps_setup_reset_to_default | | sys | ps_setup_save | | sys | ps_setup_show_disabled | | sys | ps_setup_show_disabled_consumers | | sys | ps_setup_show_disabled_instruments | | sys | ps_setup_show_enabled | | sys | ps_setup_show_enabled_consumers | | sys | ps_setup_show_enabled_instruments | | sys | ps_statement_avg_latency_histogram | | sys | ps_thread_account | | sys | ps_thread_id | | sys | ps_thread_stack | | sys | ps_thread_trx_info | | sys | ps_trace_statement_digest | | sys | ps_trace_thread | | sys | ps_truncate_all_tables | | sys | quote_identifier | | sys | statement_performance_analyzer | | sys | sys_get_config | | sys | table_exists | | sys | version_major | | sys | version_minor | | sys | version_patch | +-----+-------------------------------------+ 48 rows in set (0.00 sec)   mysql> show create view sys.host_summary\G *************************** 1. row *************************** View: host_summary Create View: CREATE ALGORITHM=TEMPTABLE DEFINER=`mysql.sys`@`localhost` SQL SECURITY INVOKER VIEW `sys`.`host_summary` AS select if(isnull(`performance_schema`.`accounts`.`HOST`),'background',`performance_schema`.`accounts`.`HOST`) AS `host`,sum(`stmt`.`total`) AS `statements`,`sys`.`format_time`(sum(`stmt`.`total_latency`)) AS `statement_latency`,`sys`.`format_time`(ifnull((sum(`stmt`.`total_latency`) / nullif(sum(`stmt`.`total`),0)),0)) AS `statement_avg_latency`,sum(`stmt`.`full_scans`) AS `table_scans`,sum(`io`.`ios`) AS `file_ios`,`sys`.`format_time`(sum(`io`.`io_latency`)) AS `file_io_latency`,sum(`performance_schema`.`accounts`.`CURRENT_CONNECTIONS`) AS `current_connections`,sum(`performance_schema`.`accounts`.`TOTAL_CONNECTIONS`) AS `total_connections`,count(distinct `performance_schema`.`accounts`.`USER`) AS `unique_users`,`sys`.`format_bytes`(sum(`mem`.`current_allocated`)) AS `current_memory`,`sys`.`format_bytes`(sum(`mem`.`total_allocated`)) AS `total_memory_allocated` from (((`performance_schema`.`accounts` join `sys`.`x$host_summary_by_statement_latency` `stmt` on((`performance_schema`.`accounts`.`HOST` = `stmt`.`host`))) join `sys`.`x$host_summary_by_file_io` `io` on((`performance_schema`.`accounts`.`HOST` = `io`.`host`))) join `sys`.`x$memory_by_host_by_current_bytes` `mem` on((`performance_schema`.`accounts`.`HOST` = `mem`.`host`))) group by if(isnull(`performance_schema`.`accounts`.`HOST`),'background',`performance_schema`.`accounts`.`HOST`) character_set_client: utf8 collation_connection: utf8_general_ci 1 row in set (0.00 sec)   mysql> show create function sys.format_time\G *************************** 1. row *************************** Function: format_time sql_mode: Create Function: CREATE DEFINER=`mysql.sys`@`localhost` FUNCTION `format_time`( picoseconds TEXT ) RETURNS text CHARSET utf8 NO SQL DETERMINISTIC SQL SECURITY INVOKER COMMENT '\n Description\n \n Takes a raw picoseconds value, and converts it to a human readable form.\n \n Picoseconds are the precision that all latency values are printed in\n within Performance Schema, however are not user friendly when wanting\n to scan output from the command line.\n \n Parameters\n \n picoseconds (TEXT):\n The raw picoseconds value to convert.\n \n Returns\n \n TEXT\n \n Example\n \n mysql> select format_time(342342342342345);\n +------------------------------+\n | format_time(342342342342345) |\n +------------------------------+\n | 00:05:42 |\n +------------------------------+\n 1 row in set (0.00 sec)\n \n mysql> select format_time(342342342);\n +------------------------+\n | format_time(342342342) |\n +------------------------+\n | 342.34 us |\n +------------------------+\n 1 row in set (0.00 sec)\n \n mysql> select format_time(34234);\n +--------------------+\n | format_time(34234) |\n +--------------------+\n | 34.23 ns |\n +--------------------+\n 1 row in set (0.00 sec)\n ' BEGIN IF picoseconds IS NULL THEN RETURN NULL; ELSEIF picoseconds >= 604800000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 604800000000000000, 2), ' w'); ELSEIF picoseconds >= 86400000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 86400000000000000, 2), ' d'); ELSEIF picoseconds >= 3600000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 3600000000000000, 2), ' h'); ELSEIF picoseconds >= 60000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 60000000000000, 2), ' m'); ELSEIF picoseconds >= 1000000000000 THEN RETURN CONCAT(ROUND(picoseconds / 1000000000000, 2), ' s'); ELSEIF picoseconds >= 1000000000 THEN RETURN CONCAT(ROUND(picoseconds / 1000000000, 2), ' ms'); ELSEIF picoseconds >= 1000000 THEN RETURN CONCAT(ROUND(picoseconds / 1000000, 2), ' us'); ELSEIF picoseconds >= 1000 THEN RETURN CONCAT(ROUND(picoseconds / 1000, 2), ' ns'); ELSE RETURN CONCAT(picoseconds, ' ps'); END IF; END character_set_client: utf8 collation_connection: utf8_general_ci Database Collation: utf8_general_ci 1 row in set (0.00 sec)   mysql> select version(); +-----------+ | version() | +-----------+ | 5.7.37 | +-----------+ 1 row in set (0.00 sec) So MySQL's sys schema views depend on stored functions. fixing views does a mysqlcheck on all views the aspect of CHECK/REPAIR TABLE cause mariadb to open the view and validate the resolution of these functions. Its not until Phase 4/7: Running 'mysql_fix_privilege_tables' when the mysql.proc gets updated (sql_mode, aggregate functions column etc), where mariadb will recognise it without error So technically this can happen to any mysql view that has a reference to a stored function.

            For the record, the message about InnoDB persistent statistics tables being in the wrong format was fixed in MDEV-30483.

            marko Marko Mäkelä added a comment - For the record, the message about InnoDB persistent statistics tables being in the wrong format was fixed in MDEV-30483 .
            danblack Daniel Black added a comment -

            Great.

            10.6-ce547cfc0564bf54e73bcc5171a2212d6650eb00

            $  podman run --rm -v m57:/var/lib/mysql:Z -e MARIADB_AUTO_UPGRADE=1 --name m106 quay.io/mariadb-foundation/mariadb-devel:10.6
            2023-05-30 01:50:34+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.14+maria~ubu2004 started.
            2023-05-30 01:50:35+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
            2023-05-30 01:50:35+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.14+maria~ubu2004 started.
            2023-05-30 01:50:36+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
            2023-05-30 01:50:36+00:00 [Note] [Entrypoint]: Starting temporary server
            2023-05-30 01:50:36+00:00 [Note] [Entrypoint]: Waiting for server startup
            2023-05-30  1:50:36 0 [Note] Starting MariaDB 10.6.14-MariaDB-1:10.6.14+maria~ubu2004 source revision ce547cfc0564bf54e73bcc5171a2212d6650eb00 as process 226
            2023-05-30  1:50:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
            2023-05-30  1:50:36 0 [Note] InnoDB: Number of pools: 1
            2023-05-30  1:50:36 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
            2023-05-30  1:50:36 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
            2023-05-30  1:50:36 0 [Note] InnoDB: Using Linux native AIO
            2023-05-30  1:50:36 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
            2023-05-30  1:50:36 0 [Note] InnoDB: Completed initialization of buffer pool
            2023-05-30  1:50:36 0 [Note] InnoDB: 128 rollback segments are active.
            2023-05-30  1:50:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
            2023-05-30  1:50:36 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
            2023-05-30  1:50:36 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
            2023-05-30  1:50:36 0 [Note] InnoDB: 10.6.14 started; log sequence number 12222619; transaction id 2306
            2023-05-30  1:50:36 0 [Note] Plugin 'FEEDBACK' is disabled.
            2023-05-30  1:50:36 1 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
            2023-05-30  1:50:36 0 [Note] mariadbd: ready for connections.
            Version: '10.6.14-MariaDB-1:10.6.14+maria~ubu2004'  socket: '/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
            2023-05-30 01:50:37+00:00 [Note] [Entrypoint]: Temporary server started.
            2023-05-30 01:50:37+00:00 [Note] [Entrypoint]: Backing up system database to system_mysql_backup_unknown_version.sql.zst
            2023-05-30 01:50:37+00:00 [Note] [Entrypoint]: Backing up complete
            2023-05-30 01:50:37+00:00 [Note] [Entrypoint]: Starting mariadb-upgrade
            The --upgrade-system-tables option was used, user tables won't be touched.
            MariaDB upgrade detected
            Phase 1/7: Checking and upgrading mysql database
            Processing databases
            mysql
            mysql.columns_priv                                 OK
            mysql.db                                           OK
            mysql.engine_cost                                  OK
            mysql.event                                        OK
            mysql.func                                         OK
            mysql.gtid_executed                                OK
            mysql.help_category                                OK
            mysql.help_keyword                                 OK
            mysql.help_relation                                OK
            mysql.help_topic                                   OK
            mysql.innodb_index_stats                           OK
            mysql.innodb_table_stats                           OK
            mysql.ndb_binlog_index                             OK
            mysql.plugin                                       OK
            mysql.proc                                         OK
            mysql.procs_priv                                   OK
            mysql.proxies_priv                                 OK
            mysql.server_cost                                  OK
            mysql.servers                                      OK
            mysql.slave_master_info                            OK
            mysql.slave_relay_log_info                         OK
            mysql.slave_worker_info                            OK
            mysql.tables_priv                                  OK
            mysql.time_zone                                    OK
            mysql.time_zone_leap_second                        OK
            mysql.time_zone_name                               OK
            mysql.time_zone_transition                         OK
            mysql.time_zone_transition_type                    OK
            mysql.user                                         OK
            Phase 2/7: Installing used storage engines... Skipped
            Phase 3/7: Fixing views from mysql
            2023-05-30  1:50:37 10 [ERROR] Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            2023-05-30  1:50:37 10 [Note] View `sys`.`ps_check_lost_instrumentation`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`schema_auto_increment_columns`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`schema_object_overview`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`schema_redundant_indexes`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`schema_unused_indexes`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`session_ssl_status`: the version is set to 100614, algorithm restored to be MERGE
            sys.host_summary
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.host_summary_by_file_io
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.host_summary_by_file_io_type
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.host_summary_by_stages
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.host_summary_by_statement_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.host_summary_by_statement_type
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.innodb_buffer_stats_by_schema
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.innodb_buffer_stats_by_table
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.innodb_lock_waits
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.io_by_thread_by_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.io_global_by_file_by_bytes
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.io_global_by_file_by_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.io_global_by_wait_by_bytes
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.io_global_by_wait_by_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.latest_file_io
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.memory_by_host_by_current_bytes
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.memory_by_thread_by_current_bytes
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.memory_by_user_by_current_bytes
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.memory_global_by_current_bytes
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.memory_global_total
            Error   2023-05-30  1:50:37 10 [Note] View `sys`.`version`: the version is set to 100614
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$host_summary`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$host_summary_by_file_io`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$host_summary_by_file_io_type`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$host_summary_by_stages`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$host_summary_by_statement_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$host_summary_by_statement_type`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$innodb_buffer_stats_by_schema`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$innodb_buffer_stats_by_table`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$innodb_lock_waits`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$io_by_thread_by_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$io_global_by_file_by_bytes`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$io_global_by_file_by_latency`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$io_global_by_wait_by_bytes`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$io_global_by_wait_by_latency`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$latest_file_io`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$memory_by_host_by_current_bytes`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$memory_by_thread_by_current_bytes`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$memory_by_user_by_current_bytes`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$memory_global_by_current_bytes`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$memory_global_total`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$processlist`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$ps_digest_95th_percentile_by_avg_us`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$ps_digest_avg_latency_distribution`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$schema_flattened_keys`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$schema_index_statistics`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$schema_tables_with_full_table_scans`: the version is set to 100614, algorithm restored to be MERGE
             : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.metrics
            Error    : Unknown column 'information_schema.INNODB_METRICS.STATUS' in 'field list'
            Error    : View 'sys.metrics' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
            error    : Corrupt
            sys.processlist
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.ps_check_lost_instrumentation                  OK
            sys.schema_auto_increment_columns                  OK
            sys.schema_index_statistics
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.schema_object_overview                         OK
            sys.schema_redundant_indexes                       OK
            sys.schema_table_lock_waits
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.schema_table_statistics
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.schema_table_statistics_with_buffer
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.schema_tables_with_full_table_scans
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.schema_unused_indexes                          OK
            sys.session
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.session_ssl_status                             OK
            sys.statement_analysis
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.statements_with_errors_or_warnings
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.statements_with_full_table_scans
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.statements_with_runtimes_in_95th_percentile
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.statements_with_sorting
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.statements_with_temp_tables
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.user_summary
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.user_summary_by_file_io
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.user_summary_by_file_io_type
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Ple2023-05-30  1:50:37 10 [Note] View `sys`.`x$session`: the version is set to 100614
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$statement_analysis`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$statements_with_errors_or_warnings`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$statements_with_full_table_scans`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$statements_with_runtimes_in_95th_percentile`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$statements_with_sorting`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$statements_with_temp_tables`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$user_summary`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$user_summary_by_file_io`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$user_summary_by_file_io_type`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$user_summary_by_stages`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$user_summary_by_statement_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$user_summary_by_statement_type`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$wait_classes_global_by_avg_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$wait_classes_global_by_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$waits_by_host_by_latency`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$waits_by_user_by_latency`: the version is set to 100614, algorithm restored to be MERGE
            2023-05-30  1:50:37 10 [Note] View `sys`.`x$waits_global_by_latency`: the version is set to 100614, algorithm restored to be MERGE
            ase use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.user_summary_by_stages
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.user_summary_by_statement_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.user_summary_by_statement_type
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.version                                        OK
            sys.wait_classes_global_by_avg_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.wait_classes_global_by_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.waits_by_host_by_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.waits_by_user_by_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.waits_global_by_latency
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.x$host_summary                                 OK
            sys.x$host_summary_by_file_io                      OK
            sys.x$host_summary_by_file_io_type                 OK
            sys.x$host_summary_by_stages                       OK
            sys.x$host_summary_by_statement_latency            OK
            sys.x$host_summary_by_statement_type               OK
            sys.x$innodb_buffer_stats_by_schema                OK
            sys.x$innodb_buffer_stats_by_table                 OK
            sys.x$innodb_lock_waits                            OK
            sys.x$io_by_thread_by_latency                      OK
            sys.x$io_global_by_file_by_bytes                   OK
            sys.x$io_global_by_file_by_latency                 OK
            sys.x$io_global_by_wait_by_bytes                   OK
            sys.x$io_global_by_wait_by_latency                 OK
            sys.x$latest_file_io                               OK
            sys.x$memory_by_host_by_current_bytes              OK
            sys.x$memory_by_thread_by_current_bytes            OK
            sys.x$memory_by_user_by_current_bytes              OK
            sys.x$memory_global_by_current_bytes               OK
            sys.x$memory_global_total                          OK
            sys.x$processlist                                  OK
            sys.x$ps_digest_95th_percentile_by_avg_us          OK
            sys.x$ps_digest_avg_latency_distribution           OK
            sys.x$ps_schema_table_statistics_io
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.x$schema_flattened_keys                        OK
            sys.x$schema_index_statistics                      OK
            sys.x$schema_table_lock_waits
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.x$schema_table_statistics
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.x$schema_table_statistics_with_buffer
            Error    : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error
            error    : Corrupt
            sys.x$schema_tables_with_full_table_scans          OK
            sys.x$session                                      OK
            sys.x$statement_analysis                           OK
            sys.x$statements_with_errors_or_warnings           OK
            sys.x$statements_with_full_table_scans             OK
            sys.x$statements_with_runtimes_in_95th_percentile  OK
            sys.x$statements_with_sorting                      OK
            sys.x$statements_with_temp_tables                  OK
            sys.x$user_summary                                 OK
            sys.x$user_summary_by_file_io                      OK
            sys.x$user_summary_by_file_io_type                 OK
            sys.x$user_summary_by_stages                       OK
            sys.x$user_summary_by_statement_latency            OK
            sys.x$user_summary_by_statement_type               OK
            sys.x$wait_classes_global_by_avg_latency           OK
            sys.x$wait_classes_global_by_latency               OK
            sys.x$waits_by_host_by_latency                     OK
            sys.x$waits_by_user_by_latency                     OK
            sys.x$waits_global_by_latency                      OK
            Phase 4/7: Running 'mysql_fix_privilege_tables'
            Phase 5/7: Fixing table and database names ... Skipped
            Phase 6/7: Checking and upgrading tables... Skipped
            Phase 7/7: Running 'FLUSH PRIVILEGES'
            OK
            2023-05-30 01:50:38+00:00 [Note] [Entrypoint]: Finished mariadb-upgrade
            2023-05-30 01:50:38+00:00 [Note] [Entrypoint]: Stopping temporary server
            2023-05-30  1:50:38 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
            2023-05-30  1:50:38 0 [Note] InnoDB: FTS optimize thread exiting.
            2023-05-30  1:50:38 0 [Note] InnoDB: Starting shutdown...
            2023-05-30  1:50:38 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
            2023-05-30  1:50:38 0 [Note] InnoDB: Shutdown completed; log sequence number 12237556; transaction id 2345
            2023-05-30  1:50:38 0 [Note] mariadbd: Shutdown complete
             
            2023-05-30 01:50:38+00:00 [Note] [Entrypoint]: Temporary server stopped
            2023-05-30  1:50:38 0 [Note] Starting MariaDB 10.6.14-MariaDB-1:10.6.14+maria~ubu2004 source revision ce547cfc0564bf54e73bcc5171a2212d6650eb00 as process 1
            2023-05-30  1:50:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
            2023-05-30  1:50:38 0 [Note] InnoDB: Number of pools: 1
            2023-05-30  1:50:38 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
            2023-05-30  1:50:38 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
            2023-05-30  1:50:38 0 [Note] InnoDB: Using Linux native AIO
            2023-05-30  1:50:38 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
            2023-05-30  1:50:38 0 [Note] InnoDB: Completed initialization of buffer pool
            2023-05-30  1:50:38 0 [Note] InnoDB: 128 rollback segments are active.
            2023-05-30  1:50:38 0 [Note] InnoDB: Creating shared tablespace for temporary tables
            2023-05-30  1:50:38 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
            2023-05-30  1:50:38 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
            2023-05-30  1:50:38 0 [Note] InnoDB: 10.6.14 started; log sequence number 12237556; transaction id 2340
            2023-05-30  1:50:38 0 [Note] Plugin 'FEEDBACK' is disabled.
            2023-05-30  1:50:38 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
            2023-05-30  1:50:38 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
            2023-05-30  1:50:38 0 [Note] InnoDB: Buffer pool(s) load completed at 230530  1:50:38
            2023-05-30  1:50:38 0 [Note] Server socket created on IP: '0.0.0.0'.
            2023-05-30  1:50:38 0 [Note] Server socket created on IP: '::'.
            2023-05-30  1:50:39 0 [Note] mariadbd: ready for connections.
            Version: '10.6.14-MariaDB-1:10.6.14+maria~ubu2004'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
            

            mysql.proc was corrected late in the update. Maybe best to drop 10.6 sys and install our version?

            danblack Daniel Black added a comment - Great. 10.6-ce547cfc0564bf54e73bcc5171a2212d6650eb00 $ podman run --rm -v m57:/var/lib/mysql:Z -e MARIADB_AUTO_UPGRADE=1 --name m106 quay.io/mariadb-foundation/mariadb-devel:10.6 2023-05-30 01:50:34+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.14+maria~ubu2004 started. 2023-05-30 01:50:35+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 2023-05-30 01:50:35+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.14+maria~ubu2004 started. 2023-05-30 01:50:36+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required 2023-05-30 01:50:36+00:00 [Note] [Entrypoint]: Starting temporary server 2023-05-30 01:50:36+00:00 [Note] [Entrypoint]: Waiting for server startup 2023-05-30 1:50:36 0 [Note] Starting MariaDB 10.6.14-MariaDB-1:10.6.14+maria~ubu2004 source revision ce547cfc0564bf54e73bcc5171a2212d6650eb00 as process 226 2023-05-30 1:50:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2023-05-30 1:50:36 0 [Note] InnoDB: Number of pools: 1 2023-05-30 1:50:36 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2023-05-30 1:50:36 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) 2023-05-30 1:50:36 0 [Note] InnoDB: Using Linux native AIO 2023-05-30 1:50:36 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2023-05-30 1:50:36 0 [Note] InnoDB: Completed initialization of buffer pool 2023-05-30 1:50:36 0 [Note] InnoDB: 128 rollback segments are active. 2023-05-30 1:50:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2023-05-30 1:50:36 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2023-05-30 1:50:36 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2023-05-30 1:50:36 0 [Note] InnoDB: 10.6.14 started; log sequence number 12222619; transaction id 2306 2023-05-30 1:50:36 0 [Note] Plugin 'FEEDBACK' is disabled. 2023-05-30 1:50:36 1 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist 2023-05-30 1:50:36 0 [Note] mariadbd: ready for connections. Version: '10.6.14-MariaDB-1:10.6.14+maria~ubu2004' socket: '/run/mysqld/mysqld.sock' port: 0 mariadb.org binary distribution 2023-05-30 01:50:37+00:00 [Note] [Entrypoint]: Temporary server started. 2023-05-30 01:50:37+00:00 [Note] [Entrypoint]: Backing up system database to system_mysql_backup_unknown_version.sql.zst 2023-05-30 01:50:37+00:00 [Note] [Entrypoint]: Backing up complete 2023-05-30 01:50:37+00:00 [Note] [Entrypoint]: Starting mariadb-upgrade The --upgrade-system-tables option was used, user tables won't be touched. MariaDB upgrade detected Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.columns_priv OK mysql.db OK mysql.engine_cost OK mysql.event OK mysql.func OK mysql.gtid_executed OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.innodb_index_stats OK mysql.innodb_table_stats OK mysql.ndb_binlog_index OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.server_cost OK mysql.servers OK mysql.slave_master_info OK mysql.slave_relay_log_info OK mysql.slave_worker_info OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Phase 2/7: Installing used storage engines... Skipped Phase 3/7: Fixing views from mysql 2023-05-30 1:50:37 10 [ERROR] Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error 2023-05-30 1:50:37 10 [Note] View `sys`.`ps_check_lost_instrumentation`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`schema_auto_increment_columns`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`schema_object_overview`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`schema_redundant_indexes`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`schema_unused_indexes`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`session_ssl_status`: the version is set to 100614, algorithm restored to be MERGE sys.host_summary Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.host_summary_by_file_io Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.host_summary_by_file_io_type Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.host_summary_by_stages Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.host_summary_by_statement_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.host_summary_by_statement_type Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.innodb_buffer_stats_by_schema Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.innodb_buffer_stats_by_table Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.innodb_lock_waits Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.io_by_thread_by_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.io_global_by_file_by_bytes Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.io_global_by_file_by_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.io_global_by_wait_by_bytes Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.io_global_by_wait_by_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.latest_file_io Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.memory_by_host_by_current_bytes Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.memory_by_thread_by_current_bytes Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.memory_by_user_by_current_bytes Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.memory_global_by_current_bytes Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.memory_global_total Error 2023-05-30 1:50:37 10 [Note] View `sys`.`version`: the version is set to 100614 2023-05-30 1:50:37 10 [Note] View `sys`.`x$host_summary`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$host_summary_by_file_io`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$host_summary_by_file_io_type`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$host_summary_by_stages`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$host_summary_by_statement_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$host_summary_by_statement_type`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$innodb_buffer_stats_by_schema`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$innodb_buffer_stats_by_table`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$innodb_lock_waits`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$io_by_thread_by_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$io_global_by_file_by_bytes`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$io_global_by_file_by_latency`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$io_global_by_wait_by_bytes`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$io_global_by_wait_by_latency`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$latest_file_io`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$memory_by_host_by_current_bytes`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$memory_by_thread_by_current_bytes`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$memory_by_user_by_current_bytes`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$memory_global_by_current_bytes`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$memory_global_total`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$processlist`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$ps_digest_95th_percentile_by_avg_us`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$ps_digest_avg_latency_distribution`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$schema_flattened_keys`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$schema_index_statistics`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$schema_tables_with_full_table_scans`: the version is set to 100614, algorithm restored to be MERGE : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.metrics Error : Unknown column 'information_schema.INNODB_METRICS.STATUS' in 'field list' Error : View 'sys.metrics' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.processlist Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.ps_check_lost_instrumentation OK sys.schema_auto_increment_columns OK sys.schema_index_statistics Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.schema_object_overview OK sys.schema_redundant_indexes OK sys.schema_table_lock_waits Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.schema_table_statistics Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.schema_table_statistics_with_buffer Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.schema_tables_with_full_table_scans Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.schema_unused_indexes OK sys.session Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.session_ssl_status OK sys.statement_analysis Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.statements_with_errors_or_warnings Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.statements_with_full_table_scans Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.statements_with_runtimes_in_95th_percentile Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.statements_with_sorting Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.statements_with_temp_tables Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.user_summary Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.user_summary_by_file_io Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.user_summary_by_file_io_type Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Ple2023-05-30 1:50:37 10 [Note] View `sys`.`x$session`: the version is set to 100614 2023-05-30 1:50:37 10 [Note] View `sys`.`x$statement_analysis`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$statements_with_errors_or_warnings`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$statements_with_full_table_scans`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$statements_with_runtimes_in_95th_percentile`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$statements_with_sorting`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$statements_with_temp_tables`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$user_summary`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$user_summary_by_file_io`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$user_summary_by_file_io_type`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$user_summary_by_stages`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$user_summary_by_statement_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$user_summary_by_statement_type`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$wait_classes_global_by_avg_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$wait_classes_global_by_latency`: the version is set to 100614, algorithm restored to be TEMPTABLE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$waits_by_host_by_latency`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$waits_by_user_by_latency`: the version is set to 100614, algorithm restored to be MERGE 2023-05-30 1:50:37 10 [Note] View `sys`.`x$waits_global_by_latency`: the version is set to 100614, algorithm restored to be MERGE ase use mariadb-upgrade to fix this error error : Corrupt sys.user_summary_by_stages Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.user_summary_by_statement_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.user_summary_by_statement_type Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.version OK sys.wait_classes_global_by_avg_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.wait_classes_global_by_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.waits_by_host_by_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.waits_by_user_by_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.waits_global_by_latency Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.x$host_summary OK sys.x$host_summary_by_file_io OK sys.x$host_summary_by_file_io_type OK sys.x$host_summary_by_stages OK sys.x$host_summary_by_statement_latency OK sys.x$host_summary_by_statement_type OK sys.x$innodb_buffer_stats_by_schema OK sys.x$innodb_buffer_stats_by_table OK sys.x$innodb_lock_waits OK sys.x$io_by_thread_by_latency OK sys.x$io_global_by_file_by_bytes OK sys.x$io_global_by_file_by_latency OK sys.x$io_global_by_wait_by_bytes OK sys.x$io_global_by_wait_by_latency OK sys.x$latest_file_io OK sys.x$memory_by_host_by_current_bytes OK sys.x$memory_by_thread_by_current_bytes OK sys.x$memory_by_user_by_current_bytes OK sys.x$memory_global_by_current_bytes OK sys.x$memory_global_total OK sys.x$processlist OK sys.x$ps_digest_95th_percentile_by_avg_us OK sys.x$ps_digest_avg_latency_distribution OK sys.x$ps_schema_table_statistics_io Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.x$schema_flattened_keys OK sys.x$schema_index_statistics OK sys.x$schema_table_lock_waits Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.x$schema_table_statistics Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.x$schema_table_statistics_with_buffer Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50742, now running 100614. Please use mariadb-upgrade to fix this error error : Corrupt sys.x$schema_tables_with_full_table_scans OK sys.x$session OK sys.x$statement_analysis OK sys.x$statements_with_errors_or_warnings OK sys.x$statements_with_full_table_scans OK sys.x$statements_with_runtimes_in_95th_percentile OK sys.x$statements_with_sorting OK sys.x$statements_with_temp_tables OK sys.x$user_summary OK sys.x$user_summary_by_file_io OK sys.x$user_summary_by_file_io_type OK sys.x$user_summary_by_stages OK sys.x$user_summary_by_statement_latency OK sys.x$user_summary_by_statement_type OK sys.x$wait_classes_global_by_avg_latency OK sys.x$wait_classes_global_by_latency OK sys.x$waits_by_host_by_latency OK sys.x$waits_by_user_by_latency OK sys.x$waits_global_by_latency OK Phase 4/7: Running 'mysql_fix_privilege_tables' Phase 5/7: Fixing table and database names ... Skipped Phase 6/7: Checking and upgrading tables... Skipped Phase 7/7: Running 'FLUSH PRIVILEGES' OK 2023-05-30 01:50:38+00:00 [Note] [Entrypoint]: Finished mariadb-upgrade 2023-05-30 01:50:38+00:00 [Note] [Entrypoint]: Stopping temporary server 2023-05-30 1:50:38 0 [Note] mariadbd (initiated by: unknown): Normal shutdown 2023-05-30 1:50:38 0 [Note] InnoDB: FTS optimize thread exiting. 2023-05-30 1:50:38 0 [Note] InnoDB: Starting shutdown... 2023-05-30 1:50:38 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2023-05-30 1:50:38 0 [Note] InnoDB: Shutdown completed; log sequence number 12237556; transaction id 2345 2023-05-30 1:50:38 0 [Note] mariadbd: Shutdown complete   2023-05-30 01:50:38+00:00 [Note] [Entrypoint]: Temporary server stopped 2023-05-30 1:50:38 0 [Note] Starting MariaDB 10.6.14-MariaDB-1:10.6.14+maria~ubu2004 source revision ce547cfc0564bf54e73bcc5171a2212d6650eb00 as process 1 2023-05-30 1:50:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2023-05-30 1:50:38 0 [Note] InnoDB: Number of pools: 1 2023-05-30 1:50:38 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2023-05-30 1:50:38 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) 2023-05-30 1:50:38 0 [Note] InnoDB: Using Linux native AIO 2023-05-30 1:50:38 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2023-05-30 1:50:38 0 [Note] InnoDB: Completed initialization of buffer pool 2023-05-30 1:50:38 0 [Note] InnoDB: 128 rollback segments are active. 2023-05-30 1:50:38 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2023-05-30 1:50:38 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2023-05-30 1:50:38 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2023-05-30 1:50:38 0 [Note] InnoDB: 10.6.14 started; log sequence number 12237556; transaction id 2340 2023-05-30 1:50:38 0 [Note] Plugin 'FEEDBACK' is disabled. 2023-05-30 1:50:38 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2023-05-30 1:50:38 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. 2023-05-30 1:50:38 0 [Note] InnoDB: Buffer pool(s) load completed at 230530 1:50:38 2023-05-30 1:50:38 0 [Note] Server socket created on IP: '0.0.0.0'. 2023-05-30 1:50:38 0 [Note] Server socket created on IP: '::'. 2023-05-30 1:50:39 0 [Note] mariadbd: ready for connections. Version: '10.6.14-MariaDB-1:10.6.14+maria~ubu2004' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution mysql.proc was corrected late in the update. Maybe best to drop 10.6 sys and install our version?

            People

              Unassigned Unassigned
              anel Anel Husakovic
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.