http://blog.gmane.org/gmane.network.nagios.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.network.nagios.devel/8339 <pre>Hi All, Could anyone point me towards / recommend perl module working with status.dat (if it exists), please? Trying to be current ...v 3.4.x ... Many Thanks, - John ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ </pre> John 2012-05-24T23:34:23 http://comments.gmane.org/gmane.network.nagios.devel/8336 <pre>Version 1.5.1 of the NDOUtils add-on has now been released. You can download NDOUtils from: https://sourceforge.net/projects/nagios/files/ Changelog follows... * Fixed off-by-one error packing data in ndomod. Eric </pre> Eric Stanley 2012-05-17T11:20:55 http://comments.gmane.org/gmane.network.nagios.devel/8335 <pre>Everyone, I played with the "-c" and "-s" Parameters of a 3.2.3's nagiostats today and noticed the odd behavior shown below. I didn't look at the source yet, much less write a patch, but I thought you might want to check on 3.3.x and 3.4.x beforehand (and maybe extend t/705nagiostats.t a bit). Kind regards, J. Bern Normal operation: # N="/usr/local/nagios" # $N/bin/nagiostats -m -d NUMSVCOK 1659 status.dat has been moved elsewhere (onto a ramdisk): # strings - $N/bin/nagiostats | grep /nagios/ /usr/local/nagios/etc/nagios.cfg /usr/local/nagios/var/status.dat # grep /status.dat $N/etc/nagios.cfg status_file=/usr/local/nagios/var/spool/status.dat # strace $N/bin/nagiostats -m -d NUMSVCOK 2&gt;&amp;1 | \ open("/usr/local/nagios/etc/nagios.cfg", O_RDONLY) = 3 open("/usr/local/nagios/var/spool/status.dat", O_RDONLY) = 3 Specifying nagios.cfg explicitly works: # $N/bin/nagiostats -c $N/etc/nagios.cfg -m -d NUMSVCOK 1659 Specifying status.dat explicitly - no go: # $N/bin/nagiostats -s $N/var/spool/status.dat -m -d NUMSVCOK 0 # $N/bin/nagiostats -s$N/var/spool/status.dat -m -d NUMSVCOK 0 # $N/bin/nagiostats --statsfile $N/var/spool/status.dat -m -d NUMSVCOK 0 # $N/bin/nagiostats --statsfile=$N/var/spool/status.dat -m -d NUMSVCOK 0 (Doesn't work together with -c, either.) It *does* read the status.dat, though: # strace $N/bin/nagiostats -s $N/var/spool/status.dat -m -d NUMSVCOK \ open("/etc/ld.so.cache", O_RDONLY) = 3 open("/lib/libm.so.6", O_RDONLY) = 3 open("/lib/libc.so.6", O_RDONLY) = 3 open("/usr/local/nagios/var/spool/status.dat", O_RDONLY) = 3 (... but where'd nagios.cfg go ... ?) </pre> Jochen Bern 2012-05-11T19:34:39 http://comments.gmane.org/gmane.network.nagios.devel/8334 <pre>Hi list, i'm having an odd problem with the development machine I installed Nagios Core 3.4.0 to. It took me some time to make sure what the problem acutally is, but there must have some change in the performance data handling. For my setup: It's two machines running CentOS 5.8 x64, the production-machine is Nagios Core 3.3.1 and the development machine is Nagios Core 3.4.0, both have the same versions of other packages both have PNP-0.6.17 and both have nagios-plugins-1.4.15 - and both have the exact same config (except the dev-machine doesn't send email to everyone). So far about the basics. I'm having the problem with the check_snmp and check_nt scripts, if there is a label (on check_snmp) or a counter (on check_nt) with blanks and it's therefor in apostrophes. So that means, that Nagios is still checking the state of the checks, but there is no performance data handled by PNP, as the input is invalid. Let me explain that with an example: This checks the environment temperature sensor of APC UPS. ______ command_line$USER1$/check_snmp -H $HOSTADDRESS$ -C $ARG1$ -o .1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1 -w 29 -c 40 -l 'environment Temperature' -u °C ______ as you can see the label "-l 'environment Temperature'" is set in apostrophes. If that check is run by Nagios 3.3.1 it looks like follows in Service State Information window: _____ Status Information:SNMP OK - environment Temperature 24 °C Performance Data:environment Temperature=24 _____ If that exact same check is run by Nagios 3.4.0 it looks like: _____ Status Information:SNMP OK - 24 °C Performance Data:=24 _____ So Nagios is still recognizing the value and handling the notifications and escalations as it should, but "=24" is sent to PNP as performance data, what clearly is invalid. In production system (Nagios Core 3.3.1 - PNP-0.6.17) perfdata.log tells: _____ Found Performance Data for APC_5000XL / Environment-Temperature (environment Temperature=24) _____ and is put into the graph just fine. In development system (Nagios Core 3.4.0 - same PNP-version!) it is: _____ Found Performance Data for APC_5000XL / Environment-Temperature (=24) Invalid Perfdata detected _____ So Nagios 3.4.0 is doing something to the performance data. The only possibility to change that behavior back to normal is to change the check-command to anything valid without apostrophes, like: ______ command_line$USER1$/check_snmp -H $HOSTADDRESS$ -C $ARG1$ -o .1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1 -w 29 -c 40 -l Temperature -u °C ______ but that's not what I'd call "solution". I downgraded the development system to 3.3.1 and instantly that checks were reported correctly and graphs are drawn. Back to 3.4.0 that stops immediately. Does anyone else have registered such behaviour or can this be confirmed as a bug? Maybe I'm having blinders for changes that were clearly communicated... or am missing some major point, so please tell me. I would appreciate any help or confirmation that this is a bug and will be fixed in further releases. If you have any further queries, please do not hesitate to contact me. cheers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ </pre> shells< at >wannabepunk.de 2012-05-10T14:23:09 http://comments.gmane.org/gmane.network.nagios.devel/8330 <pre>Hi everybody, I use Nagios, release 3.2.3, in a distributed environment, with a central server and several colector servers. For a long time I´m seeing errors on the passive check mechanism on the central server, as we can see below. Sometimes, on the central server, the states and number of attempts don´t follow the correct order, going from SOFT2 to HARD4, for example. However, on the colector server everything is OK. Log from Central Server: Host Up[2012-05-05 01:06:48] HOST ALERT: node;UP;HARD;1;TCP OK - 0.005 second response time on port 135 Host Down[2012-05-05 01:05:40] HOST ALERT: node;DOWN;HARD;4;CRITICAL - Socket timeout after 10 seconds Host Down[2012-05-05 01:04:16] HOST ALERT: node;DOWN;SOFT;2;CRITICAL - Socket timeout after 10 seconds Host Down[2012-05-05 01:02:55] HOST ALERT: node;DOWN;SOFT;1;CRITICAL - Socket timeout after 10 seconds Log from Colector Server: Host Up[05-05-2012 01:06:31] HOST ALERT: node;UP;SOFT;4;TCP OK - 0.005 second response time on port 135 Host Down[05-05-2012 01:05:21] HOST ALERT: node;DOWN;SOFT;3;CRITICAL - Socket timeout after 10 seconds Host Down[05-05-2012 01:04:01] HOST ALERT: node;DOWN;SOFT;2;CRITICAL - Socket timeout after 10 seconds Host Down[05-05-2012 01:02:41] HOST ALERT: nodeDOWN;SOFT;1;CRITICAL - Socket timeout after 10 seconds Has anybody seen this kind of problem? Can someone help me? Thanks. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ Nagios-devel mailing list Nagios-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-devel </pre> Rodney Ramos 2012-05-08T15:07:05 http://comments.gmane.org/gmane.network.nagios.devel/8319 <pre>Hi, I'm running nagios 3.3.1 on sles 10. I've defined a contact which uses a customized macro called _EMAILCONTACTID However, when I try to reference this macro, from a script defined to run as part of a service check, as an environment variable $NAGIOS__CONTACTEMAILCONTACTID, is blank If I define a customized macro in the service definition, I can see the contents of $NAGIOS_SERVICEEMAILCONTACTID. I've followed the docs and it does state that you can define a customized macro in a contact definition, so this to me looks like a bug in 3.3.1 When will a fix be available ? Regards, Deborah This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please delete this e-mail immediately. Any unauthorised distribution or copying is strictly prohibited. Whilst Kognitio endeavours to prevent the transmission of viruses via e-mail, we cannot guarantee that any e-mail or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions. Kognitio grants no warranties regarding performance, use or quality of any e-mail or attachment and undertakes no liability for loss or damage, howsoever caused. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ Nagios-devel mailing list Nagios-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-devel </pre> Deborah Martin 2012-05-03T10:42:53 http://comments.gmane.org/gmane.network.nagios.devel/8313 <pre>Hi All I don't know the technical reason why Nagios developers didn't thought about this: I know its not a standard syntax for Username to be as part of DISABLING/ENABLING checks/notifications but it would be nice if your team can start thinking about add it as feature in next releases of Nagios. Its really giving us HARD time to know who trigger the DISABLE and ENABLE checks/notifications among the teams. This should apply to BOTH: HOST/SERVICE type of DISABLE/ENABLE external commands. DISABLE_ALL_NOTIFICATIONS_BEYOND_HOST DISABLE_CONTACTGROUP_SVC_NOTIFICATIONS DISABLE_CONTACT_SVC_NOTIFICATIONS DISABLE_HOSTGROUP_PASSIVE_SVC_CHECKS DISABLE_HOSTGROUP_SVC_CHECKS DISABLE_HOSTGROUP_SVC_NOTIFICATIONS DISABLE_HOST_SVC_CHECKS DISABLE_HOST_SVC_NOTIFICATIONS DISABLE_PASSIVE_SVC_CHECKS DISABLE_SERVICEGROUP_PASSIVE_SVC_CHECKS DISABLE_SERVICEGROUP_SVC_CHECKS DISABLE_SERVICEGROUP_SVC_NOTIFICATIONS DISABLE_SERVICE_FLAP_DETECTION DISABLE_SERVICE_FRESHNESS_CHECKS DISABLE_SVC_CHECK DISABLE_SVC_EVENT_HANDLER DISABLE_SVC_FLAP_DETECTION DISABLE_SVC_NOTIFICATIONS ENABLE_ALL_NOTIFICATIONS_BEYOND_HOST ENABLE_CONTACTGROUP_SVC_NOTIFICATIONS ENABLE_CONTACT_SVC_NOTIFICATIONS ENABLE_HOSTGROUP_PASSIVE_SVC_CHECKS ENABLE_HOSTGROUP_SVC_CHECKS ENABLE_HOSTGROUP_SVC_NOTIFICATIONS ENABLE_HOST_SVC_CHECKS ENABLE_HOST_SVC_NOTIFICATIONS ENABLE_PASSIVE_SVC_CHECKS ENABLE_SERVICEGROUP_PASSIVE_SVC_CHECKS ENABLE_SERVICEGROUP_SVC_CHECKS ENABLE_SERVICEGROUP_SVC_NOTIFICATIONS ENABLE_SERVICE_FRESHNESS_CHECKS ENABLE_SVC_CHECK ENABLE_SVC_EVENT_HANDLER ENABLE_SVC_FLAP_DETECTION ENABLE_SVC_NOTIFICATIONS With Regards Deepak Kosaraju www.kkdk.us ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev_______________________________________________ Nagios-devel mailing list Nagios-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-devel </pre> Deepak Kosaraju 2012-04-05T02:44:17 http://comments.gmane.org/gmane.network.nagios.devel/8312 <pre>Hi, We have been investigating an issue with nrpe with regard to reuse of port numbers and client hickups (check_nrpe). It seems that the closing of the network sockets has a race condition which can confuse firewalls, NAT-gateways etc. I have seen reports about this issue in several forms: - http://permalink.gmane.org/gmane.network.nagios.devel/3037 1) - http://tracker.nagios.org/view.php?id=305 - http://sourceforge.net/mailarchive/message.php?msg_id=29054957 With my IPv6 patch the bug exposes itself more often if used in combination with -b (bind) on the client. I had to consult Stevens' Unix network programming seriously to find this one. It appears that if a client is connected with a server that the most optimal way of closing the connection is that the client takes the initiative to close() as most modern network protocols do. The server also has en open socket so it has to close() is at some time too. The one who closes first sends a FIN to the other side ultimately resulting in its socket to become in TIME_WAIT state for a few minutes. The nrpe server did a close() too at the end of its logic resulting in a race of FIN packets being sent from both client and server resulting in sometimes TIME_WAIT on the client and sometimes on the server side depending on who won the race. When making the next connection the connection table is consulted to choose a new source port, thereby skipping all TIME_WAIT states. Using IPV6 in combination with bind() on the client the closing of a connection seems to take slightly longer, I don't know why. Making the server win the race more often resulting in more TIME_WAIT states on the server. The client doesn't see these entries in its connection table increasing the chance to reuse a source port which is still in TIME_WAIT on the server. The server will refuse by sending a RST. Strangely the connection table changes to SYN_RCVD and as soon as the SYN tables overflows it starts reporting synflooding. Long story short: semantically the server should wait with a read() on a end-of-file (0 bytes read) and then close() its side of the connection. The end-of-file is caused by the FIN of the client (the so called active close) The close() of the server will then be a passive close so only one FIN will be sent, resulting in only LISTEN on the server and all TIME_WAIT's on the client. The patch introduces a read with timeout of 10 seconds just in case you have to deal with high latency. In practice however the server receives the FIN instanly so this timeout is just in case the FIN gets lost. I have taken the liberty to also remove some logic to force sending FIN introduced in 2006 in 1). The patch also introduces -Wall n the Makefile to find and fix several compiletime errors. </pre> Leo Baltus 2012-04-02T09:10:58 http://comments.gmane.org/gmane.network.nagios.devel/8311 <pre>Hi, Attached patch fixes a small memory leak introduced by my IPv6 patch I sent earlier, see below. As I haven't got any reponse on my first post so I'll just resubmit the complete patch. Op 02/05/2011 om 17:32:55 +0200, schreef Leo Baltus: </pre> Leo Baltus 2012-04-02T09:10:09 http://comments.gmane.org/gmane.network.nagios.devel/8301 <pre>Hello, I came across the same TCP RST issue as reported in http://tracker.nagios.org/view.php?id=305. I've attached a patch for nrpe.c, and also check_nrpe.c as pointed out by dnsmichi. The problem is that when we call SSL_shutdown() only once, the server sends an SSL shutdown message to the client. The client then responds with it's own SSL shutdown message, and this ends up in the server's socket receive buffer. However, since we never consume this message, the kernel will send a RST to the client when the server process exits. This pollutes our firewall logs and makes it harder to detect more serious TCP errors in our monitoring. The solution is to call SSL_shutdown() at least twice, and up to 4 times to be safe (usually SSL_shutdown() will return 1 after two calls). There's a good explanation of this behaviour in the links I provided within the bug report. I won't take up too much space explaining it here. Please apply the attached patch. Thanks! Jari ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure_______________________________________________ Nagios-devel mailing list Nagios-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-devel </pre> Jari Takkala 2012-03-29T08:52:46 http://comments.gmane.org/gmane.network.nagios.devel/8294 <pre>I'd like to set up Nagios contact_groups in the following way (but it's not working as expected): 1) In general, contact_groups for a host are notified about problems with the host and any service on the host. 2) Occasionally, we'd like other contact_groups to be notified about problems with certain services on the host. If I'm understanding the documentation at http://nagios.sourceforge.net/docs/nagioscore/3/en/objectinheritance.html correctly (I'm running (3.3.1), it indicates that #1 can be done using implied inheritance and #2 by using additive inheritance, but it's not working as expected. I've found other posts from people with the same issue, but never any resolution. For example, if I define: define host{ host_name linux-server contact_groups linux-admins ... } define service{ host_name linux-server service_description l_proc_sshd contact_groups +management ... } I would like this to be equivalent to: define service{ host_name linux-server service_description l_proc_sshd contact_groups linux-admins,management ... } But instead, the implied inheritance of "linux-admins" is ignored, and it's equivalent to: define service{ host_name linux-server service_description l_proc_sshd contact_groups management ... } So contact_groups is overwritten rather than added to. No warnings/errors were generated about the plus sign being used inappropriately or anything else. Am I misunderstanding the documentation? Is this possibly a bug? If this is not the way it's intended to work, could Nagios be easily enhanced to support this? It seems very logical and powerful, and apparently other people are thinking along the same lines as I am. I posted this on the nagios-users list where people confirmed that it doesn't work for them, either. They suggested a workaround using escalations, but it seems like that's a more complicated solution and less logical (there are no escalations happening, just regular notifications). Thanks in advance for any light you can shed on this! </pre> Jim Winkle 2012-03-28T16:44:31 http://comments.gmane.org/gmane.network.nagios.devel/8291 <pre>Hi. Someone replied to my post on nagios forum, that devel list would be better for my topic, so I'm repeating my question here. I'm considering to integrate my Nagios server with Nagiosgraph (and possibly migrate with performance graphs from Munin). Unfortunately, some graphs cannot work correctly because of max packet size (e.g. check_disk for some of my servers). There is a working patch, see http://labs.opsview.com/2008/08/enhancing-nrpe-for-large-output/ - it looks nice and works perfect - I've checked patched nrpe_check (2.12) with unpatched/patched nagios-nrpe-server. Is it possible, that some day you include such a patch in nagios upstream? Best regards, R. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure </pre> Ryszard Łach 2012-03-26T09:40:45 http://comments.gmane.org/gmane.network.nagios.devel/8290 <pre>I had a few problems with the latest version 2.9.1 of nsca: 1) The package age in handle_connection_read of the nsca server part is calculated based on uninitialized values. This resulted in nsca dropping packages because it thinks they are too old. See nsca.c.patch which fixes the problem for me. 2) I had problems compiling it for solaris10. Sol10 misses asprintf. See solaris10.patch. The patch adds code for the missing asprintf, and makes also changes to configure.in and Makefile.in to compile the asprintf part depending on which operating system you compile it for. (I've compiled it for solaris successfully using a cross compiler: sparc-sun-solaris2.10-gcc (GCC) 4.6.1) NOTE: after applying this patch you have to run autoconf Regards, Matthias ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d_______________________________________________ Nagios-devel mailing list Nagios-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-devel </pre> Matthias Schlachter 2012-03-06T04:27:09 http://comments.gmane.org/gmane.network.nagios.devel/8289 <pre>just figured that current svn/git head does not compile within t-tap/, attached git patch resolves that. test_checks segfaults for various reasons i've not yet debugged. </pre> Michael Friedrich 2012-02-13T17:31:03 http://comments.gmane.org/gmane.network.nagios.devel/8288 <pre>Version 1.5 of the NDOUtils add-on has now been released. You can download NDOUtils from: https://sourceforge.net/projects/nagios/files/ Changelog follows... * Added various performance improvements originally added for Nagios XI (Ethan Galstad) * Added asynchronous data spooling to increase performance (andree) * Fixed to small es array (Michael Friedrich) * Fixed wrong type of object_id in ndo2db_save_custom_variables() (Michael Friedrich) Eric </pre> Eric Stanley 2012-02-03T18:49:16 http://comments.gmane.org/gmane.network.nagios.devel/8286 <pre>Version 2.9.1 of the NSCA add-on has now been released. You can download NSCA from: https://sourceforge.net/projects/nagios/files/ Changelog follows... - Applied patch to allow packets arriving with a future time stamp (Daniel Wittenberg) - Updated server (nsca) to allow packets with older, smaller packet size (Eric Stanley) Eric </pre> Eric Stanley 2012-01-27T13:59:11 http://comments.gmane.org/gmane.network.nagios.devel/8273 <pre>Hi everyone, I'd like to have a community discussion on a possible new feature for Nagios. To start of, I have written a number of plugins that reuse data from their previous run, for optimization reasons (one time find correct SNMP OID to pull data based on regex and just pull from that OID after) and to calculate percent of change from counters values. The standard way plugins deal with this is by creating temporary files or using database. I'm not big fan of those approaches - large number of such files is a maintenance issue and its a a performance disadvantage to write/read those files, database is an external service and you want to avoid relying on that and opening/closing connection for every plugin run. Instead the plugins I write cache this data using nagios itself. My plugins that do that are check_snmp_netint.pl, check_sasraid_megaraid.pl and at least 2 others you can find at http://william.leibzon.org/nagios/. Right now all these plugins output these "cache" data as part of part of Nagios performance data which is then fed back to plugin at each run. This all works ok except for some graphing programs (pnp4nagios) that parse performance data and get confused about non-numeric values my plugins may output, but I have patches for these issues too. The thing is it all seems like hack. At the same time its a good feature to be able to use nagios itself to store small amount of data for use by plugins. So I have a proposal on how to move forward with this. I propose that we have a way for plugins to return data back to nagios that would be stored as Nagios MACRO variables. The idea is basically to add another line of data that nagios plugins would output in addition to status line and performance data. Something like: eth0:UP (0.0Mbps/0.0Mbps/0.0/0.0/0.0/0.0):(1 UP): OK | 'eth0_in_prct'=0%;50;100;0;100 'eth0_out_prct'=0%;50;100;0;100 'eth0_in_octet'=402666722c 'eth0_out_octet'=1053106629c 'eth0_in_error'=0c 'eth0_in_discard'=0c 'eth0_out_error'=0c 'eth0_out_discard'=0c || cache_descr_ids=2 cache_descr_names=eth0 cache_descr_time=1326310364 eth0_in_octet.1=400843541 eth0_out_octet.1=1052938634 eth0_in_error.1=0 eth0_out_error.1=0 eth0_in_discard.1=0 eth0_out_discard.1=0 time.1=1326340964 I above I separated new type of data with ||. It can be something else or just one |. I'm quite open to suggestions on how to best do this. In any case the idea here is that Nagios would not just put everything after || into some new variable like EXTRASERVICEDATA but would parse the line looking for name=data pairs. These would be interpreted as new values for MACRO variables previously defined in Nagios config. In order to have proper security any variable that can be modified in this way would have to be specifically listed as such so I propose to add a new "immutable_macros" config line. Here is an example of what I have in mind: define service { ... immutable_macros cache_descr_ids, cache_descr_names, cache_descr_time, eth0_in_octet.p1, eth0_out_octet.1, eth0_in_error.1, eth0_out_discard.1, eth0_in_discard.1, time.1 _cache_descr_ids = '' _cache_descr_names = '' _cache_descr_time = 0 ... } Both host and service macros would be allowed to be immutable (but it would have to be specified only in service definition, for security) which would allow a new features where one plugin can pass data to another plugin by means of a macro that both share from a host. This may get quite useful i.e. you may already be retrieving OS version/string from a box with one plugin (maybe by remote with SNMP and not just 'uname') which would be used by several plugins to determine what data is retrieved and how. There are really lots of opportunities for improvement in this area. Functions can also be added to libraries (i.e. Nagios::Plugin which I personally don't use) to make it easy to store data as nagios macros variables and retrieve it back when plugin runs. These are kind-of like web session variables really. I'm proficient with Nagios core code and willing to write this all myself and submit it as a patch to Nagios. But this is a serious enough feature enhancement that it requires community discussion. Specifically big here is a proposal to add 3rd type of data output for plugins since for very long time plugins have been expected to return "status data | perf data". I'm sure any plugin that supports this new feature would have to have an option to enable it so it does not screw up its use on older systems. Performance parsing addons would probably not be affected because they would just get output before || - and I'm sure will make them very happy to see only real data in perfparse line. Let me know what you think about this idea and if you see any serious issues. And sorry for long post. William ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 </pre> William Leibzon 2012-01-12T04:49:36 http://comments.gmane.org/gmane.network.nagios.devel/8267 <pre> I wanted to use Mike Lindsey's new features in nsca-2.9 but found that clients on 2.7.2 were not able to communicate after updating the server. I found this on the Nagios bug tracker: http://tracker.nagios.org/view.php?id=78 Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________ Nagios-devel mailing list Nagios-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-devel </pre> Andrew Widdersheim 2012-01-11T19:16:51 http://comments.gmane.org/gmane.network.nagios.devel/8250 <pre>We're using an external script to handle connection caching for NSCA.. Once we have X seconds of OCSP and OCHP results queued in the local cache, we fire off a batch submission through send_nsca. One TCP connection, one encryption handshake. Under extreme load, we've been having some issues and I'm thinking about re-engineering it. Only, I think if I do much work, I'd like to add the cache logic to the send_nsca binary itself. Changes would involve adding a cache directory and cache age (and/or max cache items) config directives. Without the new directives, program flow would be as normal. With those directives, any submitted OC*P events submitted to send_nsca would get dumped into the cache directory until the oldest file exceeds the max cache age, or the number of items exceeds the max. Once either of those are reached the next send_nsca call would submit all results at once. A lockfile mechanism of some sort would be in place to prevent any subsequent send_nsca runs that get kicked off, before the submitting run has finished, from doing duplicate submissions. Any concerns, requests, or gentle guidance towards alternate solutions? </pre> Mike Lindsey 2012-01-03T23:23:10 http://comments.gmane.org/gmane.network.nagios.devel/8250 <pre>We're using an external script to handle connection caching for NSCA.. Once we have X seconds of OCSP and OCHP results queued in the local cache, we fire off a batch submission through send_nsca. One TCP connection, one encryption handshake. Under extreme load, we've been having some issues and I'm thinking about re-engineering it. Only, I think if I do much work, I'd like to add the cache logic to the send_nsca binary itself. Changes would involve adding a cache directory and cache age (and/or max cache items) config directives. Without the new directives, program flow would be as normal. With those directives, any submitted OC*P events submitted to send_nsca would get dumped into the cache directory until the oldest file exceeds the max cache age, or the number of items exceeds the max. Once either of those are reached the next send_nsca call would submit all results at once. A lockfile mechanism of some sort would be in place to prevent any subsequent send_nsca runs that get kicked off, before the submitting run has finished, from doing duplicate submissions. Any concerns, requests, or gentle guidance towards alternate solutions? </pre> Mike Lindsey 2012-01-03T23:23:10 http://comments.gmane.org/gmane.network.nagios.devel/8249 <pre> Je serai absent(e) à partir du 23/12/2011 de retour le 02/01/2012. Merci de contacter Jean-Michel Daguet (04 93 95 55 84) pour toutes demandes urgentes.------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________ Nagios-devel mailing list Nagios-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-devel </pre> Pierre SMOROWINSKI 2011-12-30T03:01:24 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.network.nagios.devel