set up chkservd to monitor redis

[joaowall]

Hello, I would like help setting up redis monitoring through chkservd.

I have tried the following commands but have not been successful.

command: service[redis]=6379,PING,\+PONG,systemctl restart redis.service,redis,redis
message: Service check failed to completeredis: [-NOAUT != \+PONG

command: service[redis]=6379,redis-cli -a "$password" PING,\+PONG,systemctl restart redis.service,redis,redis
message: Service check failed to completeredis: [-ERR w != \+PONG]

command: service[redis]=6379,redis-cli -a "$password" -h 127.0.0.1 -p 6379 PING,\+PONG,systemctl restart redis.service,redis,redis
message: Service check failed to completeredis: [-ERR w != \+PONG]


Can someone help me, please?

 

[cPRex]

Hey there! Can you check the details in this thread to see if that will help with your situation? We were able to get that user more details through a ticket:

SOLVED - Chkservd continues restarting Redis

I had followed this forum post https://forums.cpanel.net/threads/chkserv-with-one-application-and-multiple-processes.562011/#post-2280571 And created monitoring for my redis service as echo "service[redis]=6379,QUIT,220,systemctl restart redis.service,redis-server,redis" > /etc/chkserv.d/redis...

forums.cpanel.net

 

[joaowall]

Hey there! Can you check the details in this thread to see if that will help with your situation? We were able to get that user more details through a ticket:

SOLVED - Chkservd continues restarting Redis

I had followed this forum post https://forums.cpanel.net/threads/chkserv-with-one-application-and-multiple-processes.562011/#post-2280571 And created monitoring for my redis service as echo "service[redis]=6379,QUIT,220,systemctl restart redis.service,redis-server,redis" > /etc/chkserv.d/redis...

forums.cpanel.net

Hi cPRex, I looked at this topic before, but it didn't work for me. My case is a little different because redis uses authentication. Thanks for your attention

 

[cPRex]

I'm not finding any additional details on my end, so it might be best to create a ticket with our support team so we can check this out.