From muratoetzi at freenet.de Tue Jul 2 22:01:57 2013
From: muratoetzi at freenet.de (muratoetzi at freenet.de)
Date: Tue, 02 Jul 2013 22:01:57 +0200
Subject: [omd-users] check_mk_agent logwatch.cfg rewriting funktioniert nicht
Message-ID: <69a703bf3b257f5612757669faf3d9b4@email.freenet.de>
Hallo zusammen,
Ich habe folgende Umgebung:
CENTOS 6.4
OMD 1.00
check_mk-agent-1.2.2p1-1
check_mk-agent-logwatch-1.2.2p1-1
In der Logwatch.cfg habe ich das rewriting laut Besipiel definiert.
/var/log/messages
?C Error: (.*)
?R There is a Error: 1
Wenn ich den Agenten lokal ausf?hre bekomme ich die Fehlermeldung:
<<>>
CANNOT READ CONFIG FILE: Invalid regular expression in line ' R There is a Error: 1'
Habt ihr eine Idee, woran das liegen k?nnte.
Danke und Gr??e
Murat?
---
Alle Postf?cher an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! Rundum gl?cklich mit freenetMail
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logwatch.cfg
Type: application/octet-stream
Size: 2369 bytes
Desc: not available
URL:
From digestr at gmail.com Wed Jul 3 08:53:14 2013
From: digestr at gmail.com (readers digest)
Date: Wed, 3 Jul 2013 10:53:14 +0400
Subject: [omd-users] Distributed Monitoring with OMD
Message-ID:
Hello Team,
I am new to Nagios and OMD. When I was trying to implement a monitoring
system for my client; I came across omd which gives an excellent graphical
interface.
I have installed it on a test system and was able to connect some other
linux and windows machines to be monitored. How ever I was wondering if
there is a documentation available on how to set up a distributed
monitoring system; i.e my client has offices in different locations. They
need to monitor devices behind NAT on all these locations. How can we set
up OMD in such a way that these sites are monitored individually and the
central location can collect data from all these locations?
Thanks for your help!
Best Regards!
/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From zstevens at zynga.com Wed Jul 3 18:10:07 2013
From: zstevens at zynga.com (Zach Stevens)
Date: Wed, 3 Jul 2013 16:10:07 +0000
Subject: [omd-users] ruleset replication?
Message-ID:
Greetings all,
I have an environment with several check_mk/OMD servers. They are all running OMD 1.0 , check_mk 1.2.2p2.
WATO distributed monitoring replication works great but is there a good/best way to replicate the rulesets (parameters for checks, etc?) with out replicating the hosts from server to server? I don't want the OMD servers to all monitor the same hosts.
Thanks,
Zach Stevens
Linux Systems Administrator | Zynga
415-470-6021 | Skype: zachatzynga
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From cmd3187 at gmail.com Fri Jul 12 19:47:15 2013
From: cmd3187 at gmail.com (Carmen De Vito)
Date: Fri, 12 Jul 2013 13:47:15 -0400
Subject: [omd-users] Question about site.conf and omd config
Message-ID:
Hello,
I am currently experimenting with Puppet and OMD to create a distributed
monitoring solution. I have puppet modifying the contents of the
OMD_ROOT/etc/omd/site.conf file and restarting the site, under the
assumption that it would take those variables and apply them to my setup.
What I have found is that the changes are not applied on the rest of the
site configuration unless "omd config/cp/mv/upgrade" commands are run.
Does anyone know of a way to have OMD forcibly read the whole site.conf and
reapply those variables to the configuration?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From James.Cross at uea.ac.uk Mon Jul 15 13:10:02 2013
From: James.Cross at uea.ac.uk (Jimmy Cross)
Date: Mon, 15 Jul 2013 12:10:02 +0100
Subject: [omd-users] Question with regards to HTTPS
In-Reply-To: <51C84576.9090800@uea.ac.uk>
References: <51C82140.1080507@uea.ac.uk>
<51C826B9.50500@uea.ac.uk>
<51C84576.9090800@uea.ac.uk>
Message-ID: <51E3D88A.6080401@uea.ac.uk>
Hi All,
Just to let you all know that I fixed the http to https issue by using
the following rule on Ubuntu 12.04 in the apache2 default config file.
ServerAdmin webmaster at localhost
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R,L]
DocumentRoot /var/www
Hope that helps someone
Best wishes
Jimmy
On 24/06/13 14:11, Jimmy Cross wrote:
> Hi Marcel,
>
> Many thanks again for your help, I have tried what you suggested and
> it doesn't seem to have made a difference.
>
> I have also tried to edit the site specific file:
> etc/apache/conf.d/site.conf
>
> With that I get:
> 403 Forbidden
> You dont have pemission to access /hpc/thruk/startup.html on this server.
>
> Anything that I might be able to try or check?
>
> Best wishes
> Jimmy
>
>
>
> On 24/06/13 12:08, Marcel Schulte wrote:
>> Hi Jimmy,
>>
>> I'm not on Ubuntu but on Debian at another system so maybe the paths
>> are similar...
>>
>> I'd try to copy /etc/apache2/sites-available/default-ssl to
>> /etc/apache2/sites-available/default-ssl-with-rewrite and put the
>> modifications at the end of that file. Second step would be to link
>> that new file to /etc/apache2/sites-enabled/ and
>> restart apache.
>>
>> Quick and dirty, no warranty this works ;-)
>>
>> HTH,
>> Marcel
>>
>> 2013/6/24 Jimmy Cross :
>>> Hi Marcel,
>>>
>>> Many thanks for your prompt reply, sorry I should have said I am
>>> running
>>> Ubuntu 12.04.
>>> Do you know which file I should be looking at adding those
>>> directives to on
>>> that distro?
>>>
>>> Best wishes
>>> Jimmy
>>>
>>>
>>>
>>> On 24/06/13 11:45, Marcel Schulte wrote:
>>>> Hi Jimmy,
>>>>
>>>> We added this to the end of /etc/httpd/conf.d/ssl.conf (RH6, OMD
>>>> running own (Sub-)Apache):
>>>>
>>>> RewriteEngine on
>>>> RewriteCond %{HTTPS} off
>>>> RewriteCond %{HTTPS_HOST} !^hostname\.domain\.tld [NC]
>>>> RewriteRule ^.*$ https://hostname.domain.tld%{REQUEST_URI} [L,R]
>>>>
>>>> ...this ensures redirected hostname is always hostname.domain.tld and
>>>> http gets https.
>>>>
>>>> HTH,
>>>> Marcel
>>>>
>>>>
>>>>
>>>>
>>>> 2013/6/24 Jimmy Cross :
>>>>> Hi All,
>>>>>
>>>>> I am attempting to setup https on my OMD server, re-direction
>>>>> works when
>>>>> I
>>>>> got straight to server root:
>>>>>
>>>>> http:\\myserver.co.uk\
>>>>>
>>>>> will re-direct to https ok
>>>>>
>>>>> I achieved this by changing the main apache config file.
>>>>>
>>>>> However when I attempt to go
>>>>>
>>>>> http:\myserver.co.uk\site\thruk
>>>>>
>>>>> It will not re-direct to https.
>>>>>
>>>>> Could someone please let me know which files I should be looking
>>>>> at in
>>>>> order
>>>>> to ensure that everything will be re-directed through https.
>>>>>
>>>>> Many thanks in advance
>>>>>
>>>>> Best wishes
>>>>> Jimmy
>>>>>
>>>>> --
>>>>> -----------------------------
>>>>> Mr James Cross
>>>>> Linux Systems Developer
>>>>> University of East Anglia
>>>>> Norwich Research Park
>>>>> ITCS
>>>>> Norwich, Norfolk
>>>>> NR4 7TJ
>>>>>
>>>>> Information Services
>>>>>
>>>>> _______________________________________________
>>>>> omd-users mailing list
>>>>> omd-users at lists.mathias-kettner.de
>>>>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
>>>
>>>
>>> --
>>> -----------------------------
>>> Mr James Cross
>>> Linux Systems Developer
>>> University of East Anglia
>>> Norwich Research Park
>>> ITCS
>>> Norwich, Norfolk
>>> NR4 7TJ
>>>
>>> Information Services
>>>
>
>
--
-----------------------------
Mr James Cross
Linux Systems Developer
University of East Anglia
Norwich Research Park
ITCS
Norwich, Norfolk
NR4 7TJ
Information Services
From James.Cross at uea.ac.uk Mon Jul 15 15:22:02 2013
From: James.Cross at uea.ac.uk (Jimmy Cross)
Date: Mon, 15 Jul 2013 14:22:02 +0100
Subject: [omd-users] Auto host creation with Active Directory
Message-ID: <51E3F77A.20904@uea.ac.uk>
Hi All,
Before starting on developing this I'm Just enquiring if anyone has
managed automatic host configuration by syncing with Active Directory
using VAS or similar?
Best wishes
Jimmy
--
-----------------------------
Mr James Cross
Linux Systems Developer
University of East Anglia
Norwich Research Park
ITCS
Norwich, Norfolk
NR4 7TJ
Information Services
From tfines at digitalriver.com Wed Jul 17 00:39:27 2013
From: tfines at digitalriver.com (Ted Fines)
Date: Tue, 16 Jul 2013 22:39:27 +0000
Subject: [omd-users] Errors with Install from repo on Scientific Linux 6.4
Message-ID: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
Hi,
I have installed omd-1.00 from the repo onto Scientific Linux x86_64. No problems getting dependencies met.
"yum search omd-" returns both omd-1.00 and omd-0.52. "yum install omd" attempts to install version 0.52. I can't say that is 'wrong' or 'broken' but it is unusual to offer two versions of the same product like that, and that "yum install" would default to the older one. If I do "yum install omd-1.00" it installs that one.
OK, so that install seemed to work. But then...
The key issue it seems is that everything is getting installed in /opt/omd (like the web site reads), but all configuration files for omd are set for /omd/.
For instance, the /etc/fstab mount point entry for instance is /omd/sites//tmp. (no preceding /opt/) Here's the actual line: "tmpfs /omd/sites/TestSite/tmp tmpfs noauto,user,mode=755,uid=TestSite,gid=TestSite 0 0"
For instance pt. 2, the rpm installs the symlink /usr/bin/omd, but this links to /omd/versions/default/bin/omd (again, no preceding /opt)
Also, "omd create TestSite" successfully adds an entry to /etc/fstab, but it doesn't mount it. If I mount it by hand it mounts fine. Again though, it mounts on /omd, and the omd installer doesn't create a symlink.
So I thought, maybe it just needs a symlink. I created one with "ln -s /opt/omd /omd".
Then onto "omd start TestSite":
# omd start TestSite
Starting dedicated Apache for site TestSite...OK
Starting rrdcached...OK
Starting npcd...touch: cannot touch `/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No such file or directory
chown: cannot access `/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No such file or directory
An Error occured while reading your config on line 197
Message was: "Could not open pidfile '/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No such file or directory"
OK
/omd/sites/TestSite/etc/rc.d/80-nagios: line 66: /omd/sites/TestSite/tmp/nagios/nagios.cfg: No such file or directory
Nagios configuration file /omd/sites/TestSite/tmp/nagios/nagios.cfg not found. Terminating...
Initializing Crontab...You (TestSite) are not allowed to use this program (/usr/bin/crontab)
See crontab(1) for more information
close failed in file object destructor:
Error in sys.excepthook:
Original exception was:
ERROR
As you can see from the error above, the "pnp4nagios" subdirectory doesn't get created. I tried creating it and its 'run' subdirectory by hand, and creating the 'nagios' subdirectory under tmp by hand too and starting again. The nagios.cfg file it created there then produced a bunch of errors because all of its config was for /omd instead of /opt/omd.
You get the idea. The installed config just doesn't match the install location is what seems to be the problem. Any advice or help would be appreciated.
Thanks,
Ted
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pitchfork at pnp4nagios.org Wed Jul 17 06:08:05 2013
From: pitchfork at pnp4nagios.org (Joerg Linge)
Date: Wed, 17 Jul 2013 06:08:05 +0200
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
In-Reply-To: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
Message-ID: <643BA6B8-9448-4DAD-8423-577135F4DB8F@pnp4nagios.org>
Am 17.07.2013 um 00:39 schrieb Ted Fines :
> Hi,
Hi Ted,
>
> I have installed omd-1.00 from the repo onto Scientific Linux x86_64. No problems getting dependencies met.
There is OMD support for Scientific Linux?
IMHO there is no Support for this Linux Distribution
See http://git.mathias-kettner.de/git/?p=omd.git;a=tree;f=distros;h=ca462a878017e31d4f1e5dde90b7bfacd922ad03;hb=HEAD
Which repo do you use?
Joerg
>
> ?yum search omd-? returns both omd-1.00 and omd-0.52. ?yum install omd? attempts to install version 0.52. I can?t say that is ?wrong? or ?broken? but it is unusual to offer two versions of the same product like that, and that ?yum install? would default to the older one. If I do ?yum install omd-1.00? it installs that one.
>
> OK, so that install seemed to work. But then?
>
> The key issue it seems is that everything is getting installed in /opt/omd (like the web site reads), but all configuration files for omd are set for /omd/.
>
> For instance, the /etc/fstab mount point entry for instance is /omd/sites//tmp. (no preceding /opt/) Here?s the actual line: ?tmpfs /omd/sites/TestSite/tmp tmpfs noauto,user,mode=755,uid=TestSite,gid=TestSite 0 0?
> For instance pt. 2, the rpm installs the symlink /usr/bin/omd, but this links to /omd/versions/default/bin/omd (again, no preceding /opt)
>
> Also, ?omd create TestSite? successfully adds an entry to /etc/fstab, but it doesn?t mount it. If I mount it by hand it mounts fine. Again though, it mounts on /omd, and the omd installer doesn?t create a symlink.
>
> So I thought, maybe it just needs a symlink. I created one with ?ln ?s /opt/omd /omd?.
>
> Then onto ?omd start TestSite?:
>
> # omd start TestSite
> Starting dedicated Apache for site TestSite...OK
> Starting rrdcached...OK
> Starting npcd...touch: cannot touch `/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No such file or directory
> chown: cannot access `/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No such file or directory
> An Error occured while reading your config on line 197
> Message was: "Could not open pidfile '/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No such file or directory"
> OK
> /omd/sites/TestSite/etc/rc.d/80-nagios: line 66: /omd/sites/TestSite/tmp/nagios/nagios.cfg: No such file or directory
> Nagios configuration file /omd/sites/TestSite/tmp/nagios/nagios.cfg not found. Terminating...
> Initializing Crontab...You (TestSite) are not allowed to use this program (/usr/bin/crontab)
> See crontab(1) for more information
> close failed in file object destructor:
> Error in sys.excepthook:
>
> Original exception was:
> ERROR
>
> As you can see from the error above, the ?pnp4nagios? subdirectory doesn?t get created. I tried creating it and its ?run? subdirectory by hand, and creating the ?nagios? subdirectory under tmp by hand too and starting again. The nagios.cfg file it created there then produced a bunch of errors because all of its config was for /omd instead of /opt/omd.
>
> You get the idea. The installed config just doesn?t match the install location is what seems to be the problem. Any advice or help would be appreciated.
>
> Thanks,
> Ted
> _______________________________________________
> omd-users mailing list
> omd-users at lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4154 bytes
Desc: not available
URL:
From yoshi314 at gmail.com Wed Jul 17 08:08:51 2013
From: yoshi314 at gmail.com (marcin kowalski)
Date: Wed, 17 Jul 2013 08:08:51 +0200
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
In-Reply-To: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
Message-ID:
What version of SL are you using?
I remember that on RHEL5 based systems there was a problem with mount not
following symlinks, and a small patch to omd binary is required. It's not
necessary for more recent EL systems, and i think EL5 systems are
eventually getting a patch.
the patch in question is : ( for /usr/bin/omd )
(....)
--- file("/etc/fstab", "a+").write("tmpfs %s tmpfs
noauto,user,mode=755,uid=%s,gid=%s 0 0\n" % \
+++ file("/etc/fstab", "a+").write("tmpfs /opt%s tmpfs
noauto,user,mode=755,uid=%s,gid=%s 0 0\n" % \
(....)
2013/7/17 Ted Fines
> Hi,****
>
> ** **
>
> I have installed omd-1.00 from the repo onto Scientific Linux x86_64. No
> problems getting dependencies met.****
>
> ** **
>
> ?yum search omd-? returns both omd-1.00 and omd-0.52. ?yum install omd?
> attempts to install version 0.52. I can?t say that is ?wrong? or ?broken?
> but it is unusual to offer two versions of the same product like that, and
> that ?yum install? would default to the older one. If I do ?yum install
> omd-1.00? it installs that one.****
>
> ** **
>
> OK, so that install seemed to work. But then?****
>
> ** **
>
> The key issue it seems is that everything is getting installed in /opt/omd
> (like the web site reads), but all configuration files for omd are set for
> /omd/.****
>
> ** **
>
> For instance, the /etc/fstab mount point entry for instance is
> /omd/sites//tmp. (no preceding /opt/) Here?s the actual line:
> ?tmpfs /omd/sites/TestSite/tmp tmpfs
> noauto,user,mode=755,uid=TestSite,gid=TestSite 0 0?****
>
> For instance pt. 2, the rpm installs the symlink /usr/bin/omd, but this
> links to /omd/versions/default/bin/omd (again, no preceding /opt)****
>
> ** **
>
> Also, ?omd create TestSite? successfully adds an entry to /etc/fstab, but
> it doesn?t mount it. If I mount it by hand it mounts fine. Again though,
> it mounts on /omd, and the omd installer doesn?t create a symlink.****
>
> ** **
>
> So I thought, maybe it just needs a symlink. I created one with ?ln ?s
> /opt/omd /omd?.****
>
> ** **
>
> Then onto ?omd start TestSite?:****
>
> ** **
>
> # omd start TestSite****
>
> Starting dedicated Apache for site TestSite...OK****
>
> Starting rrdcached...OK****
>
> Starting npcd...touch: cannot touch
> `/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No such file or directory
> ****
>
> chown: cannot access `/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No
> such file or directory****
>
> An Error occured while reading your config on line 197****
>
> Message was: "Could not open pidfile
> '/omd/sites/TestSite/tmp/pnp4nagios/run/npcd.pid': No such file or
> directory"****
>
> OK****
>
> /omd/sites/TestSite/etc/rc.d/80-nagios: line 66:
> /omd/sites/TestSite/tmp/nagios/nagios.cfg: No such file or directory****
>
> Nagios configuration file /omd/sites/TestSite/tmp/nagios/nagios.cfg not
> found. Terminating...****
>
> Initializing Crontab...You (TestSite) are not allowed to use this program
> (/usr/bin/crontab)****
>
> See crontab(1) for more information****
>
> close failed in file object destructor:****
>
> Error in sys.excepthook:****
>
> ** **
>
> Original exception was:****
>
> ERROR****
>
> ** **
>
> As you can see from the error above, the ?pnp4nagios? subdirectory doesn?t
> get created. I tried creating it and its ?run? subdirectory by hand, and
> creating the ?nagios? subdirectory under tmp by hand too and starting
> again. The nagios.cfg file it created there then produced a bunch of
> errors because all of its config was for /omd instead of /opt/omd.****
>
> ** **
>
> You get the idea. The installed config just doesn?t match the install
> location is what seems to be the problem. Any advice or help would be
> appreciated.****
>
> ** **
>
> Thanks,****
>
> Ted****
>
> _______________________________________________
> omd-users mailing list
> omd-users at lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From omd at jens.kuehnel.org Wed Jul 17 08:22:35 2013
From: omd at jens.kuehnel.org (Jens Kuehnel)
Date: Wed, 17 Jul 2013 08:22:35 +0200
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
In-Reply-To: <643BA6B8-9448-4DAD-8423-577135F4DB8F@pnp4nagios.org>
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
<643BA6B8-9448-4DAD-8423-577135F4DB8F@pnp4nagios.org>
Message-ID: <51E6382B.1070202@jens.kuehnel.org>
Hi Ted, Hi J?rg,
>> I have installed omd-1.00 from the repo onto Scientific Linux
>> x86_64. No problems getting dependencies met.
> There is OMD support for Scientific Linux?
> IMHO there is no Support for this Linux Distribution See
> http://git.mathias-kettner.de/git/?p=omd.git;a=tree;f=distros;h=ca462a878017e31d4f1e5dde90b7bfacd922ad03;hb=HEAD
Scientific Linux and Centos are both RedHat Clones. I also run OMD with
Oracle Linux and it works as well.
>> The key issue it seems is that everything is getting installed in
>> /opt/omd (like the web site reads), but all configuration files for
>> omd are set for /omd/.
If you like you could move /opt/omd to someplace else and you only have
to point the symlink /omd/ to the new location.
> So I thought, maybe it just needs a symlink. I created one with ?ln ?s /opt/omd /omd?.
That should be created by the preinstall scriptlet of omd.rpm.
What version of util-linux-ng do you use? You need 2.17.2-12.9_el6_4.3
because that fixes a bug with mount and it looks like you run into that.
CU
Jens
From omd at jens.kuehnel.org Wed Jul 17 08:24:39 2013
From: omd at jens.kuehnel.org (Jens Kuehnel)
Date: Wed, 17 Jul 2013 08:24:39 +0200
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
In-Reply-To:
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
Message-ID: <51E638A7.3080407@jens.kuehnel.org>
Hi,
> I remember that on RHEL5 based systems there was a problem with mount
> not following symlinks, and a small patch to omd binary is required.
> It's not necessary for more recent EL systems, and i think EL5 systems
> are eventually getting a patch.
> the patch in question is : ( for /usr/bin/omd )
This patch is not necessary anymore. Just update to the current version
of util-linux-ng.
CU
Jens
From pitchfork at pnp4nagios.org Wed Jul 17 08:43:05 2013
From: pitchfork at pnp4nagios.org (Joerg Linge)
Date: Wed, 17 Jul 2013 08:43:05 +0200
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
In-Reply-To: <51E6382B.1070202@jens.kuehnel.org>
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
<643BA6B8-9448-4DAD-8423-577135F4DB8F@pnp4nagios.org>
<51E6382B.1070202@jens.kuehnel.org>
Message-ID:
Am 17.07.2013 um 08:22 schrieb Jens Kuehnel :
> Hi Ted, Hi J?rg,
>
>>> I have installed omd-1.00 from the repo onto Scientific Linux
>>> x86_64. No problems getting dependencies met.
>
>> There is OMD support for Scientific Linux?
>> IMHO there is no Support for this Linux Distribution See
>> http://git.mathias-kettner.de/git/?p=omd.git;a=tree;f=distros;h=ca462a878017e31d4f1e5dde90b7bfacd922ad03;hb=HEAD
> Scientific Linux and Centos are both RedHat Clones. I also run OMD with
> Oracle Linux and it works as well.
But this Distribution is not supported and tested by the OMD Team.
J?rg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4154 bytes
Desc: not available
URL:
From tfines at digitalriver.com Wed Jul 17 15:07:22 2013
From: tfines at digitalriver.com (Ted Fines)
Date: Wed, 17 Jul 2013 13:07:22 +0000
Subject: [omd-users] Errors with Install from repo on Scientific
Linux 6.4
In-Reply-To:
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
<643BA6B8-9448-4DAD-8423-577135F4DB8F@pnp4nagios.org>
<51E6382B.1070202@jens.kuehnel.org>
Message-ID: <544005354DA4124C8C18F990595478D061F585@DC2MBX02.mpls.digitalriver.com>
Yes, I do realize using SL6.4 is going off the reservation. Good to know others have had luck with OMD on other RHEL clone distros, but I do understand there are differences and YMMV!
-----Original Message-----
From: omd-users-bounces at lists.mathias-kettner.de [mailto:omd-users-bounces at lists.mathias-kettner.de] On Behalf Of Joerg Linge
Sent: Wednesday, July 17, 2013 1:43 AM
Cc: omd-users at lists.mathias-kettner.de
Subject: Re: [omd-users] Errors with Install from repo on Scientific Linux 6.4
Am 17.07.2013 um 08:22 schrieb Jens Kuehnel :
> Hi Ted, Hi J?rg,
>
>>> I have installed omd-1.00 from the repo onto Scientific Linux
>>> x86_64. No problems getting dependencies met.
>
>> There is OMD support for Scientific Linux?
>> IMHO there is no Support for this Linux Distribution See
>> http://git.mathias-kettner.de/git/?p=omd.git;a=tree;f=distros;h=ca462
>> a878017e31d4f1e5dde90b7bfacd922ad03;hb=HEAD
> Scientific Linux and Centos are both RedHat Clones. I also run OMD
> with Oracle Linux and it works as well.
But this Distribution is not supported and tested by the OMD Team.
J?rg
From tfines at digitalriver.com Wed Jul 17 16:49:34 2013
From: tfines at digitalriver.com (Ted Fines)
Date: Wed, 17 Jul 2013 14:49:34 +0000
Subject: [omd-users] Errors with Install from repo on
Scientific Linux 6.4
In-Reply-To: <544005354DA4124C8C18F990595478D061F585@DC2MBX02.mpls.digitalriver.com>
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
<643BA6B8-9448-4DAD-8423-577135F4DB8F@pnp4nagios.org>
<51E6382B.1070202@jens.kuehnel.org>
<544005354DA4124C8C18F990595478D061F585@DC2MBX02.mpls.digitalriver.com>
Message-ID: <544005354DA4124C8C18F990595478D0620659@DC2MBX02.mpls.digitalriver.com>
For posterity's sake, I have it working on Scientific Linux 6.4 on x86_64. It looks like the same adjustments need to be made for SL6.4 as for RHEL6.4 or CentOS 6.4. The issue arises because of 6.4 doesn't want any symbolic links in path names in /etc/fstab. I do have one change suggestion for the omd devs also.
Here's what I did (two things):
ONE
Read http://blog.christian-stankowic.de/?p=5312&lang=en
He outlines the problem and fix, just for OMD 0.56.
Do this right after installing OMD and before creating any sites.
For OMD 1.00, the change to be made is the same as he outlines, but it is at line 794:
Old line starts with: "file("/etc/fstab", "a+").write("tmpfs %s tmpfs"
New line starts with: "file("/etc/fstab", "a+").write("tmpfs /opt%s tmpfs"
TWO
"omd start " will return a crontab-related error, e.g. "Initializing Crontab...You (TestSite) are not allowed to use this program (/usr/bin/crontab)"
Problem: The OS doesn't allow any users other than root to use crontab. I don't know when this was changed, but that's how it is now.
Fix: As root, edit /etc/cron.allow and add the user/site name. One per line. Fortunately omd generates the crontab for a site on every start, so just do "omd stop " and "omd start " and it will generate the crontab and start correctly.
I think the OMD devs will need to update the omd "create" script to add the site user to /etc/cron.allow.
If I run into other issues down the road I'll post (or ask) them.
Thanks,
Ted
-----Original Message-----
From: omd-users-bounces at lists.mathias-kettner.de [mailto:omd-users-bounces at lists.mathias-kettner.de] On Behalf Of Ted Fines
Sent: Wednesday, July 17, 2013 8:07 AM
To: omd-users at lists.mathias-kettner.de
Subject: Re: [omd-users] Errors with Install from repo on Scientific Linux 6.4
Yes, I do realize using SL6.4 is going off the reservation. Good to know others have had luck with OMD on other RHEL clone distros, but I do understand there are differences and YMMV!
-----Original Message-----
From: omd-users-bounces at lists.mathias-kettner.de [mailto:omd-users-bounces at lists.mathias-kettner.de] On Behalf Of Joerg Linge
Sent: Wednesday, July 17, 2013 1:43 AM
Cc: omd-users at lists.mathias-kettner.de
Subject: Re: [omd-users] Errors with Install from repo on Scientific Linux 6.4
Am 17.07.2013 um 08:22 schrieb Jens Kuehnel :
> Hi Ted, Hi J?rg,
>
>>> I have installed omd-1.00 from the repo onto Scientific Linux
>>> x86_64. No problems getting dependencies met.
>
>> There is OMD support for Scientific Linux?
>> IMHO there is no Support for this Linux Distribution See
>> http://git.mathias-kettner.de/git/?p=omd.git;a=tree;f=distros;h=ca462
>> a878017e31d4f1e5dde90b7bfacd922ad03;hb=HEAD
> Scientific Linux and Centos are both RedHat Clones. I also run OMD
> with Oracle Linux and it works as well.
But this Distribution is not supported and tested by the OMD Team.
J?rg
_______________________________________________
omd-users mailing list
omd-users at lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/omd-users
From stephen.berg.ctr at nrlssc.navy.mil Wed Jul 17 16:57:17 2013
From: stephen.berg.ctr at nrlssc.navy.mil (Stephen Berg (Contractor))
Date: Wed, 17 Jul 2013 09:57:17 -0500
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
In-Reply-To: <544005354DA4124C8C18F990595478D0620659@DC2MBX02.mpls.digitalriver.com>
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
<643BA6B8-9448-4DAD-8423-577135F4DB8F@pnp4nagios.org>
<51E6382B.1070202@jens.kuehnel.org>
<544005354DA4124C8C18F990595478D061F585@DC2MBX02.mpls.digitalriver.com>
<544005354DA4124C8C18F990595478D0620659@DC2MBX02.mpls.digitalriver.com>
Message-ID:
On 07/17/2013 09:49 AM, Ted Fines wrote:
> TWO
> "omd start " will return a crontab-related error, e.g. "Initializing Crontab...You (TestSite) are not allowed to use this program (/usr/bin/crontab)"
> Problem: The OS doesn't allow any users other than root to use crontab. I don't know when this was changed, but that's how it is now.
> Fix: As root, edit /etc/cron.allow and add the user/site name. One per line. Fortunately omd generates the crontab for a site on every start, so just do "omd stop " and "omd start " and it will generate the crontab and start correctly.
>
> I think the OMD devs will need to update the omd "create" script to add the site user to /etc/cron.allow.
I have omd running on multiple SL6.4 systems here and have not seen this
issue on any of them. None of these systems have a cron.allow file
anywhere in /etc. Could that be something that was configured on your
system locally? I could be wrong, but I don't think it's set up from a
default install of SL.
--
Stephen Berg
Systems Administrator
NRL Code: 7320
Office: 228-688-5738
stephen.berg.ctr at nrlssc.navy.mil
From tfines at digitalriver.com Wed Jul 17 17:19:11 2013
From: tfines at digitalriver.com (Ted Fines)
Date: Wed, 17 Jul 2013 15:19:11 +0000
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
In-Reply-To:
References: <544005354DA4124C8C18F990595478D0615D82@DC2MBX02.mpls.digitalriver.com>
<643BA6B8-9448-4DAD-8423-577135F4DB8F@pnp4nagios.org>
<51E6382B.1070202@jens.kuehnel.org>
<544005354DA4124C8C18F990595478D061F585@DC2MBX02.mpls.digitalriver.com>
<544005354DA4124C8C18F990595478D0620659@DC2MBX02.mpls.digitalriver.com>
Message-ID: <544005354DA4124C8C18F990595478D0620AAF@DC2MBX02.mpls.digitalriver.com>
You are correct. Ignore my point #2. Per our default security policies, /etc/cron.allow is created. If it does not exist, which by default it does not, all users may use crontab. I had forgotten that we make that setting. Thanks!
-----Original Message-----
From: omd-users-bounces at lists.mathias-kettner.de [mailto:omd-users-bounces at lists.mathias-kettner.de] On Behalf Of Stephen Berg (Contractor)
Sent: Wednesday, July 17, 2013 9:57 AM
To: omd-users at lists.mathias-kettner.de
Subject: Re: [omd-users] Errors with Install from repo on Scientific Linux 6.4
On 07/17/2013 09:49 AM, Ted Fines wrote:
> TWO
> "omd start " will return a crontab-related error, e.g. "Initializing Crontab...You (TestSite) are not allowed to use this program (/usr/bin/crontab)"
> Problem: The OS doesn't allow any users other than root to use crontab. I don't know when this was changed, but that's how it is now.
> Fix: As root, edit /etc/cron.allow and add the user/site name. One per line. Fortunately omd generates the crontab for a site on every start, so just do "omd stop " and "omd start " and it will generate the crontab and start correctly.
>
> I think the OMD devs will need to update the omd "create" script to add the site user to /etc/cron.allow.
I have omd running on multiple SL6.4 systems here and have not seen this issue on any of them. None of these systems have a cron.allow file anywhere in /etc. Could that be something that was configured on your system locally? I could be wrong, but I don't think it's set up from a default install of SL.
--
Stephen Berg
Systems Administrator
NRL Code: 7320
Office: 228-688-5738
stephen.berg.ctr at nrlssc.navy.mil
_______________________________________________
omd-users mailing list
omd-users at lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/omd-users
From cncook001 at yahoo.com Wed Jul 17 22:51:17 2013
From: cncook001 at yahoo.com (Craig Cook)
Date: Wed, 17 Jul 2013 13:51:17 -0700 (PDT)
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
Message-ID: <1374094277.73091.YahooMailNeo@web164802.mail.gq1.yahoo.com>
>This patch is not necessary anymore. Just update to the current version of util-linux-ng.
What version should be installed?
I am using this on 6.4:
util-linux-ng.x86_64??????????????? 2.17.2-12.9.el6
Craig
From cncook001 at yahoo.com Wed Jul 17 22:57:16 2013
From: cncook001 at yahoo.com (Craig Cook)
Date: Wed, 17 Jul 2013 13:57:16 -0700 (PDT)
Subject: [omd-users] Errors with Install from repo on Scientific Linux
6.4
In-Reply-To: <1374094277.73091.YahooMailNeo@web164802.mail.gq1.yahoo.com>
References: <1374094277.73091.YahooMailNeo@web164802.mail.gq1.yahoo.com>
Message-ID: <1374094636.57543.YahooMailNeo@web164803.mail.gq1.yahoo.com>
Never mind, I just saw the post.
?2.17.2-12.9_el6_4.3
Craig
----- Original Message -----
From: Craig Cook
To: "omd-users at lists.mathias-kettner.de"
Cc:
Sent: Wednesday, July 17, 2013 4:51 PM
Subject: RE: [omd-users] Errors with Install from repo on Scientific Linux 6.4
>This patch is not necessary anymore. Just update to the current version of util-linux-ng.
What version should be installed?
I am using this on 6.4:
util-linux-ng.x86_64??????????????? 2.17.2-12.9.el6
Craig
From jersoncifuentes at gmail.com Thu Jul 25 16:50:44 2013
From: jersoncifuentes at gmail.com (Jerson Cifuentes)
Date: Thu, 25 Jul 2013 09:50:44 -0500
Subject: [omd-users] Fwd: trouble monitoring with SNMP
In-Reply-To:
References:
Message-ID:
Best Regards.
I recently had a server with centos 6 and 0.56 omd working properly.
Perform backup and a new facility in centos 6, but with omd 1.00
The backup is restored smoothly, customers monitored by check_mk client work
correctly.
But when I try with SNMP monitor always shows Error.
This is the error page check_mk:
Inventory failed for this host:
error
Incomplete or invalid response from SNMP agent
I checked and have the same snmp packages, correct community but still
fails.
Also issued the command and everything works out something like this:
. / check_mk - debug - try-inventory automation - contabi1
and introduces me an error
ERROR: SNMP Error
Trying inventory for ucd_cpu_util on contabi1
I appreciate the ideas to solve this problem
--
Jerson Cifuentes
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From schulte.marcel at gmail.com Thu Jul 25 18:40:35 2013
From: schulte.marcel at gmail.com (Marcel Schulte)
Date: Thu, 25 Jul 2013 18:40:35 +0200
Subject: [omd-users] Fwd: trouble monitoring with SNMP
In-Reply-To:
References:
Message-ID:
Hi Jerson,
had the same problem here with RH6.4 and latest (OS-) updates.
After downgrading all net-snmp packages to the second last one solved
this for us.
You could try the same on your CentOS 6 system... ('grep -i snmp
/var/log/yum.log' to get the updated packages and which version they
were installed before the upgrade)
Again, for me the OS update of the snmp packages caused the errors,
nothing regarding OMD.
HTH,
Marcel
2013/7/25 Jerson Cifuentes :
> Best Regards.
> I recently had a server with centos 6 and 0.56 omd working properly.
> Perform backup and a new facility in centos 6, but with omd 1.00
> The backup is restored smoothly, customers monitored by check_mk client work
> correctly.
> But when I try with SNMP monitor always shows Error.
> This is the error page check_mk:
>
> Inventory failed for this host:
> error
> Incomplete or invalid response from SNMP agent
>
> I checked and have the same snmp packages, correct community but still
> fails.
>
> Also issued the command and everything works out something like this:
>
> . / check_mk - debug - try-inventory automation - contabi1
>
> and introduces me an error
>
> ERROR: SNMP Error
> Trying inventory for ucd_cpu_util on contabi1
>
> I appreciate the ideas to solve this problem
>
> --
> Jerson Cifuentes
>
> _______________________________________________
> omd-users mailing list
> omd-users at lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
>
From jersoncifuentes at gmail.com Fri Jul 26 01:47:47 2013
From: jersoncifuentes at gmail.com (Jerson Cifuentes)
Date: Thu, 25 Jul 2013 18:47:47 -0500
Subject: [omd-users] Fwd: trouble monitoring with SNMP
In-Reply-To:
References:
Message-ID:
Thank you very much Marce for the help, I did what you recommended and it
worked immediately.
This is what I did:
[root at monitoreo2 ~]# grep -i snmp /var/log/yum.log
Jul 11 07:04:02 Updated: 1:net-snmp-libs-5.5-44.el6_4.2.x86_64
Jul 11 07:04:34 Updated: 1:net-snmp-5.5-44.el6_4.2.x86_64
Jul 11 07:15:56 Installed: perl-Net-SNMP-5.2.0-4.el6.noarch
Jul 11 07:16:00 Installed: 1:net-snmp-utils-5.5-44.el6_4.2.x86_64
[root at monitoreo2 ~]# yum downgrade net-snmp-libs net-snmp net-snmp-utils
Loaded plugins: fastestmirror, refresh-packagekit, security
Setting up Downgrade Process
Loading mirror speeds from cached hostfile
* base: centos.secrel.com.br
* epel: epel.gtdinternet.com
* extras: centos.secrel.com.br
* updates: centos.secrel.com.br
Resolving Dependencies
--> Running transaction check
---> Package net-snmp.x86_64 1:5.5-44.el6_4.1 will be a downgrade
---> Package net-snmp.x86_64 1:5.5-44.el6_4.2 will be erased
---> Package net-snmp-libs.x86_64 1:5.5-44.el6_4.1 will be a downgrade
---> Package net-snmp-libs.x86_64 1:5.5-44.el6_4.2 will be erased
---> Package net-snmp-utils.x86_64 1:5.5-44.el6_4.1 will be a downgrade
---> Package net-snmp-utils.x86_64 1:5.5-44.el6_4.2 will be erased
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================================================================================================================================
Package
Arch
Version
Repository Size
============================================================================================================================================================================================================================================
Downgrading:
net-snmp
x86_64
1:5.5-44.el6_4.1
updates 303 k
net-snmp-libs
x86_64
1:5.5-44.el6_4.1
updates 1.5 M
net-snmp-utils
x86_64
1:5.5-44.el6_4.1
updates 172 k
Transaction Summary
============================================================================================================================================================================================================================================
Downgrade 3 Package(s)
Total download size: 2.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/3):
net-snmp-5.5-44.el6_4.1.x86_64.rpm
| 303 kB 00:00
(2/3):
net-snmp-libs-5.5-44.el6_4.1.x86_64.rpm
| 1.5 MB 00:01
(3/3):
net-snmp-utils-5.5-44.el6_4.1.x86_64.rpm
| 172 kB 00:00
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total
675 kB/s | 2.0 MB 00:03
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing :
1:net-snmp-libs-5.5-44.el6_4.1.x86_64
1/6
Installing :
1:net-snmp-5.5-44.el6_4.1.x86_64
2/6
Installing :
1:net-snmp-utils-5.5-44.el6_4.1.x86_64
3/6
Cleanup :
1:net-snmp-utils-5.5-44.el6_4.2.x86_64
4/6
Cleanup :
1:net-snmp-5.5-44.el6_4.2.x86_64
5/6
Cleanup :
1:net-snmp-libs-5.5-44.el6_4.2.x86_64
6/6
Verifying :
1:net-snmp-5.5-44.el6_4.1.x86_64
1/6
Verifying :
1:net-snmp-libs-5.5-44.el6_4.1.x86_64
2/6
Verifying :
1:net-snmp-utils-5.5-44.el6_4.1.x86_64
3/6
Verifying :
1:net-snmp-utils-5.5-44.el6_4.2.x86_64
4/6
Verifying :
1:net-snmp-5.5-44.el6_4.2.x86_64
5/6
Verifying :
1:net-snmp-libs-5.5-44.el6_4.2.x86_64
6/6
Removed:
net-snmp.x86_64 1:5.5-44.el6_4.2
net-snmp-libs.x86_64
1:5.5-44.el6_4.2
net-snmp-utils.x86_64
1:5.5-44.el6_4.2
Installed:
net-snmp.x86_64 1:5.5-44.el6_4.1
net-snmp-libs.x86_64
1:5.5-44.el6_4.1
net-snmp-utils.x86_64
1:5.5-44.el6_4.1
Complete!
2013/7/25 Marcel Schulte
> Hi Jerson,
>
> had the same problem here with RH6.4 and latest (OS-) updates.
>
> After downgrading all net-snmp packages to the second last one solved
> this for us.
>
> You could try the same on your CentOS 6 system... ('grep -i snmp
> /var/log/yum.log' to get the updated packages and which version they
> were installed before the upgrade)
>
> Again, for me the OS update of the snmp packages caused the errors,
> nothing regarding OMD.
>
> HTH,
> Marcel
>
> 2013/7/25 Jerson Cifuentes :
> > Best Regards.
> > I recently had a server with centos 6 and 0.56 omd working properly.
> > Perform backup and a new facility in centos 6, but with omd 1.00
> > The backup is restored smoothly, customers monitored by check_mk client
> work
> > correctly.
> > But when I try with SNMP monitor always shows Error.
> > This is the error page check_mk:
> >
> > Inventory failed for this host:
> > error
> > Incomplete or invalid response from SNMP agent
> >
> > I checked and have the same snmp packages, correct community but still
> > fails.
> >
> > Also issued the command and everything works out something like this:
> >
> > . / check_mk - debug - try-inventory automation - contabi1
> >
> > and introduces me an error
> >
> > ERROR: SNMP Error
> > Trying inventory for ucd_cpu_util on contabi1
> >
> > I appreciate the ideas to solve this problem
> >
> > --
> > Jerson Cifuentes
> >
> > _______________________________________________
> > omd-users mailing list
> > omd-users at lists.mathias-kettner.de
> > http://lists.mathias-kettner.de/mailman/listinfo/omd-users
> >
>
--
Jerson Cifuentes
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From david.corral at gpex.es Tue Jul 30 09:22:02 2013
From: david.corral at gpex.es (David Corral)
Date: Tue, 30 Jul 2013 09:22:02 +0200
Subject: [omd-users] safe way to upgrade from 0.56 to 1.00
Message-ID: <51F7699A.6050200@gpex.es>
Hello list,
after some research, I'm not seeing a clear way to upgrade from 0.56 to
1.00 via package. I've updated from repositories, and I noticed a new
"omd-1.00" package is available. Should I purge the previous one
(omd-0.56?), or keep both and change apache configuration somewhere? Is
the configuration kept between versions?
Thanks in advance.
Dave.
From Klipp.M at eppendorf.de Tue Jul 30 10:41:34 2013
From: Klipp.M at eppendorf.de (Marco Klipp)
Date: Tue, 30 Jul 2013 08:41:34 +0000
Subject: [omd-users] safe way to upgrade from 0.56 to 1.00
In-Reply-To: <51F7699A.6050200@gpex.es>
References: <51F7699A.6050200@gpex.es>
Message-ID: <50AE934A0F41EB4FB259B7C02FE63D782E600B5D@mail-hh-04.emea.epglobal.org>
Hello Dave,
Updates in OMD are really easy.
Install the version 1.00.
The sites are still in version 0.56.
You have to upgrade them manually, e.g.
cmd> omd update prod
This will upgrade your site PROD from version 0.56 to 1.00
See this guide, but it's in german...
http://mathias-kettner.de/omd_update.html
regards
Marco
Am Dienstag, den 30.07.2013, 09:22 +0200 schrieb David Corral:
Hello list,
after some research, I'm not seeing a clear way to upgrade from 0.56 to
1.00 via package. I've updated from repositories, and I noticed a new
"omd-1.00" package is available. Should I purge the previous one
(omd-0.56?), or keep both and change apache configuration somewhere? Is
the configuration kept between versions?
Thanks in advance.
Dave.
_______________________________________________
omd-users mailing list
omd-users at lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/omd-users
________________________________
This email including its attachments is intended for the person or entity only to which it is addressed. It may contain confidential and/or privileged material. Any review, forwarding, dissemination, other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this email in error, please contact the sender and delete the material from any computer system.
________________________________
Eppendorf AG, Hamburg, Barkhausenweg 1, 22339 Hamburg, Amtsgericht Hamburg HRB 76249
Vors. des Aufsichtsrats: Klaus Fink
Vorstand: Dr. Dirk Ehlers (Vorsitzender), Detmar Ammermann, Dr. Heinz G. Koehn, Dr. Michael Schroeder
Eppendorf Instrumente GmbH, Hamburg, Amtsgericht Hamburg, HRB 69077
Gesch?ftsf?hrer: Rainer Treptow, Dr. Wilhelm Pluester
Eppendorf Liquid Handling GmbH, Hamburg, Amtsgericht Hamburg, HRB 92250
Gesch?ftsf?hrer: Boris von Beichmann
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wrjacqmein at gmail.com Tue Jul 30 16:56:59 2013
From: wrjacqmein at gmail.com (Bill Jacqmein)
Date: Tue, 30 Jul 2013 10:56:59 -0400
Subject: [omd-users] safe way to upgrade from 0.56 to 1.00
In-Reply-To: <51F7699A.6050200@gpex.es>
References: <51F7699A.6050200@gpex.es>
Message-ID:
Dave,
Im in the process of upgrading as well. My process of very similar
to Marco but I created a test site in 1.00 copied config from .56 and
figured out any issues on the test site versus the scramble on prod.
Then upgrade prod using the command (omd update prod) Marco
referenced.
Bill
On Tue, Jul 30, 2013 at 3:22 AM, David Corral wrote:
> Hello list,
>
> after some research, I'm not seeing a clear way to upgrade from 0.56 to
> 1.00 via package. I've updated from repositories, and I noticed a new
> "omd-1.00" package is available. Should I purge the previous one
> (omd-0.56?), or keep both and change apache configuration somewhere? Is the
> configuration kept between versions?
>
> Thanks in advance.
> Dave.
> ______________________________**_________________
> omd-users mailing list
> omd-users at lists.mathias-**kettner.de
> http://lists.mathias-kettner.**de/mailman/listinfo/omd-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pflaherty at wsi.com Tue Jul 30 17:23:10 2013
From: pflaherty at wsi.com (Patrick Flaherty)
Date: Tue, 30 Jul 2013 11:23:10 -0400
Subject: [omd-users] safe way to upgrade from 0.56 to 1.00
In-Reply-To:
References: <51F7699A.6050200@gpex.es>
Message-ID:
I went from .56 to 1.00 without any "issues", but Bill's comment is making
me wonder if I missed something.
Bill, what problems did you have to fix? Were they in stock features or
custom work you had done.
On Tue, Jul 30, 2013 at 10:56 AM, Bill Jacqmein wrote:
> Dave,
>
> Im in the process of upgrading as well. My process of very similar
> to Marco but I created a test site in 1.00 copied config from .56 and
> figured out any issues on the test site versus the scramble on prod.
> Then upgrade prod using the command (omd update prod) Marco
> referenced.
>
> Bill
>
>
>
> On Tue, Jul 30, 2013 at 3:22 AM, David Corral wrote:
>
>> Hello list,
>>
>> after some research, I'm not seeing a clear way to upgrade from 0.56 to
>> 1.00 via package. I've updated from repositories, and I noticed a new
>> "omd-1.00" package is available. Should I purge the previous one
>> (omd-0.56?), or keep both and change apache configuration somewhere? Is the
>> configuration kept between versions?
>>
>> Thanks in advance.
>> Dave.
>> ______________________________**_________________
>> omd-users mailing list
>> omd-users at lists.mathias-**kettner.de
>> http://lists.mathias-kettner.**de/mailman/listinfo/omd-users
>>
>
>
> _______________________________________________
> omd-users mailing list
> omd-users at lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wrjacqmein at gmail.com Tue Jul 30 17:53:06 2013
From: wrjacqmein at gmail.com (Bill Jacqmein)
Date: Tue, 30 Jul 2013 11:53:06 -0400
Subject: [omd-users] safe way to upgrade from 0.56 to 1.00
In-Reply-To:
References: <51F7699A.6050200@gpex.es>
Message-ID:
Patrick,
Nothing show stopping.
Some Ricoh's that were being picked up by the inventory as a Ricoh
and as a standard printer producing two check with the same name
(printer_supply and printer_supply_ricoh both create an item called Toner).
Temp work around was to remove the host or one of the duplicate checks.
UPS voltages setting the values for the US.
The limited custom stuff made it through safely.
BiIl
On Tue, Jul 30, 2013 at 11:23 AM, Patrick Flaherty wrote:
> I went from .56 to 1.00 without any "issues", but Bill's comment is making
> me wonder if I missed something.
>
> Bill, what problems did you have to fix? Were they in stock features or
> custom work you had done.
>
>
> On Tue, Jul 30, 2013 at 10:56 AM, Bill Jacqmein wrote:
>
>> Dave,
>>
>> Im in the process of upgrading as well. My process of very similar
>> to Marco but I created a test site in 1.00 copied config from .56 and
>> figured out any issues on the test site versus the scramble on prod.
>> Then upgrade prod using the command (omd update prod) Marco
>> referenced.
>>
>> Bill
>>
>>
>>
>> On Tue, Jul 30, 2013 at 3:22 AM, David Corral wrote:
>>
>>> Hello list,
>>>
>>> after some research, I'm not seeing a clear way to upgrade from 0.56 to
>>> 1.00 via package. I've updated from repositories, and I noticed a new
>>> "omd-1.00" package is available. Should I purge the previous one
>>> (omd-0.56?), or keep both and change apache configuration somewhere? Is the
>>> configuration kept between versions?
>>>
>>> Thanks in advance.
>>> Dave.
>>> ______________________________**_________________
>>> omd-users mailing list
>>> omd-users at lists.mathias-**kettner.de
>>> http://lists.mathias-kettner.**de/mailman/listinfo/omd-users
>>>
>>
>>
>> _______________________________________________
>> omd-users mailing list
>> omd-users at lists.mathias-kettner.de
>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From peter.david at vocatus.de Wed Jul 31 14:13:54 2013
From: peter.david at vocatus.de (Peter David)
Date: Wed, 31 Jul 2013 12:13:54 +0000 (UTC)
Subject: [omd-users] =?utf-8?q?check=5Fmk=2Eini_logwatch_restriction?=
Message-ID:
Hello List!
I have omd 1.00 installed on SLES 11 SP2 with multiple servers monitored.
Everything is working fine, i really like OMD!!
There are a few Windows (2k3 and 2k8R2) machines as well where i want to
restrict the logwatch-notification to critical only. I'm not sure if it is
working, because i've added
[logwatch]
# Nur critical senden
logfile application = crit
logfile internet explorer = crit
logfile system = crit
logfile security = crit
logfile * = off
(http://mathias-kettner.de/checkmk_windows.html)
to the check_mk.ini on multiple servers but from some of them i still get
warning-messages based on the logwatch. Where is the error?
Greetings!
From schulte.marcel at gmail.com Wed Jul 31 14:19:42 2013
From: schulte.marcel at gmail.com (Marcel Schulte)
Date: Wed, 31 Jul 2013 14:19:42 +0200
Subject: [omd-users] check_mk.ini logwatch restriction
In-Reply-To:
References:
Message-ID:
Hi Peter,
did you restart every agent (the windows service) after changing its
config? Changes are only applied at agent startup...
Possible but I think you've checked this: CRIT messages could be set
to WARN by rules at OMD server...
HTH,
Marcel
2013/7/31 Peter David :
> Hello List!
>
> I have omd 1.00 installed on SLES 11 SP2 with multiple servers monitored.
> Everything is working fine, i really like OMD!!
> There are a few Windows (2k3 and 2k8R2) machines as well where i want to
> restrict the logwatch-notification to critical only. I'm not sure if it is
> working, because i've added
>
> [logwatch]
> # Nur critical senden
> logfile application = crit
> logfile internet explorer = crit
> logfile system = crit
> logfile security = crit
> logfile * = off
>
> (http://mathias-kettner.de/checkmk_windows.html)
>
> to the check_mk.ini on multiple servers but from some of them i still get
> warning-messages based on the logwatch. Where is the error?
>
> Greetings!
>
> _______________________________________________
> omd-users mailing list
> omd-users at lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
From schulte.marcel at gmail.com Wed Jul 31 14:22:34 2013
From: schulte.marcel at gmail.com (Marcel Schulte)
Date: Wed, 31 Jul 2013 14:22:34 +0200
Subject: [omd-users] check_mk.ini logwatch restriction
In-Reply-To:
References:
Message-ID:
Hi Peter,
sorry, forgot something:
1. existing services in WARN and CRIT status at OMD site are not
cleared by agent config changes.
2. if you had LOG services from logs other than the ones shown in the
config you'll have to reinventorize the appropriate hosts to get rid
of these services.
HTH,
Marcel
2013/7/31 Marcel Schulte :
> Hi Peter,
>
> did you restart every agent (the windows service) after changing its
> config? Changes are only applied at agent startup...
>
> Possible but I think you've checked this: CRIT messages could be set
> to WARN by rules at OMD server...
>
> HTH,
> Marcel
>
> 2013/7/31 Peter David :
>> Hello List!
>>
>> I have omd 1.00 installed on SLES 11 SP2 with multiple servers monitored.
>> Everything is working fine, i really like OMD!!
>> There are a few Windows (2k3 and 2k8R2) machines as well where i want to
>> restrict the logwatch-notification to critical only. I'm not sure if it is
>> working, because i've added
>>
>> [logwatch]
>> # Nur critical senden
>> logfile application = crit
>> logfile internet explorer = crit
>> logfile system = crit
>> logfile security = crit
>> logfile * = off
>>
>> (http://mathias-kettner.de/checkmk_windows.html)
>>
>> to the check_mk.ini on multiple servers but from some of them i still get
>> warning-messages based on the logwatch. Where is the error?
>>
>> Greetings!
>>
>> _______________________________________________
>> omd-users mailing list
>> omd-users at lists.mathias-kettner.de
>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
From Peter.David at vocatus.de Wed Jul 31 14:30:44 2013
From: Peter.David at vocatus.de (David Peter)
Date: Wed, 31 Jul 2013 14:30:44 +0200
Subject: [omd-users] check_mk.ini logwatch restriction
References:
Message-ID: <79FD523C7864794C97DA38464538DE3203BEA634@mail2-muc.int.vocatus-ag.de>
Hi Marcel,
yes i restarted the windows service after changing the config. I know that I can change the level of the message, but I thought that with
>> [logwatch]
>> # Nur critical senden
>> logfile application = crit
>> logfile internet explorer = crit
>> logfile system = crit
>> logfile security = crit
>> logfile * = off
I can get rid of warning-messages. I also re-inventorized the server where I have the issue, now I have something strange:
State "UNKN" Service "- "Status detail "invalid output from agent, invalid check parameters or error in implementation of check local. Please set debug_log to a filename in main.mk for enabling exception logging."
This is strange.
--
Peter David
Information Services
Vocatus AG * Oppelner Stra?e 5 * 82194 Gr?benzell/M?nchen
Telefon +49 8142 5069 117 * Fax +49 8142 5069 299
www.vocatus.de
Vorstandsmitglieder: Dr. Florian Bauer, Hardy C. Koth, Alexander S. Weigmann,
Dr. Gaby Wiegran, Aufsichtsratsvorsitzender: Dr. Rolf W. Habbel,
Sitz der Gesellschaft: Gr?benzell, Registergericht M?nchen HRB 128851
-----Original Message-----
From: Marcel Schulte [mailto:schulte.marcel at gmail.com]
Sent: Mittwoch, 31. Juli 2013 14:23
To: David Peter
Cc: omd-users at lists.mathias-kettner.de
Subject: Re: [omd-users] check_mk.ini logwatch restriction
Hi Peter,
sorry, forgot something:
1. existing services in WARN and CRIT status at OMD site are not cleared by agent config changes.
2. if you had LOG services from logs other than the ones shown in the config you'll have to reinventorize the appropriate hosts to get rid of these services.
HTH,
Marcel
2013/7/31 Marcel Schulte :
> Hi Peter,
>
> did you restart every agent (the windows service) after changing its
> config? Changes are only applied at agent startup...
>
> Possible but I think you've checked this: CRIT messages could be set
> to WARN by rules at OMD server...
>
> HTH,
> Marcel
>
> 2013/7/31 Peter David :
>> Hello List!
>>
>> I have omd 1.00 installed on SLES 11 SP2 with multiple servers monitored.
>> Everything is working fine, i really like OMD!!
>> There are a few Windows (2k3 and 2k8R2) machines as well where i want
>> to restrict the logwatch-notification to critical only. I'm not sure
>> if it is working, because i've added
>>
>> [logwatch]
>> # Nur critical senden
>> logfile application = crit
>> logfile internet explorer = crit
>> logfile system = crit
>> logfile security = crit
>> logfile * = off
>>
>> (http://mathias-kettner.de/checkmk_windows.html)
>>
>> to the check_mk.ini on multiple servers but from some of them i still
>> get warning-messages based on the logwatch. Where is the error?
>>
>> Greetings!
>>
>> _______________________________________________
>> omd-users mailing list
>> omd-users at lists.mathias-kettner.de
>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
From schulte.marcel at gmail.com Wed Jul 31 15:06:02 2013
From: schulte.marcel at gmail.com (Marcel Schulte)
Date: Wed, 31 Jul 2013 15:06:02 +0200
Subject: [omd-users] check_mk.ini logwatch restriction
In-Reply-To: <79FD523C7864794C97DA38464538DE3203BEA634@mail2-muc.int.vocatus-ag.de>
References:
<79FD523C7864794C97DA38464538DE3203BEA634@mail2-muc.int.vocatus-ag.de>
Message-ID:
You can get rid of such warnings - but not of the warnings
alarmed/received before the agent's reconfiguration and restart. These
warnings stay until purged.
What does the debug log say for the UNKNOWN status?
Marcel
2013/7/31 David Peter :
> Hi Marcel,
>
> yes i restarted the windows service after changing the config. I know that I can change the level of the message, but I thought that with
>
>>> [logwatch]
>>> # Nur critical senden
>>> logfile application = crit
>>> logfile internet explorer = crit
>>> logfile system = crit
>>> logfile security = crit
>>> logfile * = off
>
> I can get rid of warning-messages. I also re-inventorized the server where I have the issue, now I have something strange:
>
> State "UNKN" Service "- "Status detail "invalid output from agent, invalid check parameters or error in implementation of check local. Please set debug_log to a filename in main.mk for enabling exception logging."
>
> This is strange.
>
> --
> Peter David
> Information Services
>
> Vocatus AG * Oppelner Stra?e 5 * 82194 Gr?benzell/M?nchen
> Telefon +49 8142 5069 117 * Fax +49 8142 5069 299
> www.vocatus.de
>
> Vorstandsmitglieder: Dr. Florian Bauer, Hardy C. Koth, Alexander S. Weigmann,
> Dr. Gaby Wiegran, Aufsichtsratsvorsitzender: Dr. Rolf W. Habbel,
> Sitz der Gesellschaft: Gr?benzell, Registergericht M?nchen HRB 128851
>
> -----Original Message-----
> From: Marcel Schulte [mailto:schulte.marcel at gmail.com]
> Sent: Mittwoch, 31. Juli 2013 14:23
> To: David Peter
> Cc: omd-users at lists.mathias-kettner.de
> Subject: Re: [omd-users] check_mk.ini logwatch restriction
>
> Hi Peter,
>
> sorry, forgot something:
>
> 1. existing services in WARN and CRIT status at OMD site are not cleared by agent config changes.
> 2. if you had LOG services from logs other than the ones shown in the config you'll have to reinventorize the appropriate hosts to get rid of these services.
>
> HTH,
> Marcel
>
> 2013/7/31 Marcel Schulte :
>> Hi Peter,
>>
>> did you restart every agent (the windows service) after changing its
>> config? Changes are only applied at agent startup...
>>
>> Possible but I think you've checked this: CRIT messages could be set
>> to WARN by rules at OMD server...
>>
>> HTH,
>> Marcel
>>
>> 2013/7/31 Peter David :
>>> Hello List!
>>>
>>> I have omd 1.00 installed on SLES 11 SP2 with multiple servers monitored.
>>> Everything is working fine, i really like OMD!!
>>> There are a few Windows (2k3 and 2k8R2) machines as well where i want
>>> to restrict the logwatch-notification to critical only. I'm not sure
>>> if it is working, because i've added
>>>
>>> [logwatch]
>>> # Nur critical senden
>>> logfile application = crit
>>> logfile internet explorer = crit
>>> logfile system = crit
>>> logfile security = crit
>>> logfile * = off
>>>
>>> (http://mathias-kettner.de/checkmk_windows.html)
>>>
>>> to the check_mk.ini on multiple servers but from some of them i still
>>> get warning-messages based on the logwatch. Where is the error?
>>>
>>> Greetings!
>>>
>>> _______________________________________________
>>> omd-users mailing list
>>> omd-users at lists.mathias-kettner.de
>>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
From Peter.David at vocatus.de Wed Jul 31 15:23:39 2013
From: Peter.David at vocatus.de (David Peter)
Date: Wed, 31 Jul 2013 15:23:39 +0200
Subject: [omd-users] check_mk.ini logwatch restriction
References: <79FD523C7864794C97DA38464538DE3203BEA634@mail2-muc.int.vocatus-ag.de>
Message-ID: <79FD523C7864794C97DA38464538DE3203BEA655@mail2-muc.int.vocatus-ag.de>
Hi there,
i could get rid of the old warnings. The log says
[1375276456] SERVICE ALERT: mail2(...).de;-;UNKNOWN;HARD;1;UNKNOWN - invalid output from agent, invalid check parameters or error in implementation of check local. Please set debug_log to a filename in main.mk for enabling exception logging.
[1375276456] SERVICE NOTIFICATION: david;mail2(...).de;-;UNKNOWN;check-mk-notify;UNKNOWN - invalid output from agent, invalid check parameters or error in implementation of check local. Please set ttdebug_log/tt to a filename in ttmain.mk/tt for enabling exception logging.
Did I forgot something?
--
Peter David
Information Services
Vocatus AG * Oppelner Stra?e 5 * 82194 Gr?benzell/M?nchen
Telefon +49 8142 5069 117 * Fax +49 8142 5069 299
www.vocatus.de
Vorstandsmitglieder: Dr. Florian Bauer, Hardy C. Koth, Alexander S. Weigmann,
Dr. Gaby Wiegran, Aufsichtsratsvorsitzender: Dr. Rolf W. Habbel,
Sitz der Gesellschaft: Gr?benzell, Registergericht M?nchen HRB 128851
-----Original Message-----
From: Marcel Schulte [mailto:schulte.marcel at gmail.com]
Sent: Mittwoch, 31. Juli 2013 15:06
To: David Peter
Cc: omd-users at lists.mathias-kettner.de
Subject: Re: [omd-users] check_mk.ini logwatch restriction
You can get rid of such warnings - but not of the warnings alarmed/received before the agent's reconfiguration and restart. These warnings stay until purged.
What does the debug log say for the UNKNOWN status?
Marcel
2013/7/31 David Peter :
> Hi Marcel,
>
> yes i restarted the windows service after changing the config. I know
> that I can change the level of the message, but I thought that with
>
>>> [logwatch]
>>> # Nur critical senden
>>> logfile application = crit
>>> logfile internet explorer = crit
>>> logfile system = crit
>>> logfile security = crit
>>> logfile * = off
>
> I can get rid of warning-messages. I also re-inventorized the server where I have the issue, now I have something strange:
>
> State "UNKN" Service "- "Status detail "invalid output from agent, invalid check parameters or error in implementation of check local. Please set debug_log to a filename in main.mk for enabling exception logging."
>
> This is strange.
>
> --
> Peter David
> Information Services
>
> Vocatus AG * Oppelner Stra?e 5 * 82194 Gr?benzell/M?nchen Telefon +49
> 8142 5069 117 * Fax +49 8142 5069 299 www.vocatus.de
>
> Vorstandsmitglieder: Dr. Florian Bauer, Hardy C. Koth, Alexander S.
> Weigmann, Dr. Gaby Wiegran, Aufsichtsratsvorsitzender: Dr. Rolf W.
> Habbel, Sitz der Gesellschaft: Gr?benzell, Registergericht M?nchen HRB
> 128851
>
> -----Original Message-----
> From: Marcel Schulte [mailto:schulte.marcel at gmail.com]
> Sent: Mittwoch, 31. Juli 2013 14:23
> To: David Peter
> Cc: omd-users at lists.mathias-kettner.de
> Subject: Re: [omd-users] check_mk.ini logwatch restriction
>
> Hi Peter,
>
> sorry, forgot something:
>
> 1. existing services in WARN and CRIT status at OMD site are not cleared by agent config changes.
> 2. if you had LOG services from logs other than the ones shown in the config you'll have to reinventorize the appropriate hosts to get rid of these services.
>
> HTH,
> Marcel
>
> 2013/7/31 Marcel Schulte :
>> Hi Peter,
>>
>> did you restart every agent (the windows service) after changing its
>> config? Changes are only applied at agent startup...
>>
>> Possible but I think you've checked this: CRIT messages could be set
>> to WARN by rules at OMD server...
>>
>> HTH,
>> Marcel
>>
>> 2013/7/31 Peter David :
>>> Hello List!
>>>
>>> I have omd 1.00 installed on SLES 11 SP2 with multiple servers monitored.
>>> Everything is working fine, i really like OMD!!
>>> There are a few Windows (2k3 and 2k8R2) machines as well where i
>>> want to restrict the logwatch-notification to critical only. I'm not
>>> sure if it is working, because i've added
>>>
>>> [logwatch]
>>> # Nur critical senden
>>> logfile application = crit
>>> logfile internet explorer = crit
>>> logfile system = crit
>>> logfile security = crit
>>> logfile * = off
>>>
>>> (http://mathias-kettner.de/checkmk_windows.html)
>>>
>>> to the check_mk.ini on multiple servers but from some of them i
>>> still get warning-messages based on the logwatch. Where is the error?
>>>
>>> Greetings!
>>>
>>> _______________________________________________
>>> omd-users mailing list
>>> omd-users at lists.mathias-kettner.de
>>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
From schulte.marcel at gmail.com Wed Jul 31 15:48:02 2013
From: schulte.marcel at gmail.com (Marcel Schulte)
Date: Wed, 31 Jul 2013 15:48:02 +0200
Subject: [omd-users] check_mk.ini logwatch restriction
In-Reply-To: <79FD523C7864794C97DA38464538DE3203BEA655@mail2-muc.int.vocatus-ag.de>
References:
<79FD523C7864794C97DA38464538DE3203BEA634@mail2-muc.int.vocatus-ag.de>
<79FD523C7864794C97DA38464538DE3203BEA655@mail2-muc.int.vocatus-ag.de>
Message-ID:
Peter, the message says it:
"Please set ttdebug_log/tt to a filename in ttmain.mk/tt for enabling
exception logging."
After setting the variable you have to issue 'cmk -O' or 'cmk -R' for
the setting to be applied.
At the end watch the output in the debug log for the error regarding logwatch.
When found deactivate the debug_log setting again and issue 'cmk
-O/-R' - the log can get really big.
Log should point you (or us) to the right direction.
HTH,
Marcel
2013/7/31 David Peter :
> Hi there,
>
> i could get rid of the old warnings. The log says
>
> [1375276456] SERVICE ALERT: mail2(...).de;-;UNKNOWN;HARD;1;UNKNOWN - invalid output from agent, invalid check parameters or error in implementation of check local. Please set debug_log to a filename in main.mk for enabling exception logging.
> [1375276456] SERVICE NOTIFICATION: david;mail2(...).de;-;UNKNOWN;check-mk-notify;UNKNOWN - invalid output from agent, invalid check parameters or error in implementation of check local. Please set ttdebug_log/tt to a filename in ttmain.mk/tt for enabling exception logging.
>
> Did I forgot something?
>
> --
> Peter David
> Information Services
>
> Vocatus AG * Oppelner Stra?e 5 * 82194 Gr?benzell/M?nchen
> Telefon +49 8142 5069 117 * Fax +49 8142 5069 299
> www.vocatus.de
>
> Vorstandsmitglieder: Dr. Florian Bauer, Hardy C. Koth, Alexander S. Weigmann,
> Dr. Gaby Wiegran, Aufsichtsratsvorsitzender: Dr. Rolf W. Habbel,
> Sitz der Gesellschaft: Gr?benzell, Registergericht M?nchen HRB 128851
>
> -----Original Message-----
> From: Marcel Schulte [mailto:schulte.marcel at gmail.com]
> Sent: Mittwoch, 31. Juli 2013 15:06
> To: David Peter
> Cc: omd-users at lists.mathias-kettner.de
> Subject: Re: [omd-users] check_mk.ini logwatch restriction
>
> You can get rid of such warnings - but not of the warnings alarmed/received before the agent's reconfiguration and restart. These warnings stay until purged.
>
> What does the debug log say for the UNKNOWN status?
>
> Marcel
>
> 2013/7/31 David Peter :
>> Hi Marcel,
>>
>> yes i restarted the windows service after changing the config. I know
>> that I can change the level of the message, but I thought that with
>>
>>>> [logwatch]
>>>> # Nur critical senden
>>>> logfile application = crit
>>>> logfile internet explorer = crit
>>>> logfile system = crit
>>>> logfile security = crit
>>>> logfile * = off
>>
>> I can get rid of warning-messages. I also re-inventorized the server where I have the issue, now I have something strange:
>>
>> State "UNKN" Service "- "Status detail "invalid output from agent, invalid check parameters or error in implementation of check local. Please set debug_log to a filename in main.mk for enabling exception logging."
>>
>> This is strange.
>>
>> --
>> Peter David
>> Information Services
>>
>> Vocatus AG * Oppelner Stra?e 5 * 82194 Gr?benzell/M?nchen Telefon +49
>> 8142 5069 117 * Fax +49 8142 5069 299 www.vocatus.de
>>
>> Vorstandsmitglieder: Dr. Florian Bauer, Hardy C. Koth, Alexander S.
>> Weigmann, Dr. Gaby Wiegran, Aufsichtsratsvorsitzender: Dr. Rolf W.
>> Habbel, Sitz der Gesellschaft: Gr?benzell, Registergericht M?nchen HRB
>> 128851
>>
>> -----Original Message-----
>> From: Marcel Schulte [mailto:schulte.marcel at gmail.com]
>> Sent: Mittwoch, 31. Juli 2013 14:23
>> To: David Peter
>> Cc: omd-users at lists.mathias-kettner.de
>> Subject: Re: [omd-users] check_mk.ini logwatch restriction
>>
>> Hi Peter,
>>
>> sorry, forgot something:
>>
>> 1. existing services in WARN and CRIT status at OMD site are not cleared by agent config changes.
>> 2. if you had LOG services from logs other than the ones shown in the config you'll have to reinventorize the appropriate hosts to get rid of these services.
>>
>> HTH,
>> Marcel
>>
>> 2013/7/31 Marcel Schulte :
>>> Hi Peter,
>>>
>>> did you restart every agent (the windows service) after changing its
>>> config? Changes are only applied at agent startup...
>>>
>>> Possible but I think you've checked this: CRIT messages could be set
>>> to WARN by rules at OMD server...
>>>
>>> HTH,
>>> Marcel
>>>
>>> 2013/7/31 Peter David :
>>>> Hello List!
>>>>
>>>> I have omd 1.00 installed on SLES 11 SP2 with multiple servers monitored.
>>>> Everything is working fine, i really like OMD!!
>>>> There are a few Windows (2k3 and 2k8R2) machines as well where i
>>>> want to restrict the logwatch-notification to critical only. I'm not
>>>> sure if it is working, because i've added
>>>>
>>>> [logwatch]
>>>> # Nur critical senden
>>>> logfile application = crit
>>>> logfile internet explorer = crit
>>>> logfile system = crit
>>>> logfile security = crit
>>>> logfile * = off
>>>>
>>>> (http://mathias-kettner.de/checkmk_windows.html)
>>>>
>>>> to the check_mk.ini on multiple servers but from some of them i
>>>> still get warning-messages based on the logwatch. Where is the error?
>>>>
>>>> Greetings!
>>>>
>>>> _______________________________________________
>>>> omd-users mailing list
>>>> omd-users at lists.mathias-kettner.de
>>>> http://lists.mathias-kettner.de/mailman/listinfo/omd-users