Kickstart Update 3 / Nagios Update

Kickstart Update / Nagios Update

I have managed to add a copy of the Oracle Linux 7 ISO to the boot-up process, so that every time the system boots, it mounts a copy of the ISO so that it should be able to serve the files over the network for kickstarts. After looking through a couple of other guides (mainly this one: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html and this one for FSTAB http://itekblog.com/mount-iso-using-fstab/, as well as the older linux-mag one which a lot of this is based on http://www.linux-mag.com/id/6747/), I noticed that once the Linux DVD is mounted, there are a couple of additional folders/files on the disc which have a lot of the necessary settings pre-configured. These are called install trees, which is exactly the type of file that Kickstart should be pointed to, as this install tree should point Kickstart in the right direction of the files based on the ISO defaults as opposed to guessing them. I have added the base and core packages to the Kickstart file, but these will be tweaked further once we can get this server to function properly.

Unfortunately, it still looks like booting from the server doesn't get any further than it used to.

I have tried pointing the Kickstart file towards both the directory with the install tree, the actual install tree file, the live-mounted ISO, a directory containing all the files from the OL7 disk obtained using the "cp -r /dev/sr0/* /var/www/html/pub/OL7/*/" all of which have not worked directly. It seems like the installation tree concept makes the most sense.

I decided to help Maheer out with his Nagios project a bit, as I asked him how far he was with it, and knew enough to be able to help him. First, we rebooted the VM his Nagios server is on. We then began to change some of the files in /usr/local/nagios/etc/. First, we looked at nagios.cfg in that directory, which needed to have some things commented on based on the setup path we chose. Since Maheer's main goal is to get Ping based monitoring done, we set it so that Ping is the only attribute monitored by the projectors that are added to it and defined properly under /usr/local/nagios/etc/objects/localhost.cfg

Typically we would NOT place all of this in the localhost.cfg file, but attempting to play with the printers, and the switches configs caused start-up errors within Nagios. Once we re-defined the parameters to those of the Dell 1610HD in RLC 102A, we were able to see it from Monitor01.manhattan.edu. I mentioned that ideally we could have each building separated from each other in one of the spanning tree layouts, which would visually indicate downed projectors. We noticed that e-mail notifications ARE possible, but are NOT setup by default. They require either a mail-server, or a package to utilize another mail-servers API, which we have not figured out yet. We found the e-mail related configurations in /usr/local/nagios/etc/objects/commands.cfg. I will continue to work towards getting Kickstart ready to be used and helping Maheer with as much as I can due to my prior knowledge of Nagios.