IcingaWeb2 backend not running after upgrades

This forum was archived to /woltlab and is now in read-only mode. Please register a new account on our new community platform.

You can create a thread on the new site and link to an archived thread. This archive is available as knowledge base, safe and secured.

More details here.
  • After upgrading to the latest icinga2 (2.7.2-1.xenial), Icingaweb2 has lost its connection with icinga ("backend not running" message in the web UI). Icinga2 is definitely up and running fine, so something is not right. I then upgraded icingaweb2 too (to 2.4.2-1.xenial); no change.

    We have a setup where the db (MySQL), icinga and icingaweb2 are each on a different VM. Icingaweb2 is running on PHP-FPM and Apache.

    I've been trying to check all the logs (mysql, icinga, php, apache, system logs) I can think of but can find no errors indicating the reason. Network is fine, and nothing has been changed in the system AFAIK, apart some stock package updates from Ubuntu repo. This system has been in production for months now.

    Any ideas where should I be able to see indications of what might be wrong?

    The post was edited 4 times, last by Petri ().

  • As always, please include valuable details such as versions involved. Upgrades usually involve a from and to version too.

    Startup logs and so on should be included too, especially related to the ido feature in this case.

  • Hi,

    your Icinga 2 VM can establish a connection to your MySQL IDO database? There should be a log entry about the successful established connection or one if the connection is not successful established. Please also verify that you can establish a connection from your Icinga Web 2 VM to your MySQL IDO database (via CLI mysql client).

    Please also ensure that the ido-mysql feature is enabled.

  • Thank you! I must've omitted the startup log earlier when debugging things, bummer :( There it was - the ido-mysql feature had dropped off, due to too restrictive feature config file permissions.

    I don't think it had anything to do with Icinga, probably changed at some point during our configuration versioning process that's unfortunately not yet as bullet-proof as it should, it seems...

  • Hi All, I ave some problem ("backend not running" message in the web UI) after update:

    Icinga2 2.7.2 -> 2.8

    Icingaweb2 2.4.2 -> 2.5.0

    We use Apache + PHP-FPM,

    Icingaweb2 and DB are different hosts (RH7.3) and already worked before update

    There are the features:

    Disabled features: compatlog elasticsearch gelf graphite influxdb opentsdb

    Enabled features: api checker command debuglog ido-mysql livestatus mainlog notification perfdata statusdata syslog

    1. The configuration has been successfully validated.
    2. Validation Log
    3. Connection to icinga as icinga on ........: successful
    4. have_ssl: DISABLED
    5. protocol_version: 10
    6. version: 5.5.56-MariaDB
    7. version_compile_os: Linux
    1. Edit Command Transport icinga
    2. The configuration has been successfully validated.

    But when I disable api feature, and restart icinga2 daemon, i see on webui:

    icinga has been up and running with PID 9588 for 0m 10s

    Of course, the commands on the webUI do not work, but can see list of hosts, services, history ....

    When i enable api again, I see "backend not running"

    I don't know mechanism how to icingaweb does monitoring of health.

    Could you please give some advise for this issue?


  • Restart log:

  • Hi All,

    Problem has been resolved. I was my first HA cluster, I just enabled ido-mysql feature on second master