I’m trying to get Director installed & running on a new version of Icinga 2 that’s running on a new VM running Oracle Linux 8.10.
Icinga 2 and Icinga Web are up and running no problem. Installing Director was supposed to be nice & easy. Just create the db & user, create the resource, download/enable the package and blam, we’re good to go.
We had a few problems getting the db & user created, but eventually they were done without error. I created the resource per the instructions, also without error. When I went to download the package is when I started having major issues. None of the scripts/sites I tried worked, they all timed out. Now, we do have a very strict firewall here, but I tried each of the sites manually and they worked, so I don’t think it was our network blocking it. Regardless, after trying for 30 minutes, I gave up, downloaded a copy manually, copied the tar.gz file over, extracted it into the proper folder /usr/share/icingaweb2/modules. All of that went through ok without any errors. I then enabled director and that worked without any issues.
But now that all of that’s done, it’s showing in the “Modules” section of the icinga web interface, it’s “enabled” there with version 0.0.0 but it’s not showing on the left-hand bar, so I can’t actually use it. I’m not sure what else to do here or what’s going wrong, since there’s no error messages of any kind, it’s just not showing up. The resource is there & good, the module is installed, enabled & working. What’s wrong???
Yes, I tried ALL of those… it never worked, always timed out. But I got somewhere.
I did a bit of file unpacking/swapping/cleanup and I’ve got the “Director” showing up in the left bar now, but now it’s telling me I’m missing a dependency “incubator”. That wasn’t anywhere in the ‘Director’ installation instructions. How do I get this bloody thing installed now?
Your basesystem already looks like a mess so lets start over.
Oracle Linux 8.10 requires a subscription for new packages.
You can Use Debian or Ubuntu, OpenSuse or Fedora these packages are officially publicly available.
If you decide to install director manually:
Please only checkout a release tag for incubator since the dependencies are only in the releases not in the master branch.
Start over with a fresh VM on your system, you can use VirtualBox, and with this approach you can play arround not having issues with your network structure.
Once your setup works as expected, you can install it on a corporate test / prod environment. If anything that previously worked on your private virtual machine is not working on your corporate machine you can debug this a lot faster
I actually finally got permission to rebuild the entire thing from scratch with Ubuntu, like I wanted to do from the beginning.
The install process went much smoother/easier, although the official instructions are missing many steps and are not beginner friendly. I have Icinga 2 working, Icinga web working and Director working (mostly).
I’m currently getting the error:
“Unable to detect your deployment endpoint. I was looking for the first endpoint configured with an assigned API user in the “master” zone
I’ve Googled, AI’d and I can’t find a solution. I already checked the constants.conf and zones.conf and they both look fine. I re-ran the node wizard and used the FQDN for the master cn. Still getting the error and I’m completely as a loss for where to go from here for help. I’ve made a post about it but not gotten any response.