<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-GB link=blue vlink=blue> <div class=Section1> I’ve double-checked all my config files and all the important settings match yours.<o:p></o:p> <o:p> </o:p> I wonder if this is a problem when doing a fresh install on Nagios 3.0 rather than upgrading from previous versions?<o:p></o:p> <o:p> </o:p> Joe<o:p></o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: yannig.perre@externe.bnpparibas.com [mailto:yannig.perre@externe.bnpparibas.com] Sent: 04 April 2008 09:30 To: webknowledge@gmail.com; Joe Precious Cc: Nagios-users@lists.sourceforge.net Subject: RE : [Nagios-users] NDOUtils Problem<o:p></o:p> </div> </div> <o:p> </o:p> I’m using nagios 3.0 (from b6 through 3.0) and ndoutils 1.4.b7 since a few months against a Solaris 8 without problem. I’m monitoring around 50 servers and 700 services.<o:p></o:p> <o:p></o:p> Here’s my configuration:<o:p></o:p> <o:p></o:p> root@xxx # cat ndomod.cfg<o:p></o:p> instance_name=default<o:p></o:p> output_type=unixsocket<o:p></o:p> <o:p></o:p> output=/path/to/nagios/var/ndo.sock<o:p></o:p> tcp_port=5668<o:p></o:p> # increase this to a higher value if you want to be able to stop ndo2db a long time<o:p></o:p> output_buffer_items=50000<o:p></o:p> buffer_file=/path/to/nagios /var/ndomod.tmp<o:p></o:p> file_rotation_interval=14400<o:p></o:p> file_rotation_timeout=60<o:p></o:p> reconnect_interval=15<o:p></o:p> reconnect_warning_interval=15<o:p></o:p> data_processing_options=-1<o:p></o:p> config_output_options=0<o:p></o:p> <o:p></o:p> root@xxx # cat ndo2db.cfg<o:p></o:p> # set the name of the user launching ndo2db module broker<o:p></o:p> ndo2db_user=nagios<o:p></o:p> ndo2db_group=nagios<o:p></o:p> socket_type=unix<o:p></o:p> socket_name=/path/to/nagios/var/ndo.sock<o:p></o:p> tcp_port=5668<o:p></o:p> # config of the mysql backend<o:p></o:p> db_servertype=mysql<o:p></o:p> db_host=localhost<o:p></o:p> db_port=3306<o:p></o:p> db_name=nagios<o:p></o:p> db_prefix=nagios_<o:p></o:p> db_user=mysql_user<o:p></o:p> db_pass=mysql_passwd<o:p></o:p> # retention of data<o:p></o:p> max_timedevents_age=1440<o:p></o:p> max_systemcommands_age=10080<o:p></o:p> # = 100 days<o:p></o:p> max_servicechecks_age=144000<o:p></o:p> max_hostchecks_age=10080<o:p></o:p> max_eventhandlers_age=44640<o:p></o:p> debug_level=1<o:p></o:p> debug_verbosity=0<o:p></o:p> debug_file=/path/to/nagios/var/ndo.debug<o:p></o:p> max_debug_file_size=1000000<o:p></o:p> <o:p></o:p> Finaly, nagios.cfg contains this line:<o:p></o:p> # ndoutils broker<o:p></o:p> broker_module=/path/to/nagios/bin/ndomod.o config_file=/path/to/nagios/etc/ndomod.cfg<o:p></o:p> <o:p></o:p> -----Message d'origine----- De : nagios-users-bounces@lists.sourceforge.net [mailto:nagios-users-bounces@lists.sourceforge.net] De la part de webknowledge@gmail.com Envoy� : jeudi 3 avril 2008 22:47 � : JoeP@protronics.co.uk Cc : Nagios-users@lists.sourceforge.net Objet : Re: [Nagios-users] NDOUtils Problem<o:p></o:p> <o:p></o:p> >From NDOUtils 1.4.b7 Changelog: 1.4b7 - 10/31/2007 ----------------- NOTE: ** Requires Nagios 2.7 or higher, or Nagios 3.0b6 - Makefile fixes for compilation flags - Fix for bug where service check table always had same start/end time - Added sample init script for SLES (Bruno Quintais) - Added --with-ndo2db-user and --with-ndo2db-group configure script options - Fix for configfilevariables table not holding multiple entries for various variables - Changed/added indexes on various DB tables - Added some very basic debug file capabilities (not complete yet) - Fix for handling (backwards) system time changes - Fix for missing SUN_LEN definition and strtof() functions on Solaris 8 (Christian Masopust) - Fix for segfault when importing duplicate log file entries (Hendrik Frenzel) - Updated to support latest Nagios 3.x code (3.0b6) So, I think Nagios3.0.X isn't supported yet. I'm having issues with ndomod for nagios 3-x installs, so I've sticked with nagios 2.11 with 1.4b7 and it works fine. Hold your migration, for a new release of the mod. Cheers,<o:p></o:p> <div> On Thu, Apr 3, 2008 at 5:22 PM, Joe Precious <<a href="mailto:JoeP@protronics.co.uk">JoeP@protronics.co.uk</a>> wrote:<o:p></o:p> <div> <div> Hi<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> I'm having some problems getting NDOUtils running on a new Nagios installation. I have it running fine on a Nagios 3.0rc3 installation on Ubuntu 6.06 server but I need to move to a new server. I've gone to Nagios 3.0 on a Ubuntu 7.10 machine which is all running fine but when I can't get NDOUtils running. I run through the installation several times to make sure I've done everything, double-checked all config files, confirmed the database and access but it won't run. I see the following in the Nagios log:-<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> [04-03-2008 13:32:47] ndomod: Successfully reconnected to data sink! 0 items lost, 78 queued items to flush. [04-03-2008 13:32:31] ndomod: Error writing to data sink! Some output may get lost... [04-03-2008 13:32:31] ndomod: Successfully flushed 289 queued items to data sink. [04-03-2008 13:32:31] ndomod: Successfully reconnected to data sink! 0 items lost, 289 queued items to flush. [04-03-2008 13:32:15] ndomod: Error writing to data sink! Some output may get lost. 194 queued items to flush. [04-03-2008 13:32:15] ndomod: Successfully reconnected to data sink! 0 items lost, 505 queued items to flush. [04-03-2008 13:31:59] ndomod: Error writing to data sink! Some output may get lost. 424 queued items to flush. [04-03-2008 13:31:59] ndomod: Successfully reconnected to data sink! 0 items lost, 588 queued items to flush. [04-03-2008 13:31:43] ndomod: Error writing to data sink! Some output may get lost. 499 queued items to flush. [04-03-2008 13:31:43] ndomod: Successfully reconnected to data sink! 0 items lost, 676 queued items to flush. [04-03-2008 13:31:27] ndomod: Error writing to data sink! Some output may get lost... [04-03-2008 13:31:27] Finished daemonizing... (New PID=14596) [04-03-2008 13:31:27] Event broker module '/usr/local/nagios/bin/ndomod-3x.o' initialized successfully. [04-03-2008 13:31:27] ndomod: Successfully connected to data sink. 0 queued items to flush. [04-03-2008 13:31:27] ndomod: NDOMOD 1.4b7 (10-31-2007) Copyright (c) 2005-2007 Ethan Galstad (<a href="mailto:nagios@nagios.org" target="_blank">nagios@nagios.org</a>) [04-03-2008 13:31:27] LOG VERSION: 2.0 [04-03-2008 13:31:27] Local time is Thu Apr 03 13:31:27 BST 2008 [04-03-2008 13:31:27] Nagios 3.0 starting... (PID=14594)<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> I've found a few threads on the internet with similar errors but not found a resolution. I'm at a loss how to proceed with troubleshooting.<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> Thanks<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> Joe<o:p></o:p> </div> Joe Precious Protronics Tel: 0845 458 3234 support@protronics.co.uk Fax: 0207 407 2441 -------------------------------------------------------------------------- Business Driven IT Microsoft Gold Certified Partner Cisco SMB Select Partner -------------------------------------------------------------------------- Accounts • Networks • Development • Training --------------------------------------------------------------------------<o:p></o:p> <div> <o:p></o:p> </div> </div> ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. <a href="http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace" target="_blank">http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null<o:p></o:p> </div> <o:p></o:p> <pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>This message and any attachments (the "message") is<o:p></o:p></pre><pre style='margin-left:36.0pt'>intended solely for the addressees and is confidential. <o:p></o:p></pre><pre style='margin-left:36.0pt'>If you receive this message in error, please delete it and <o:p></o:p></pre><pre style='margin-left:36.0pt'>immediately notify the sender. Any use not in accord with <o:p></o:p></pre><pre style='margin-left:36.0pt'>its purpose, any dissemination or disclosure, either whole <o:p></o:p></pre><pre style='margin-left:36.0pt'>or partial, is prohibited except formal approval. The internet<o:p></o:p></pre><pre style='margin-left:36.0pt'>can not guarantee the integrity of this message. <o:p></o:p></pre><pre style='margin-left:36.0pt'>BNP PARIBAS (and its subsidiaries) shall (will) not <o:p></o:p></pre><pre style='margin-left:36.0pt'>therefore be liable for the message if modified. <o:p></o:p></pre><pre style='margin-left:36.0pt'>Do not print this message unless it is necessary,<o:p></o:p></pre><pre style='margin-left:36.0pt'>consider the environment.<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>�� ---------------------------------------------<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>Ce message et toutes les pieces jointes (ci-apres le <o:p></o:p></pre><pre style='margin-left:36.0pt'>"message") sont etablis a l'intention exclusive de ses <o:p></o:p></pre><pre style='margin-left:36.0pt'>destinataires et sont confidentiels. Si vous recevez ce <o:p></o:p></pre><pre style='margin-left:36.0pt'>message par erreur, merci de le detruire et d'en avertir <o:p></o:p></pre><pre style='margin-left:36.0pt'>immediatement l'expediteur. Toute utilisation de ce <o:p></o:p></pre><pre style='margin-left:36.0pt'>message non conforme a sa destination, toute diffusion <o:p></o:p></pre><pre style='margin-left:36.0pt'>ou toute publication, totale ou partielle, est interdite, sauf <o:p></o:p></pre><pre style='margin-left:36.0pt'>autorisation expresse. L'internet ne permettant pas <o:p></o:p></pre><pre style='margin-left:36.0pt'>d'assurer l'integrite de ce message, BNP PARIBAS (et ses<o:p></o:p></pre><pre style='margin-left:36.0pt'>filiales) decline(nt) toute responsabilite au titre de ce <o:p></o:p></pre><pre style='margin-left:36.0pt'>message, dans l'hypothese ou il aurait ete modifie.<o:p></o:p></pre><pre style='margin-left:36.0pt'>N'imprimez ce message que si necessaire,<o:p></o:p></pre><pre style='margin-left:36.0pt'>pensez a l'environnement.<o:p></o:p></pre></div> </body> </html>