By type
b"1:C 04 Sep 2026 12:29:48.880 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo\n1:C 04 Sep 2026 12:29:48.880 * Redis version=8.2.2, bits=64, commit=00000000, modified=1, pid=1, just started\n1:C 04 Sep 2026 12:29:48.880 * Configuration loaded\n1:M 04 Sep 2026 12:29:48.880 * monotonic clock: POSIX clock_gettime\n1:M 04 Sep 2026 12:29:48.882 * Running mode=standalone, port=6379.\n1:M 04 Sep 2026 12:29:48.883 * Server initialized\n1:M 04 Sep 2026 12:29:48.884 * Ready to accept connections tcp\n1:M 04 Sep 2026 12:30:50.153 * Replica 10.233.19.67:6379 asks for synchronization\n1:M 04 Sep 2026 12:30:50.154 * Full resync requested by replica 10.233.19.67:6379 \n1:M 04 Sep 2026 12:30:50.154 * Replication backlog created, my new replication IDs are 'ab57d2d353546d3b2427377e1c4f9662b66f1300' and '0000000000000000000000000000000000000000'\n1:M 04 Sep 2026 12:30:50.156 * Replica 10.233.19.67:6379 is capable of rdb channel synchronization, and partial sync isn't possible. Full sync will continue with dedicated rdb channel.\n1:M 04 Sep 2026 12:30:50.179 * Replica 127.0.0.6:6379 asks for synchronization\n1:M 04 Sep 2026 12:30:50.179 * Full resync requested by replica 127.0.0.6:6379 (rdb-channel)\n1:M 04 Sep 2026 12:30:50.179 * Delay next BGSAVE for diskless SYNC\n1:M 04 Sep 2026 12:30:55.435 * Starting BGSAVE for SYNC with target: replicas sockets (rdb-channel)\n1:M 04 Sep 2026 12:30:55.435 * Starting to deliver RDB and replication stream to replica: 10.233.19.67:6379\n1:M 04 Sep 2026 12:30:55.436 * Background RDB transfer started by pid 51 to replica socket\n51:C 04 Sep 2026 12:30:55.440 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB\n1:M 04 Sep 2026 12:30:55.460 * Synchronization with replica 10.233.19.67:6379 succeeded\n1:M 04 Sep 2026 12:30:55.460 * Connection with replica (rdbchannel) 127.0.0.6:6379 lost.\n1:M 04 Sep 2026 12:30:55.537 * Background RDB transfer terminated with success\n1:M 04 Sep 2026 12:31:58.261 * Replica 10.233.40.152:6379 asks for synchronization\n1:M 04 Sep 2026 12:31:58.261 * Full resync requested by replica 10.233.40.152:6379 \n1:M 04 Sep 2026 12:31:58.261 * Replica 10.233.40.152:6379 is capable of rdb channel synchronization, and partial sync isn't possible. Full sync will continue with dedicated rdb channel.\n1:M 04 Sep 2026 12:31:58.275 * Replica 127.0.0.6:6379 asks for synchronization\n1:M 04 Sep 2026 12:31:58.275 * Full resync requested by replica 127.0.0.6:6379 (rdb-channel)\n1:M 04 Sep 2026 12:31:58.275 * Delay next BGSAVE for diskless SYNC\n1:M 04 Sep 2026 12:32:03.921 * Starting BGSAVE for SYNC with target: replicas sockets (rdb-channel)\n1:M 04 Sep 2026 12:32:03.921 * Starting to deliver RDB and replication stream to replica: 10.233.40.152:6379\n1:M 04 Sep 2026 12:32:03.922 * Background RDB transfer started by pid 142 to replica socket\n142:C 04 Sep 2026 12:32:03.924 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB\n1:M 04 Sep 2026 12:32:03.936 * Connection with replica (rdbchannel) 127.0.0.6:6379 lost.\n1:M 04 Sep 2026 12:32:03.942 * Synchronization with replica 10.233.40.152:6379 succeeded\n1:M 04 Sep 2026 12:32:04.024 * Background RDB transfer terminated with success\n1:M 04 Sep 2026 12:44:49.044 * 1 changes in 900 seconds. Saving...\n1:M 04 Sep 2026 12:44:49.045 * Background saving started by pid 1062\n1062:C 04 Sep 2026 12:44:49.130 * DB saved on disk\n1062:C 04 Sep 2026 12:44:49.131 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB\n1:M 04 Sep 2026 12:44:49.146 * Background saving terminated with success\n"