Monitoring Engine wont start.

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
lzdravkov
Posts: 9
Joined: Mon Jul 06, 2020 2:58 am

Monitoring Engine wont start.

Post by lzdravkov »

Dear All,

Please for you assist it is our production monitoring system Nagios and is not working properly after the last update.
Monitoring engine stopped working. If I tried to start it manualy it runs for a minute or two and its going down again.
I'm able to see the following error in this log file /usr/local/nagios/var/nagios.log:

[1710699950] NDO-3: mysql_ping: Unknown error. Is the database running?
[1710699950] Caught SIGSEGV, shutting down...
[1710699950] Caught SIGTERM, shutting down...

CentOS Linux release 7.7.1908 (Core)
Current version is 2024R1.0.2.

Any suggestions ?
Last edited by lzdravkov on Sun Mar 17, 2024 2:05 pm, edited 1 time in total.
lzdravkov
Posts: 9
Joined: Mon Jul 06, 2020 2:58 am

Re: Monitoring Engine wont start.

Post by lzdravkov »

I run this command and thats the result:

mysqlcheck -f -r -u root -pnagiosxi --all-databases
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
nagios.nagios_acknowledgements OK
nagios.nagios_commands OK
nagios.nagios_commenthistory OK
nagios.nagios_comments OK
nagios.nagios_configfiles OK
nagios.nagios_configfilevariables OK
nagios.nagios_conninfo OK
nagios.nagios_contact_addresses OK
nagios.nagios_contact_notificationcommands OK
nagios.nagios_contactgroup_members OK
nagios.nagios_contactgroups OK
nagios.nagios_contactnotificationmethods OK
nagios.nagios_contactnotifications OK
nagios.nagios_contacts OK
nagios.nagios_contactstatus OK
nagios.nagios_customvariables OK
nagios.nagios_customvariablestatus OK
nagios.nagios_dbversion OK
nagios.nagios_downtimehistory OK
nagios.nagios_eventhandlers OK
nagios.nagios_externalcommands OK
nagios.nagios_flappinghistory OK
nagios.nagios_host_contactgroups OK
nagios.nagios_host_contacts OK
nagios.nagios_host_parenthosts OK
nagios.nagios_hostchecks OK
nagios.nagios_hostdependencies OK
nagios.nagios_hostescalation_contactgroups OK
nagios.nagios_hostescalation_contacts OK
nagios.nagios_hostescalations OK
nagios.nagios_hostgroup_members OK
nagios.nagios_hostgroups OK
nagios.nagios_hosts OK
nagios.nagios_hoststatus OK
nagios.nagios_instances OK
nagios.nagios_logentries OK
nagios.nagios_notifications OK
nagios.nagios_objects OK
nagios.nagios_processevents OK
nagios.nagios_programstatus OK
nagios.nagios_rebalance_affected_instances OK
nagios.nagios_regions OK
nagios.nagios_runtimevariables OK
nagios.nagios_scheduleddowntime OK
nagios.nagios_service_contactgroups OK
nagios.nagios_service_contacts OK
nagios.nagios_service_parentservices OK
nagios.nagios_servicechecks OK
nagios.nagios_servicedependencies OK
nagios.nagios_serviceescalation_contactgroups OK
nagios.nagios_serviceescalation_contacts OK
nagios.nagios_serviceescalations OK
nagios.nagios_servicegroup_members OK
nagios.nagios_servicegroups OK
nagios.nagios_services OK
nagios.nagios_servicestatus OK
nagios.nagios_statehistory OK
nagios.nagios_systemcommands OK
nagios.nagios_timedeventqueue OK
nagios.nagios_timedevents OK
nagios.nagios_timeperiod_exception_timeranges OK
nagios.nagios_timeperiod_exceptions OK
nagios.nagios_timeperiod_exclusions OK
nagios.nagios_timeperiod_timeranges OK
nagios.nagios_timeperiods OK
nagiosql.tbl_command
note : The storage engine for the table doesn't support repair
nagiosql.tbl_contact
note : The storage engine for the table doesn't support repair
nagiosql.tbl_contactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_contacttemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_domain
note : The storage engine for the table doesn't support repair
nagiosql.tbl_host
note : The storage engine for the table doesn't support repair
nagiosql.tbl_hostdependency
note : The storage engine for the table doesn't support repair
nagiosql.tbl_hostescalation
note : The storage engine for the table doesn't support repair
nagiosql.tbl_hostextinfo
note : The storage engine for the table doesn't support repair
nagiosql.tbl_hostgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_hosttemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_info
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContactToCommandHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContactToCommandService
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContactToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContactToContacttemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContactToVariabledefinition
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContactgroupToContact
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContactgroupToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContacttemplateToCommandHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContacttemplateToCommandService
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContacttemplateToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContacttemplateToContacttemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkContacttemplateToVariabledefinition
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostToContact
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostToHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostToHostgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostToHosttemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostToVariabledefinition
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostdependencyToHost_DH
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostdependencyToHost_H
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostdependencyToHostgroup_DH
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostdependencyToHostgroup_H
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostescalationToContact
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostescalationToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostescalationToHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostescalationToHostgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostgroupToHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHostgroupToHostgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHosttemplateToContact
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHosttemplateToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHosttemplateToHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHosttemplateToHostgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHosttemplateToHosttemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkHosttemplateToVariabledefinition
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceToContact
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceToHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceToHostgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceToServicegroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceToServicetemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceToVariabledefinition
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicedependencyToHost_DH
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicedependencyToHost_H
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicedependencyToHostgroup_DH
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicedependencyToHostgroup_H
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicedependencyToService_DS
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicedependencyToService_S
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicedependencyToServicegroup_DS
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicedependencyToServicegroup_S
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceescalationToContact
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceescalationToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceescalationToHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceescalationToHostgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceescalationToService
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServiceescalationToServicegroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicegroupToService
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicegroupToServicegroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicetemplateToContact
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicetemplateToContactgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicetemplateToHost
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicetemplateToHostgroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicetemplateToServicegroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicetemplateToServicetemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkServicetemplateToVariabledefinition
note : The storage engine for the table doesn't support repair
nagiosql.tbl_lnkTimeperiodToTimeperiod
note : The storage engine for the table doesn't support repair
nagiosql.tbl_logbook
note : The storage engine for the table doesn't support repair
nagiosql.tbl_mainmenu
note : The storage engine for the table doesn't support repair
nagiosql.tbl_permission
note : The storage engine for the table doesn't support repair
nagiosql.tbl_permission_inactive
note : The storage engine for the table doesn't support repair
nagiosql.tbl_service
note : The storage engine for the table doesn't support repair
nagiosql.tbl_servicedependency
note : The storage engine for the table doesn't support repair
nagiosql.tbl_serviceescalation
note : The storage engine for the table doesn't support repair
nagiosql.tbl_serviceextinfo
note : The storage engine for the table doesn't support repair
nagiosql.tbl_servicegroup
note : The storage engine for the table doesn't support repair
nagiosql.tbl_servicetemplate
note : The storage engine for the table doesn't support repair
nagiosql.tbl_session
note : The storage engine for the table doesn't support repair
nagiosql.tbl_session_locks
note : The storage engine for the table doesn't support repair
nagiosql.tbl_settings
note : The storage engine for the table doesn't support repair
nagiosql.tbl_submenu
note : The storage engine for the table doesn't support repair
nagiosql.tbl_timedefinition
note : The storage engine for the table doesn't support repair
nagiosql.tbl_timeperiod
note : The storage engine for the table doesn't support repair
nagiosql.tbl_user
note : The storage engine for the table doesn't support repair
nagiosql.tbl_variabledefinition
note : The storage engine for the table doesn't support repair
nagiosxi.xi_auditlog
note : The storage engine for the table doesn't support repair
nagiosxi.xi_auth_tokens
note : The storage engine for the table doesn't support repair
nagiosxi.xi_banner_messages
note : The storage engine for the table doesn't support repair
nagiosxi.xi_cmp_ccm_backups
note : The storage engine for the table doesn't support repair
nagiosxi.xi_cmp_favorites
note : The storage engine for the table doesn't support repair
nagiosxi.xi_cmp_nagiosbpi_backups
note : The storage engine for the table doesn't support repair
nagiosxi.xi_cmp_scheduledreports_log
note : The storage engine for the table doesn't support repair
nagiosxi.xi_cmp_trapdata
note : The storage engine for the table doesn't support repair
nagiosxi.xi_cmp_trapdata_log
note : The storage engine for the table doesn't support repair
nagiosxi.xi_commands
note : The storage engine for the table doesn't support repair
nagiosxi.xi_deploy_agents
note : The storage engine for the table doesn't support repair
nagiosxi.xi_deploy_jobs
note : The storage engine for the table doesn't support repair
nagiosxi.xi_eventqueue
note : The storage engine for the table doesn't support repair
nagiosxi.xi_events
note : The storage engine for the table doesn't support repair
nagiosxi.xi_link_users_messages
note : The storage engine for the table doesn't support repair
nagiosxi.xi_meta
note : The storage engine for the table doesn't support repair
nagiosxi.xi_mibs
note : The storage engine for the table doesn't support repair
nagiosxi.xi_options
note : The storage engine for the table doesn't support repair
nagiosxi.xi_sessions
note : The storage engine for the table doesn't support repair
nagiosxi.xi_sysstat
note : The storage engine for the table doesn't support repair
nagiosxi.xi_usermeta
note : The storage engine for the table doesn't support repair
nagiosxi.xi_users
note : The storage engine for the table doesn't support repair
nagiosxi.xi_wizard_history
note : The storage engine for the table doesn't support repair


