环境：

双主 + keepalived
版本：5.7.38

现象：
其中一个节点重启了，但是诡异的是只有启动日志，并没有服务宕的日志或者报错。在message和error-log里面都没有发现宕机的异常点，如下error-log：

2022-08-22T20:15:57.465802+08:00 9705 [Note] Got an error reading communication packets
2022-08-22T20:16:03.004961+08:00 9707 [Note] Got an error reading communication packets
2022-08-22T20:16:09.238795+08:00 9708 [Note] Got an error reading communication packets
2022-08-22T20:16:15.484480+08:00 9710 [Note] Got an error reading communication packets
2022-08-22T20:16:20.611301+08:00 9711 [Note] Got an error reading communication packets
2022-08-22T20:16:26.876640+08:00 9713 [Note] Got an error reading communication packets
2022-08-22T20:16:32.462721+08:00 9715 [Note] Got an error reading communication packets
2022-08-22T20:16:38.417674+08:00 9717 [Note] Got an error reading communication packets
2022-08-22T20:16:44.238416+08:00 9718 [Note] Got an error reading communication packets
2022-08-22T20:16:50.255752+08:00 9719 [Note] Got an error reading communication packets
2022-08-22T20:16:56.215739+08:00 9720 [Note] Got an error reading communication packets
2022-08-22T20:17:10.175327+08:00 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2022-08-22T20:17:10.175511+08:00 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2022-08-22T20:17:10.177930+08:00 0 [Note] /usr/sbin/mysqld (mysqld 5.7.38-enterprise-commercial-advanced-log) starting as process 4385 ...
2022-08-22T20:17:10.301503+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2022-08-22T20:17:10.301583+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-08-22T20:17:10.301594+08:00 0 [Note] InnoDB: Uses event mutexes
2022-08-22T20:17:10.301603+08:00 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-08-22T20:17:10.301614+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-08-22T20:17:10.301622+08:00 0 [Note] InnoDB: Using Linux native AIO
2022-08-22T20:17:10.304611+08:00 0 [Note] InnoDB: Number of pools: 1
2022-08-22T20:17:10.305220+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2022-08-22T20:17:10.313681+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 75G, instances = 8, chunk size = 128M
2022-08-22T20:17:14.412285+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2022-08-22T20:17:14.880688+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-08-22T20:17:14.898022+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-08-22T20:17:15.267908+08:00 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 406127388625
2022-08-22T20:17:15.280827+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 406127598149
2022-08-22T20:17:15.281340+08:00 0 [Note] InnoDB: Database was not shutdown normally!
2022-08-22T20:17:15.281360+08:00 0 [Note] InnoDB: Starting crash recovery.
2022-08-22T20:17:15.629491+08:00 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
2022-08-22T20:17:18.457506+08:00 0 [Note] InnoDB: Apply batch completed
2022-08-22T20:17:18.457558+08:00 0 [Note] InnoDB: Last MySQL binlog file position 0 16404727, file name mysql-bin.000006
2022-08-22T20:17:19.004933+08:00 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-08-22T20:17:19.004969+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-08-22T20:17:19.005073+08:00 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-08-22T20:17:19.019072+08:00 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-08-22T20:17:19.021214+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
····

求教各位大神如何定位宕机并自动重启原因？