[dev.icinga.com #10557] Web 2 claims that PostgreSQL IDO backend is not running when reloading active endpoint

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10557

Created by adamaflynn on 2015-11-06 20:35:55 +00:00

Assignee: (none)
Status: Feedback (closed on 2016-02-24 22:00:25 +00:00)
Target Version: (none)
Last Update: 2016-12-21 16:26:07 +00:00 (in Redmine)

Icinga Version: 2.3.11-1

---

I have an Icinga cluster with 2 nodes, each running icinga2 and icingaweb2.

When I reload icinga2 on the "Active endpoint" node, icingaweb2 shows no status update or external command check for 1 minute, then display an error saying "Backend icinga_monitoring_ido is not running".

If I reload a non-active endpoint, this doesn't happen.

After about 5 minutes, the error goes away and says that the backend has been running for 5 minutes (i.e. since the reload). So, it seems like the backend comes up fine (nothing in icinga2 logs suggesting a problem), but icingaweb2 takes ~5m to reconnect.

During this period, monitoring data in the web UI is out of date. This is problematic because reloads usually happen around config changes, so we can't interact with our new config for a few minutes.

I tried cranking log level up to debug but still don't see any log messages, so I don't have much information to share on what's happening.

Icinga2 version: 2.3.11-1

[icinga-migration]

Updated by elippmann on 2016-01-08 14:31:30 +00:00

• Project changed from Icinga Web 2 to Icinga 2
• Subject changed from pgsql IDO backend is not running to PostgreSQL IDO backend is not running when reloading active endpoint
• Icinga Version set to 2

Hi,

I assume that this is a Icinga 2 problem related to nonprioritized inserts. Did you have a chance to test the latest version of Icinga 2?

Cheers,
Eric

[icinga-migration]

Updated by elippmann on 2016-01-08 14:31:42 +00:00

• Subject changed from PostgreSQL IDO backend is not running when reloading active endpoint to Web 2 claims that PostgreSQL IDO backend is not running when reloading active endpoint

[icinga-migration]

Updated by adamaflynn on 2016-01-08 21:20:14 +00:00

Hi,

I haven't tried on 2.4.x yet because that's a much more significant upgrade. We can confirm the issue on the latest version of 2.3.x, though.

Adam

[icinga-migration]

Updated by mfriedrich on 2016-01-11 10:12:32 +00:00

• Category set to DB IDO
• Status changed from New to Feedback
• Assigned to set to adamaflynn

2.3.x is not supported anymore, please re-test with 2.4.x.

[icinga-migration]

Updated by schuetzi99 on 2016-02-09 10:07:13 +00:00

Hi,

I have the same problem, but I'm using version r2.4.1-1 on wheezy. After reloading icinga2 to activate configuration changes, it takes about 5 min. to get a new status in icingaweb2. During that time also my configured hostgroup filters can't be displayed. On the classicui, there is nothing to see about this issue.
I'm also using pgsql, version 9.4. Please let me know, if you need some more information.

Regards, Klaus

[icinga-migration]

Updated by vsakhart on 2016-02-10 02:36:19 +00:00

Hello,

I'm on Adam's team and taking over this issue. We've upgraded to version 2.4.1-1ppa1precise1 of Icinga2 and 2.1.2-2~ppa1 of Icingaweb2 and this problem persists.

If I update a service and then restart the icinga2 daemon, I get the "Backend icinga_monitoring_ido is not running" message in the UI shortly after the daemon comes up. I can confirm the UI can talk with the daemon since if I try to acknowledge a problem, I can see in the Icinga2 logs the acknowledgement was sent. It takes about 2-3 minutes for the UI to sync up with the changes I made and to recognize that it's connected with Icinga2.

We also run icinga2-classicui on both boxes and if I update the config and restart Icinga2, the classicui updates with the correct config instantly.

Regards,
Vitaliy

[icinga-migration]

Updated by mfriedrich on 2016-02-24 22:00:25 +00:00

• Status changed from Feedback to Closed
• Assigned to deleted adamaflynn

We believe this issue has been fixed with the most recent release 2.4.3.

[icinga-migration]

Updated by deneu on 2016-03-08 12:04:40 +00:00

Hey Michi,
do you know if its affected also to mysql?
I got the problem with a 2.3.1 icinga2 release and icinga_web.

Regards,
Philipp

[icinga-migration]

Updated by netphantm on 2016-04-15 15:47:15 +00:00

Hi
I have the same issue here and I'm using following versions:
ii icinga2 2.4.4-1debmon8+1 amd64 host and network monitoring system
ii icingaweb2 2.2.0-1debmon8+1 all simple and responsive web interface for Icinga
ii postgresql-9.4 9.4.6-0+deb8u1 amd64 object-relational SQL database, version 9.4 server
let me know, if you need some more info

regards,
hugo.-

[icinga-migration]

Updated by LarsEngels on 2016-12-21 16:26:07 +00:00

• Status changed from Closed to Feedback

Re-open the bug. It still persists in Icinga 2.6.0 with Icinga Web 2 2.4.0 and PostgreSQL 9.3 (9.3.14-0ubuntu0.14.04)

[dnsmichi]

It's an old bug, so please create a new issue for new problems next time @larsengels