Nagios Support Forum

Hey Everyone.

A quick question for anyone using Nagios. A client has been receiving Nagios alerts from their website. Their website is on another host, and when questioned has not giving any answers that would indicate an issue. This is the alert;

HTTP CRITICAL: HTTP/1.1 301 Moved Permanently - pattern not found - 393 bytes in 0.144 second response time

This alert is sent to the client every 2 hours. There's another monitor setup for the website and it's not sent any alerts. At the time when each alert comes in, or at least 5 minutes before, we check the site and it loads quickly. The site has not been down. The Nagios alert is set to "see" a sentence of text on a page. Once that text is missing, then the alert is sent...but yet the text is not missing (white screen of death) and the site is not down.

Any suggestions?

A few thoughts were anything cron related, but that seems to not be the case.

Hi Mastemi,

You can customize how the website check handles redirects. One possibility is that the check is set to see redirects as CRITICAL rather than OK.

In the Website Monitoring Wizard in Nagios XI, you will see an 'On Redirect' option dropdown in the top Website Options section of Step 2. Choose 'ok' here to make 301's return an OK status.

In the actual check argument (for check_http) I believe you would use the ' -f ok ' flag to specify this (in case you're just updating in the Core Config Manager, instead of re-running the wizard against the same URL and hostname).

Or, maybe the string you are verifying is present isn't an *exact* match?

455157 wrote:Hi Mastemi,

You can customize how the website check handles redirects. One possibility is that the check is set to see redirects as CRITICAL rather than OK.

In the Website Monitoring Wizard in Nagios XI, you will see an 'On Redirect' option dropdown in the top Website Options section of Step 2. Choose 'ok' here to make 301's return an OK status.

In the actual check argument (for check_http) I believe you would use the ' -f ok ' flag to specify this (in case you're just updating in the Core Config Manager, instead of re-running the wizard against the same URL and hostname).

Or, maybe the string you are verifying is present isn't an *exact* match?

Or you can add -f follow which will follow the 301 redirect and then check the status on the page you redirected to