its seems we have a problem with the db.
lzdravkov
Posts: 9
Joined: Mon Jul 06, 2020 2:58 am

Re: Monitoring Engine wont start.

Post by lzdravkov »

Thanks mate,that was genius move, but already tried it and didnt help.
sgardil
Posts: 143
Joined: Wed Aug 09, 2023 9:58 am

Re: Monitoring Engine wont start.

Post by sgardil »

Hey @Izdravkov

Can you do the following and report the output:

Navigate to CCM > Tools > Config File Management. Then click the verification buttons from top to bottom. Please share the output that is returned to the page.
kg2857
Posts: 237
Joined: Wed Apr 12, 2023 5:48 pm

Re: Monitoring Engine wont start.

Post by kg2857 »

Probably need to see why ndo3 isn't running, why it isn't responding.
User avatar
jmichaelson
Posts: 117
Joined: Wed Aug 23, 2023 1:02 pm

Re: Monitoring Engine wont start.

Post by jmichaelson »

What else is in the area of the shutdown in the log file?
Please let us know if you have any other questions or concerns.

-Jason
dacaron
Posts: 9
Joined: Mon Nov 26, 2018 2:00 pm

Re: Monitoring Engine wont start.

Post by dacaron »

I am having the same issue on NagiosXI 2024R1. From what I found it seems to haver stopped working on March 17 6:50:00 am GMT.

