Results

By type

          1:C 23 Feb 2026 16:23:05.398 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 23 Feb 2026 16:23:05.398 * Redis version=8.2.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 23 Feb 2026 16:23:05.398 * Configuration loaded
1:M 23 Feb 2026 16:23:05.399 * monotonic clock: POSIX clock_gettime
1:M 23 Feb 2026 16:23:05.402 * Running mode=standalone, port=6379.
1:M 23 Feb 2026 16:23:05.403 * Server initialized
1:M 23 Feb 2026 16:23:05.403 * Ready to accept connections tcp
1:M 23 Feb 2026 16:24:01.069 * Replica 10.233.12.254:6379 asks for synchronization
1:M 23 Feb 2026 16:24:01.069 * Full resync requested by replica 10.233.12.254:6379 
1:M 23 Feb 2026 16:24:01.069 * Replication backlog created, my new replication IDs are '11f9d1ecedc38bd425ee988c2e0b089d0dfd8527' and '0000000000000000000000000000000000000000'
1:M 23 Feb 2026 16:24:01.069 * Replica 10.233.12.254:6379 is capable of rdb channel synchronization, and partial sync isn't possible. Full sync will continue with dedicated rdb channel.
1:M 23 Feb 2026 16:24:01.074 * Replica 127.0.0.6:6379 asks for synchronization
1:M 23 Feb 2026 16:24:01.074 * Full resync requested by replica 127.0.0.6:6379 (rdb-channel)
1:M 23 Feb 2026 16:24:01.075 * Delay next BGSAVE for diskless SYNC
1:M 23 Feb 2026 16:24:06.109 * Starting BGSAVE for SYNC with target: replicas sockets (rdb-channel)
1:M 23 Feb 2026 16:24:06.109 * Starting to deliver RDB and replication stream to replica: 10.233.12.254:6379
1:M 23 Feb 2026 16:24:06.110 * Background RDB transfer started by pid 51 to replica socket
51:C 23 Feb 2026 16:24:06.111 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 23 Feb 2026 16:24:06.131 * Connection with replica (rdbchannel) 127.0.0.6:6379 lost.
1:M 23 Feb 2026 16:24:06.131 * Synchronization with replica 10.233.12.254:6379 succeeded
1:M 23 Feb 2026 16:24:06.218 * Background RDB transfer terminated with success
1:M 23 Feb 2026 16:24:55.031 * Replica 10.233.50.91:6379 asks for synchronization
1:M 23 Feb 2026 16:24:55.031 * Full resync requested by replica 10.233.50.91:6379 
1:M 23 Feb 2026 16:24:55.031 * Replica 10.233.50.91:6379 is capable of rdb channel synchronization, and partial sync isn't possible. Full sync will continue with dedicated rdb channel.
1:M 23 Feb 2026 16:24:55.044 * Replica 127.0.0.6:6379 asks for synchronization
1:M 23 Feb 2026 16:24:55.044 * Full resync requested by replica 127.0.0.6:6379 (rdb-channel)
1:M 23 Feb 2026 16:24:55.044 * Delay next BGSAVE for diskless SYNC
1:M 23 Feb 2026 16:25:00.059 * Starting BGSAVE for SYNC with target: replicas sockets (rdb-channel)
1:M 23 Feb 2026 16:25:00.059 * Starting to deliver RDB and replication stream to replica: 10.233.50.91:6379
1:M 23 Feb 2026 16:25:00.060 * Background RDB transfer started by pid 124 to replica socket
124:C 23 Feb 2026 16:25:00.061 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 23 Feb 2026 16:25:00.159 * Connection with replica (rdbchannel) 127.0.0.6:6379 lost.
1:M 23 Feb 2026 16:25:00.159 * Synchronization with replica 10.233.50.91:6379 succeeded
1:M 23 Feb 2026 16:25:00.161 * Background RDB transfer terminated with success
1:M 23 Feb 2026 16:38:06.070 * 1 changes in 900 seconds. Saving...
1:M 23 Feb 2026 16:38:06.071 * Background saving started by pid 1064
1064:C 23 Feb 2026 16:38:06.089 * DB saved on disk
1064:C 23 Feb 2026 16:38:06.089 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 23 Feb 2026 16:38:06.172 * Background saving terminated with success