We recently upgraded to the latest Icinga (2.12.2) and latest Icingaweb2.
I have a multi-master configuration with a dedicated Icingaweb2 box.
In Icingaweb2, I have acknowledged a host problem, but Icingaweb2 is displaying it as unacknowledged/unhandled:
When I click Acknowledge, Icingaweb2 errors as it is already acknowledged:
In the master logs:
[2020-12-04 12:46:10 +1100] information/ApiListener: New client connection from [126.96.36.199]:35376 (no client certificate) [2020-12-04 12:46:11 +1100] information/HttpServerConnection: Request: POST /v1/actions/acknowledge-problem (from [188.8.131.52]:35376), user: icingaweb2, agent: , status: Internal Server Error). [2020-12-04 12:46:11 +1100] information/HttpServerConnection: HTTP client disconnected (from [184.108.40.206]:35376)
This appears to be affecting all of my acknowledgements for hosts and services.
If I stop the icinga2 service on my secondary master and the primary/config master takes over, the acknowledgments return, however some of the messages are missing:
I’ve tried clearing out the configs on the secondary master and have it pull a fresh config from the primary, but I can’t seem to get these acknowledgements syncing.
They connect to a local MySQL/Galera cluster node, and the database seems in-tact otherwise.
Any idea what may be causing this? Cheers.