All that I am aware is that the notifications were turned off at March 17 12:40:00 am GMT and turned back on March 17 5:15:00 am GMT. Monitoring engine was working from there until March 17 6:50:00 am GMT.

I am not finding anything that could have possibly cause this to stopped in this time range.

Code: Select all

[1710658658] SERVICE ALERT: s1523oracqcp;CPU Load Per Core;WARNING;SOFT;1;WARNING - load average per CPU: 2.54, 2.36, 2.35
[1710658683] SERVICE ALERT: HOST;CPU Load Per Core;CRITICAL;SOFT;23;CRITICAL - load average per CPU: 16.57, 18.66, 21.21
[1710658746] SERVICE ALERT: HOST;CPU Load Per Core;CRITICAL;SOFT;12;CRITICAL - load average per CPU: 8.44, 8.83, 7.76
[1710658802] Caught SIGTERM, shutting down...
[1710658802] Caught SIGTERM, shutting down...
[1710658802] Successfully shutdown... (PID=1311834)
[1710658802] NDO-3: Callbacks deregistered
[1710658802] NDO-3: NDO - Shutdown complete
[1710658802] Event broker module '/usr/local/nagios/bin/ndo.so' deinitialized successfully.
[1710658803] Nagios 4.4.13 starting... (PID=2990833)
[1710658803] Local time is Sun Mar 17 03:00:03 EDT 2024
[1710658803] LOG VERSION: 2.0
[1710658803] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1710658803] qh: core query handler registered
[1710658803] qh: echo service query handler registered
[1710658803] qh: help for the query handler registered
[1710658803] wproc: Successfully registered manager as @wproc with query handler
[1710658803] wproc: Registry request: name=Core Worker 2990835;pid=2990835
[1710658803] wproc: Registry request: name=Core Worker 2990837;pid=2990837
[1710658803] wproc: Registry request: name=Core Worker 2990840;pid=2990840
[1710658803] wproc: Registry request: name=Core Worker 2990836;pid=2990836
[1710658803] wproc: Registry request: name=Core Worker 2990839;pid=2990839
[1710658803] wproc: Registry request: name=Core Worker 2990838;pid=2990838
[1710658803] NDO-3: NDO 3.1.0 (c) Copyright 2009-2023 Nagios - Nagios Core Development Team
[1710658803] NDO-3: Callbacks registered
[1710658803] NDO-3: Callbacks registered
[1710658803] Event broker module '/usr/local/nagios/bin/ndo.so' initialized successfully.
[1710658803] Warning: Service 'License Hosts Count' on host 'HOST'  has a notification interval less than its check interval!  Notifications are only re-sent after checks are made, so the effective notification interval will be that of the check interval.
[1710658803] Warning: Host 'HOST' has no default contacts or contactgroups defined!
[1710658803] NDO-3: Started comment thread
[1710658803] NDO-3: Started timed_event thread
[1710658803] NDO-3: Started event_handler thread
[1710658803] NDO-3: Started service_check thread
[1710658803] NDO-3: Started host_check thread
[1710658803] NDO-3: Started downtime thread
[1710658803] NDO-3: Started flapping thread
[1710658803] NDO-3: Started host_status thread
[1710658803] NDO-3: Started service_status thread
[1710658803] NDO-3: Started contact_status thread
[1710658803] NDO-3: Started acknowledgement thread
[1710658803] NDO-3: Started statechange thread
[1710658803] NDO-3: Started notification thread
[1710658803] NDO-3: Ended contact_status thread
[1710658807] NDO-3: Ended host_check thread
[1710658807] NDO-3: Ended host_status thread
[1710658817] NDO-3: Ended service_check thread
[1710658817] NDO-3: Ended flapping thread
[1710658817] NDO-3: Ended acknowledgement thread
[1710658817] NDO-3: Ended statechange thread
[1710658817] NDO-3: Ended event_handler thread
[1710658817] NDO-3: Ended timed_event thread
[1710658817] NDO-3: Ended notification thread
[1710658817] NDO-3: Ended downtime thread
[1710658817] NDO-3: Ended comment thread
[1710658821] NDO-3: Ended service_status thread
sgardil
Posts: 143
Joined: Wed Aug 09, 2023 9:58 am

