Hey, I'm a total nube, so give me a little slack and a little info,
and I may step beyond that quickly.

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.

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?  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!

murf




-- 

Steve Murphy
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to