Known Issues

A list of workarounds for known issues with check_site_simple.

Please feel free to request a solution by sending an email to developer@monitoring-plugins.pro if you are not happy with one of the workarounds presented below.

Too many requests (youtube.com)

Example

CHECK_SITE_SIMPLE CRITICAL - 9 pages checked, 9 pages with error
https://www.google.com/sorry/index?continue=https://www.youtube.com/watch%3Fv%3DsynYj3Bxosg&q=EhAqAQT4DBd7mwAAAAAAAAABGJrCpfwFIhkA8aeDSxcPBPMfEdmb9DsAlGAotkqkym2pMgFy (ERROR: 429 Too Many Requests (source: http://tour.fediverse.at/friendica/ressourcen/))
...

Youtube does not like to get crawled. If your site has many links and a small interval between checks, you may reach some threshold and will be blocked.

Workarounds

  1. Check pages with youtube-links one by one and with a higher interval

  2. Exclude links to youtube from monitoring: --ignore="\Qyoutube.com\E"

Links to linked.in are heavily protected against automatic crawling and return 999 instead of 200 if their pages are requested by a crawler.

Workaround

Exclude external linked.in requests from the check: --ignore="\Qlinkedin.com\E"

Redirected URLs show “0 resources checked”

Examples:

$ check_site_simple -U http://my-site.com
CHECK_SITE_SIMPLE CRITICAL - 0 resources checked, 0 resources with error

$ check_site_simple -U http://my-site.com --crawl
CHECK_SITE_SIMPLE CRITICAL - 0 resources checked, 0 resources with error

$ check_site_simple -U https://my-other-url.com
CHECK_SITE_SIMPLE CRITICAL - 0 resources checked, 0 resources with error

All of the above examples have one thing in common: They are redirected pages.

  • http://my-site.com redirects to the ssl-site https://my-site.com

  • https://my-other-url.com redirects to let’s say https://my-main-url.com

Explanation

check_site_simple sees any URL beside the one given with --url as an external page, where its crawler follows once but stops on the target (otherwise we would check the whole World Wide Web). Therefore if the URL itself redirects to something else it correctly reports 0 resources (pages) checked.

Solution and Configuration

The solution is simple: Just configure check_site_simple with the correct, not further redirected --url (https://my-site.com and https://my-main-url.com in the examples above).

If for whatever reason you want a “0 resources checked” result to not be CRITICAL, set the desired result with --no-pages=OK|WARNING|CRITICAL|UNKNOWN parameter. This can be used eg; to check if a URL redirects to at least something.

Setting --no-pages=OK can likely lead to false-negative results. Take extra-care not to check a redirected host with --no-pages set to OK. Redirected resources like paths and pages are not that problematic and are a good reason for --no-pages=OK.

We plan an enhanced check_site_pro tool, which will allow to extensively check for correct redirects as well. Please get in touch with us if you are interested in a trial.