Re: Monitoring Engine wont start.

Post by sgardil »

dacaron wrote: Wed Mar 20, 2024 8:17 am I am having the same issue on NagiosXI 2024R1. From what I found it seems to haver stopped working on March 17 6:50:00 am GMT.

All that I am aware is that the notifications were turned off at March 17 12:40:00 am GMT and turned back on March 17 5:15:00 am GMT. Monitoring engine was working from there until March 17 6:50:00 am GMT.

I am not finding anything that could have possibly cause this to stopped in this time range.

Code: Select all

[1710658658] SERVICE ALERT: s1523oracqcp;CPU Load Per Core;WARNING;SOFT;1;WARNING - load average per CPU: 2.54, 2.36, 2.35
[1710658683] SERVICE ALERT: HOST;CPU Load Per Core;CRITICAL;SOFT;23;CRITICAL - load average per CPU: 16.57, 18.66, 21.21
[1710658746] SERVICE ALERT: HOST;CPU Load Per Core;CRITICAL;SOFT;12;CRITICAL - load average per CPU: 8.44, 8.83, 7.76
[1710658802] Caught SIGTERM, shutting down...
[1710658802] Caught SIGTERM, shutting down...
[1710658802] Successfully shutdown... (PID=1311834)
[1710658802] NDO-3: Callbacks deregistered
[1710658802] NDO-3: NDO - Shutdown complete
[1710658802] Event broker module '/usr/local/nagios/bin/ndo.so' deinitialized successfully.
[1710658803] Nagios 4.4.13 starting... (PID=2990833)
[1710658803] Local time is Sun Mar 17 03:00:03 EDT 2024
[1710658803] LOG VERSION: 2.0
[1710658803] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1710658803] qh: core query handler registered
[1710658803] qh: echo service query handler registered
[1710658803] qh: help for the query handler registered
[1710658803] wproc: Successfully registered manager as @wproc with query handler
[1710658803] wproc: Registry request: name=Core Worker 2990835;pid=2990835
[1710658803] wproc: Registry request: name=Core Worker 2990837;pid=2990837
[1710658803] wproc: Registry request: name=Core Worker 2990840;pid=2990840
[1710658803] wproc: Registry request: name=Core Worker 2990836;pid=2990836
[1710658803] wproc: Registry request: name=Core Worker 2990839;pid=2990839
[1710658803] wproc: Registry request: name=Core Worker 2990838;pid=2990838
[1710658803] NDO-3: NDO 3.1.0 (c) Copyright 2009-2023 Nagios - Nagios Core Development Team
[1710658803] NDO-3: Callbacks registered
[1710658803] NDO-3: Callbacks registered
[1710658803] Event broker module '/usr/local/nagios/bin/ndo.so' initialized successfully.
[1710658803] Warning: Service 'License Hosts Count' on host 'HOST'  has a notification interval less than its check interval!  Notifications are only re-sent after checks are made, so the effective notification interval will be that of the check interval.
[1710658803] Warning: Host 'HOST' has no default contacts or contactgroups defined!
[1710658803] NDO-3: Started comment thread
[1710658803] NDO-3: Started timed_event thread
[1710658803] NDO-3: Started event_handler thread
[1710658803] NDO-3: Started service_check thread
[1710658803] NDO-3: Started host_check thread
[1710658803] NDO-3: Started downtime thread
[1710658803] NDO-3: Started flapping thread
[1710658803] NDO-3: Started host_status thread
[1710658803] NDO-3: Started service_status thread
[1710658803] NDO-3: Started contact_status thread
[1710658803] NDO-3: Started acknowledgement thread
[1710658803] NDO-3: Started statechange thread
[1710658803] NDO-3: Started notification thread
[1710658803] NDO-3: Ended contact_status thread
[1710658807] NDO-3: Ended host_check thread
[1710658807] NDO-3: Ended host_status thread
[1710658817] NDO-3: Ended service_check thread
[1710658817] NDO-3: Ended flapping thread
[1710658817] NDO-3: Ended acknowledgement thread
[1710658817] NDO-3: Ended statechange thread
[1710658817] NDO-3: Ended event_handler thread
[1710658817] NDO-3: Ended timed_event thread
[1710658817] NDO-3: Ended notification thread
[1710658817] NDO-3: Ended downtime thread
[1710658817] NDO-3: Ended comment thread
[1710658821] NDO-3: Ended service_status thread
Hey @dacaron

