Hello Team,
Greetings …!
We are using the below version of checkmk for our monitoring purposes, and we use it to monitor websites.
Checkmk version: Checkmk Raw Edition 2.3.0p
From the day we configured checkmk we started noticing errors for certain domains as mentioned below.
Error: checkmk Unknown error - Unable to figure out expiration date for domains
Upon further checking we found that there is one script responsible for finding the expiration date of domains, the script location is mentioned below.
/omd/sites/cmk/local/lib/check_mk/base/plugins/agent_based/check_domain.sh
The script is working fine and the domain has validity, but sometimes it shows unknown errors (false positive alerts in checkmk) - the issue becomes a headache for us. So we started testing the script from our local machine and from the checkmk server and noticed that the script failed to get the expiry date when run from the checkmk server.
Upon further investigation, we came to the conclusion that: for certain domains, the checkmk server executes the domain expiry check script (check_domain.sh) every 20 times and this is causing the domain registrar to block whois request coming from the checkmk server for a period of time.
We get the below error when this limit reaches from our checkmk server
eg: whois abc.com
Number of allowed queries exceeded.
fgets: Connection reset by peer
Question: To avoid this Whois check rate limit block what should we do, we have been looking for options to reduce the number of times checkmk executes domain expiry check for a domain.
There are around 90 websites monitored so we would like to limit domain expiry checks to be executed only one time a day globally.
Regards
SWAROOP B B