Chkservd continues restarting Redis

orvisoft

• February 10, 2021 00:21

I had followed this forum post /etc/chkserv.d/redis
The problem that is really annoying is that system continues throwing errors in [CODE=general]/var/log/chkservd.log
With messages like this [CODE=bash][check command:+][socket connect:-][socket failure threshold:163/3][fail count:161]Restarting redis....
I am now at blind spot to fix this continued issue in service manager. If I remove the monitoring, the Redis keeps working fine, but the purpose of adding in monitoring is to ensure the 100% availability of services in absence of administrator which is why the chkserv is there. Any help is really appreciated.

• 

  cPRex Jurassic Moderator

  • February 10, 2021 12:59

  Hey there! From the server itself, are you able to reach port 6379? If not, that would cause the service check to fail. We also have more official documentation on those settings here:

  0
• 

  orvisoft

  • February 10, 2021 13:46

  Hi, Yes my application is able to reach on port 6379 and application is working like a charm. From [CODE=bash][root@localhost serviceauth]# netstat -tulnp | grep "6379" tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 14374/redis-server [root@localhost serviceauth]#
  And also the lsof lists this successfully [CODE=bash][root@localhost serviceauth]# lsof -i | grep ":6379" redis-ser 14374 redis 4u IPv4 12664598 0t0 TCP localhost:6379 (LISTEN) redis-ser 14374 redis 7u IPv4 12682030 0t0 TCP localhost:6379->localhost:46860 (ESTABLISHED) redis-ser 14374 redis 8u IPv4 12684077 0t0 TCP localhost:6379->localhost:46862 (ESTABLISHED) redis-ser 14374 redis 11u IPv4 12676978 0t0 TCP localhost:6379->localhost:45950 (ESTABLISHED) redis-ser 14374 redis 15u IPv4 12679730 0t0 TCP localhost:6379->localhost:45926 (ESTABLISHED) redis-ser 14374 redis 16u IPv4 12679733 0t0 TCP localhost:6379->localhost:45928 (ESTABLISHED) redis-ser 14374 redis 19u IPv4 12676980 0t0 TCP localhost:6379->localhost:45952 (ESTABLISHED) ea-php72 15217 example 3u IPv4 12683668 0t0 TCP localhost:45926->localhost:6379 (ESTABLISHED) ea-php72 15217 example 4u IPv4 12683669 0t0 TCP localhost:45928->localhost:6379 (ESTABLISHED) ea-php72 15217 example 8u IPv4 12682526 0t0 TCP localhost:45950->localhost:6379 (ESTABLISHED) ea-php72 15217 example 9u IPv4 12682527 0t0 TCP localhost:45952->localhost:6379 (ESTABLISHED) httpd 15241 example 19u IPv4 12680104 0t0 TCP localhost:46860->localhost:6379 (ESTABLISHED) httpd 15241 example 20u IPv4 12680105 0t0 TCP localhost:46862->localhost:6379 (ESTABLISHED) [root@localhost serviceauth]#
  Also the telnet have same results as expected [CODE=bash][root@localhost serviceauth]# telnet localhost 6379 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'.
  This is the only reason why I am at blind spot.

  Hey there! From the server itself, are you able to reach port 6379? If not, that would cause the service check to fail. We also have more official documentation on those settings here:

  0
• 

  cPRex Jurassic Moderator

  • February 10, 2021 13:53

  Thanks for the additional details. I do agree that the command you've provided should work as expected. You may want to consider submitting a ticket to our team so we can check that directly on the server, as this could indicate an issue with chkservd. If you do submit a ticket please post the number here so I can follow along and keep this thread updated.

  0
• 

  ffeingol

  • February 10, 2021 15:37

  It's just a guess, but is it possible that the issue because Redis is only listing on localhost? It's hard to tell if chkservd is connecting to localhost or the server IP for the checks.

  0
• 

  orvisoft

  • February 11, 2021 05:01

  I had opened a ticket with ticket id #94225166

  Thanks for the additional details. I do agree that the command you've provided should work as expected. You may want to consider submitting a ticket to our team so we can check that directly on the server, as this could indicate an issue with chkservd. If you do submit a ticket please post the number here so I can follow along and keep this thread updated.

  
  Yeah I believe so, but I am unsure how to fix this as my application works as expected without any issue.

  It's just a guess, but is it possible that the issue because Redis is only listing on localhost? It's hard to tell if chkservd is connecting to localhost or the server IP for the checks.

  
  

  0
• 

  orvisoft

  • February 11, 2021 13:34

  So from ticket, the solution is to validate the response. cPanel team input is as below. (Might be useful for peoples searching for a solution to similar issues) I can see that the config file appears to be using an improper command to check the service, and it is expecting an incorrect response. With redis, you will want to ensure that the proper call and check commands are used in the command. [CODE=bash][07:24:26 m2production root@94225166 ~]cPs# redis-cli ping PONG
  These are the proper call and response for redis. You will want to ensure that you alter your config to include these so that when the call is made, it is returning the proper response. /etc/chkserv.d/redis
  

  0
• 

  cPRex Jurassic Moderator

  • February 11, 2021 13:58

  I'm glad we were able to help get that resolved!

  0

Please sign in to leave a comment.