Hi list,
i just upgraded my central icinga2 instance to 2.3.7 and discovered that my
icinga2.log was showing a lot errors like this one:
[2015-07-16 09:56:40 +0200] critical/IdoPgsqlConnection: Error "ERROR:
duplicate key value violates unique constraint "uq_endpointstatus"
DETAIL: Key (endpo
Hi,
I've installed a basic icinga2 setup that consists of a master and a node.
I'm trying to figure out how to monitor a service such as ypbind without
using tcp built in check.
Please help me find a way to monitor if a certain service is running on the
linux machine :)
Thank you,
Dennis.
_
Hi,
I have Icinga2.3.4 (clustered instances with one zone & 3 endpoints)
running in my prod environment and I want to upgrade it to the latest
version.
Is there any docs available or specific steps to be followed for the
upgrade?
Regards,
Sudesh
___
ic
The same happened to me upon upgrading to 2.3.7. Truncating the
icinga_endpointstatus
fixed the issue.
Markus, the issue link you sent points to an unrelated issue...
On Thu, Jul 16, 2015 at 11:05 AM, Markus Joosten
wrote:
> Hi list,
>
> i just upgraded my central icinga2 instance to 2.3.7 and
On Thu, 16 Jul 2015, Shay Rojansky wrote:
> The same happened to me upon upgrading to 2.3.7. Truncating the
> icinga_endpointstatus
> fixed the issue.
>
> Markus, the issue link you sent points to an unrelated issue...
Michi fixed the issue in git in the morning, it will be included with the
next
Hi Dennis,
your question can be answered with at least a million possibilities :-)
Just to name a few:
- tcp port check which you already mentioned
- local check on your node if a certain process is running (check_procs)
- remote check via snmpd if a certain process is running
- application-level
I'm sorry, that was a copy&paste error on my end, here is the link towards the
correct issue:
https://dev.icinga.org/issues/9634
@Alex: So this fix will be backported to 2.3.8?
Regards,
Markus
-Original message-
From: Shay Rojansky
Sent: Thursday 16th July 2015 20:53
To: Icinga User's C
On Thu, 16 Jul 2015, Markus Joosten wrote:
> I'm sorry, that was a copy&paste error on my end, here is the link towards
> the correct issue:
> https://dev.icinga.org/issues/9634
>
> @Alex: So this fix will be backported to 2.3.8?
I would think so, but dnsmichi is the authorative head.
Alex
___
Am 16.07.2015 um 21:59 schrieb Alexander Wirt:
On Thu, 16 Jul 2015, Markus Joosten wrote:
I'm sorry, that was a copy&paste error on my end, here is the link towards the
correct issue:
https://dev.icinga.org/issues/9634
@Alex: So this fix will be backported to 2.3.8?
I would think so, but dns
Am 16.07.2015 um 20:42 schrieb Sudesh Kumar:
Hi,
I have Icinga2.3.4 (clustered instances with one zone & 3 endpoints)
running in my prod environment and I want to upgrade it to the latest
version.
Is there any docs available or specific steps to be followed for the
upgrade?
Read the Chang
Am 15.07.2015 um 12:38 schrieb Bertalan Voros:
Hello All,
I would like to create a user with the following notification filter,
but can't really figure out how to achive this in the user definition.
Hosts: Recovery, Down, Unreachable
Services: Recovery, Warning, Critical, Unknown
Could someo
Am 15.07.2015 um 08:37 schrieb Patrick Hunziker:
Hello
I've set up ICINGA2, everything works just fine, except the scheduled
downtimes. I have configured recurring scheduled downtimes for our filr
(Novell) and its hypervisor. The thing is it worked for about a week and
afterwards the rule app
12 matches
Mail list logo