You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created by TheFlyingCorpse on 2016-08-14 17:55:41 +00:00
Assignee: gbeutner
Status: Resolved (closed on 2016-08-14 18:18:08 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-14 18:18:08 +00:00 (in Redmine)
Icinga Version: 2.4.10
Backport?: Not yet backported
Include in Changelog: 1
In a HA setup of 2 nodes where ha enabled=true, so only one writer to database out of the two.
Active node (writer to DB) returns expected OK with schema version and perfdata,whereas the passive node returns a critical checkresult with the output "Could not connect to database server."
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12430
Created by TheFlyingCorpse on 2016-08-14 17:55:41 +00:00
Assignee: gbeutner
Status: Resolved (closed on 2016-08-14 18:18:08 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-14 18:18:08 +00:00 (in Redmine)
In a HA setup of 2 nodes where ha enabled=true, so only one writer to database out of the two.
Active node (writer to DB) returns expected OK with schema version and perfdata,whereas the passive node returns a critical checkresult with the output "Could not connect to database server."
Changesets
2016-08-14 18:17:14 +00:00 by gbeutner 005e0f5
The text was updated successfully, but these errors were encountered: