⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.94
Server IP:
178.33.27.10
Server:
Linux cpanel.dev-unit.com 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 x86_64
Server Software:
Apache/2.4.57 (Unix) OpenSSL/1.0.2k-fips
PHP Version:
8.2.11
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
usr
/
local
/
src
/
netdata
/
health
/
guides
/
redis
/
View File Name :
redis_master_link_down.md
### Understand the alert The `redis_master_link_down` alert is triggered when there is a disconnection between a Redis master and its slave for more than 10 seconds. This alert indicates a potential problem with the replication process and can impact the data consistency across multiple instances. ### Troubleshoot the alert 1. Check the Redis logs Examine the Redis logs for any errors or issues regarding the disconnection between the master and slave instances. By default, Redis log files are located at `/var/log/redis/redis.log`. Look for messages related to replication, network errors or timeouts. ``` grep -i "replication" /var/log/redis/redis.log grep -i "timeout" /var/log/redis/redis.log ``` 2. Check the Redis replication status Connect to the Redis master using the `redis-cli` tool, and execute the `INFO` command to get the detailed information about the master instance: ``` redis-cli INFO REPLICATION ``` Also, check the replication status on the slave instance. If you have access to the IP address and port of the slave, connect to it and run the same `INFO` command. 3. Verify the network connection between the master and slave instances Test the network connectivity using `ping` and `telnet` or `nc` commands, ensuring that the connection between the master and slave instances is stable and there are no issues with firewalls or network policies. ``` ping <slave_ip_address> telnet <slave_ip_address> <redis_port> ``` 4. Restart the Redis instances (if needed) If Redis instances are experiencing issues or are unable to reconnect, consider restarting them. Be cautious as restarting instances might result in data loss or consistency issues. ``` sudo systemctl restart redis ``` 5. Monitor the situation After addressing the potential issues, keep an eye on the Redis instances to ensure that the problem doesn't reoccur. ### Useful resources 1. [Redis Replication Documentation](https://redis.io/topics/replication)