Hi,
I'm looking for a way to make OMD's alerts (warning, critical, ok, up,
down) available as a newsfeed.
On separate instances of nagios and icinga, I used blosxom, which is
easy to install and configure. Inside OMD, check_mk is my leading
solution - how can I integrate a newsfeed here? Can I
Hi,
since check_mk 1.2.4 has the possibility to check SAP services, and OMD
(1.11-20140220) still comes with 1.2.2p2, I want to update the contained
check_mk component.
Is this possible? If so, what is the diffence between installing the
package directly and inside OMD, except from the
break. Do it on a test setup first.
See README.setup_in_omd in the tarball documentation directory.
On Mon, Feb 24, 2014 at 2:59 PM, Werner Flamme werner.fla...@ufz.de wrote:
Hi,
since check_mk 1.2.4 has the possibility to check SAP services, and OMD
(1.11-20140220) still comes with 1.2.2p2
n path.
>
> Andreas already mentioned it. I am in progress integrating Python 2.7
> into OMD for all supported platforms.
> This Python is fully independent from the system global Python installation.
>
> Best regards
> Lars
>
> On 10.06.2016 12:31, Werner Flamme wrote:
&g
Hello OMDlers,
I just did a "zypper up", which pulled omd-daily and, as a dependency,
omd-daily-1.31.20160610 (from
http://labs.consol.de/repo/testing/sles11sp3/x86_64, which is defined as
a repository).
My next step was "omd sites", but then I had to stop:
Sven Nierlein [10.06.2016 12:35]:
> Hi,
>
> you cannot install the sp3 rpm on sp4. Unfortunatly, there are no sp4 packages
> yet. But you could try to build the rpms manually.
>
> Cheers,
> Sven
Hi Sven,
you do not tell me that there is libpython2.7 for SLES 11 SP3 (which is
out of
Stephen Berg (Contractor) [08.07.2016 12:53]:
> I got one omd site running 1.31.20160503 and have no issues there. I
> installed 1.31.20160708 and started to work up a new site because I'm
> starting to transition to using WATO on this system which is my main
> one, and eventually my seven
Hi everyone,
I updated to release 1.31.20160708 on friday with one instance. I
stopped the instance, did a "omd update" and started the instance again.
But now I get an error:
--- snip ---
$ omd start
Starting mkeventd...Traceback (most recent call last):
File "/omd/sites/sapmon/bin/mkeventd",
Werner Flamme [11.07.2016 10:01]:
> Hi everyone,
>
>
> But what is even worse that not being able to use mkeventd is that there
> are no results coming in any more. The last check results from all
> systems are from 2016-07-08 14:05, that was the moment I did the upd
tmy...@wellsfargo.com [20.09.2016 14:43]:
> Hello,
>
> OMD Version 1.30
> RHEL 6
>
>
> I followed the FAQ instructions: "Moving omd to another location than
> /opt/omd". After the move and updating the sym links, OMD starts up as
> expected but my host checks are failing with the following
tmy...@wellsfargo.com [20.09.2016 15:51]:
>
> After the change and a site restart, I am getting:
>
> Return code of 126 is out of bounds - plugin may be missing
>
> -rwsr-x--- 1 root root 179396 Sep 19 17:10 check_icmp
My check_icmp belongs to group omd, not to group root. And my site
Robert Sander [28.11.2016 13:38]:
> On 28.11.2016 13:31, Werner Flamme wrote:
>
>> Since SLES 12 comes with Apache 2.4, those lines should not be active,
>> and on page <https://httpd.apache.org/docs/2.4/upgrading.html> you can
>> read (in section "Compile-Tim
Hi,
on Saturday evening, I updated my central monitoring host from SLES 11
SP4 to SLES 12 SP1.
Among other problems, I saw Apache not starting with OMD instances. The
reason were those lines in /omd/sites/*/etc/apache/apache.conf that
required to load mod_authn_default and mod_authz_default.
Robert Sander [28.11.2016 14:10]:
> On 28.11.2016 14:05, Werner Flamme wrote:
>> Robert Sander [28.11.2016 13:38]:
>>> On 28.11.2016 13:31, Werner Flamme wrote:
>>>
>>>> Since SLES 12 comes with Apache 2.4, those lines should not be active,
>>>
Werner Flamme [28.11.2016 15:46]:
> Hi,
>
> on 10th November I asked what do do with the "Exception in icon plugin!"
> error in 2.11.-labs-edition of OMD.
This strange behaviour went away after switching back from icinga core
to nagios core.
I wonder why the icinga core op
Dennis Sweben [23.03.2017 11:03]:
> Hi Werner,
> “I'm not sure, but do you reach the client at all? Is xinetd running, is
> /etc/xinetd.d/check_mk active?”
>
> I can’t even get it to run on the client iself ☺
How that? AFAIK all checks are run via xinetd. xinetd listens at port
6556, and a
Dennis Sweben [23.03.2017 09:59]:
> Hi all,
>
> I’m trying to install the agent on an SLES11SP4 server.
>
> I have copied the check_mk_agent.linux from my monitoring server to
> /usr/bin/check_mk_agent
> #sudo cp check_mk_agent.linux /usr/bin/check_mk_agent
> Made sure its executable:
> #sudo
Imre Bertalan [17.01.2018 09:39]:
> Hey Forum!
>
> I'm using NginX ever since I'm working with webservers, but have not used
> apache yet. (Didn't have to). Therefore, the configurations for OMD looks
> very confusing for me. My main issue yet is to install an SSL certificate
> for my omd
18 matches
Mail list logo