Am 24.11.2015 um 17:28 schrieb Chris Heerschap:
I found the same thing upgrading to 2.4 recently - thankfully, it's an
easy fix, found the answer here:
http://www.monitoring-portal.org/wbb/index.php?page=Thread&threadID=32998
mysql -u root -p icinga2_data <
/usr/share/icinga2-ido-mysql/schema/u
> On 24 Nov 2015, at 17:28, Chris Heerschap wrote:
>
> I found the same thing upgrading to 2.4 recently - thankfully, it's an easy
> fix, found the answer here:
>
> http://www.monitoring-portal.org/wbb/index.php?page=Thread&threadID=32998
That’s also found in the documentation.
http://docs.ici
I found the same thing upgrading to 2.4 recently - thankfully, it's an easy
fix, found the answer here:
http://www.monitoring-portal.org/wbb/index.php?page=Thread&threadID=32998
mysql -u root -p icinga2_data <
/usr/share/icinga2-ido-mysql/schema/upgrade/2.4.0.sql
where "icinga2_data" is your ici
>From experience run apt-get autoremove before update upgrade
On Tue, Nov 24, 2015 at 5:34 PM, Yann Lehmann wrote:
> Hi
>
> After one of the last updates of icinga2, the backend won't start anymore
> (unfortunately, I didn't notice when it went wrong).
>
> As I understand the error message of t
Hi
After one of the last updates of icinga2, the backend won't start
anymore (unfortunately, I didn't notice when it went wrong).
As I understand the error message of the 'checkconfig' command, this is
due to a mismatch of the database schema (see below).
[2015-11-24 16:04:57 +0100] critica
