> On 24 Feb 2017, at 07:10, Gerald Vogt wrote:
>
> On 23/02/2017 23:01, Michael Martinez wrote:
>> Hi Rob, thanks for the info.
>> Actually I was able to fix it by appending the following in icinga2.conf:
>>
>> include_recursive "/var/lib/icinga2/api/packages/_api/conf.d"
>
> That will break i
Hi,
I'm planning to set up a redundant setup with two nodes running Icinga Web 2
behind a HAproxy instance.
In the default configuration, PHP session storage is in the local file system
on the Icinga Web 2 servers. This works very fine unless the load balancer
decides to fail over to the oth
Il giorno 24 feb 2017, alle ore 13:33, Peter Eckel ha
scritto:
> Hi,
> I'm planning to set up a redundant setup with two nodes running Icinga Web 2
> behind a HAproxy instance.
> In the default configuration, PHP session storage is in the local file system
> on the Icinga Web 2 servers. This
I think the sessions is the least of the problems. We run load -balanced
icingaweb2 setup and the re-login is not an issue. The major thing is the
configs that are not yet database driven. ( dashboards, announcements, ). User
pref can now be in database.
So if you don't have a mean to replicate
Hi Pascal,
> I think the sessions is the least of the problems. We run load -balanced
> icingaweb2 setup and the re-login is not an issue. The major thing is the
> configs that are not yet database driven. ( dashboards, announcements, ).
> User pref can now be in database.
>
> So if you don't
Hi Luca,
> Of course you’d have problems during an actual failover (one backend fails or
> you manually take it out of the pool) but it should be a minor issue.
that's exactly the issue I'm trying to solve. My other solution (keeping the
sessions directory in sync) is quite clumsy, and I'm loo
Il giorno 24 feb 2017, alle ore 14:17, Peter Eckel ha
scritto:
> Hi Luca,
>> Of course you’d have problems during an actual failover (one backend fails
>> or you manually take it out of the pool) but it should be a minor issue.
> that's exactly the issue I'm trying to solve. My other solution (
It _should_ be possible to use multiple memcached servers as session storage
for your PHP sessions. One memcached goes on each of your Icinga Web 2
instances. I used memcached for PHP sessions before and its a common use case,
but never tried it with Icinga Web 2.
I found a good article about i
On Thu, Feb 23, 2017 at 10:10 PM, Gerald Vogt wrote:
> Check for missing conf files in /var/lib/icinga2/api/packages/_api/
>
> See https://github.com/Icinga/icinga2/issues/3668
>
> You should have
>
> _api/active.conf
> _api/include.conf
> _api/hostname-141.../include.conf
I don't have them. How
On 24/02/2017 18:58, Michael Martinez wrote:
On Thu, Feb 23, 2017 at 10:10 PM, Gerald Vogt wrote:
Check for missing conf files in /var/lib/icinga2/api/packages/_api/
See https://github.com/Icinga/icinga2/issues/3668
You should have
_api/active.conf
_api/include.conf
_api/hostname-141.../inc
I was able to fix it by blowing away the _api/ directory and
restarting icinga. The missing files got recreated automatically and
everything is working correctliy now.
On Fri, Feb 24, 2017 at 10:02 AM, Gerald Vogt wrote:
> They are all three missing?? What files/directories do you have in
> /var/
11 matches
Mail list logo
