10:23:05 GMT <ren0v0> Hi, why would i be getting this?  *** FATAL CONFIG FILE ERROR *** Reading the configuration file, at line 2 >>> 'supervised systemd'  Bad directive or wrong number of arguments
10:23:08 GMT <ren0v0> i see nothing wrong with it
10:40:19 GMT <ren0v0> apparently this config option is newer than 3.0.7 :D
12:28:06 GMT <ren0v0> I'm running redis like this and its silently exiting with no error and the process isn't starting either.   sudo redis-server /etc/redis/redis_6379.conf
12:28:13 GMT <ren0v0> starting to get annoyed now!
12:57:16 GMT <minus> Don't run redis as root!
12:58:52 GMT <minus> Using redis-cli you can check what commands are executed (using the monitor command) e.g. SHUTDOWN
12:59:46 GMT <ren0v0> minus, i was going that because the damn systemd unit isn't working
12:59:56 GMT <ren0v0> and ffs sentinel keeps rewriting my config........
13:01:36 GMT <ren0v0> it keeps adding known-sentinel lines, with duplicates and its writing to a different filename and using it
13:01:59 GMT <ren0v0> my config is  "sentinel_26380", and it keeps writing to "sentinel.conf" and somehow its using it
13:02:58 GMT <ren0v0> minus, ah yes, systemd unit isn't working because sentinel keeps wanting to write to my config that is in /etc/redis/ and its not writable by redis user
13:03:45 GMT <ren0v0> what is the correct way to change those permissions? I have this in my systemd unit but its not working http://pastebin.com/hMc9mhHq
13:05:27 GMT <ren0v0> 8399:X 01 Feb 13:05:08.972 # Sentinel config file /etc/redis/sentinel_6380.conf is not writable: Permission denied. Exiting
13:06:15 GMT <minus> Seems like a systemd problem, not really related to redis directly
13:06:48 GMT <minus> Haven't configured systemd units to this extent
13:06:51 GMT <ren0v0> isn't the systemd unit shipped with redis ?
13:23:56 GMT <ren0v0> minus, i keep getting "+sdown sentinel"  any ideas where i could look to find out why that is ?
13:24:43 GMT <ren0v0> just after starting >  http://pastebin.com/wnDdJYkf
13:36:06 GMT <ren0v0> now my slave seemingly won't sync either :(  http://pastebin.com/rXEfBL57
13:44:53 GMT <ren0v0> error after error >>>  I/O error reading bulk count from MASTER: Operation now in progress
13:51:13 GMT <ren0v0> Failed opening the RDB file dump.rdb (in server root dir /var/lib/redis-6380) for saving: Read-only file system
13:51:16 GMT <ren0v0> yawn
14:01:22 GMT <ren0v0> 4.0K drwxrwx---  2 redis   redis   4.0K Feb  1 13:57 redis-6380
14:01:26 GMT <ren0v0> what's wrong with that ?
14:02:07 GMT <minus> that's not the same path as in your systemd config, is it?
14:11:43 GMT <ren0v0> erm, this is my systemd config  http://pastebin.com/j1k2EXsB
14:11:52 GMT <ren0v0> its taken fro the package
14:12:54 GMT <minus> ReadWriteDirectories=-/var/lib/redis ← is not /var/lib/redis-6380
14:13:05 GMT <ren0v0> ah, hmm
14:14:19 GMT <ren0v0> to be honest all the dirs are set in redis.conf so i assumed this wouldn't matter
14:14:27 GMT <ren0v0> the dir is owned by redis:redis as well
14:21:04 GMT <ren0v0> made that change and for some reason the unit wont start now
14:21:12 GMT <ren0v0> no logs in redis and the systemd logs are completely useless
14:52:12 GMT <shmoon_> i understood brpop vs rpop, basically former takes a timeout so that it doesn't return null instantly. if a new element is added in that timeout timeframe it will rpop that and return.
14:52:22 GMT <shmoon_> how is it better though ? what are the use cases
15:52:27 GMT <badboy_> shmoon_: blocking until new elements are available
15:52:30 GMT <badboy_> e.g. a worker queue
15:52:53 GMT <badboy_> shmoon_: ↑
16:33:42 GMT <cyberdog> hi