On Sat, Feb 7, 2015 at 4:51 PM, Michael Friedrich < [email protected]> wrote:
> Am 07.02.2015 um 20:57 schrieb Steve Murphy: > >> >> Hey, I'm a total nube, so give me a little slack and a little info, >> and I may step beyond that quickly. >> > > It would be nice to know which versions you are using, and where and how > you keep Icinga and its components installed. That will help the reader to > identify problems more easily in case. > > Sorry, IIn on a Centos 6 machine, yum updated. icinga2 reports that it is at 2.2.4. Icingaweb2 ... I don't know how to get it to tell me its version, but I assume it's at whatever is in your yum repo right now. The /etc/icinga2 dir contains conf.d, and in there are most of my config changes. I have found the /usr/share/icinga2/include the templates for plugins, etc. I'm assuming the standard locations when you do package installs from your repo. I installed icingaweb2 also from packages. Went very smoothly! >> I'm not so much a nube to nagios, tho. >> >> I'm trying out icinga2, and icingaweb2; To do so, I'm translating >> my nagios "define" stuff to icinga "object" stuff. >> >> I have two problems: >> >> 1. Repeated notification at 90 min internval; I don't see that number >> anywhere in the configs, where/how do I get rid of repeated >> notifications? They >> are extremely irritating. >> > > There's plenty of documentation written for that every case. > http://docs.icinga.org/icinga2/latest/doc/module/ > icinga2/chapter/monitoring-basics#notifications > > The default notification value is documented as well. > http://docs.icinga.org/icinga2/latest/doc/module/ > icinga2/chapter/configuring-icinga2#objecttype-notification > Many, many Thanks! I googled for icinga2 notification interval, and got pointers to the icinga1 docs. Silly me. I should stuck with the info in the icinga2 docs. It is all there. > > >> 2. Web2 http interface. After installation, and updating my config, and >> getting >> my various nrpe probes working again, I go to the web interface, and >> the only thing that seems to work is the Overview => Services. >> >> Dashboard: Recently Recoverd Services shows things. Service Problems is >> empty, >> with "Server error: No such column: hosts_total. The bottom half of the >> screen >> says: "No such column: hosts_total, with a php stack trace (13 lines) >> below that. >> the top entries in the stack dump mention Protocol/Livestatus .... >> >> Problems: every subcategory says: Server error: No such column: >> hosts_total, >> with a stack trace. (Except unhandled services, which works). HostGroups >> says "Server error: Query "Groupsummary" doesn not exist for backend >> livestatus" >> and on and on it goes! >> >> A lookup on google reveals bug #8524, Usability of mk_live as backend, >> where >> tgelf updated the bug a mere 5 days ago, with the statement: >> >> "Yes, Livestatus is not in a usable state right now - we will take care >> of it after beta2." >> >> So, ..., I'm wondering. How long could it be, before mk_live is updated >> and working? >> In the meantime, any suggestions? >> > > Use DB IDO as backend. > > I'm just one of perhaps many, who visited the site, >> read the download stuff, thought I'd pick up the latest and greatest. A >> little note on >> the downloads page that icingaweb2 is mostly non-functional at the moment >> might >> have saved me a lot of time installing it! >> > > Those are hard words for a software still being in beta. Not something a > developer would want to hear in terms of helping you out (for free that is). > Now I truly feel bad. I didn't mean to insult you or any of the folks working on icinga2, nor make you feel discouraged. After all, I'm giving it a definite spin, and if, no, WHEN it works I'll engineer it into our workflow and retire the older nagios stuff. And, I didn't mean to give a condemnatory sort of sound to it. Quite the opposite, I am an eager user anxious to try out the new goodies you and your team has put together. To be truthful, I was kinda expecting to get a response like: "You lout, it may have a few problems, but it's working better than that! You configured it wrong!" ... and apparently, I did! In following the install instructions, I read this: ( http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chaper/getting-started#setting-up-livestatus ) Tip Only install the livestatus feature if your web interface or addon requires you to do so (for example, Icinga Web 2). Icinga Classic UI and Icinga Web do not use Livestatus as backend. And from that, I concluded that livestatus was the only game in town for the Web 2 interface. Apparently, mistakenly, as a review of the "Configuring DB IDO" section mentions it is is used by icinga2 and Icinga Web 2, and also bears the same Tip as provided in the LiveStatus section, but implying that Web 2 requires the DB IDO interface... So, I'll take some time tomorrow and switch over to the DB IDO stuff. I'm being entirely honest and forthright here. I offer bug reports, reviews of documentation, first impressions, etc, to help the project. I am not spitting on you or your work. And I'm not one of the guys who criticises projects and never helps. If I think it is necessary, and no-one else seems to want to do it, I'll roll up my sleeves and code up a solution myself. If I didn't think your project would be useful, I wouldn't be bothering with it. No code is perfect (at least, within the first 20 years for large projects), and no project will ever do everything that everybody wishes it could. All of us involved in open source are totally insane working for free, but we each have our reasons, and usually making the world a better place is part of it. ( And so is the joy of solving problems, building a reputation for consulting work, and so on.) So, let me thank you for your efforts, and your helpful suggestions above. murf -- Steve Murphy
_______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
