[Nagiosplug-help] ndoutils-1.4b8_1 dose not work and no error in nagios.log

[Witchaphon S.]

Dear Marc Powell,

Thks for you comment. Let's me share more information.


On 5/3/2553 2:30, Marc Powell wrote:
> Hello,
>
> This e-mail is probably better suited on nagios-users than here since it's not about the plugins... More below --
>
> On Mar 3, 2010, at 9:10 PM, Witchaphon S. wrote:
>
>    
>> After installation, I copy alls config files of ndo and configured as
>> the installation manual without any error during installation.
>>      
> Are you sure you followed the installation instructions fully? It looks like the ndomod module is not being loaded by nagios.
>
>    
This is configuration in my nagios.cfg.

event_broker_options=-1
broker_module=/usr/local/bin/ndomod.o 
config_file=/usr/local/etc/nagios/ndomod.cfg

# ls -alh /usr/local/bin | grep ndo
-r-xr-xr-x   1 root  wheel    99K Feb 12 15:13 ndo2db
-r-xr-xr-x   1 root  wheel    99K Feb 12 15:13 ndo2db-3x
-r-xr-xr-x   1 root  wheel    63K Feb 12 15:13 ndomod-3x.o
-r-xr-xr-x   1 root  wheel    63K Feb 12 15:13 ndomod.o

-------------------------------------------------------------
For the configuration of ndo2db.cfg and ndomod.cfg, plz see below :

# less ndo2db.cfg | grep -v "^#" | sed -e '/^$/d'
lock_file=/var/spool/nagios/ndo2db.lock
ndo2db_user=nagios
ndo2db_group=nagios
socket_type=unix
socket_name=/var/spool/nagios/rw/ndo.sock
db_servertype=mysql
db_host=localhost
db_port=3306
db_name=nagios
db_prefix=nagios_
db_user=XXXXXX
db_pass=XXXXXX
max_timedevents_age=1440
max_systemcommands_age=10080
max_servicechecks_age=10080
max_hostchecks_age=10080
max_eventhandlers_age=44640
debug_level=-1
debug_verbosity=1
debug_file=/var/spool/nagios/ndo2db.debug
max_debug_file_size=1000000

# less ndomod.cfg | grep -v "^#" | sed -e '/^$/d'

instance_name=default
output_type=unixsocket
output=/var/spool/nagios/rw/ndo.sock
output_buffer_items=5000
buffer_file=/var/spool/nagios/ndomod.tmp
file_rotation_interval=14400
file_rotation_timeout=60
reconnect_interval=15
reconnect_warning_interval=15
data_processing_options=-1
config_output_options=2
---------------------------------------------------------------

Any more configuration else??
>> Below is an example of nagios.log after start ndo2db and Nagios.
>>
>> [1267612308] Caught SIGTERM, shutting down...
>> [1267612308] Successfully shutdown... (PID=3805)
>> [1267612308] Nagios 3.2.0 starting... (PID=4108)
>> [1267612308] Local time is Wed Mar 03 17:31:48 ICT 2010
>> [1267612308] LOG VERSION: 2.0
>> [1267612308] Finished daemonizing... (New PID=4109)
>>      
> This is what a normal startup should look like --
>
> [1267730749] Nagios 3.1.2 starting... (PID=26539)
> [1267730749] Local time is Thu Mar 04 13:25:49 CST 2010
> [1267730749] LOG VERSION: 2.0
> [1267730749] ndomod: NDOMOD 1.4b9 (10-27-2009) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
> [1267730749] ndomod: Successfully connected to data sink.  0 queued items to flush.
> [1267730749] Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
> [1267730750] Finished daemonizing... (New PID=26542)
>
>    
Yesss, it should be like that. But I don't know why mine doesn't work.
Are there any compatible OS or any requirement to complete this 
installation?



Thks

Un ^^
>> Any idea or comment about this issue?
>>      
> My guess is that you haven't changed nagios.cfg to specify the broker_module and to set the event_broker_options.
>
> --
> Marc
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
>