02:29:13 GMT since 3.2.1 (from 3.0.7) (remi RPM repository) sentinels are detecting all other sentinels as "s_down,sentinel,disconnected" 02:35:05 GMT sentinel either receives a tcp RST (if the sentinel is not running a redis server) or a message as follows if the sentinel is running a redis server: 02:36:16 GMT "-DENIED Redis is running in protected mode because protected mode is enabled, no bind address was specified, no authentication password is requested to clients. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback inte 02:36:16 GMT rface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart 02:36:17 GMT it with the '--protected-mode no' option. 4) Setup a bind address or an authentication password. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside." 02:36:59 GMT The suggests solutions from the rejection notice do nothing to fix the problem... 09:42:22 GMT Hi. If an AOF file has some missing data in the middle, is it possible to restore most of it? Not just what’s there before the empty spots, like redis-fix-aof does? 12:31:48 GMT has an proposal for having an weighted order on the blocking pop commands ? 14:07:29 GMT anybody here using blocking operations as a primary way to distribute msgs ? 18:07:44 GMT hi 18:08:20 GMT Is there anyone who could help me with migration from one server to another? I have no access to the server's filesystem because of poorly chosen hosting and I need to migrate ALL data from one server to another... 18:09:30 GMT use the replication 18:13:16 GMT minus: can I do that without an access to the config files? 18:13:44 GMT if you can connect to redis you can clone it 18:13:49 GMT (unless disabled) 18:17:09 GMT minus: could you please direct me somewhere where I could read more about this? I know pretty much nothing about redis and use it just because one of my apps need it... 18:18:00 GMT the manual: http://redis.io/topics/replication 18:19:00 GMT in short: spin up a redis instance on your new machine, connect to it with redis-cli, run "slaveof oldhost 6379" and watch "info replication" to see the replication status 18:20:02 GMT you probably need to use an ssh tunnel or vpn since redis probably isn't exposed to the internet (if you're going over the internet. and it shouldn't be exposed) 18:21:14 GMT minus: it is exposed (bad hosting once again), how do I use the slaveof command when both of the instances are password protected? 18:22:05 GMT config set requirepass 18:22:41 GMT eh 18:22:45 GMT wrong one 18:23:06 GMT masterauth 18:23:18 GMT to set the password for the master on the slave 18:23:58 GMT make sure you don't expose it to the internet afterwards anymore if you don't absolutely need to 18:26:33 GMT minus: ok, thanks, I'll give it a shot and report back.. 18:28:41 GMT minus: I've been told by the cli, that there's no such command as slaveof... Guess it's disabled then 18:40:17 GMT looks like it 18:45:46 GMT minus: is there any other way? 20:29:52 GMT nice listInsertNode isn't used anywhere in the code ? :) 21:25:17 GMT hi 21:25:44 GMT I want to parse a json feed over an API and save the content of that on a redis database 21:26:11 GMT but the feed will keep adding data, there is a mtime on it that I want to use to track the last data I added 21:26:20 GMT how can I do that efficiently? 21:26:32 GMT so I can resume by the mtime 21:27:27 GMT a sorted set with timestamp as score maybe? 21:27:36 GMT a key with the latest timestamp? 21:28:24 GMT yeah but how do I resume from the latest timestamp when rerunning my program 21:28:37 GMT probably not a redis question anymore 21:29:02 GMT I'll need to compare with what is in the redis db I guess? 22:16:04 GMT so should I keep track of the mtime? or just check for duplicates when parsing? 22:17:47 GMT I mean track the mtime in a way that I can use it for resuming later 22:17:58 GMT rather than parsing from the start again 22:25:13 GMT AFAIK redis has sets that will not allow for duplicates, right?