Hi,
in the zones.conf on your master you need to add a endpoint (and zone) for your client. I recommend to read the documentation about distributed monitoring.
I guess the video tutorial that you followed used the bottom up mode to add satellites/clients. This mode got removed in the latest stable release v2.8.0. You must now use the top down mode, which is also explained in the linked documentation chapter.
After you configured the client, did you restart the icinga2 daemon?
The service looks good to me. Did you tried to force a check via "Check now"?
Please show us the current zone.conf from your master and client, also run the following command on both systems # icinga2 daemon --validate and post the output here. Please also search the Log on the client for entries that indicates that the config from master will be ignored.
Just to be sure, the hostname that you configured is identical with the hostname that you set on the master for the client?
If I understood you correctly your check_disk service have check results, but it is still pending? I guess that the check results are old and coming from your bottom up mode setup.
Please show us the configuration of that service (# icinga2 object list --type Service --name "<Your Service Name here>").
The Icinga related communication between your master and client works? The certificate issue from your post above is resolved?
Please verfiy if your client accepts commands and/or configuration. Check /etc/icinga2/features-enabled/api.conf for accept_commands and accept_config. Pointer to the related documentation for those attributes: https://www.icinga.com/docs/ic…object-types/#apilistener
There is a migration path from bottom up mode to top down mode: https://github.com/Icinga/icin…up-migration-to-top-down-
The zone.conf on your master should contain the satellite/client. I recommend to read the Distributed Monitoring chapterin the documentation.
Hi,
the Log is from your satellite or your master? Did you used the bottom up mode beforehand?
Please share your zone.conf from your master & satellite/client, as well as the versions that are included (# icinga2 --version) .
The network communication works, for example a ping from your master to your satellite and vice versa?
And you want to do this with the Director module? Did you have already installed the Director module and ran the kickstart wizard?
What do you understand under the terminology "icinga agent" ?
Do you mean installing Icinga 2 as an agent on a System? You can find advises for this in the documentation.
Please describe what you understand under "icinga agent" and what you exactly want, than we can help with hopefully good tips and advises 
//edit:
I found your issue on GitHub, so I guess you mean "How can I configure an Icinga Agent in the Director module?", right?
A side note: Please don't use the GitHub issue tracker for such questions. It is better to put those questions on the community channels like this forum.
Hi,
is the problem from you other thread (API not syncing files to satellite) resolved?
How did you verify that the host objects are correctly synced to the satellite?
Please show us your current zone.conf (from your master & satellite).
The "accept_config" attribute is set to true on your satellite?
Hi,
the bottom up mode was removed in v2.8.0.
https://www.icinga.com/docs/ic…ved-bottom-up-client-mode
You can find a migration guide on GitHub
https://github.com/Icinga/icin…up-migration-to-top-down-
Hope this helps so far
You can use the icinga2 node setup CLI command. Inside the docs you can find the attributes.
I found this issue https://github.com/Icinga/icingaweb2/issues/3141
The issue is closed and you wrote that it is working now, so I assume the issue here is resolved?
Hi,
did you verified that your MySQL user "apache" exist and that he has the right permissions to write to your database?
Please also share more information about your setup, see the FAQ.
Did you made an update to the v2.8.0?
If yes, the problem was discussed in an other Thread:
Please also read the update documentation:
AFAIK the Director can't handle downtimes for now.
In the documentation you will find more examples and explanations https://www.icinga.com/docs/ic…6-distributed-monitoring/ I can highly recommend you to read through the docs, it is really good.
From your last post I assume that it is working (for now)?
Can you please show us your current zones.conf? From what I see from the Log, did you used the same IP address for the endpoint "gestion0.upr.edu.cu" as for "gestion1.upr.edu.cu"?
Yes. You need to configure the Endpoint (and Zone) objects on your master.
Example:
If the Endpoint object is not configured, the Icinga master does not know about this endpoint and when it tries to connect to the Icinga master will drop the connection. This si
