Nagios ndomod_REMOTE not working

[Ǫrvar]

Hi

Nagios stopped to working on multiple instances (not all) using ndomod_REMOTE on distribuited nagios monitoring system.
This is configured to connect to mysql database shared for all instances (output_type=tcpsocket).
Now using ndomod_LOCAL nagios working and it is configured with "output_type=unixsocket" .

When i try to start nagios with mysl connection config (ndomod_REMOTE), the node starts but it remains with "starting".
In some case i see back online from browser but the scheduled checks will not start and notifications won't send them.
If i don't see back online the page remains on loading but i think this is related to livestatus
I know for sure that the connection through remote server DB is working well and there is no issue on mysql user credentials.

Via logs i see no errors and if i try to set up hard logging i don't see difference.

--------------------------
ndomod: NDOMOD 1.4b9 (10-27-2009) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
ndomod: Successfully connected to data sink. 0 queued items to flush.
-------------------------

have you any idea?

Thank you for your help

[tgriep]

Can you post your ndomod and ndo2db config files so we can review them?
Have you tried to disable livestatus from running and see if the nagios process starts?
Do you see any errors in any of the log files in /var/log ?

[Ǫrvar]

Hi thanks for your reply,

I don't see any errors in the logs, also doing different test.
What do you mean with stopping livestatus? I didn't do that but i ask you why do you suppose that livestatus can be the problem or something related on that ?

Here the configurations (standard) :

# NDOMOD CONFIG FILE
instance_name=xxxxxxx
output_type=tcpsocket
output=ipaddress
tcp_port=5668
output_buffer_items=5000
buffer_file=/var/cache/ndoutils/ndomod.buffer
file_rotation_interval=14400
file_rotation_timeout=60
reconnect_interval=15
reconnect_warning_interval=15
#reconnect_warning_interval=900
data_processing_options=-1
config_output_options=2

# NDO2DB DAEMON CONFIG FILE

ndo2db_user=usernagios
ndo2db_group=groupnagios
socket_type=unix
#socket_type=tcp
socket_name=/var/run/ndoutils/ndoutils.sock
tcp_port=5668
db_servertype=mysql
db_host=ipaddressremoteserver
db_port=3306
db_name=nagios
db_prefix=nagios_
db_user=nagios_dbsuer
db_pass=xxxxxxxxxxxxxx
max_timedevents_age=1440
max_systemcommands_age=10080
max_servicechecks_age=10080
max_hostchecks_age=10080
max_eventhandlers_age=44640
debug_level=2
debug_verbosity=2
debug_file=/var/log/nagios/ndo2db.debug
max_debug_file_size=1000000

Thankssss

[tgriep]

Disabling livestatus is first step you can try to see if that is causing the issue.
If you edit your nagios.cfg file and comment out the livestatus broker line, see if that helps on this issue.

Are all of the failing systems using the same mysql server and are they configured to use different databases?

Are there any errors in the /var/log/nagios/ndo2db.debug file?

Can you run the following on the server and post the output?

Code: Select all

ps -ef