After upgrading to 2.0 my clustered haproxy backend is in state CRIT. I have seen that haproxy in now integrated in the agent, so I made sure that both clusternodes run the current agent. Furthermore I removed the old haproxy plugin as it is no longer required with the new agent.
When checking the services of both nodes in wato, I can see the service in the section Monitored clustered services (located on cluster host).
On node1 it shows as OK and on node2 it shaws as CRIT which is correct as the haproxy backend specifies a source IP which is only avalable on the active node.
Nevertheless the service is CRIT on the virtual cluster host
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.