Redis won't start with maxmemory values .. why?

[Brian Dunbar]

Redis 2.8.14

CentOS 7.0.1406

Single host in staging.

Two hosts in production

Installed using yum.

With these values in staging host:/etc/redis.conf the service cranks up ok. 

maxmemory 500mb

maxmemory-policy volatile-ttl

Installed production hosts, told host2 it was a slave of host1,and with the above values in /etc/redis.conf and it would not start.

# systemctl status redis.service

redis.service - Redis persistent key-value database

   Loaded: loaded (/usr/lib/systemd/system/redis.service; enabled)

   Active: failed (Result: exit-code) since Mon 2015-01-19 15:39:59 EST; 2min 32s ago

  Process: 20624 ExecStop=/usr/bin/redis-shutdown (code=exited, status=1/FAILURE)

 Main PID: 20608 (code=exited, status=0/SUCCESS)

Removed the two maxmemory lines and it fires up okay, keypairs written to master show up in slave.

What in the wide world of sports am I doing wrong?

~brian

[Jan-Erik Rediger]

Check the log (either a log file you set our using journalctl).
It should tell you more.

> --
> You received this message because you are subscribed to the Google Groups "Redis DB" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
> To post to this group, send email to redi...@googlegroups.com.
> Visit this group at http://groups.google.com/group/redis-db.
> For more options, visit https://groups.google.com/d/optout.