I'm testing this on EC2. Nagios is configured with the check_drupal command.

Before configuring the module for localhost, NAGIOS is reporting that the status of DRUPAL is OK. Status reads "DRUPAL OK, DRUPAL:OK=Unauthorized "

Image attached.

CommentFileSizeAuthor
#1 Nagios-1.png44.89 KBlangworthy

Comments

langworthy’s picture

langworthy commented
StatusFileSize
new Nagios-1.png44.89 KB

attaching image.

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

Subscribing - I should look at this if I get time.

malc0mn’s picture

malc0mn commented

Isn't this simply a problem with the useragent and unique ID not being set / the same?

jeffvoskamp’s picture

jeffvoskamp commented

My question is "was the original message wrong?" Drupal is fine (I can send you a page) to the limits of what I'm allowed to tell a stranger on the street.

Nothing to see here, move along. :-)

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented
Status: Active » Closed (works as designed)

I'm inclined to agree with JeffVoskamp here - in fact, Pingdom does the opposite, much to my frustration! It was convinced the 403 on my home page (content access deliberately removed from anonymous users) meant the site was down - site is *not* down.

If you are expecting Drupal to display particular text, for example, then a regex check of the front page is much better, and is out of scope for this module at the moment. We do this with Nagios' check_http plugin:
http://nagiosplugins.org/man/check_http