-
Hi,
2 hosts are incorrectly reported as down (hostalive) by IcingaDB. They are not reported by Icinga as down.
Also the performance data makes them appear as responding to ping.
I tried restart…
-
## Describe the bug
The Icinga2 daemon on the configuration master in a HA setup crashes a few minutes after start.
Just for a hint: It doesn't seem to fail when the notification feature is disabl…
-
## Describe the bug
It looks like I have a bug with the `apply Service` and a for loop
My service is defined like that :
```
apply Service "SSL - " for (name => file in host.vars.urls_to_chec…
DB-CL updated
3 years ago
-
## Describe the bug
A number of defunct/zombie processes accumulate. There are 10-30 day (check @ 5 min intervals) and do not seem to be related to master reloads (as previous bugs/forums reference…
-
There are detail views for events in the monitoring module. Here they're missing.
-
## Describe the bug
Host/Service group right column view mode switcher not working correctly. If you change the view mode in the right column, this affects the left column.
## To Reproduce
1. H…
-
When you have configured broken connection details in an `IcingaDB` object, multiple connections are started at once and they will all log that they failed to connect. There already was #8883 which wa…
-
We should avoid redundant titles wherever possible. e.g. in the host detail view the `Services` and `Host Group` titles are such a case.
![Screenshot from 2020-06-15 08-53-19](https://user-images.g…
-
How to reproduce:
[root@p3i212t4-idb ~]# systemctl start icingadb; ss -lautnp | grep 3306 | grep 'TIME-WAIT' -c; sleep 10; ss -lautnp | grep 3306 | grep 'TIME-WAIT' -c
```
0
386
```
On databas…