Error following upgrade from 1.8.2 to 3.14

To be completed by the original poster:

CMS Version

1.8.2

Installation Method

Docker

Operating System

Ubuntu 20.04

Issue

Attempting to do an upgrade to the latest version and when the upgrade seems complete I receive an error on the login page

Error

Unexpected Error, please contact support.

Please press the button below to go to your homepage or press back in your browser

What information should I include to help with this error?

I did upgrade the docker-compose version to the v2.7.0 version and that seemed to be operating properly.

Hi, welcome to the community.

Have you followed the upgrade instructions detailed here: Upgrade Xibo for Docker Install?

Yes I was working from that set of instructions and I attempted 2 different upgrades, one to the 2.x version and one to the 3.x version and both had errors when I try to login to the CMS. which logs can I view to see what has gone wrong?

I can go back to the 1.8.2 version that was working and make an additional attempt.

root@Neptune:/opt/xibo# docker-compose up
[+] Running 6/6
⠿ Network xibo_default Created 0.1s
⠿ Container xibo-cms-xmr-1 Created 1.1s
⠿ Container xibo-cms-memcached-1 Created 1.1s
⠿ Container xibo-cms-db-1 Created 1.1s
⠿ Container xibo-cms-quickchart-1 Created 1.1s
⠿ Container xibo-cms-web-1 Created 0.7s
Attaching to xibo-cms-db-1, xibo-cms-memcached-1, xibo-cms-quickchart-1, xibo-cms-web-1, xibo-cms-xmr-1
xibo-cms-db-1 | 2022-07-22 17:29:18+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.34-1debian10 started.
xibo-cms-db-1 | 2022-07-22 17:29:19+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
xibo-cms-db-1 | 2022-07-22 17:29:19+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.34-1debian10 started.
xibo-cms-db-1 | 2022-07-22T17:29:19.552355Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
xibo-cms-db-1 | 2022-07-22T17:29:19.555978Z 0 [Note] mysqld (mysqld 5.7.34) starting as process 1 …
xibo-cms-db-1 | 2022-07-22T17:29:19.562154Z 0 [Note] InnoDB: PUNCH HOLE support available
xibo-cms-db-1 | 2022-07-22T17:29:19.562191Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
xibo-cms-db-1 | 2022-07-22T17:29:19.562200Z 0 [Note] InnoDB: Uses event mutexes
xibo-cms-db-1 | 2022-07-22T17:29:19.562208Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
xibo-cms-db-1 | 2022-07-22T17:29:19.562216Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
xibo-cms-db-1 | 2022-07-22T17:29:19.562224Z 0 [Note] InnoDB: Using Linux native AIO
xibo-cms-db-1 | 2022-07-22T17:29:19.562745Z 0 [Note] InnoDB: Number of pools: 1
xibo-cms-db-1 | 2022-07-22T17:29:19.562961Z 0 [Note] InnoDB: Not using CPU crc32 instructions
xibo-cms-db-1 | 2022-07-22T17:29:19.566958Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
xibo-cms-db-1 | 2022-07-22T17:29:19.586352Z 0 [Note] InnoDB: Completed initialization of buffer pool
xibo-cms-db-1 | 2022-07-22T17:29:19.591446Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
xibo-cms-db-1 | 2022-07-22T17:29:19.606169Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
xibo-cms-quickchart-1 | Stackdriver logging is disabled
xibo-cms-quickchart-1 | {“name”:“quickchart”,“hostname”:“ed4102870cca”,“pid”:1,“level”:30,“msg”:“Telemetry is enabled”,“time”:“2022-07-22T17:29:19.649Z”,“v”:0}
xibo-cms-db-1 | 2022-07-22T17:29:19.664018Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
xibo-cms-db-1 | 2022-07-22T17:29:19.664169Z 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
xibo-cms-db-1 | 2022-07-22T17:29:19.888024Z 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.
xibo-cms-db-1 | 2022-07-22T17:29:19.890078Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
xibo-cms-db-1 | 2022-07-22T17:29:19.890495Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
xibo-cms-db-1 | 2022-07-22T17:29:19.891592Z 0 [Note] InnoDB: 5.7.34 started; log sequence number 4715272058
xibo-cms-db-1 | 2022-07-22T17:29:19.891954Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
xibo-cms-db-1 | 2022-07-22T17:29:19.892439Z 0 [Note] Plugin ‘FEDERATED’ is disabled.
xibo-cms-db-1 | 2022-07-22T17:29:19.900272Z 0 [Warning] System table ‘plugin’ is expected to be transactional.
xibo-cms-db-1 | 2022-07-22T17:29:19.901613Z 0 [Warning] Gtid table is not ready to be used. Table ‘mysql.gtid_executed’ cannot be opened.
xibo-cms-db-1 | 2022-07-22T17:29:19.901920Z 0 [Note] InnoDB: Buffer pool(s) load completed at 220722 17:29:19
xibo-cms-db-1 | 2022-07-22T17:29:19.904944Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
xibo-cms-db-1 | 2022-07-22T17:29:19.905176Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
xibo-cms-db-1 | 2022-07-22T17:29:19.906473Z 0 [Warning] CA certificate ca.pem is self signed.
xibo-cms-db-1 | 2022-07-22T17:29:19.906761Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
xibo-cms-db-1 | 2022-07-22T17:29:19.908048Z 0 [Note] Server hostname (bind-address): ‘'; port: 3306
xibo-cms-db-1 | 2022-07-22T17:29:19.908459Z 0 [Note] IPv6 is available.
xibo-cms-db-1 | 2022-07-22T17:29:19.909748Z 0 [Note] - ‘::’ resolves to ‘::’;
xibo-cms-db-1 | 2022-07-22T17:29:19.910057Z 0 [Note] Server socket created on IP: ‘::’.
xibo-cms-db-1 | 2022-07-22T17:29:19.939324Z 0 [Warning] Insecure configuration for --pid-file: Location ‘/var/run/mysqld’ in the path is accessible to all OS users. Consider choosing a different directory.
xibo-cms-db-1 | 2022-07-22T17:29:19.940014Z 0 [Warning] Failed to open optimizer cost constant tables
xibo-cms-db-1 |
xibo-cms-db-1 | 2022-07-22T17:29:19.941436Z 0 [Warning] ‘proxies_priv’ entry ‘@ root@d8cb24d10c31’ ignored in --skip-name-resolve mode.
xibo-cms-db-1 | 2022-07-22T17:29:19.942890Z 0 [Warning] System table ‘time_zone_leap_second’ is expected to be transactional.
xibo-cms-db-1 | 2022-07-22T17:29:19.942908Z 0 [Warning] System table ‘time_zone_name’ is expected to be transactional.
xibo-cms-db-1 | 2022-07-22T17:29:19.942914Z 0 [Warning] System table ‘time_zone’ is expected to be transactional.
xibo-cms-db-1 | 2022-07-22T17:29:19.942919Z 0 [Warning] System table ‘time_zone_transition_type’ is expected to be transactional.
xibo-cms-db-1 | 2022-07-22T17:29:19.942924Z 0 [Warning] System table ‘time_zone_transition’ is expected to be transactional.
xibo-cms-db-1 | 2022-07-22T17:29:19.944443Z 0 [Warning] System table ‘servers’ is expected to be transactional.
xibo-cms-db-1 | 2022-07-22T17:29:19.945244Z 0 [ERROR] Incorrect definition of table performance_schema.events_waits_current: expected column ‘NESTING_EVENT_TYPE’ at position 15 to have type enum(‘TRANSACTION’,‘STATEMENT’,‘STAGE’,‘WAIT’, found type enum(‘STATEMENT’,‘STAGE’,‘WAIT’).
xibo-cms-db-1 | 2022-07-22T17:29:19.945503Z 0 [ERROR] Incorrect definition of table performance_schema.events_waits_history: expected column ‘NESTING_EVENT_TYPE’ at position 15 to have type enum(‘TRANSACTION’,‘STATEMENT’,‘STAGE’,‘WAIT’, found type enum(‘STATEMENT’,‘STAGE’,‘WAIT’).
xibo-cms-db-1 | 2022-07-22T17:29:19.945683Z 0 [ERROR] Incorrect definition of table performance_schema.events_waits_history_long: expected column ‘NESTING_EVENT_TYPE’ at position 15 to have type enum(‘TRANSACTION’,‘STATEMENT’,‘STAGE’,‘WAIT’, found type enum(‘STATEMENT’,‘STAGE’,‘WAIT’).
xibo-cms-db-1 | 2022-07-22T17:29:19.946367Z 0 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_user_by_event_name: expected column ‘USER’ at position 0 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.946671Z 0 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_account_by_event_name: expected column ‘USER’ at position 0 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.947780Z 0 [ERROR] Column count of performance_schema.setup_actors is wrong. Expected 5, found 3. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.948156Z 0 [ERROR] Incorrect definition of table performance_schema.setup_objects: expected column ‘OBJECT_TYPE’ at position 0 to have type enum(‘EVENT’,‘FUNCTION’,‘PROCEDURE’,‘TABLE’,‘TRIGGER’, found type enum(‘TABLE’).
xibo-cms-db-1 | 2022-07-22T17:29:19.948860Z 0 [ERROR] Column count of performance_schema.table_lock_waits_summary_by_table is wrong. Expected 68, found 73. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.949044Z 0 [ERROR] Column count of performance_schema.threads is wrong. Expected 17, found 14. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.949217Z 0 [ERROR] Column count of performance_schema.events_stages_current is wrong. Expected 12, found 10. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.949386Z 0 [ERROR] Column count of performance_schema.events_stages_history is wrong. Expected 12, found 10. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.949554Z 0 [ERROR] Column count of performance_schema.events_stages_history_long is wrong. Expected 12, found 10. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.949832Z 0 [ERROR] Incorrect definition of table performance_schema.events_stages_summary_by_account_by_event_name: expected column ‘USER’ at position 0 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.950008Z 0 [ERROR] Incorrect definition of table performance_schema.events_stages_summary_by_user_by_event_name: expected column ‘USER’ at position 0 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.950432Z 0 [ERROR] Column count of performance_schema.events_statements_current is wrong. Expected 41, found 40. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.950651Z 0 [ERROR] Column count of performance_schema.events_statements_history is wrong. Expected 41, found 40. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.951582Z 0 [ERROR] Column count of performance_schema.events_statements_history_long is wrong. Expected 41, found 40. Created with MySQL 50636, now running 50734. Please use mysql_upgrade to fix this error.
xibo-cms-db-1 | 2022-07-22T17:29:19.951951Z 0 [ERROR] Incorrect definition of table performance_schema.events_statements_summary_by_account_by_event_name: expected column ‘USER’ at position 0 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.952087Z 0 [ERROR] Incorrect definition of table performance_schema.events_statements_summary_by_user_by_event_name: expected column ‘USER’ at position 0 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.952639Z 0 [ERROR] Native table ‘performance_schema’.‘events_statements_summary_by_program’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.952689Z 0 [ERROR] Native table ‘performance_schema’.‘events_transactions_current’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.952731Z 0 [ERROR] Native table ‘performance_schema’.‘events_transactions_history’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.952846Z 0 [ERROR] Native table ‘performance_schema’.‘events_transactions_history_long’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.952939Z 0 [ERROR] Native table ‘performance_schema’.‘events_transactions_summary_by_thread_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.953010Z 0 [ERROR] Native table ‘performance_schema’.‘events_transactions_summary_by_account_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.953058Z 0 [ERROR] Native table ‘performance_schema’.‘events_transactions_summary_by_user_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.953105Z 0 [ERROR] Native table ‘performance_schema’.‘events_transactions_summary_by_host_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.953193Z 0 [ERROR] Native table ‘performance_schema’.‘events_transactions_summary_global_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.953350Z 0 [ERROR] Incorrect definition of table performance_schema.users: expected column ‘USER’ at position 0 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.953514Z 0 [ERROR] Incorrect definition of table performance_schema.accounts: expected column ‘USER’ at position 0 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.954255Z 0 [ERROR] Native table ‘performance_schema’.‘memory_summary_global_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954307Z 0 [ERROR] Native table ‘performance_schema’.‘memory_summary_by_account_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954383Z 0 [ERROR] Native table ‘performance_schema’.‘memory_summary_by_host_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954455Z 0 [ERROR] Native table ‘performance_schema’.‘memory_summary_by_thread_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954526Z 0 [ERROR] Native table ‘performance_schema’.‘memory_summary_by_user_by_event_name’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954610Z 0 [ERROR] Native table ‘performance_schema’.‘table_handles’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954685Z 0 [ERROR] Native table ‘performance_schema’.‘metadata_locks’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954771Z 0 [ERROR] Native table ‘performance_schema’.‘replication_connection_configuration’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954839Z 0 [ERROR] Native table ‘performance_schema’.‘replication_group_members’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954929Z 0 [ERROR] Native table ‘performance_schema’.‘replication_connection_status’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.954996Z 0 [ERROR] Native table ‘performance_schema’.‘replication_applier_configuration’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955073Z 0 [ERROR] Native table ‘performance_schema’.‘replication_applier_status’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955143Z 0 [ERROR] Native table ‘performance_schema’.‘replication_applier_status_by_coordinator’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955233Z 0 [ERROR] Native table ‘performance_schema’.‘replication_applier_status_by_worker’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955311Z 0 [ERROR] Native table ‘performance_schema’.‘replication_group_member_stats’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955382Z 0 [ERROR] Native table ‘performance_schema’.‘prepared_statements_instances’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955451Z 0 [ERROR] Native table ‘performance_schema’.‘user_variables_by_thread’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955517Z 0 [ERROR] Native table ‘performance_schema’.‘status_by_account’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955590Z 0 [ERROR] Native table ‘performance_schema’.‘status_by_host’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955655Z 0 [ERROR] Native table ‘performance_schema’.‘status_by_thread’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955742Z 0 [ERROR] Native table ‘performance_schema’.‘status_by_user’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955807Z 0 [ERROR] Native table ‘performance_schema’.‘global_status’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955894Z 0 [ERROR] Native table ‘performance_schema’.‘session_status’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.955960Z 0 [ERROR] Native table ‘performance_schema’.‘variables_by_thread’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.956031Z 0 [ERROR] Native table ‘performance_schema’.‘global_variables’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.956099Z 0 [ERROR] Native table ‘performance_schema’.‘session_variables’ has the wrong structure
xibo-cms-db-1 | 2022-07-22T17:29:19.956339Z 0 [ERROR] Incorrect definition of table mysql.db: expected column ‘User’ at position 2 to have type char(32), found type char(16).
xibo-cms-db-1 | 2022-07-22T17:29:19.956408Z 0 [ERROR] mysql.user has no Event_priv column at position 28
xibo-cms-db-1 | 2022-07-22T17:29:19.956802Z 0 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
xibo-cms-db-1 | 2022-07-22T17:29:19.959352Z 0 [Note] mysqld: ready for connections.
xibo-cms-db-1 | Version: ‘5.7.34’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
xibo-cms-web-1 | Waiting for MySQL to start - max 300 seconds
xibo-cms-db-1 | 2022-07-22T17:29:20.019857Z 2 [Note] Got an error reading communication packets
xibo-cms-quickchart-1 | Fri, 22 Jul 2022 17:29:20 GMT body-parser deprecated undefined extended: provide extended option at index.js:38:17
xibo-cms-quickchart-1 | {“name”:“quickchart”,“hostname”:“ed4102870cca”,“pid”:1,“level”:30,“msg”:“Setting request timeout: 5000 ms”,“time”:“2022-07-22T17:29:20.688Z”,“v”:0}
xibo-cms-quickchart-1 | {“name”:“quickchart”,“hostname”:“ed4102870cca”,“pid”:1,“level”:30,“msg”:“NODE_ENV: production”,“time”:“2022-07-22T17:29:20.688Z”,“v”:0}
xibo-cms-quickchart-1 | {“name”:“quickchart”,“hostname”:“ed4102870cca”,“pid”:1,“level”:30,“msg”:“Listening on port 3400”,“time”:“2022-07-22T17:29:20.688Z”,“v”:0}
xibo-cms-web-1 | MySQL started
xibo-cms-web-1 | Configuring MySQL cnf file
xibo-cms-web-1 | Updating settings.php
xibo-cms-db-1 | 2022-07-22T17:29:22.057044Z 3 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.057141Z 3 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-web-1 | settingId
xibo-cms-web-1 | 1
xibo-cms-web-1 | Existing Database, checking if we need to upgrade it
xibo-cms-web-1 | Phinx by CakePHP - https://phinx.org. 0.9.2
xibo-cms-web-1 |
xibo-cms-web-1 | using config file .varwwwcmsphinx.php
xibo-cms-web-1 | using config parser php
xibo-cms-web-1 | using migration paths
xibo-cms-web-1 | - /var/www/cms/db/migrations
xibo-cms-web-1 | warning no environment specified, defaulting to: production
xibo-cms-web-1 | ordering by creation time
xibo-cms-web-1 |
xibo-cms-web-1 | Status [Migration ID] Started Finished Migration Name
xibo-cms-web-1 | ----------------------------------------------------------------------------------
xibo-cms-db-1 | 2022-07-22T17:29:22.216268Z 4 [Warning] InnoDB: Cannot open table cms/phinxlog from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to MySQL :: MySQL 5.7 Reference Manual :: 14.22 InnoDB Troubleshooting for how to resolve the issue.
xibo-cms-web-1 |
xibo-cms-web-1 | In PdoAdapter.php line 145:
xibo-cms-web-1 |
xibo-cms-web-1 | SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘cms.phinxlog’ do
xibo-cms-web-1 | esn’t exist
xibo-cms-web-1 |
xibo-cms-web-1 |
xibo-cms-web-1 | status [-c|–configuration CONFIGURATION] [-p|–parser PARSER] [-e|–environment ENVIRONMENT] [-f|–format FORMAT]
xibo-cms-web-1 |
xibo-cms-web-1 | We will upgrade it, take a backup
xibo-cms-web-1 | mysqldump: Error: ‘Access denied; you need (at least one of) the PROCESS privilege(s) for this operation’ when trying to dump tablespaces
xibo-cms-db-1 | 2022-07-22T17:29:22.243958Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.243990Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.244344Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.244362Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.244608Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.244625Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.244935Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.244953Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.245388Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.245406Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.245686Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.245704Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.246077Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.246095Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.246355Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.246373Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.246682Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.246700Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.246954Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.246971Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.247300Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.247318Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.247848Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.247866Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.248182Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.248200Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.248551Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.248568Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.248856Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.248874Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.249277Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.249294Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.249569Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.249586Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.249908Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.249926Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.250165Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.250182Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.250542Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.250559Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.250851Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.250869Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.251115Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.251133Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.251477Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.251496Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.251787Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.251805Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.252120Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.252137Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.252428Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.252445Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.252756Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.252773Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.253069Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.253086Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.253392Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.253410Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.253689Z 5 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.253707Z 5 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.253963Z 5 [Warning] InnoDB: Cannot open table cms/lktagdisplaygroup from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to MySQL :: MySQL 5.7 Reference Manual :: 14.22 InnoDB Troubleshooting for how to resolve the issue.
xibo-cms-web-1 | mysqldump: Got error: 1146: “Table ‘cms.lktagdisplaygroup’ doesn’t exist” when using LOCK TABLES
xibo-cms-web-1 | Running database migrations
xibo-cms-web-1 | Phinx by CakePHP - https://phinx.org. 0.9.2
xibo-cms-web-1 |
xibo-cms-web-1 | using config file .varwwwcmsphinx.php
xibo-cms-web-1 | using config parser php
xibo-cms-web-1 | using migration paths
xibo-cms-web-1 | - /var/www/cms/db/migrations
xibo-cms-web-1 | warning no environment specified, defaulting to: production
xibo-cms-web-1 | using adapter mysql
xibo-cms-web-1 | using database cms
xibo-cms-db-1 | 2022-07-22T17:29:22.395750Z 6 [Warning] InnoDB: Cannot open table cms/phinxlog from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to MySQL :: MySQL 5.7 Reference Manual :: 14.22 InnoDB Troubleshooting for how to resolve the issue.
xibo-cms-web-1 |
xibo-cms-web-1 | In PdoAdapter.php line 145:
xibo-cms-web-1 |
xibo-cms-web-1 | SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘cms.phinxlog’ do
xibo-cms-web-1 | esn’t exist
xibo-cms-web-1 |
xibo-cms-web-1 |
xibo-cms-web-1 | migrate [-c|–configuration CONFIGURATION] [-p|–parser PARSER] [-e|–environment ENVIRONMENT] [-t|–target TARGET] [-d|–date DATE] [-x|–dry-run]
xibo-cms-web-1 |
xibo-cms-web-1 | Importing ca-certs
xibo-cms-web-1 | cp: can’t stat '/var/www/cms/ca-certs/
.pem’: No such file or directory
xibo-cms-web-1 | cp: can’t stat ‘/var/www/cms/ca-certs/*.crt’: No such file or directory
xibo-cms-web-1 | WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
xibo-cms-web-1 | Setting up Quickchart
xibo-cms-db-1 | 2022-07-22T17:29:22.529415Z 8 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:22.529451Z 8 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-web-1 | Configuring Maintenance
xibo-cms-web-1 | Removing web/install/index.php from production container
xibo-cms-web-1 | Starting cron
xibo-cms-web-1 | Starting webserver
xibo-cms-web-1 | AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using 172.21.0.6. Set the ‘ServerName’ directive globally to suppress this message
xibo-cms-db-1 | 2022-07-22T17:29:24.474718Z 10 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:24.474756Z 10 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:24.475579Z 10 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-db-1 | 2022-07-22T17:29:24.475600Z 10 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name. Please run mysql_upgrade
xibo-cms-web-1 | 192.168.2.123 - - [22/Jul/2022:17:29:24 +0000] “POST /xmds.php?v=5 HTTP/1.1” 500 - “-” “Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)”
xibo-cms-db-1 | 2022-07-22T17:30:00.897461Z 11 [Warning] InnoDB: Cannot open table cms/phinxlog from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to MySQL :: MySQL 5.7 Reference Manual :: 14.22 InnoDB Troubleshooting for how to resolve the issue.
xibo-cms-web-1 | 192.168.2.123 - - [22/Jul/2022:17:30:03 +0000] “POST /xmds.php?v=5 HTTP/1.1” 500 - “-” “Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)”
xibo-cms-web-1 | 192.168.2.123 - - [22/Jul/2022:17:30:03 +0000] “POST /xmds.php?v=5 HTTP/1.1” 500 - “-” “Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)”
xibo-cms-web-1 | 192.168.2.123 - - [22/Jul/2022:17:30:23 +0000] “POST /xmds.php?v=5 HTTP/1.1” 500 - “-” “Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)”
xibo-cms-web-1 | 192.168.2.123 - - [22/Jul/2022:17:30:25 +0000] “POST /xmds.php?v=5 HTTP/1.1” 500 - “-” “Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)”
xibo-cms-db-1 | 2022-07-22T17:31:00.897206Z 16 [Warning] InnoDB: Cannot open table cms/phinxlog from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to MySQL :: MySQL 5.7 Reference Manual :: 14.22 InnoDB Troubleshooting for how to resolve the issue.

I am going to roll back to 1.8.2 and then try to upgrade to the latest in the 1.8.x version then make another attempt at moving to a newer version.

Went back to 1.8.2 and then moved to 1.8.13, following that I was able to login but was unable to edit any of the layouts. Currently I am back to 1.8.2 and could use some help.

thanks,
Baz

I am attempting to get to the last of the 1.8.x releases prior to moving to the 2.x release and then the 3.x release but when I run upgrade in the web portal I receive the following error.

SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘cms.lktagdisplaygroup’ doesn’t exist

How do I repair this?

So far, after doing some work with the mysql tools I think both the lktagdisplaygroup table and the phinx.log tables were corrupted. I was able to, after a backup, remove the files in the shared section for these 2 tables (4 files) and I have been able to get to 2.02. I will keep trying to move forward and eventually get to 3.14

Thanks for your updates.

If those tables were corrupted then there could be other database corruption. You might be better exporting your layouts from your 1.8.2 CMS and importing them in to a new 3.x CMS instead.

If you want to press ahead regardless, you’ll need to recreate those tables - they can’t just be removed I’m afraid. So you’d need to restore your v1.8 CMS backup, repair or recreate those tables, and then upgrade. If you have to recreate then I don’t think it will ever upgrade properly as phinx requires the data in that table to manage the upgrade, so you should try and repair it first.

The logs there also suggest you’re trying to run MySQL 5.7 with a MySQL 5.6 data file. You need to ensure you’re running MySQL 5.6 until you have completed the upgrade to 2.3.16, and then you can switch to MySQL 5.7. It is not supported prior to that.

Once you have switched, you’ll need to manually run the mysql_upgrade command - details here:

I did in the end export my layouts and imported them into a new install of 3.x. The unexpected issue prior to the export/import with MySQL is that I am running the docker versions and I was able to press along until I reached 2.3.10 where the upgrade to 5.7 occurs and that seems to fail.

Now I just need to find out why my newly authorized display will not contact the CMS.

Thanks for the help, I have gotten the new display to connect to the CMS and I am ready to make the jump to 3.x.

Have a great day.
B

1 Like