From: Burnson, R. <rbu...@cp...> - 2003-01-03 21:53:31
|
I am trying to setup distributed monitoring with Nagios 1.0 (Stable) on RedHat 7.2. I have the nsca daemon running on the central server, and I have been able to successfully send a service check result via nsca-send from the distributed server. The issue appears to be that the distributed server is not executing the ocsp_command. Here are the settings on the distributed server: 1. Obsess over services is enabled both globally and per service. 2. The ocsp_command is defined in nagios.cfg as ocsp_command=submit_check_result 3. "submit_check_result" is defined in the command definitions section exactly from the documentation. 4. The submit_check_result script was created in the libexec directory and the command definition points directly to this file. I can log in as nagios and run the submit_check_result shell script successfully, and the service check is received by the central server. It simply seems to be that Nagios is not executing the ocsp command with every service check. I've tried to watch the service check as they happen via the nagios.log file and even compiled nagios with debug 3. Is there a better way to debug this? Anyone have any ideas on what I may be missing? Thanks, Richard |
From: Stephane A. <sa...@pr...> - 2005-03-14 18:06:44
|
Hi everyone, =20 I have multiple sites and will be implementing them in my setup in the next few weeks. I've read that Nagios does distributed monitoring, which would fit my needs perfectly. Anyone know where I could get more information on how to set this up? All I've found so far is pretty vague... =20 Cheers! =20 Stephen =20 |
From: Chris W. <ch...@ai...> - 2005-03-29 11:18:34
|
Hi all, I'm trying to implement distributed monitoring with Nagios, to reduce the load on our servers as the redundant load balancers each evaluate the state of each server. However, I have run into a problem which I could again use your help with. We have two distributed servers which control the redundant load balancers, and should forward the results of active checks to each other. When both servers are up, they will randomly distribute active checks between themselves, running an active check whenever the current status becomes stale. If one server goes down, the other should automatically take over monitoring of all services, as all the results become stale. The problem is that when a passive service check result is received by a distributed server, it is treated exactly the same as an active result, in that the OCSP handler is called. This means that the two distributed servers end up sending each other the same events in a loop, until the NCSA packet timeout expires. There doesn't appear to be any way for the OCSP handler to know whether the result was received from an active or a passive check (and thus to ignore passive checks, preventing loops). Does anyone know if it's possible? I can't see any macro for this purpose documented at [http://nagios.sourceforge.net/docs/1_0/macros.html]. Cheers, Chris. -- (aidworld) chris wilson | chief engineer (ch...@ai...) |
From: Jason M. <jhm...@to...> - 2005-03-29 15:30:24
|
On Tue, Mar 29, 2005 at 12:18:28PM +0100, Chris Wilson wrote: > There doesn't appear to be any way for the OCSP handler to know whether > the result was received from an active or a passive check (and thus to I don't believe there is a way to do this right now, but it should be pretty easy to add a $LASTCHECKTYPE$ macro that would allow the OCSP to differentiate between the two. -Jason Martin --=20 This message is PGP/MIME signed. |
From: InnovationsTech, M. T. <MThomas@InnovationsTech.com> - 2006-04-13 00:08:58
|
I've setup a distributed monitoring server. One issue I'm seeing is that the distributed server only updates the central server every 4-6 minutes.=20 I have service checks running every 90 seconds on the distributed server. I have it set to obsess over services. =20 Is there any way to adjust how often the send_nsca utility is actually ran, or adjust how often the distributed server updates the central server? I have freshness turned on, and it always wants to go out and get the results, because it thinks they are stale after 2-3 min. (threshold set to 450sec). But this creates double traffic, and kind of defeats the reason for distributed monitoring. =20 Thank You, Matt |
From: Jason M. <jhm...@to...> - 2006-04-13 00:31:26
|
On Wed, Apr 12, 2006 at 08:06:08PM -0400, InnovationsTech, Matthew Thomas w= rote: > ran, or adjust how often the distributed server updates the central > server? If you are obsessing over services, then send_nsca is called for each and every service check. > I have freshness turned on, and it always wants to go out and get the > results, because it thinks they are stale after 2-3 min. (threshold set > to 450sec). But this creates double traffic, and kind of defeats the > reason for distributed monitoring. It sounds like send_nsca is not actually succeeding in getting the data to the central server. -Jason Martin > =20 >=20 > Thank You, >=20 > Matt >=20 --=20 All stressed out, and no one to choke... This message is PGP/MIME signed. |
From: Moayad M. <mmo...@ba...> - 2007-01-22 09:23:58
|
Dears, I have one nagios server working in my company, and I need to add another nagios server to monitor another servers in other subnets, I don't know if there's any solution to have 2 nagios servers(1 central nagios) and 1 monitor screen... it's mean the second server will send all check results to the central nagios. =20 =20 Thank you in advance Moayad Mohammad |
From: Dmitriy K. <di...@hi...> - 2007-01-22 10:08:54
|
On Mon, Jan 22, 2007 at 11:28:43AM +0200, Moayad Mohammad wrote: > I have one nagios server working in my company, and I > need to add another nagios server to monitor another servers in other > subnets, > > I don't know if there's any solution to have 2 nagios servers(1 central > nagios) and 1 monitor screen... it's mean the second server will send > all check results to the central nagios. It's work in our installation. But, I don't find no one web config tool support this. :( It's not complicated. Look schema: Central Host (location1 + location2) ^ ^ | | | | location1 location2 You making service_template_locations and host_template_locations. On central host and on locations it's different templates (active_check_enable 0 and 1 correspondingly) All checks for locations based on this templates. Next, you must setup nsca on central host and send_nsca on location{1,2}, configure on location{1,2}: obsess_over_services= ocsp_command= obsess_over_hosts= ochp_command= and disable direct notification on locations -- only central host sending notifications. Also, good idea make checks on location{1,2} for nagios on central host (over nrpe) and make eventhandler in this check for enabling notification directly on location[1,2}, when nagios on central host dead. eventhadler example: -------------------- #!/bin/sh # $Id: service_notification,v 1.1 2006/01/18 14:40:02 dkirhlarov Exp $ # this handler switching notifications. # for details contact di...@oi... DATE="`which date 2>/dev/null`" || DATE="/bin/date" CAT="`which cat 2>/dev/null`" || CAT="/bin/cat" BASENAME="`which basename 2>/dev/null`" || BASENAME="/bin/basename" ECHO="`which echo 2>/dev/null`" || ECHO="/bin/echo" AWK="`which awk 2>/dev/null`" || AWK="/bin/awk" PRINTF="`which printf 2>/dev/null`" || PRINTF="/usr/bin/printf" PROGNAME=`${BASENAME} $0` NAGIOSCMD="/usr/local/nagios/var/rw/nagios.cmd" NOW=`${DATE} +%s` print_help() { ${CAT} <<EOF Event Handler for switch on|off notifications Usage: $PROGNAME -s $SERVICESTATE$ -st $SERVICESTATETYPE$ [-c /path/to/nagios/cmd/file] Keys: -s -- STATE of service -st -- TYPE of service STATE (for details read nagios documentation) -c -- command nagios socket. By default /usr/local/nagios/var/rw/nagios.cmd Usage: $PROGNAME --help EOF } enable_event() { ${PRINTF} "[%lu] ENABLE_NOTIFICATIONS\n" ${NOW} > ${NAGIOSCMD} } disable_event() { ${PRINTF} "[%lu] DISABLE_NOTIFICATIONS\n" ${NOW} > ${NAGIOSCMD} } # Make sure the correct number of command line # arguments have been supplied if [ $# -lt 4 ]; then print_help exit -1 fi $ECHO $* >> /usr/local/nagios/var/event.out # Grab the command line arguments while [ -n "$1" ]; do case "$1" in --help|-h) print_help exit -1 ;; -s) # state of service STATE=$2 shift ;; -st) # state type of service STATETYPE=$2 shift ;; -c) # command file NAGIOSCMD=$2 shift ;; *) ${ECHO} "Wrong param '$1'" print_help exit -1 ;; esac shift done # Run check case "$STATETYPE" in HARD) case "$STATE" in CRITICAL) # Time to enabling local notification feature enable_event ;; WARNING|UNKNOWN) # Just smoke ;; OK) # Disable local notification feature disable_event ;; *) # What the shit we are get? ${ECHO} "What?.. Can't understand '$STATE'" exit -1 ;; esac ;; esac exit 0 -------------------- WBR. Dmitriy |
From: Marcel M. F. S. <ms...@uo...> - 2007-01-22 19:03:19
|
On Mon, 2007-01-22 at 13:08 +0300, Dmitriy Kirhlarov wrote: >=20 > > I have one nagios server working in my company, and > I > > need to add another nagios server to monitor another servers in > other > > subnets, > >=20 > > I don't know if there's any solution to have 2 nagios servers(1 > central > > nagios) and 1 monitor screen... it's mean the second server will > send > > all check results to the central nagios. >=20 > It's work in our installation. > But, I don't find no one web config tool support this. :( I've tested monarch, and with wome tweaking you can generate configs for distributed and central nagios instances. You just tell monarch the file you are generating, and with something like cronned ssh/scp/rsync you can upload the config to your distributed server and reload the new config in an automated way. > It's not complicated. >=20 > Look schema: >=20 > Central Host (location1 + location2) > ^ ^ > | | > | | > location1 location2 >=20 > You making service_template_locations and host_template_locations. On > central host and on locations it's different templates > (active_check_enable 0 and 1 correspondingly) Not necessarily that configuration. Central nagios can act as a fail-over active nagios instance if you configure it correctly. Like, if for some dark force, your distributed nagios instance fails to monitor correctly, the central instance can detect that (freshness_checking), and issue the active check instead of waiting any longer for the passive check to come up. > All checks for locations based on this templates. Also, you don't need to stick with nsca to send results from distributed to central nagios. You can do that with syslog-ng too. At my location, we have hibrid syslog-ng/nsca distributing passive check results to both instances of central nagios, that act redundantly. Fail over is coming soon :) HTH, Marcel AVISO: A informa=E7=E3o contida neste e-mail, bem como em qualquer de = seus anexos, =E9 CONFIDENCIAL e destinada ao uso exclusivo do(s) = destinat=E1rio(s) acima referido(s), podendo conter informa=E7=F5es = sigilosas e/ou legalmente protegidas. Caso voc=EA n=E3o seja o = destinat=E1rio desta mensagem, informamos que qualquer divulga=E7=E3o, = distribui=E7=E3o ou c=F3pia deste e-mail e/ou de qualquer de seus anexos = =E9 absolutamente proibida. Solicitamos que o remetente seja comunicado = imediatamente, respondendo esta mensagem, e que o original desta = mensagem e de seus anexos, bem como toda e qualquer c=F3pia e/ou = impress=E3o realizada a partir destes, sejam permanentemente apagados = e/ou destru=EDdos. Informa=E7=F5es adicionais sobre nossa empresa podem = ser obtidas no site http://sobre.uol.com.br/. NOTICE: The information contained in this e-mail and any attachments = thereto is CONFIDENTIAL and is intended only for use by the recipient = named herein and may contain legally privileged and/or secret = information. If you are not the e-mail=B4s intended recipient, you are = hereby notified that any dissemination, distribution or copy of this = e-mail, and/or any attachments thereto, is strictly prohibited. Please = immediately notify the sender replying to the above mentioned e-mail = address, and permanently delete and/or destroy the original and any copy = of this e-mail and/or its attachments, as well as any printout thereof. = Additional information about our company may be obtained through the = site http://www.uol.com.br/ir/. |
From: Gerheim <wal...@gm...> - 2011-03-30 13:01:19
|
Hello folks, I'm new on Nagios and nagios-users mailing list. I was looking for addons for Nagios but i didn't find one wich attends me. Let me explain my scenario. If someone could help me, i ll be grateful. I have one nagios central with centreon. I have another nagios (worker), with centreon, wich i want to configure some hots and hostgroups that i don't want to configure on nagios central. But i want to monitor workers host and hotsgroups with nagios central. Summarizing, when i manipulate hosts on workers i don't want to put in nagios central. I've found NCSA, DNX and Gearman but it don't help. Could anyone? Thanks! *Wallace Knopp de Menezes Gerheim* |
From: Assaf F. <na...@fl...> - 2011-03-30 13:08:07
|
Gerheim wrote: > Hello folks, > > I'm new on Nagios and nagios-users mailing list. > I was looking for addons for Nagios but i didn't find one wich attends me. > Let me explain my scenario. If someone could help me, i ll be grateful. > > I have one nagios central with centreon. I have another nagios > (worker), with centreon, wich i want to configure some hots and > hostgroups that i don't want to configure on nagios central. But i > want to monitor workers host and hotsgroups with nagios central. > > Summarizing, when i manipulate hosts on workers i don't want to put in > nagios central. > I've found NCSA, DNX and Gearman but it don't help. > > Could anyone? > Thanks! > > /Wallace Knopp de Menezes Gerheim/ Hello and Welcome. For distributed nagios you want to start here http://nagios.sourceforge.net/docs/3_0/distributed.html The main point that you will need to know is that in order for the central nagios to see the hosts monitored by the worker , the definition of the remote monitored hosts need to also be on the central nagios ( defined as passive checks and hosts) . Nagios currently has no way of "detecting "the "child" hosts of the worker and adding them to it's configuration , there for they have to be defined on both servers ( with minor changes : active/passive) . Assaf |
From: Steve W. <ste...@sw...> - 2011-03-30 15:02:53
|
On 30/03/11 14:00, Gerheim wrote: > Hello folks, > > I'm new on Nagios and nagios-users mailing list. > I was looking for addons for Nagios but i didn't find one wich attends me. > Let me explain my scenario. If someone could help me, i ll be grateful. > > I have one nagios central with centreon. I have another nagios > (worker), with centreon, wich i want to configure some hots and > hostgroups that i don't want to configure on nagios central. But i > want to monitor workers host and hotsgroups with nagios central. > > Summarizing, when i manipulate hosts on workers i don't want to put in > nagios central. > I've found NCSA, DNX and Gearman but it don't help. > > Could anyone? > Thanks! > At $dayjob I discovered the same problem, however we also had another problem in that a lot of the servers we want to monitor are in "walled gardens" and only have http(s) access to the internet. Our solution was to semi-create our own uploader mechanism, we use nsca on the receiver side and use a custom submit_check_results that instead of piping the results through nsca_send it writes them into a data file for the time/service which gets stored for scheduled upload via cron. This scheduled uploader keeps track of the hosts/localhost.cfg file and if it detects change adds that to be uploaded too. These files are then bzipped and uploaded via curl to a php script on the nagios server that knows how to save them in for use. The nagios server then has a scheduled process that first looks to see if there's a new config file for hosts and moves it into etc/hosts/*.cfg ( separate files per host ) and then reloads nagios, it then takes the contents of the remaining nagios data files and pipes the contents of them through ncsa. Although this scenario is far from perfect and we've only been working on it for 2 weeks on and off it seems to suit our needs. Maybe looking at a config collector plugin, something like the cisco router config one, and modifying it to store the nagios host config could be used to pass the config through nsca, although I'm not sure how you'd process that on the server to update the host config there. / / -- Steve Wilson |
From: Daniel W. <dan...@st...> - 2011-03-30 16:20:50
|
My vote is to look at Multisite and livestatus from check_mk project. Dan From: Gerheim [mailto:wal...@gm...] Sent: Wednesday, March 30, 2011 8:01 AM To: nag...@li... Subject: [Nagios-users] Distributed Monitoring Hello folks, I'm new on Nagios and nagios-users mailing list. I was looking for addons for Nagios but i didn't find one wich attends me. Let me explain my scenario. If someone could help me, i ll be grateful. I have one nagios central with centreon. I have another nagios (worker), with centreon, wich i want to configure some hots and hostgroups that i don't want to configure on nagios central. But i want to monitor workers host and hotsgroups with nagios central. Summarizing, when i manipulate hosts on workers i don't want to put in nagios central. I've found NCSA, DNX and Gearman but it don't help. Could anyone? Thanks! Wallace Knopp de Menezes Gerheim |
From: Romain Le M. <rle...@me...> - 2011-03-30 17:41:00
|
Hi Wallace, On Wed, Mar 30, 2011 at 3:00 PM, Gerheim <wal...@gm...> wrote: > I'm new on Nagios and nagios-users mailing list. > I was looking for addons for Nagios but i didn't find one wich attends me. > Let me explain my scenario. If someone could help me, i ll be grateful. > I have one nagios central with centreon. I have another nagios (worker), > with centreon, wich i want to configure some hots and hostgroups that i > don't want to configure on nagios central. But i want to monitor workers > host and hotsgroups with nagios central. > Summarizing, when i manipulate hosts on workers i don't want to put in > nagios central. > The standard distributed configuration for Centreon is to have a central web server (Centreon & Nagios) and pollers (Nagios). The whole configuration is define on the central server and you associate each host recorded on the correct Nagios engine. Then, with the access control list feature, you can easily choose to display or not hostgroup/host monitoring on the web side for each user connected. Best regards. -- Romain LE MERLUS |
From: Gerheim <wal...@gm...> - 2011-03-30 18:49:30
|
Thanks everyone for reply. I think i wasn't correctly on my explanation ... My nagios central have a lot of objects (included nagios client objects). I want to manipulate only a few on nagios client. I'm looking to decentralize the "scope" of clients. For example: i have 3 clients. Each one are responsable to monitor some hosts. When they do that, they return the results to central. Clients have nagios and centreon too. Thanks Ps.: Sorry if i wasn't clear. I'm learning English. -- Wallace |
From: Gerheim <wal...@gm...> - 2011-04-05 19:29:18
|
Hi Thanks Dan! I'm reading about check_mk with Livestatus and I think it'll help me. -- Wallace Gerheim |