-
Transaction failure results in service crash
```
pq: could not serialize access due to read/write dependencies among transactions
can't perf…
-
## Describe the bug
HA Icinga2 setup, two nodes in master zone. Database is AWS RDS MySQL, Multi-AZ. During/after scheduled maintenance of the database service we found both IcingaDB systemd units …
-
We received a report of IcingaDB 1.2.0 crashing while logging the following:
```
Jun 21 18:58:45 icingadb[1628]: runtime-updates: Upserted 2 ServiceState items
Jun 21 18:58:57 icingadb[1628]: his…
-
## Describe the bug
I am uncertain as to whether this is a bug or something that needs more warnings in Icinga.
I was running a check command with a java library that was loaded like this:
`j…
-
## Describe the bug
Apparently there is a race condition in our HA realize handlings that can occur from time to time, causing both Icinga DB instances to become active/responsible at the same time…
-
## Is your feature request related to a problem? Please describe.
Today we use the monitoring-module's api to schedule and remove downtimes for hosts and their services on demand in automated ways. T…
-
## Affected Puppet, Ruby, OS and module versions/distributions
- Puppet: 8.6.0
- Ruby:
- Distribution: PE 2023.7.0
- Module version: 6.0.0
## How to reproduce (e.g Puppet code you use)
…
-
We are running Postgres as a backend for IcingaDB. Postgres is running as a Patroni cluster with 3 nodes. On the Icinga Masters we use `pgbouncer` and `haproxy` for the connection to the database.
pg…
-
To be able to display the Collection's documentation on Ansible Galaxy (and by proxy by using `ansible-doc`) we should change the location of certain pieces of documentation, merge and add some files.…
-
It is more of a question maybe you have already verified the schema changes, however it would be important to have IcingaDB support which will become the de facto db from version 2.12 of Icinga.
Grea…