James writes (in a private email):
Recently we fetched and installed 2.8.2 on some test servers and we encountered the following minor irritation:
If you attempt to test redis-server in sentinel mode using a command like:
redis --sentinel /etc/redis/sentinel.conf
... it gives an error message like:
*** FATAL CONFIG FILE ERROR *** Reading the configuration file, at line 2
'sentinel "/etc/redis/sentinel.conf"' Unrecognized sentinel configuration statement.
... but, of course, it works if you add the --sentinel after the config file name.
Perhaps a small change to the error message will save some others some time. If you see --sentinel anywhere in the argument list and are about to abort with a fatal config error you could add something like:
Perhaps you meant $ARG[0] $CONFPATH --sentinel ???
(I mention this because it flies in the face of Unix command line argument parsing conventions and may lead many users to the mistaken impression that they have built the package incorrectly ... leaving out the sentinel support, for example).
Comment From: joshpmcghee
I've submitted a pull request that addresses this.
Comment From: yossigo
The canonical form should really be to run redis-sentinel, closing this.