-
Notifications
You must be signed in to change notification settings - Fork 570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HA master doesn't seem to activate the api stage #7292
Comments
Well, both nodes didn't have the same instance ID in the ido object. Docs didn't mention anything about that so I set both to the hostnames of each node 🤷♂️ |
I was wondering why you did copy |
Mainly because the docs mention this. So is this unneeded? Or is only |
Maybe the docs should be clarified on this, I only added this because of customer requests. The initial sync is required when you decide e.g. 1 month after setting up one master, that a secondary would be needed. This is to ensure that the state file is intact, and you may of course overcome the problem with different _api stage names (doesn't matter though). One problem I do see with the description is the content of I'll think about this and fix it, thanks for the discussion. |
Describe the bug
Creating a HA master as explained in the manual doesn't seem to work properly. I'll explain the steps I performed below.
When both masters are running (let's say I had A running, and added B as a second master), A is performing the checks while B writes to IDO.
This works great and I can see the messages A sends to B in the debug log:
Received 'event::CheckResult' message from 'A'
.However, the event is never written to IDO. Inspecting the output of
icinga2 object list
shows that the objects for which the checks are executed do not exist.I therefore think icinga2 just doesn't write any results to the IDO when it doesn't know the object.
However, the file with the objects (
/var/lib/icinga2/api/zones/master/_etc/icinga2.conf
) exists and is valid.To Reproduce
I created the HA setup by:
/var/lib/icinga2
from A to BExpected behavior
B should create all objects it needs in order to write the results to the IDO.
Also, a warning would be nice if it was asked to write results into the IDO and it doesn't know the object of which the results are to be written.
Your Environment
Include as many relevant details about the environment you experienced the problem in
icinga2 --version
):I tested both icinga 2.10.5 and 2.11
icinga2 feature list
):On both A and B:
icinga2 daemon -C
):On A:
zones.conf
file (oricinga2 object list --type Endpoint
andicinga2 object list --type Zone
) from all affected nodes.The text was updated successfully, but these errors were encountered: