Skip to content

Instantly share code, notes, and snippets.

@georgexsh

georgexsh/redis.log

Last active March 17, 2020 02:17
Show Gist options
  • Save georgexsh/66767ca358a807929c9400b1dab00f72 to your computer and use it in GitHub Desktop.
Save georgexsh/66767ca358a807929c9400b1dab00f72 to your computer and use it in GitHub Desktop.
Download ZIP
strange redis log
Raw
redis.log
1:M 16 Mar 06:48:01.553 * DB saved on disk
1:S 16 Mar 11:31:32.720 * Before turning into a slave, using my master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer.
1:S 16 Mar 11:31:32.720 * SLAVE OF 82.118.17.133:8887 enabled (user request from 'id=4 addr=172.18.0.1:42860 fd=8 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r cmd=slaveof')
1:S 16 Mar 11:31:33.143 * Connecting to MASTER 82.118.17.133:8887
1:S 16 Mar 11:31:33.143 * MASTER <-> SLAVE sync started
1:S 16 Mar 11:31:33.392 * Non blocking connect for SYNC fired the event.
1:S 16 Mar 11:31:33.643 * Master replied to PING, replication can continue...
1:S 16 Mar 11:31:34.188 * Trying a partial resynchronization (request a84315cfa80813b3d6cf01ccd815be4e24cdd83c:1).
1:S 16 Mar 11:31:34.498 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:1
1:S 16 Mar 11:31:34.498 * Discarding previously cached master state.
1:S 16 Mar 11:31:34.499 * MASTER <-> SLAVE sync: receiving 55640 bytes from master
1:S 16 Mar 11:31:35.424 * MASTER <-> SLAVE sync: Flushing old data
1:S 16 Mar 11:31:35.424 * MASTER <-> SLAVE sync: Loading DB in memory
1:S 16 Mar 11:31:35.424 # Wrong signature trying to load DB from file
1:S 16 Mar 11:31:35.424 # Failed trying to load the MASTER synchronization DB from disk
1:S 16 Mar 11:31:36.300 * Connecting to MASTER 82.118.17.133:8887
1:S 16 Mar 11:31:36.300 * MASTER <-> SLAVE sync started
1:S 16 Mar 11:31:36.503 * Non blocking connect for SYNC fired the event.
1:S 16 Mar 11:31:36.708 # Error reply to PING from master: '-Reading from master: Resource temporarily unavailable'
1:S 16 Mar 11:31:37.350 * Connecting to MASTER 82.118.17.133:8887
1:S 16 Mar 11:31:37.351 * MASTER <-> SLAVE sync started
1:S 16 Mar 11:31:37.780 * Non blocking connect for SYNC fired the event.
1:S 16 Mar 11:31:38.012 # Error reply to PING from master: '-Reading from master: Resource temporarily unavailable'
1:S 16 Mar 11:31:38.411 * Connecting to MASTER 82.118.17.133:8887
1:S 16 Mar 11:31:38.411 * MASTER <-> SLAVE sync started
1:S 16 Mar 11:31:38.669 * Non blocking connect for SYNC fired the event.
1:S 16 Mar 11:31:38.929 # Error reply to PING from master: '-Reading from master: Resource temporarily unavailable'
1:S 16 Mar 11:31:39.481 * Connecting to MASTER 82.118.17.133:8887
1:S 16 Mar 11:31:39.481 * MASTER <-> SLAVE sync started
1:S 16 Mar 11:31:39.736 * Non blocking connect for SYNC fired the event.
1:S 16 Mar 11:31:39.988 # Error reply to PING from master: '-Reading from master: Resource temporarily unavailable'
1:S 16 Mar 11:31:40.184 * Module 'system' loaded from ./red2.so
1:S 16 Mar 11:31:40.524 * Connecting to MASTER 82.118.17.133:8887
1:S 16 Mar 11:31:40.524 * MASTER <-> SLAVE sync started
1:S 16 Mar 11:31:40.778 * Non blocking connect for SYNC fired the event.
1:M 16 Mar 11:31:40.893 # Setting secondary replication ID to a84315cfa80813b3d6cf01ccd815be4e24cdd83c, valid up to offset: 1. New replication ID is 81a6bd5a051b0e61c0c7eb1ae0ccd1bb5dda5fd5
1:M 16 Mar 11:31:40.893 * MASTER MODE enabled (user request from 'id=4 addr=172.18.0.1:42860 fd=8 name= age=8 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r cmd=slaveof')
Raw
redis_2.log
1:M 17 Mar 02:15:31.921 * DB loaded from disk: 0.000 seconds
1:M 17 Mar 02:15:31.921 * Ready to accept connections
1:M 17 Mar 02:15:32.066 # Possible SECURITY ATTACK detected. It looks like somebody is sending POST or Host: commands to Redis. This is likely due to an attacker attempting to use Cross Protocol Scripting to compromise your Redis instance. Connection aborted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment