02:02:20 GMT hey guys, is there a way we can find how many hashes currently in a redis db? 05:09:23 GMT Hellow dear forum, i have a question regarding communication of redis and haproxy 05:18:38 GMT if redis configured with authen password then it is allowing connection from haproxy with tcp mode - is there any haproxy configuration parameter that can introduce the password? 06:38:18 GMT greg_: you need to send the AUTH command in your checks, there's no parameter as HAProxy does not understand the redis protocol itself 06:50:45 GMT i tried parameter "reqadd Proxy-Authorization:\ Basic\$password" but still getting Error: Server closed the connection 06:51:42 GMT redis doesn't speak HTTP 06:52:15 GMT i see 06:52:38 GMT but which parameter i can use to introduce the password 06:52:57 GMT you should have commands like `tcp-check send PING\r\n` and need to add a tcp-check send AUTH... too 06:53:24 GMT or do you want clients to be able to use redis through HAProxy without password? 06:53:54 GMT tcp-check send AUTH\ auth_key\r\n 06:54:01 GMT http://blog.haproxy.com/2014/01/02/haproxy-advanced-redis-health-check/ 06:54:16 GMT that only works for the checks though 06:54:41 GMT i've never used HAProxy with Redis with authentication, so not sure if it works 06:54:57 GMT i must use password 06:55:54 GMT thanks for the information minus 08:34:06 GMT hi 08:34:54 GMT I am new to redis, redis service doesnt want to start. Logs says "Opening Unix socket: bind: No such file or directory" 08:35:17 GMT When I set maxmemory with maxmemory-policy to noeviction, how does that work? Is the data, when using save, release from memory when it writes? Or will it just keep on increasing? Using it to store sessions in magento and I want to limit redis to 64M ram since php, mysql and a lot of other stuff runs on the same server. 08:35:39 GMT Or is it up to magento to clear it perhaps? 08:36:00 GMT maybe there is a better policy for me? Not sure which to pick 08:44:12 GMT ok the problem was that the path to write the socket was missing 08:45:34 GMT now I can see on the configuration file "unixsocketperm 755" is that the permissions I have to setup on "/var/run/redis/redis.sock"? 08:57:49 GMT do i need to create the redis.sock file myself? 09:00:13 GMT masber: socket files are created by the application, it's a special socket file 09:00:33 GMT It'll be created when you get redis up and running 09:02:05 GMT Mattias, ok.. it is not creating the file then... because it says permission denied, I put 777 as permission to folder /var/run/redis 09:02:32 GMT masber: which OS? 09:02:38 GMT centos 7 09:07:04 GMT Mattias, I also changed the folder to /tmp/redis.sock but same result 09:07:26 GMT Hm, I just did the same on centos 7 but I have no issues. Did you modify the redis.conf file? 09:08:05 GMT I assume you used the official package "yum -y install redis" 09:09:08 GMT Mattias, ok, let me uninstall and reinstall it 09:11:27 GMT ok, it is working now 09:11:32 GMT not sure what was wrong 09:11:42 GMT Mattias, thank you!!! 10:04:00 GMT ok 10:04:04 GMT I got redis working 10:05:20 GMT Hi. Running redis for a third party app. For some reason, a BGSAVE tries to write to /dev/fd0 at random times. I can’t figure out why, but it’s causing redis to fail with a MISCONF 10:07:16 GMT simmerz: someone re-configured that instance? :) 10:07:34 GMT nope. only I have access to it, and no one’s tampered with it 10:07:39 GMT Redis doesn't randomly change it's dump file path 10:07:42 GMT if i restart redis, BGSAVE works 10:07:52 GMT are you sure? is it available on the internet? passwort protected? 10:07:53 GMT and did all of yesterday, until 1.27 this morning 10:08:00 GMT only accessibly via my ssh key 10:08:27 GMT no root access 10:08:47 GMT Redis by default listens on an tcp port, if that port is open to the internet anyone can access it 10:09:06 GMT <*> simmerz looks 10:09:17 GMT what config setting sets it to write to floppy? 10:09:49 GMT https://github.com/antirez/redis/blob/unstable/redis.conf#L255 10:10:07 GMT and https://github.com/antirez/redis/blob/unstable/redis.conf#L245 10:10:42 GMT thanks for the pointers 10:11:12 GMT and yep, didn’t realise it was bound to 0.0.0.0 10:11:27 GMT so someone was fiddling with the redis instance itself 10:11:34 GMT now bound to 127.0.0.1 10:14:04 GMT ;) 10:15:14 GMT https://web.archive.org/web/20160419180101/http://antirez.com/news/96 10:16:04 GMT thanks again :) 10:16:10 GMT now a little more secure 15:26:33 GMT the redis-lua test suite checks that 'list-max-ziplist-entries' is in the output of CONFIG GET * 15:26:34 GMT but it was removed 15:26:42 GMT can anybody recommend a key that has been stable in that output? 15:42:04 GMT bind, pidfile, logfile, ... 15:42:16 GMT literally everything else that's not exposing some internals 16:08:08 GMT badboy_, ack 16:08:10 GMT next question 16:08:13 GMT is nil allowed in -commands-? 16:08:26 GMT i.e. the null bulk string "$-1\r\n" 16:10:31 GMT redis says -ERR Protocol error: invalid bulk length 16:11:10 GMT when i send "*3\r\n$3\r\nSET\r\n$-1\r\n$3\r\nbar\r\n" 16:23:55 GMT then you know it: nil is not allowed ;) 16:24:01 GMT figured 16:24:23 GMT redis-lua 2.0.4 would just skip a nil, hanging the connection while redis waits for another argument 16:24:26 GMT 2.0.5 maps it to "" 16:24:33 GMT which feels wrong to me as in replies "" and nil are clearly different 16:24:43 GMT i'm going to propose to make it an error in redis-lua itself 16:24:45 GMT thanks badboy_ 16:51:27 GMT How to choose the expiration time length for redis keys? 16:52:07 GMT trump4redis, do you mean 'how to tell redis' or 'how to decide'? 16:52:53 GMT How to decide? 16:53:10 GMT well, that's hard to answer without more information 16:53:17 GMT what kind of info is in it? why should it expire? 16:53:36 GMT it is ebay product links 16:57:17 GMT Habbie: it is ebay product links. what should be an appropriate time length? 16:57:30 GMT i asked two questions 16:57:34 GMT you gave 0.5 answers 16:58:35 GMT Habbie: 1.ebay product links. 2. some product may become no longer available, i.e. ended auctions. 17:05:48 GMT trump4redis, well, you can see the end time for an auction 17:09:13 GMT Habbie: As they are all different, I'm hoping to use some kind rule of thumb, i.e. not too long or too short amount of time. but lacking of experience to begin the guess. 17:09:24 GMT so what happens if you expire too soon? 17:09:29 GMT or what happens if you expire too late? 17:09:33 GMT what bad things would happen in those cases? 17:11:43 GMT expire too soon, will lead to unnecessary API calls, hence reduce paging loading speed. expire too late, some listings will no longer be available, hence defeats the purpose of the whole app. 17:17:12 GMT you can set different expiration times on different keys 17:33:55 GMT minus: cool, but i was hoping for something even more simpler. 19:27:42 GMT a portent of things to come 23:11:27 GMT does master slave gives high throughput? 23:11:39 GMT scalling without clustering? 23:12:54 GMT is this achievable with sentinel