![]() ![]() I am a bit disappointed that Nagios 4 has been released on the 20th of September 2013, and 7 years on, Livestatus still expects to find Nagios 3.5, which, by any measure in IT parlance, is a dinosaur. Given the popularity of Nagios, I believe it would deserve at least a mention, even more so that the RPM is compiled for a pre-historic version of it. I believe in this instance it is a bit of both as the RPM installer fails to look for Nagios dependencies (if it does any detection at all), and the documentation also fails to mention any version-related constraints. If following the documentation to the letter ends in failure then there is either a problem with the product, the documentation, or both. If there are specific product version requirements then I believe they should be in the documentation. In fact the word Nagios is not mentioned once on the page. The instructions make no mention whatsoever of version constraints. I followed the instructions, to the letter, specific for CentOS 8. I had no option but to search for the install instructions which I found at, for my specific environment. I’ve done exactly that and I arrived to the site, which is not exactly an installation manual. Refer to h_t_t_p_s_: //_/cms_livestatus.html on how to install livestatus onto your monitoring box. ![]() I am trying to install Thruk, following the instructions at Thruk - Installation, where, when it comes to Livestatus, it says : Then I installed the latest stable Nagios Core version, which is 4.4.6, released on 28th of April 2020, using the Nagios Core install guide published on the Nagios site. I started by installing a brand-new CentOS 8 box using the latest OS ISO image. Let me start by saying that I am not a Linux person in that I have some experience but my background lies in Microsoft enterprise and cloud solutions. Hi r.sander, wow, that was quick! Didn’t expect a reply so soon ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |