点击参与 GreatSQL 8.0.32-26 文档捉虫~~~

GreatSQL社区

搜索

GreatSQL群集服务，每天早上6点过几分都会被关闭

155 9 2025-5-22 10:51
以下是日志


2025-05-21T19:21:58.530727+08:00 0 [System] [MY-011492] [Repl] Plugin group_replication reported: 'The member with address 10.28.0.193:3306 was declared online within the replication group.'
2025-05-21T19:22:28.381746+08:00 31 [Note] [MY-010914] [Server] Aborted connection 31 to db: 'unconnected' user: 'boxunrepl' host: '10.28.0.192' (failed on flush_net()).
2025-05-22T06:06:54.904288+08:00 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.32-27).
2025-05-22T06:06:54.904640+08:00 14 [Note] [MY-010596] [Repl] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
2025-05-22T06:06:54.905194+08:00 14 [Note] [MY-010587] [Repl] Slave SQL thread for channel 'group_replication_applier' exiting, replication stopped in log 'FIRST' at position 0
2025-05-22T06:06:54.906976+08:00 0 [Note] [MY-011647] [Repl] Plugin group_replication reported: 'Going to wait for view modification'
2025-05-22T06:06:54.907039+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] xcom_client_remove_node: Try to push xcom_client_remove_node to XCom'
2025-05-22T06:06:54.907522+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] new_site_def, new:0x75544d777c80'
2025-05-22T06:06:54.907557+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] clone_site_def, new:0x75544d777c80,old site:0x755473ba1fa0'
2025-05-22T06:06:54.907576+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] remove_site_def n:1, site:0x75544d777c80'
2025-05-22T06:06:54.907599+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] handle_remove_node calls site_install_action, nodes:1, node number:0'
2025-05-22T06:06:54.907892+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] update_servers is called, max nodes:2'
2025-05-22T06:06:54.907910+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Updating physical connections to other servers'
2025-05-22T06:06:54.907922+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Using existing server node 0 host 10.28.0.192:33061'
2025-05-22T06:06:54.907933+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Using existing server node 1 host 10.28.0.193:33061'
2025-05-22T06:06:54.907955+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Sucessfully installed new site definition. Start synode for this configuration is {20ad2e8c 214557 0}, boot key synode is {20ad2e8c 214546 0}, configured event horizon
=10, my node identifier is 4294967295'
2025-05-22T06:06:54.907977+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] free_site_def site:0x755473b01ec0, x.msgno:214521, x.node:0'
2025-05-22T06:06:57.910829+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] 1747865222.631014 pid 40044 xcom_id 7b18f7d1 state xcom_fsm_run action x_fsm_terminate'
2025-05-22T06:06:57.910901+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] set CON_NULL for fd:82 in close_connection'
2025-05-22T06:06:57.910945+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] set CON_NULL for fd:81 in close_connection'
2025-05-22T06:06:57.910984+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] 1747865222.631187 pid 40044 xcom_id 4c9c119b state xcom_fsm_start action x_fsm_exit'
2025-05-22T06:06:57.911007+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Exiting xcom thread'
2025-05-22T06:06:57.911020+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] terminate_and_exit calls here'
2025-05-22T06:06:57.911038+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] cb_xcom_expel is called'
2025-05-22T06:06:57.911095+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] set CON_NULL for fd:80 in close_connection'
2025-05-22T06:06:57.911148+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] set CON_NULL for fd:85 in close_connection'
2025-05-22T06:06:57.936554+08:00 13 [Note] [MY-011725] [Repl] Plugin group_replication reported: 'Error while sending stats message'
2025-05-22T06:06:58.840396+08:00 13 [Note] [MY-011457] [Repl] Plugin group_replication reported: 'Broadcast of committed transactions message failed.'
2025-05-22T06:06:58.924873+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Installing leave view.'
2025-05-22T06:06:58.924928+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] ::install_view():: No exchanged data'
2025-05-22T06:06:58.924946+08:00 0 [Note] [MY-011071] [Repl] Plugin group_replication reported: 'on_view_changed is called'
2025-05-22T06:06:58.924995+08:00 0 [System] [MY-011504] [Repl] Plugin group_replication reported: 'Group membership changed: This member has left the group.'
2025-05-22T06:06:58.925029+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] notify_xcom_truly_remove failed'
2025-05-22T06:06:58.925050+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] make_gcs_leave_group_on_error calls do_remove_node_from_group'
2025-05-22T06:06:58.925062+08:00 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] call do_remove_node_from_group started!'
2025-05-22T06:06:58.925912+08:00 0 [Note] [MY-010067] [Server] Giving 7 client threads a chance to die gracefully
2025-05-22T06:06:58.925946+08:00 0 [Note] [MY-010117] [Server] Shutting down slave threads
2025-05-22T06:06:58.925958+08:00 0 [Note] [MY-010054] [Server] Event Scheduler: Killing the scheduler thread, thread id 7
2025-05-22T06:06:58.925972+08:00 0 [Note] [MY-010050] [Server] Event Scheduler: Waiting for the scheduler thread to reply
2025-05-22T06:06:58.926081+08:00 0 [Note] [MY-010048] [Server] Event Scheduler: Stopped
2025-05-22T06:07:00.926206+08:00 0 [Note] [MY-010118] [Server] Forcefully disconnecting 6 remaining clients
2025-05-22T06:07:00.926277+08:00 0 [Note] [MY-011650] [Repl] Plugin group_replication reported: 'Plugin 'group_replication' is stopping.'
2025-05-22T06:07:00.927060+08:00 12 [Note] [MY-011444] [Repl] Plugin group_replication reported: 'The group replication applier thread was killed.'
2025-05-22T06:07:00.927193+08:00 0 [Note] [MY-011071] [Repl] Plugin group_replication reported: 'Destroy certifier broadcast thread'
2025-05-22T06:07:00.927391+08:00 0 [System] [MY-011651] [Repl] Plugin group_replication reported: 'Plugin 'group_replication' has been stopped.'
2025-05-22T06:07:00.927800+08:00 0 [Note] [MY-010043] [Server] Event Scheduler: Purging the queue. 0 events
2025-05-22T06:07:00.960190+08:00 0 [Note] [MY-012330] [InnoDB] FTS optimize thread exiting.
2025-05-22T06:07:01.924723+08:00 0 [Note] [MY-010120] [Server] Binlog end
2025-05-22T06:07:01.926764+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'group_replication'
2025-05-22T06:07:01.926839+08:00 0 [Note] [MY-011665] [Repl] Plugin group_replication reported: 'All Group Replication server observers have been successfully unregistered'
2025-05-22T06:07:01.926887+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'clone'
2025-05-22T06:07:01.926903+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'mysqlx'
2025-05-22T06:07:01.927433+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'mysqlx_cache_cleaner'
2025-05-22T06:07:01.927451+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'ngram'
2025-05-22T06:07:01.927459+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'BLACKHOLE'
2025-05-22T06:07:01.927468+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'ARCHIVE'
2025-05-22T06:07:01.927475+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'TempTable'
2025-05-22T06:07:01.927482+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'MRG_MYISAM'
2025-05-22T06:07:01.927489+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'MyISAM'
2025-05-22T06:07:01.927501+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_ASYNC_PURGE_FILES'
2025-05-22T06:07:01.927508+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_SESSION_TEMP_TABLESPACES'
2025-05-22T06:07:01.927516+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_CACHED_INDEXES'
2025-05-22T06:07:01.927523+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_VIRTUAL'
2025-05-22T06:07:01.927530+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_COLUMNS'
2025-05-22T06:07:01.927537+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_TABLESPACES'
2025-05-22T06:07:01.927543+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_INDEXES'
2025-05-22T06:07:01.927550+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_TABLESTATS'
2025-05-22T06:07:01.927557+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_TABLES'
2025-05-22T06:07:01.927563+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2025-05-22T06:07:01.927570+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2025-05-22T06:07:01.927576+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_FT_CONFIG'
2025-05-22T06:07:01.927583+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2025-05-22T06:07:01.927590+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_FT_DELETED'
2025-05-22T06:07:01.927596+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2025-05-22T06:07:01.927603+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_METRICS'
2025-05-22T06:07:01.927609+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
2025-05-22T06:07:01.927616+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2025-05-22T06:07:01.927623+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2025-05-22T06:07:01.927629+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_BUFFER_PAGE'
2025-05-22T06:07:01.927636+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2025-05-22T06:07:01.927642+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2025-05-22T06:07:01.927649+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_CMPMEM_RESET'
2025-05-22T06:07:01.927656+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_CMPMEM'
2025-05-22T06:07:01.927673+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_CMP_RESET'
2025-05-22T06:07:01.927679+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_CMP'
2025-05-22T06:07:01.927691+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_TRX'
2025-05-22T06:07:01.927697+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'InnoDB'
2025-05-22T06:07:01.927724+08:00 0 [Note] [MY-013072] [InnoDB] Starting shutdown...
2025-05-22T06:07:01.927819+08:00 0 [Note] [MY-011944] [InnoDB] Dumping buffer pool(s) to /usr/local/greatdb/data/GreatSQL/ib_buffer_pool
2025-05-22T06:07:01.928116+08:00 0 [Note] [MY-011944] [InnoDB] Buffer pool(s) dump completed at 250522  6:07:01
2025-05-22T06:07:02.029166+08:00 0 [Note] [MY-013084] [InnoDB] Log background threads are being closed...
2025-05-22T06:07:03.364128+08:00 0 [Note] [MY-013854] [InnoDB] Bytes written to disk by DBLWR (ON): 3309568
2025-05-22T06:07:03.364951+08:00 0 [Note] [MY-012980] [InnoDB] Shutdown completed; log sequence number 20420584
2025-05-22T06:07:03.365043+08:00 0 [Note] [MY-012255] [InnoDB] Removed temporary tablespace data file: "ibtmp1"
2025-05-22T06:07:03.365071+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'MEMORY'
2025-05-22T06:07:03.365082+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'dlk'
2025-05-22T06:07:03.365091+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'CSV'
2025-05-22T06:07:03.365099+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'PERFORMANCE_SCHEMA'
2025-05-22T06:07:03.365132+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'daemon_keyring_proxy_plugin'
2025-05-22T06:07:03.365151+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'sha2_cache_cleaner'
2025-05-22T06:07:03.365158+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'caching_sha2_password'
2025-05-22T06:07:03.365167+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'sha256_password'
2025-05-22T06:07:03.365172+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'mysql_native_password'
2025-05-22T06:07:03.366761+08:00 0 [Note] [MY-010733] [Server] Shutting down plugin 'binlog'
2025-05-22T06:07:03.369303+08:00 0 [System] [MY-010910] [Server] /usr/local/greatdb/bin/mysqld: Shutdown complete (mysqld 8.0.32-27)  GreatSQL, Release 27, Revision aa66a385910.
2025-05-22T06:07:03.913224+08:00 0 [Warning] [MY-011068] [Server] The syntax 'log_slow_slave_statements' is deprecated and will be removed in a future release. Please use log_slow_replica_statements instead.
2025-05-22T06:07:03.913265+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_parallel_type' is deprecated and will be removed in a future release. Please use replica_parallel_type instead.
2025-05-22T06:07:03.913271+08:00 0 [Warning] [MY-011069] [Server] The syntax '--replica-parallel-type' is deprecated and will be removed in a future release.
2025-05-22T06:07:03.913279+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_parallel_workers' is deprecated and will be removed in a future release. Please use replica_parallel_workers instead.
2025-05-22T06:07:03.913290+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_preserve_commit_order' is deprecated and will be removed in a future release. Please use replica_preserve_commit_order instead.
2025-05-22T06:07:03.913299+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_checkpoint_period' is deprecated and will be removed in a future release. Please use replica_checkpoint_period instead.
2025-05-22T06:07:03.913471+08:00 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2025-05-22T06:07:03.913477+08:00 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-log-path: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2025-05-22T06:07:03.913541+08:00 0 [Note] [MY-013932] [Server] BuildID[sha1]=
2025-05-22T06:07:03.913548+08:00 0 [Note] [MY-010949] [Server] Basedir set to /usr/local/greatdb/.
2025-05-22T06:07:03.913556+08:00 0 [System] [MY-010116] [Server] /usr/local/greatdb/bin/mysqld (mysqld 8.0.32-27) starting as process 145674
2025-05-22T06:07:03.942332+08:00 0 [Note] [MY-012366] [InnoDB] Using Linux native AIO
2025-05-22T06:07:03.942394+08:00 0 [Warning] [MY-013869] [InnoDB] Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.
2025-05-22T06:07:03.942418+08:00 0 [Warning] [MY-013870] [InnoDB] Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.
2025-05-22T06:07:03.942720+08:00 0 [Note] [MY-010747] [Server] Plugin 'FEDERATED' is disabled.
2025-05-22T06:07:03.942804+08:00 0 [Note] [MY-010747] [Server] Plugin 'ndbcluster' is disabled.
2025-05-22T06:07:03.942821+08:00 0 [Note] [MY-010747] [Server] Plugin 'ndbinfo' is disabled.
2025-05-22T06:07:03.942832+08:00 0 [Note] [MY-010747] [Server] Plugin 'ndb_transid_mysql_connection_map' is disabled.
2025-05-22T06:07:03.944376+08:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-05-22T06:07:03.944441+08:00 1 [Note] [MY-013546] [InnoDB] Atomic write enabled
2025-05-22T06:07:03.944488+08:00 1 [Note] [MY-012932] [InnoDB] PUNCH HOLE support available
2025-05-22T06:07:03.944503+08:00 1 [Note] [MY-012944] [InnoDB] Uses event mutexes
2025-05-22T06:07:03.944508+08:00 1 [Note] [MY-012945] [InnoDB] GCC builtin __atomic_thread_fence() is used for memory barrier
2025-05-22T06:07:03.944520+08:00 1 [Note] [MY-012948] [InnoDB] Compressed tables use zlib 1.2.13
2025-05-22T06:07:03.950761+08:00 1 [Note] [MY-011066] [InnoDB] File purge : set file purge path : /usr/local/greatdb/data/GreatSQL/#file_purge
2025-05-22T06:07:03.950864+08:00 1 [Note] [MY-012951] [InnoDB] Using hardware accelerated crc32 and polynomial multiplication.
2025-05-22T06:07:03.951703+08:00 1 [Note] [MY-012203] [InnoDB] Directories to scan './'
2025-05-22T06:07:03.951751+08:00 1 [Note] [MY-012204] [InnoDB] Scanning './'
2025-05-22T06:07:03.999869+08:00 1 [Note] [MY-012208] [InnoDB] Completed space ID check of 8 files.
2025-05-22T06:07:04.001820+08:00 1 [Note] [MY-012955] [InnoDB] Initializing buffer pool, total size = 8.000000G, instances = 16, chunk size =128.000000M
2025-05-22T06:07:04.001851+08:00 1 [Note] [MY-011872] [InnoDB] Setting NUMA memory policy to MPOL_INTERLEAVE
2025-05-22T06:07:08.327234+08:00 1 [Note] [MY-011874] [InnoDB] Setting NUMA memory policy to MPOL_DEFAULT
2025-05-22T06:07:08.327376+08:00 1 [Note] [MY-012957] [InnoDB] Completed initialization of buffer pool
2025-05-22T06:07:08.391625+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_0.dblwr' for doublewrite
2025-05-22T06:07:08.398236+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_1.dblwr' for doublewrite
2025-05-22T06:07:08.417687+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_2.dblwr' for doublewrite
2025-05-22T06:07:08.423394+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_3.dblwr' for doublewrite
2025-05-22T06:07:08.434649+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_4.dblwr' for doublewrite
2025-05-22T06:07:08.435135+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_5.dblwr' for doublewrite
2025-05-22T06:07:08.460155+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_6.dblwr' for doublewrite
2025-05-22T06:07:08.466350+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_7.dblwr' for doublewrite
2025-05-22T06:07:08.477069+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_8.dblwr' for doublewrite
2025-05-22T06:07:08.483276+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_9.dblwr' for doublewrite
2025-05-22T06:07:08.494925+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_10.dblwr' for doublewrite
2025-05-22T06:07:08.495261+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_11.dblwr' for doublewrite
2025-05-22T06:07:08.506898+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_12.dblwr' for doublewrite
2025-05-22T06:07:08.507302+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_13.dblwr' for doublewrite
2025-05-22T06:07:08.519273+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_14.dblwr' for doublewrite
2025-05-22T06:07:08.525031+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_15.dblwr' for doublewrite
2025-05-22T06:07:08.533696+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_16.dblwr' for doublewrite
2025-05-22T06:07:08.541984+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_17.dblwr' for doublewrite
2025-05-22T06:07:08.549344+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_18.dblwr' for doublewrite
2025-05-22T06:07:08.549738+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_19.dblwr' for doublewrite
2025-05-22T06:07:08.557422+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_20.dblwr' for doublewrite
2025-05-22T06:07:08.557902+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_21.dblwr' for doublewrite
2025-05-22T06:07:08.563877+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_22.dblwr' for doublewrite
2025-05-22T06:07:08.564218+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_23.dblwr' for doublewrite
2025-05-22T06:07:08.566593+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_24.dblwr' for doublewrite
2025-05-22T06:07:08.566975+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_25.dblwr' for doublewrite
2025-05-22T06:07:08.569455+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_26.dblwr' for doublewrite
2025-05-22T06:07:08.569777+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_27.dblwr' for doublewrite
2025-05-22T06:07:08.577463+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_28.dblwr' for doublewrite
2025-05-22T06:07:08.577844+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_29.dblwr' for doublewrite
2025-05-22T06:07:08.580247+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_30.dblwr' for doublewrite
2025-05-22T06:07:08.580536+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_31.dblwr' for doublewrite
2025-05-22T06:07:08.583743+08:00 1 [Note] [MY-013566] [InnoDB] Double write buffer files: 32
2025-05-22T06:07:08.583763+08:00 1 [Note] [MY-013565] [InnoDB] Double write buffer pages per instance: 4
2025-05-22T06:07:08.583789+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_0.dblwr' for doublewrite
2025-05-22T06:07:08.583818+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_1.dblwr' for doublewrite
2025-05-22T06:07:08.583846+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_2.dblwr' for doublewrite
2025-05-22T06:07:08.583872+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_3.dblwr' for doublewrite
2025-05-22T06:07:08.583899+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_4.dblwr' for doublewrite
2025-05-22T06:07:08.583926+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_5.dblwr' for doublewrite
2025-05-22T06:07:08.583952+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_6.dblwr' for doublewrite
2025-05-22T06:07:08.583989+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_7.dblwr' for doublewrite
2025-05-22T06:07:08.584016+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_8.dblwr' for doublewrite
2025-05-22T06:07:08.584043+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_9.dblwr' for doublewrite
2025-05-22T06:07:08.584071+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_10.dblwr' for doublewrite
2025-05-22T06:07:08.584103+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_11.dblwr' for doublewrite
2025-05-22T06:07:08.584129+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_12.dblwr' for doublewrite
2025-05-22T06:07:08.584155+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_13.dblwr' for doublewrite
2025-05-22T06:07:08.584181+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_14.dblwr' for doublewrite
2025-05-22T06:07:08.584207+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_15.dblwr' for doublewrite
2025-05-22T06:07:08.584233+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_16.dblwr' for doublewrite
2025-05-22T06:07:08.584259+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_17.dblwr' for doublewrite
2025-05-22T06:07:08.584296+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_18.dblwr' for doublewrite
2025-05-22T06:07:08.584323+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_19.dblwr' for doublewrite
2025-05-22T06:07:08.584350+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_20.dblwr' for doublewrite
2025-05-22T06:07:08.584375+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_21.dblwr' for doublewrite
2025-05-22T06:07:08.584412+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_22.dblwr' for doublewrite
2025-05-22T06:07:08.584442+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_23.dblwr' for doublewrite
2025-05-22T06:07:08.584473+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_24.dblwr' for doublewrite
2025-05-22T06:07:08.584499+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_25.dblwr' for doublewrite
2025-05-22T06:07:08.584525+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_26.dblwr' for doublewrite
2025-05-22T06:07:08.584551+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_27.dblwr' for doublewrite
2025-05-22T06:07:08.584577+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_28.dblwr' for doublewrite
2025-05-22T06:07:08.584604+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_29.dblwr' for doublewrite
2025-05-22T06:07:08.584630+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_30.dblwr' for doublewrite
2025-05-22T06:07:08.584657+08:00 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_31.dblwr' for doublewrite
2025-05-22T06:07:08.657499+08:00 1 [Note] [MY-013883] [InnoDB] The latest found checkpoint is at lsn = 20420584 in redo log file ./#innodb_redo/#ib_redo0.
2025-05-22T06:07:08.657674+08:00 1 [Note] [MY-013086] [InnoDB] Starting to parse redo log at lsn = 20420210, whereas checkpoint_lsn = 20420584 and start_lsn = 20420096
2025-05-22T06:07:08.692921+08:00 1 [Note] [MY-013083] [InnoDB] Log background threads are being started...
2025-05-22T06:07:08.693869+08:00 1 [Note] [MY-012532] [InnoDB] Applying a batch of 0 redo log records ...
2025-05-22T06:07:08.694157+08:00 1 [Note] [MY-012535] [InnoDB] Apply batch completed!
2025-05-22T06:07:08.694863+08:00 1 [Note] [MY-013252] [InnoDB] Using undo tablespace './undo_001'.
2025-05-22T06:07:08.695587+08:00 1 [Note] [MY-013252] [InnoDB] Using undo tablespace './undo_002'.
2025-05-22T06:07:08.696860+08:00 1 [Note] [MY-012910] [InnoDB] Opened 2 existing undo tablespaces.
2025-05-22T06:07:08.696922+08:00 1 [Note] [MY-011980] [InnoDB] GTID recovery trx_no: 2116
2025-05-22T06:07:09.159695+08:00 1 [Note] [MY-013776] [InnoDB] Parallel initialization of rseg complete
2025-05-22T06:07:09.159750+08:00 1 [Note] [MY-013777] [InnoDB] Time taken to initialize rseg using 4 thread: 462830 ms.
2025-05-22T06:07:09.159840+08:00 1 [Note] [MY-012923] [InnoDB] Creating shared tablespace for temporary tables
2025-05-22T06:07:09.159897+08:00 1 [Note] [MY-012265] [InnoDB] Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2025-05-22T06:07:09.180826+08:00 1 [Note] [MY-012266] [InnoDB] File './ibtmp1' size is now 12 MB.
2025-05-22T06:07:09.180938+08:00 1 [Note] [MY-013627] [InnoDB] Scanning temp tablespace dir:'./#innodb_temp/'
2025-05-22T06:07:09.193533+08:00 1 [Note] [MY-013018] [InnoDB] Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.
2025-05-22T06:07:09.194050+08:00 1 [Note] [MY-012976] [InnoDB] Percona XtraDB (http://www.percona.com) 8.0.32-8.0.32 started; log sequence number 20420594
2025-05-22T06:07:09.194940+08:00 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2025-05-22T06:07:09.220691+08:00 1 [Note] [MY-011089] [Server] Data dictionary restarting version '80023'.
2025-05-22T06:07:09.607200+08:00 1 [Note] [MY-012357] [InnoDB] Reading DD tablespace files
2025-05-22T06:07:09.608330+08:00 1 [Note] [MY-012356] [InnoDB] Scanned 10 tablespaces. Validated 10.
2025-05-22T06:07:09.628007+08:00 1 [Note] [MY-010006] [Server] Using data dictionary with version '80023'.
2025-05-22T06:07:09.660768+08:00 0 [Note] [MY-011332] [Server] Plugin mysqlx reported: 'IPv6 is available'
2025-05-22T06:07:09.661948+08:00 0 [Note] [MY-011323] [Server] Plugin mysqlx reported: 'X Plugin ready for connections. bind-address: '::' port: 33060'
2025-05-22T06:07:09.661973+08:00 0 [Note] [MY-011323] [Server] Plugin mysqlx reported: 'X Plugin ready for connections. socket: '/tmp/mysqlx.sock''
2025-05-22T06:07:09.752887+08:00 0 [Note] [MY-010902] [Server] Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.
2025-05-22T06:07:09.793415+08:00 0 [Note] [MY-013911] [Server] Crash recovery finished in binlog engine. No attempts to commit, rollback or prepare any transactions.
2025-05-22T06:07:09.793456+08:00 0 [Note] [MY-013911] [Server] Crash recovery finished in InnoDB engine. No attempts to commit, rollback or prepare any transactions.
2025-05-22T06:07:09.798127+08:00 0 [Note] [MY-012487] [InnoDB] DDL log recovery : begin
2025-05-22T06:07:09.815368+08:00 0 [Note] [MY-012488] [InnoDB] DDL log recovery : end
2025-05-22T06:07:09.815611+08:00 0 [Note] [MY-011946] [InnoDB] Loading buffer pool(s) from /usr/local/greatdb/data/GreatSQL/ib_buffer_pool
2025-05-22T06:07:09.823098+08:00 0 [Note] [MY-012922] [InnoDB] Waiting for purge to start
2025-05-22T06:07:09.885971+08:00 0 [Note] [MY-010182] [Server] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2025-05-22T06:07:09.885997+08:00 0 [Note] [MY-010304] [Server] Skipping generation of SSL certificates as certificate files are present in data directory.
2025-05-22T06:07:09.886764+08:00 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2025-05-22T06:07:09.886793+08:00 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2025-05-22T06:07:09.886821+08:00 0 [Note] [MY-010308] [Server] Skipping generation of RSA key pair through --sha256_password_auto_generate_rsa_keys as key files are present in data directory.
2025-05-22T06:07:09.886832+08:00 0 [Note] [MY-010308] [Server] Skipping generation of RSA key pair through --caching_sha2_password_auto_generate_rsa_keys as key files are present in data directory.
2025-05-22T06:07:09.886954+08:00 0 [Note] [MY-010252] [Server] Server hostname (bind-address): '*'; port: 3306
2025-05-22T06:07:09.886988+08:00 0 [Note] [MY-010253] [Server] IPv6 is available.
2025-05-22T06:07:09.886996+08:00 0 [Note] [MY-010264] [Server]   - '::' resolves to '::';
2025-05-22T06:07:09.887008+08:00 0 [Note] [MY-010251] [Server] Server socket created on IP: '::'.
2025-05-22T06:07:09.916653+08:00 0 [Note] [MY-011946] [InnoDB] Buffer pool(s) load completed at 250522  6:07:09
2025-05-22T06:07:09.931167+08:00 0 [Warning] [MY-010604] [Repl] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=nfcgw02-relay-bin' to avoid this p
roblem.
2025-05-22T06:07:09.934789+08:00 0 [Warning] [MY-013836] [Repl] Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.
2025-05-22T06:07:09.941191+08:00 0 [Warning] [MY-013836] [Repl] Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.
2025-05-22T06:07:09.942699+08:00 0 [Note] [MY-011025] [Repl] Failed to start slave threads for channel ''.
2025-05-22T06:07:09.944540+08:00 7 [Note] [MY-010051] [Server] Event Scheduler: scheduler thread started with id 7
2025-05-22T06:07:09.944657+08:00 0 [System] [MY-010931] [Server] /usr/local/greatdb/bin/mysqld: ready for connections. Version: '8.0.32-27'  socket: '/usr/local/greatdb/data/GreatSQL/mysql.sock'  port: 3306  GreatSQL, Release 27, Revision aa66a385910.
2025-05-22T06:07:09.944749+08:00 0 [Note] [MY-011240] [Server] Plugin mysqlx reported: 'Using SSL configuration from MySQL Server'
2025-05-22T06:07:09.945283+08:00 0 [Note] [MY-011243] [Server] Plugin mysqlx reported: 'Using OpenSSL for TLS connections'
2025-05-22T06:07:09.945515+08:00 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /tmp/mysqlx.sock
以上是错误日志，我用的ubuntu24.04系统，查看系统后，也没有发现有定时任务来关闭群集服务，现在我也找不到原因了


全部回复(9)
只看楼主
yejr 2025-5-22 23:32:54
2025-05-22T06:06:54.904288+08:00 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.32-27).

