Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ubuntu@vps-ed88406e:~/darkot2/database$ docker-compose up
- Recreating database_database_1 ... done
- Starting database_phpmyadmin_1 ... done
- Attaching to database_phpmyadmin_1, database_database_1
- database_1 | 2022-08-18 16:34:46+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.38-1.el7 started.
- phpmyadmin_1 | [Thu Aug 18 16:34:46.487213 2022] [mpm_prefork:notice] [pid 1] A H00163: Apache/2.4.53 (Debian) PHP/8.0.19 configured -- resuming normal operatio ns
- phpmyadmin_1 | [Thu Aug 18 16:34:46.487273 2022] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
- database_1 | 2022-08-18 16:34:46+00:00 [Note] [Entrypoint]: Switching to dedi cated user 'mysql'
- database_1 | 2022-08-18 16:34:46+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 5.7.38-1.el7 started.
- database_1 | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
- database_1 | 2022-08-18T16:34:46.950784Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- database_1 | 2022-08-18T16:34:46.952981Z 0 [Note] mysqld (mysqld 5.7.38) star ting as process 1 ...
- database_1 | 2022-08-18T16:34:46.957475Z 0 [Note] InnoDB: PUNCH HOLE support available
- database_1 | 2022-08-18T16:34:46.957605Z 0 [Note] InnoDB: Mutexes and rw_lock s use GCC atomic builtins
- database_1 | 2022-08-18T16:34:46.957694Z 0 [Note] InnoDB: Uses event mutexes
- database_1 | 2022-08-18T16:34:46.957781Z 0 [Note] InnoDB: GCC builtin __atomi c_thread_fence() is used for memory barrier
- database_1 | 2022-08-18T16:34:46.957869Z 0 [Note] InnoDB: Compressed tables u se zlib 1.2.11
- database_1 | 2022-08-18T16:34:46.957949Z 0 [Note] InnoDB: Using Linux native AIO
- database_1 | 2022-08-18T16:34:46.958714Z 0 [Note] InnoDB: Number of pools: 1
- database_1 | 2022-08-18T16:34:46.959085Z 0 [Note] InnoDB: Using CPU crc32 ins tructions
- database_1 | 2022-08-18T16:34:46.962068Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
- database_1 | 2022-08-18T16:34:46.972422Z 0 [Note] InnoDB: Completed initializ ation of buffer pool
- database_1 | 2022-08-18T16:34:46.975391Z 0 [Note] InnoDB: If the mysqld execu tion user is authorized, page cleaner thread priority can be changed. See the ma n page of setpriority().
- database_1 | 2022-08-18T16:34:46.992140Z 0 [Note] InnoDB: Highest supported f ile format is Barracuda.
- database_1 | 2022-08-18T16:34:47.003192Z 0 [Note] InnoDB: pre-5.7.2 rseg: 8 h olds data to be purged. History length: 1. Recommend slow shutdown with innodb_f ast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.004713Z 0 [Note] InnoDB: pre-5.7.2 rseg: 9 h olds data to be purged. History length: 2. Recommend slow shutdown with innodb_f ast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.005970Z 0 [Note] InnoDB: pre-5.7.2 rseg: 10 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.006675Z 0 [Note] InnoDB: pre-5.7.2 rseg: 11 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.007417Z 0 [Note] InnoDB: pre-5.7.2 rseg: 12 holds data to be purged. History length: 1. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.010144Z 0 [Note] InnoDB: pre-5.7.2 rseg: 23 holds data to be purged. History length: 1. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.011238Z 0 [Note] InnoDB: pre-5.7.2 rseg: 24 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.012299Z 0 [Note] InnoDB: pre-5.7.2 rseg: 25 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.013779Z 0 [Note] InnoDB: pre-5.7.2 rseg: 26 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.014324Z 0 [Note] InnoDB: pre-5.7.2 rseg: 27 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.015160Z 0 [Note] InnoDB: pre-5.7.2 rseg: 28 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.015772Z 0 [Note] InnoDB: pre-5.7.2 rseg: 29 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.016475Z 0 [Note] InnoDB: pre-5.7.2 rseg: 30 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.016852Z 0 [Note] InnoDB: pre-5.7.2 rseg: 31 holds data to be purged. History length: 2. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.017304Z 0 [Note] InnoDB: pre-5.7.2 rseg: 32 holds data to be purged. History length: 1. Recommend slow shutdown with innodb_ fast_shutdown=0 and restart
- database_1 | 2022-08-18T16:34:47.020780Z 0 [Warning] InnoDB: Upgrading redo l og: 2*3072 pages, LSN=1698596
- database_1 | 2022-08-18T16:34:47.123519Z 0 [Warning] InnoDB: Starting to dele te and rewrite log files.
- database_1 | 2022-08-18T16:34:47.124655Z 0 [Note] InnoDB: Setting log file ./ ib_logfile101 size to 48 MB
- database_1 | 2022-08-18T16:34:47.210659Z 0 [Note] InnoDB: Setting log file ./ ib_logfile1 size to 48 MB
- database_1 | 2022-08-18T16:34:47.287013Z 0 [Note] InnoDB: Renaming log file . /ib_logfile101 to ./ib_logfile0
- database_1 | 2022-08-18T16:34:47.287240Z 0 [Warning] InnoDB: New log files cr eated, LSN=1698596
- database_1 | 2022-08-18T16:34:47.287913Z 0 [Note] InnoDB: Successfully reset 17 pre-5.7.2 rseg slots.
- database_1 | 2022-08-18T16:34:47.288035Z 0 [Note] InnoDB: Creating shared tab lespace for temporary tables
- database_1 | 2022-08-18T16:34:47.288348Z 0 [Note] InnoDB: Setting file './ibt mp1' size to 12 MB. Physically writing the file full; Please wait ...
- database_1 | 2022-08-18T16:34:47.306916Z 0 [Note] InnoDB: File './ibtmp1' siz e is now 12 MB.
- database_1 | 2022-08-18T16:34:47.308174Z 0 [Note] InnoDB: 96 redo rollback se gment(s) found. 96 redo rollback segment(s) are active.
- database_1 | 2022-08-18T16:34:47.308300Z 0 [Note] InnoDB: 32 non-redo rollbac k segment(s) are active.
- database_1 | 2022-08-18T16:34:47.308774Z 0 [Note] InnoDB: Creating sys_virtua l system tables.
- database_1 | 2022-08-18T16:34:47.310343Z 0 [Note] InnoDB: sys_virtual table c reated
- database_1 | 2022-08-18T16:34:47.310691Z 0 [Note] InnoDB: Waiting for purge t o start
- database_1 | 2022-08-18T16:34:47.360948Z 0 [Note] InnoDB: 5.7.38 started; log sequence number 0
- database_1 | 2022-08-18T16:34:47.361829Z 0 [Note] InnoDB: Loading buffer pool (s) from /var/lib/mysql/ib_buffer_pool
- database_1 | 2022-08-18T16:34:47.362026Z 0 [ERROR] InnoDB: Cannot open '/var/ lib/mysql/ib_buffer_pool' for reading: No such file or directory
- database_1 | 2022-08-18T16:34:47.363111Z 0 [Note] Plugin 'FEDERATED' is disab led.
- database_1 | 2022-08-18T16:34:47.369546Z 0 [Warning] System table 'plugin' is expected to be transactional.
- database_1 | 2022-08-18T16:34:47.371091Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
- database_1 | 2022-08-18T16:34:48.197622Z 0 [Note] Auto generated SSL certific ates are placed in data directory.
- database_1 | 2022-08-18T16:34:48.197866Z 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
- database_1 | 2022-08-18T16:34:48.197913Z 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
- database_1 | 2022-08-18T16:34:48.198863Z 0 [Warning] CA certificate ca.pem is self signed.
- database_1 | 2022-08-18T16:34:48.386983Z 0 [Note] Auto generated RSA key file s are placed in data directory.
- database_1 | 2022-08-18T16:34:48.387907Z 0 [Note] Server hostname (bind-addre ss): '*'; port: 3306
- database_1 | 2022-08-18T16:34:48.388083Z 0 [Note] IPv6 is available.
- database_1 | 2022-08-18T16:34:48.388171Z 0 [Note] - '::' resolves to '::';
- database_1 | 2022-08-18T16:34:48.388265Z 0 [Note] Server socket created on IP : '::'.
- database_1 | 2022-08-18T16:34:48.390613Z 0 [Warning] Insecure configuration f or --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS us ers. Consider choosing a different directory.
- database_1 | 2022-08-18T16:34:48.391093Z 0 [Warning] Failed to open optimizer cost constant tables
- database_1 |
- database_1 | 2022-08-18T16:34:48.394478Z 0 [Warning] 'proxies_priv' entry '@ root@vps-ed88406e' ignored in --skip-name-resolve mode.
- database_1 | 2022-08-18T16:34:48.398438Z 0 [Warning] System table 'time_zone_ leap_second' is expected to be transactional.
- database_1 | 2022-08-18T16:34:48.398702Z 0 [Warning] System table 'time_zone_ name' is expected to be transactional.
- database_1 | 2022-08-18T16:34:48.398969Z 0 [Warning] System table 'time_zone' is expected to be transactional.
- database_1 | 2022-08-18T16:34:48.399105Z 0 [Warning] System table 'time_zone_ transition_type' is expected to be transactional.
- database_1 | 2022-08-18T16:34:48.399440Z 0 [Warning] System table 'time_zone_ transition' is expected to be transactional.
- database_1 | 2022-08-18T16:34:48.402759Z 0 [Warning] System table 'servers' i s expected to be transactional.
- database_1 | 2022-08-18T16:34:48.405170Z 0 [ERROR] Incorrect definition of ta ble performance_schema.events_waits_current: expected column 'NESTING_EVENT_TYPE ' at position 15 to have type enum('TRANSACTION','STATEMENT','STAGE','WAIT', fou nd type enum('STATEMENT','STAGE','WAIT').
- database_1 | 2022-08-18T16:34:48.405769Z 0 [ERROR] Incorrect definition of ta ble performance_schema.events_waits_history: expected column 'NESTING_EVENT_TYPE ' at position 15 to have type enum('TRANSACTION','STATEMENT','STAGE','WAIT', fou nd type enum('STATEMENT','STAGE','WAIT').
- database_1 | 2022-08-18T16:34:48.406450Z 0 [ERROR] Incorrect definition of ta ble 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').
- database_1 | 2022-08-18T16:34:48.408109Z 0 [ERROR] Incorrect definition of ta ble performance_schema.events_waits_summary_by_user_by_event_name: expected colu mn 'USER' at position 0 to have type char(32), found type char(16).
- database_1 | 2022-08-18T16:34:48.408826Z 0 [ERROR] Incorrect definition of ta ble performance_schema.events_waits_summary_by_account_by_event_name: expected c olumn 'USER' at position 0 to have type char(32), found type char(16).
- database_1 | 2022-08-18T16:34:48.412469Z 0 [ERROR] Column count of performanc e_schema.setup_actors is wrong. Expected 5, found 3. Created with MySQL 50651, n ow running 50738. Please use mysql_upgrade to fix this error.
- database_1 | 2022-08-18T16:34:48.413920Z 0 [ERROR] Incorrect definition of ta ble performance_schema.setup_objects: expected column 'OBJECT_TYPE' at position 0 to have type enum('EVENT','FUNCTION','PROCEDURE','TABLE','TRIGGER', found type enum('TABLE').
- database_1 | 2022-08-18T16:34:48.415575Z 0 [ERROR] Column count of performanc e_schema.table_lock_waits_summary_by_table is wrong. Expected 68, found 73. Crea ted with MySQL 50651, now running 50738. Please use mysql_upgrade to fix this er ror.
- database_1 | 2022-08-18T16:34:48.416046Z 0 [ERROR] Column count of performanc e_schema.threads is wrong. Expected 17, found 14. Created with MySQL 50651, now running 50738. Please use mysql_upgrade to fix this error.
- database_1 | 2022-08-18T16:34:48.416558Z 0 [ERROR] Column count of performanc e_schema.events_stages_current is wrong. Expected 12, found 10. Created with MyS QL 50651, now running 50738. Please use mysql_upgrade to fix this error.
- database_1 | 2022-08-18T16:34:48.417007Z 0 [ERROR] Column count of performanc e_schema.events_stages_history is wrong. Expected 12, found 10. Created with MyS QL 50651, now running 50738. Please use mysql_upgrade to fix this error.
- database_1 | 2022-08-18T16:34:48.417503Z 0 [ERROR] Column count of performanc e_schema.events_stages_history_long is wrong. Expected 12, found 10. Created wit h MySQL 50651, now running 50738. Please use mysql_upgrade to fix this error.
- database_1 | 2022-08-18T16:34:48.418342Z 0 [ERROR] Incorrect definition of ta ble 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).
- database_1 | 2022-08-18T16:34:48.419229Z 0 [ERROR] Incorrect definition of ta ble performance_schema.events_stages_summary_by_user_by_event_name: expected col umn 'USER' at position 0 to have type char(32), found type char(16).
- database_1 | 2022-08-18T16:34:48.420377Z 0 [ERROR] Column count of performanc e_schema.events_statements_current is wrong. Expected 41, found 40. Created with MySQL 50651, now running 50738. Please use mysql_upgrade to fix this error.
- database_1 | 2022-08-18T16:34:48.420918Z 0 [ERROR] Column count of performanc e_schema.events_statements_history is wrong. Expected 41, found 40. Created with MySQL 50651, now running 50738. Please use mysql_upgrade to fix this error.
- database_1 | 2022-08-18T16:34:48.421506Z 0 [ERROR] Column count of performanc e_schema.events_statements_history_long is wrong. Expected 41, found 40. Created with MySQL 50651, now running 50738. Please use mysql_upgrade to fix this error .
- database_1 | 2022-08-18T16:34:48.422348Z 0 [ERROR] Incorrect definition of ta ble performance_schema.events_statements_summary_by_account_by_event_name: expec ted column 'USER' at position 0 to have type char(32), found type char(16).
- database_1 | 2022-08-18T16:34:48.422884Z 0 [ERROR] Incorrect definition of ta ble 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).
- database_1 | 2022-08-18T16:34:48.424075Z 0 [ERROR] Native table 'performance_ schema'.'events_statements_summary_by_program' has the wrong structure
- database_1 | 2022-08-18T16:34:48.424213Z 0 [ERROR] Native table 'performance_ schema'.'events_transactions_current' has the wrong structure
- database_1 | 2022-08-18T16:34:48.424334Z 0 [ERROR] Native table 'performance_ schema'.'events_transactions_history' has the wrong structure
- database_1 | 2022-08-18T16:34:48.424627Z 0 [ERROR] Native table 'performance_ schema'.'events_transactions_history_long' has the wrong structure
- database_1 | 2022-08-18T16:34:48.424919Z 0 [ERROR] Native table 'performance_ schema'.'events_transactions_summary_by_thread_by_event_name' has the wrong stru cture
- database_1 | 2022-08-18T16:34:48.425022Z 0 [ERROR] Native table 'performance_ schema'.'events_transactions_summary_by_account_by_event_name' has the wrong str ucture
- database_1 | 2022-08-18T16:34:48.425262Z 0 [ERROR] Native table 'performance_ schema'.'events_transactions_summary_by_user_by_event_name' has the wrong struct ure
- database_1 | 2022-08-18T16:34:48.425516Z 0 [ERROR] Native table 'performance_ schema'.'events_transactions_summary_by_host_by_event_name' has the wrong struct ure
- database_1 | 2022-08-18T16:34:48.425674Z 0 [ERROR] Native table 'performance_ schema'.'events_transactions_summary_global_by_event_name' has the wrong structu re
- database_1 | 2022-08-18T16:34:48.426336Z 0 [ERROR] Incorrect definition of ta ble performance_schema.users: expected column 'USER' at position 0 to have type char(32), found type char(16).
- database_1 | 2022-08-18T16:34:48.426828Z 0 [ERROR] Incorrect definition of ta ble performance_schema.accounts: expected column 'USER' at position 0 to have ty pe char(32), found type char(16).
- database_1 | 2022-08-18T16:34:48.428968Z 0 [ERROR] Native table 'performance_ schema'.'memory_summary_global_by_event_name' has the wrong structure
- database_1 | 2022-08-18T16:34:48.429086Z 0 [ERROR] Native table 'performance_ schema'.'memory_summary_by_account_by_event_name' has the wrong structure
- database_1 | 2022-08-18T16:34:48.429225Z 0 [ERROR] Native table 'performance_ schema'.'memory_summary_by_host_by_event_name' has the wrong structure
- database_1 | 2022-08-18T16:34:48.429465Z 0 [ERROR] Native table 'performance_ schema'.'memory_summary_by_thread_by_event_name' has the wrong structure
- database_1 | 2022-08-18T16:34:48.429598Z 0 [ERROR] Native table 'performance_ schema'.'memory_summary_by_user_by_event_name' has the wrong structure
- database_1 | 2022-08-18T16:34:48.429755Z 0 [ERROR] Native table 'performance_ schema'.'table_handles' has the wrong structure
- database_1 | 2022-08-18T16:34:48.429999Z 0 [ERROR] Native table 'performance_ schema'.'metadata_locks' has the wrong structure
- database_1 | 2022-08-18T16:34:48.430130Z 0 [ERROR] Native table 'performance_ schema'.'replication_connection_configuration' has the wrong structure
- database_1 | 2022-08-18T16:34:48.430458Z 0 [ERROR] Native table 'performance_ schema'.'replication_group_members' has the wrong structure
- database_1 | 2022-08-18T16:34:48.430650Z 0 [ERROR] Native table 'performance_ schema'.'replication_connection_status' has the wrong structure
- database_1 | 2022-08-18T16:34:48.430814Z 0 [ERROR] Native table 'performance_ schema'.'replication_applier_configuration' has the wrong structure
- database_1 | 2022-08-18T16:34:48.431167Z 0 [ERROR] Native table 'performance_ schema'.'replication_applier_status' has the wrong structure
- database_1 | 2022-08-18T16:34:48.431384Z 0 [ERROR] Native table 'performance_ schema'.'replication_applier_status_by_coordinator' has the wrong structure
- database_1 | 2022-08-18T16:34:48.431655Z 0 [ERROR] Native table 'performance_ schema'.'replication_applier_status_by_worker' has the wrong structure
- database_1 | 2022-08-18T16:34:48.431891Z 0 [ERROR] Native table 'performance_ schema'.'replication_group_member_stats' has the wrong structure
- database_1 | 2022-08-18T16:34:48.432107Z 0 [ERROR] Native table 'performance_ schema'.'prepared_statements_instances' has the wrong structure
- database_1 | 2022-08-18T16:34:48.432320Z 0 [ERROR] Native table 'performance_ schema'.'user_variables_by_thread' has the wrong structure
- database_1 | 2022-08-18T16:34:48.432534Z 0 [ERROR] Native table 'performance_ schema'.'status_by_account' has the wrong structure
- database_1 | 2022-08-18T16:34:48.432732Z 0 [ERROR] Native table 'performance_ schema'.'status_by_host' has the wrong structure
- database_1 | 2022-08-18T16:34:48.432875Z 0 [ERROR] Native table 'performance_ schema'.'status_by_thread' has the wrong structure
- database_1 | 2022-08-18T16:34:48.433123Z 0 [ERROR] Native table 'performance_ schema'.'status_by_user' has the wrong structure
- database_1 | 2022-08-18T16:34:48.433236Z 0 [ERROR] Native table 'performance_ schema'.'global_status' has the wrong structure
- database_1 | 2022-08-18T16:34:48.433395Z 0 [ERROR] Native table 'performance_ schema'.'session_status' has the wrong structure
- database_1 | 2022-08-18T16:34:48.433705Z 0 [ERROR] Native table 'performance_ schema'.'variables_by_thread' has the wrong structure
- database_1 | 2022-08-18T16:34:48.434023Z 0 [ERROR] Native table 'performance_ schema'.'global_variables' has the wrong structure
- database_1 | 2022-08-18T16:34:48.434151Z 0 [ERROR] Native table 'performance_ schema'.'session_variables' has the wrong structure
- database_1 | 2022-08-18T16:34:48.434602Z 0 [ERROR] Incorrect definition of ta ble mysql.db: expected column 'User' at position 2 to have type char(32), found type char(16).
- database_1 | 2022-08-18T16:34:48.434709Z 0 [ERROR] mysql.user has no `Event_p riv` column at position 28
- database_1 | 2022-08-18T16:34:48.435977Z 0 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
- database_1 | 2022-08-18T16:34:48.436486Z 0 [Note] mysqld: ready for connectio ns.
- database_1 | Version: '5.7.38' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)
Add Comment
Please, Sign In to add comment