Thanks Jerome
I just see this setup goes in line with that you are saying.
https://yemaosheng.com/2016/04/haproxy-cfg-for-redis-sentinel/
Thanks so much for replying.
Regards
Brent
On 05/06/2018 13:49, Jerome Magnin wrote:
Hi Brent,
On Tue, Jun 05, 2018 at 01:18:36PM +0200, Brent Clark wrote:
Good day Guys
I am at a total loss, and Im hoping someone on this list, would be so kind
to review my setup.
I am trying to get haproxy to monitor redis / sentinel. But I keep getting.
[WARNING] 155/110602 (309) : config : log format ignored for frontend
'ft_redis' since it has no log address.
[ALERT] 155/110602 (309) : parsing [/usr/local/etc/haproxy/haproxy.cfg:29] :
unable to find server '10.42.131.120' in proxy 'bk_redis', referenced in arg
1 of ACL keyword 'srv_is_up' in proxy 'bk_redis'.
[ALERT] 155/110602 (309) : parsing [/usr/local/etc/haproxy/haproxy.cfg:30] :
unable to find server '10.42.40.236' in proxy 'bk_redis', referenced in arg
1 of ACL keyword 'srv_is_up' in proxy 'bk_redis'.
[ALERT] 155/110602 (309) : parsing [/usr/local/etc/haproxy/haproxy.cfg:31] :
unable to find server '10.42.224.133' in proxy 'bk_redis', referenced in arg
1 of ACL keyword 'srv_is_up' in proxy 'bk_redis'.
[ALERT] 155/110602 (309) : Fatal errors found in configuration.
What I cant understand is, I changed to ips as opposed to hostnames. But
haproxy still cant see the peer.
Here is my configuration file.
https://pastebin.com/raw/DGTsNRDs
If someone can assist it would be appreciated.
srv_is_up takes an optionnal backend name and a mandatory server name as
argument. server name is the second argument on a server line, it does not have
to be a (resolvable) fqdn.
example:
use-server redis-server-0 if { srv_is_up(10.42.131.120/sentinel0) } ...
I'm not sure I understand what you want to do, though.