这个是用户主动发出的shutdown指令，需要找出源头，比如定时任务、监控及其他。

有个方法是：在这个时段提前打开general log，然后观察这个指令发起的源头IP和用户等信息。
回复 采纳

举报

少辉 2025-5-23 08:47:50
yejr 发表于 2025-5-22 23:32
2025-05-22T06:06:54.904288+08:00 0 [System] [MY-013172] [Server] Received SHUTDOWN from user . Shutt ...

这几台数据库服务器是安在堡垒机中的，昨天和堡垒机的管理人员说这个情况之后，今天就正常了，我估计问题出在他们那边。
回复 采纳

举报

yejr 2025-5-23 08:50:05
yejr 发表于 2025-5-22 23:32
2025-05-22T06:06:54.904288+08:00 0 [System] [MY-013172] [Server] Received SHUTDOWN from user . Shutt ...

看这个时间并不是整点，应该不是定时任务重启GreatSQL，更大概率是每天这个时间有其他大任务在跑，比如海量数据查询统计、备份等，导致GreatSQL内存暴增，引发OOM Killer。

所以你也可以查一查系统日志，看看这个时段是否有OOM Killer事件。
回复 采纳

举报

reddey 2025-5-23 09:01:17
2025-05-21T19:22:28.381746+08:00 31 [Note] [MY-010914] [Server] Aborted connection 31 to db: 'unconnected' user: 'boxunrepl' host: '10.28.0.192' (failed on flush_net()).，这个你们服务器的用户名和密码吗？
回复 采纳

