Results

By type

          1:C 05 May 2026 09:10:06.440 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 05 May 2026 09:10:06.441 * Redis version=8.2.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 05 May 2026 09:10:06.441 * Configuration loaded
1:M 05 May 2026 09:10:06.445 * monotonic clock: POSIX clock_gettime
1:M 05 May 2026 09:10:06.452 * Running mode=standalone, port=6379.
1:M 05 May 2026 09:10:06.455 * Server initialized
1:M 05 May 2026 09:10:06.460 * Ready to accept connections tcp
1:M 05 May 2026 09:11:06.949 * Replica 10.233.40.190:6379 asks for synchronization
1:M 05 May 2026 09:11:06.949 * Full resync requested by replica 10.233.40.190:6379 
1:M 05 May 2026 09:11:06.949 * Replication backlog created, my new replication IDs are '0c1cc4ea2d5c41553d6383950a6d24d180856a2e' and '0000000000000000000000000000000000000000'
1:M 05 May 2026 09:11:06.949 * Replica 10.233.40.190:6379 is capable of rdb channel synchronization, and partial sync isn't possible. Full sync will continue with dedicated rdb channel.
1:M 05 May 2026 09:11:06.959 * Replica 127.0.0.6:6379 asks for synchronization
1:M 05 May 2026 09:11:06.959 * Full resync requested by replica 127.0.0.6:6379 (rdb-channel)
1:M 05 May 2026 09:11:06.959 * Delay next BGSAVE for diskless SYNC
1:M 05 May 2026 09:11:11.901 * Starting BGSAVE for SYNC with target: replicas sockets (rdb-channel)
1:M 05 May 2026 09:11:11.901 * Starting to deliver RDB and replication stream to replica: 10.233.40.190:6379
1:M 05 May 2026 09:11:11.902 * Background RDB transfer started by pid 51 to replica socket
51:C 05 May 2026 09:11:11.904 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 05 May 2026 09:11:11.922 * Synchronization with replica 10.233.40.190:6379 succeeded
1:M 05 May 2026 09:11:11.925 * Connection with replica (rdbchannel) 127.0.0.6:6379 lost.
1:M 05 May 2026 09:11:12.004 * Background RDB transfer terminated with success
1:M 05 May 2026 09:12:05.155 * Replica 10.233.46.95:6379 asks for synchronization
1:M 05 May 2026 09:12:05.156 * Full resync requested by replica 10.233.46.95:6379 
1:M 05 May 2026 09:12:05.156 * Replica 10.233.46.95:6379 is capable of rdb channel synchronization, and partial sync isn't possible. Full sync will continue with dedicated rdb channel.
1:M 05 May 2026 09:12:05.169 * Replica 127.0.0.6:6379 asks for synchronization
1:M 05 May 2026 09:12:05.169 * Full resync requested by replica 127.0.0.6:6379 (rdb-channel)
1:M 05 May 2026 09:12:05.169 * Delay next BGSAVE for diskless SYNC
1:M 05 May 2026 09:12:10.066 * Starting BGSAVE for SYNC with target: replicas sockets (rdb-channel)
1:M 05 May 2026 09:12:10.066 * Starting to deliver RDB and replication stream to replica: 10.233.46.95:6379
1:M 05 May 2026 09:12:10.067 * Background RDB transfer started by pid 123 to replica socket
123:C 05 May 2026 09:12:10.068 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 05 May 2026 09:12:10.087 * Connection with replica (rdbchannel) 127.0.0.6:6379 lost.
1:M 05 May 2026 09:12:10.087 * Synchronization with replica 10.233.46.95:6379 succeeded
1:M 05 May 2026 09:12:10.169 * Background RDB transfer terminated with success
1:M 05 May 2026 09:25:07.096 * 1 changes in 900 seconds. Saving...
1:M 05 May 2026 09:25:07.098 * Background saving started by pid 1073
1073:C 05 May 2026 09:25:07.109 * DB saved on disk
1073:C 05 May 2026 09:25:07.111 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 05 May 2026 09:25:07.202 * Background saving terminated with success