Icinga-Web displaying instance as "down" (V1.10)

This forum was archived to /woltlab and is now in read-only mode.
  • We have distributed version of ICINGA. We could see on icingaweb text I get the instance status is this:

    Instance 'default' (status is false, data is 420.08 minutes old)



    only Services were not getting updated from Jan7.



    1) Mysql was not rebooted. I have rebooted mysql which looks good



    2) php.ini - No changes to file


    ; Defines the default timezone used by the date functions

    ; http://www.php.net/manual/en/d…ion.php#ini.date.timezone

    ;date.timezone = America/Chicago



    Please suggest me any other things to check it

  • Is ido2db running (2 processes) and is it actually populating the database ("select * from icinga_programstatus")? Check both icinga.log for idomod errors and syslog for ido2db errors.

  • Yes its running fine.


    IDO2db is running 2 processes .


    0 Jan26 ? 00:00:09 xx/icinga/bin/ido2db -c xx/icinga/etc/ido2db.cfg


    0 Jan26 ? 00:02:07 xx/icinga/bin/ido2db -c xx/icinga/etc/ido2db.cfg

    I couldnt find any idomod errors in icinga.log

    Let me check the Db putput

  • DB ouput:

    programstatus_id instance_id status_update_time program_start_time program_end_time is_currently_running process_id daemon_mode last_command_check last_log_rotation notifications_enabled disable_notif_expire_time active_service_checks_enabled passive_service_checks_enabled active_host_checks_enabled passive_host_checks_enabled event_handlers_enabled flap_detection_enabled failure_prediction_enabled process_performance_data obsess_over_hosts obsess_over_services modified_host_attributes modified_service_attributes global_host_event_handler global_service_event_handler

    98 2 2014-03-20 11:13:47 2014-03-19 23:46:40 2014-03-20 11:13:47 0 30939 1 2014-03-20 11:13:47 2014-03-20 00:00:10 0 0000-00-00 00:00:00 1 1 1 1 1 1 1 0 0


    and also our server runs with following timezone :

    Fri Jan 27 14:09:45 MST 2017


    ON ICINGA-WEB it displays with this:

    Servertime:21:11:48

  • status_update_time being 2014-03-20 11:13:47 seems fairly outdated compared to today. Are you sure that Icinga did write to the database for the last 3 years?