举报

yejr 2025-5-23 09:37:55
reddey 发表于 2025-5-23 09:01
2025-05-21T19:22:28.381746+08:00 31 [Note] [MY-010914] [Server] Aborted connection 31 to db: 'unconn ...

想啥呢，MySQL咋可能蠢到在日志里记录密码。。。
回复 采纳

举报

reddey 2025-5-23 15:45:15
yejr 发表于 2025-5-23 09:37
想啥呢，MySQL咋可能蠢到在日志里记录密码。。。

哦，原来这样。
回复 采纳

举报

yejr 2025-5-23 23:47:27
少辉 发表于 2025-5-23 08:47
这几台数据库服务器是安在堡垒机中的，昨天和堡垒机的管理人员说这个情况之后，今天就正常了，我估计问题 ...

可以深入了解下具体什么原因，要不然以后还可能莫名其妙重启
回复 采纳

举报

少辉 前天 23:31
yejr 发表于 2025-5-23 23:47
可以深入了解下具体什么原因，要不然以后还可能莫名其妙重启

今天又重启了一次，导致我节假日都没好好休息，出现的问题和以前一样，greatsql数据库也是先收到了一个shutdown命令，然后数据库就重启了，现已经查到原因，我用的系统是ubuntu24.04版本的，这个系统启用了一个无人值守的软件包更新软件，这个软件叫unattended-upgrades，Ubuntu 利用这个unattended-upgrades在更新 Kerberos 库后，自动重启了所有依赖 Kerberos 的服务，导致 GreatSQL 数据库被强制重启。这是因为Ubuntu 的 apt在更新共享库时，会尝试重启所有链接到该库的正在运行的服务，导致greatsql.service服务被重启了，我的GreatSQL群集就此断开。GreatSQL数据库我才关注没多久，也是经人介绍说还可以，所以我就建议公司用这个数据库了，现在我不知道GreatSQL数据库是否依赖一些系统的库文件，目前我只知道它依赖了libaio.so.1，而在Ubuntu24.04版本中是没有这个libaio.so.1文件的，它将libaio已改用 成了1t64.0.2 版本，于是我在安装GreatSQL时想办法创建了一个链接，让依赖libaio.so.1程序的GreatSQL数据库自动指向了libaio.so.1t64.0.2,这样才安装成功。我不知道是不是ubuntu系统的apt在更新libaio.so.1t64.0.2时，查看到了依赖于此的GreatSQL，然后就去重启了GreatSQL服务。这只是我个人的观点，也不知道对不对。
回复 采纳

举报

yejr 昨天 14:48
少辉 发表于 2025-6-1 23:31
今天又重启了一次，导致我节假日都没好好休息，出现的问题和以前一样，greatsql数据库也是先收到了一个sh ...

你可以查一下 Kerberos 库的依赖关系，应该是 Kerberos 库依赖 MySQL 数据库，而安装 GreatSQL 后的作用就是取代 MySQL，所以会被关联起来
回复 采纳

举报

少辉

1

主题

0

博客

5

贡献

新手上路

Rank: 1

积分
8
发消息
互动与交流
社区活动
论坛问答
加入社区
贡献者指南
学习与应用
文章博客
文档资料
视频资料
常见问题
发现社区
社区准则
建议反馈
社区之星

合作电话：010-64087828

社区邮箱：greatsql@greatdb.com

社区公众号
社区小助手
QQ群
友情链接
万里数据库开源中国墨天轮开放原子开源基金会OpenEuler
©2022 GreatSQL All Rights Reserved. ( 京ICP备06057874号 )
GMT+8, 2025-6-3 09:56 , Processed in 0.021796 second(s), 19 queries , Redis On.
快速回复 返回顶部 返回列表