Could you post what you find from running verify files in Core Config Manager -> Tools -> Config File Management and let us know what you see from that?
dacaron
Posts: 9
Joined: Mon Nov 26, 2018 2:00 pm

Re: Monitoring Engine wont start.

Post by dacaron »

sgardil wrote: Wed Mar 20, 2024 10:31 am
dacaron wrote: Wed Mar 20, 2024 8:17 am I am having the same issue on NagiosXI 2024R1. From what I found it seems to haver stopped working on March 17 6:50:00 am GMT.

All that I am aware is that the notifications were turned off at March 17 12:40:00 am GMT and turned back on March 17 5:15:00 am GMT. Monitoring engine was working from there until March 17 6:50:00 am GMT.

I am not finding anything that could have possibly cause this to stopped in this time range.

Code: Select all

[1710658658] SERVICE ALERT: s1523oracqcp;CPU Load Per Core;WARNING;SOFT;1;WARNING - load average per CPU: 2.54, 2.36, 2.35
[1710658683] SERVICE ALERT: HOST;CPU Load Per Core;CRITICAL;SOFT;23;CRITICAL - load average per CPU: 16.57, 18.66, 21.21
[1710658746] SERVICE ALERT: HOST;CPU Load Per Core;CRITICAL;SOFT;12;CRITICAL - load average per CPU: 8.44, 8.83, 7.76
[1710658802] Caught SIGTERM, shutting down...
[1710658802] Caught SIGTERM, shutting down...
[1710658802] Successfully shutdown... (PID=1311834)
[1710658802] NDO-3: Callbacks deregistered
[1710658802] NDO-3: NDO - Shutdown complete
[1710658802] Event broker module '/usr/local/nagios/bin/ndo.so' deinitialized successfully.
[1710658803] Nagios 4.4.13 starting... (PID=2990833)
[1710658803] Local time is Sun Mar 17 03:00:03 EDT 2024
[1710658803] LOG VERSION: 2.0
[1710658803] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1710658803] qh: core query handler registered
[1710658803] qh: echo service query handler registered
[1710658803] qh: help for the query handler registered
[1710658803] wproc: Successfully registered manager as @wproc with query handler
[1710658803] wproc: Registry request: name=Core Worker 2990835;pid=2990835
[1710658803] wproc: Registry request: name=Core Worker 2990837;pid=2990837
[1710658803] wproc: Registry request: name=Core Worker 2990840;pid=2990840
[1710658803] wproc: Registry request: name=Core Worker 2990836;pid=2990836
[1710658803] wproc: Registry request: name=Core Worker 2990839;pid=2990839
[1710658803] wproc: Registry request: name=Core Worker 2990838;pid=2990838
[1710658803] NDO-3: NDO 3.1.0 (c) Copyright 2009-2023 Nagios - Nagios Core Development Team
[1710658803] NDO-3: Callbacks registered
[1710658803] NDO-3: Callbacks registered
[1710658803] Event broker module '/usr/local/nagios/bin/ndo.so' initialized successfully.
[1710658803] Warning: Service 'License Hosts Count' on host 'HOST'  has a notification interval less than its check interval!  Notifications are only re-sent after checks are made, so the effective notification interval will be that of the check interval.
[1710658803] Warning: Host 'HOST' has no default contacts or contactgroups defined!
[1710658803] NDO-3: Started comment thread
[1710658803] NDO-3: Started timed_event thread
[1710658803] NDO-3: Started event_handler thread
[1710658803] NDO-3: Started service_check thread
[1710658803] NDO-3: Started host_check thread
[1710658803] NDO-3: Started downtime thread
[1710658803] NDO-3: Started flapping thread
[1710658803] NDO-3: Started host_status thread
[1710658803] NDO-3: Started service_status thread
[1710658803] NDO-3: Started contact_status thread
[1710658803] NDO-3: Started acknowledgement thread
[1710658803] NDO-3: Started statechange thread
[1710658803] NDO-3: Started notification thread
[1710658803] NDO-3: Ended contact_status thread
[1710658807] NDO-3: Ended host_check thread
[1710658807] NDO-3: Ended host_status thread
[1710658817] NDO-3: Ended service_check thread
[1710658817] NDO-3: Ended flapping thread
[1710658817] NDO-3: Ended acknowledgement thread
[1710658817] NDO-3: Ended statechange thread
[1710658817] NDO-3: Ended event_handler thread
[1710658817] NDO-3: Ended timed_event thread
[1710658817] NDO-3: Ended notification thread
[1710658817] NDO-3: Ended downtime thread
[1710658817] NDO-3: Ended comment thread
[1710658821] NDO-3: Ended service_status thread
Hey @dacaron

Could you post what you find from running verify files in Core Config Manager -> Tools -> Config File Management and let us know what you see from that?

Code: Select all

Nagios Core 4.4.13
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2023-06-01
License: GPL

Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
Checked 4654 services.
Warning: Host 'NagiosXI-server' has no default contacts or contactgroups defined!
Checked 295 hosts.
Checked 8 host groups.
Checked 0 service groups.
Checked 21 contacts.
Checked 2 contact groups.
Checked 157 commands.
Checked 26 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 295 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 26 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 1
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
The warning is about a host without default contacts or contactgroups defined

https://pasteboard.co/8DeiAdBg8Fbd.png
https://pasteboard.co/4pQhLBUocysr.png
Post Reply