Sponsored Content
Full Discussion: Nagios alert on HTTP
Top Forums UNIX for Dummies Questions & Answers Nagios alert on HTTP Post 302603929 by lramsb4u on Friday 2nd of March 2012 10:36:43 AM
Old 03-02-2012
Nagios alert on HTTP

Getting below alert from Nagios server.
How to resolve this issue.

Code:
Notification Type: PROBLEM
Service: HTTPHost: localhostAddress: 127.0.0.1State:
WARNINGDate/Time: Fri Mar 2 08:45:21 EST 2012
Additional Info:HTTP WARNING: HTTP/1.1 403 Forbidden - 4183 bytes in 0.001 second response time

Thanks in advance!

---------- Post updated at 10:36 AM ---------- Previous update was at 10:21 AM ----------

Hi all,

Found the solution at linux help topics: Ngaios HTTP WARNING: HTTP/1.1 403 Forbidden

How to mark thread as solved ?

Thanks!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ALERT!!! ALERT!!! I messed up the UNIX!!!

Hello If you want a short description read my last thread! I have no root access anymore. No remote access! By user access i get a programm started and when i close it, i got logged off! So I guess I messed up the passwd file! is there a chance of booting a unix system (SCO-UNIX UnixWare... (15 Replies)
Discussion started by: Fwurm
15 Replies

2. Programming

sending http url through http socket programming..

hi am senthil am developing a software to send and receive SMS using HTTP connection first of all am forming a URL and sending that URL to a remote server using my Client Program i send that url through Socket(using Send() Function) if i send more than one URL one by one using the same... (0 Replies)
Discussion started by: senkerth
0 Replies

3. Shell Programming and Scripting

sending http url through http socket programming..

hi am senthil am developing a software to send and receive SMS using HTTP connection first of all am forming a URL and sending that URL to a remote server using my Client Program i send that url through Socket(using Send() Function) if i send more than one URL one by one using the same... (4 Replies)
Discussion started by: senkerth
4 Replies

4. Infrastructure Monitoring

Nagios - alert during business hours

Is there a way for certain nagios alerts to only alert during business hours? (1 Reply)
Discussion started by: streetfighter2
1 Replies

5. Infrastructure Monitoring

Nagios Alert in Japanese

I have googled for weeks now and all I am getting is the same results from frank4dd's notes on setting up perl script to produce alerts in Japanese. On the contrary I wish to ensure all my alerts come in English as primary language. What I am getting from Japanese-language-Windows-machine added... (1 Reply)
Discussion started by: hedkandi
1 Replies

6. Red Hat

Nagios is sending "Service Alert: CentOS 5/HTTP is WARNING"

Hello All, I have setup Nagios 3.2.3 on CentOS release 5.7 (Final) with the default config files and added 1 host to it and it is sending "Service Alert: CentOS 5/HTTP is WARNING" frequently, how do you fix this one? what are the additional files that need to be added so that I can monitor the... (0 Replies)
Discussion started by: lovesaikrishna
0 Replies

7. Infrastructure Monitoring

Nagios check dependent on second nagios server

We have a dual Nagios server setup. One is setup for internal server monitoring on our LAN, while the second Nagios server is hosted externally and is used for external checks only such as URL and ping checks form the WAN side. I was wondering if there is any way to setup cross dependencies... (1 Reply)
Discussion started by: eugenes18t
1 Replies

8. Web Development

HTTP Headers Reference: HTTP Status-Codes

Hypertext Transfer Protocol -- HTTP/1.1 for Reference - HTTP Headers 10 Status Code Definitions Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response. (1 Reply)
Discussion started by: Neo
1 Replies

9. Shell Programming and Scripting

awk script to find time difference between HTTP PUT and HTTP DELETE requests in access.log

Hi, I'm trying to write a script to determine the time gap between HTTP PUT and HTTP DELETE requests in the HTTP Servers access log. Normally client will do HTTP PUT to push content e.g. file_1.txt and 21 seconds later it will do HTTP DELETE, but sometimes the time varies causing some issues... (3 Replies)
Discussion started by: Juha
3 Replies

10. Cybersecurity

**ALERT**ALERT* Whats app requesting users to upgrade to latest version as; its vulnerability found.

Hello All, Want to share here an article for Whats app users that team whats app is requesting users to upgrade to its latest version since they have found a vulnerability; where Hacker could turn on a cell's camera, mic and scan messages and emails. Here is an article from "THE VERGE" for... (1 Reply)
Discussion started by: RavinderSingh13
1 Replies
DAV::Response(3pm)					User Contributed Perl Documentation					DAV::Response(3pm)

NAME
HTTP::DAV::Response - represents a WebDAV HTTP Response (ala HTTP::Response) SYNOPSIS
require HTTP::DAV::Response; DESCRIPTION
The HTTP::DAV::Response class encapsulates HTTP style responses. A response consists of a response line, some headers, and (potentially empty) content. HTTP::DAV::Response is a subclass of "HTTP::Response" and therefore inherits its methods. (HTTP::Response in turn inherits it's methods from "HTTP::Message"). Therefore, this class actually inherits a rich library of functions. You are more likely wanting to read the "HTTP::Response" class as opposed to this class. Instances of this class are usually created by a "HTTP::DAV::Resource" object after it has performed some request (such as get, lock, delete, etc). You use the object to analyse the success or otherwise of the request. HTTP::DAV::Response was created to handle two extra functions that normal HTTP Responses don't require: - WebDAV reponses have 6 extra error codes: 102, 207, 422, 423, 424 and 507. Older versions of the LWP's C<HTTP::Status> class did not have these extra codes. These were added. - WebDAV responses can actually contain more than one response (and often DO contain more than one) in the form of a "Multistatus". These multistatus responses come in the form of an XML document. HTTP::DAV::Response can accurately parse these XML responses and emulate the normal of the C<HTTP::Response>. HTTP::DAV::Response transparently implements these extra features without the user having to be aware, so you really should be reading the "HTTP::Response" documentation for most of the things you want to do (have I already said that?). There are only a handful of custom functions that HTTP::DAV::Response returns and those are to handle multistatus requests, "messages()" and "codes()". The six extra status codes that DAV servers can be returned in an HTTP Response are: 102 => "Processing. Server has accepted the request, but has not yet completed it", 207 => "Multistatus", 422 => "Unprocessable Entity. Bad client XML sent?", 423 => "Locked. The source or destination resource is locked", 424 => "Failed Dependency", 507 => "Insufficient Storage. The server is unable to store the request", See "HTTP::Status" for the rest. HANDLING A MULTISTATUS
So, many DAV requests may return a multistatus ("207 multistatus") instead of, say, "200 OK" or "403 Forbidden". The HTTP::DAV::Response object stores each "response" sent back in the multistatus. You access them by array number. The following code snippet shows what you will normally want to do: ... $response = $resource->lock(); if ( $response->is_multistatus() ) { foreach $num ( 0 .. $response->response_count() ) { ($err_code,$mesg,$url,$desc) = $response->response_bynum($num); print "$mesg ($err_code) for $url "; } } Would produce something like this: Failed Dependency(424) for /test/directory Locked(423) for /test/directory/file3 This says that we couldn't lock /test/directory because file3 which exists inside is already locked by somebody else. METHODS
is_multistatus This function takes no arguments and returns a 1 or a 0. For example: if ($response->is_multistatus() ) { } If the HTTP reply had "207 Multistatus" in the header then that indicates that there are multiple status messages in the XML content that was returned. In this event, you may be interested in knowing what the individual messages were. To do this you would then use "messages". response_count Takes no arguments and returns "the number of error responses -1" that we got. Why -1? Because usually you will want to use this like an array operator: foreach $num ( 0 .. $response->response_count() ) { print $response->message_bynum(); } response_bynum Takes one argument, the "response number" that you're interested in. And returns an array of details: ($code,$message,$url,$description) = response_bynum(2); where $code - is the HTTP error code (e.g. 403, 423, etc). $message - is the associated message for that error code. $url - is the url that this error applies to (recall that there can be multiple responses within one response and they all relate to one URL) $description - is server's attempt at an english description of what happened. code_bynum Takes one argument, the "response number" that you're interested in, and returns it's code. E.g: $code = $response->code_bynum(1); See "response_bynum()" message_bynum Takes one argument, the "response number" that you're interested in, and returns it's message. E.g: $code = $response->message_bynum(1); See "response_bynum()" url_bynum Takes one argument, the "response number" that you're interested in, and returns it's url. E.g: $code = $response->message_bynum(1); See "response_bynum()" description_bynum Takes one argument, the "response number" that you're interested in, and returns it's description. E.g: $code = $response->message_description(1); See "response_bynum()" messages Takes no arguments and returns all of the messages returned in a multistatus response. If called in a scalar context then all of the messages will be returned joined together by newlines. If called in an array context the messages will be returned as an array. $messages = $response->messages(); e.g. $messages eq "Forbidden Locked"; @messages = $response->messages(); e.g. @messages eq ["Forbidden", "Locked"]; This routine is a variant on the standard "HTTP::Response" "message()". perl v5.10.1 2009-01-29 DAV::Response(3pm)
All times are GMT -4. The time now is 08:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy