similar to: Bug#514335: logcheck-database: Nagios rules don't match the new nagios3 version

Package: logcheck-database Version: 1.2.68 Severity: minor openssh-server version 1:5.1p1-2 ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ sshd\[[0-9]+\]: reverse mapping checking getaddrinfo for [._[:alnum:]-]+ failed - POSSIBLE BREAK-?IN ATTEMPT!$ should look like ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ sshd\[[0-9]+\]: reverse mapping checking getaddrinfo for [._[:alnum:]-]+ \[[.[:alnum:]:]+\] failed -

I am using stored configs to manage my nagios host and services checks and I have run into a problem that I have been unable to solve. When the stored configs are purged from puppet the nagios server correctly removes them from the services and hosts file but does not notify the nagios service and instead throws an error. So the entries are still there and nagios still reports on them until

Hello ! I''m trying to implement a Nagios solution based on David Schmitt''s Complete Config. But I the following error when running puppetd -t - v : notice: Starting catalog run err: //Node[monitoring]/nagios::target/Nagios::Host[]/File[/conf.d/ _host.cfg]/ensure: change from absent to present failed: Could not set present on ensure: No such file or directory - /conf.d/

Package: logcheck-database Version: 1.2.43a Followup-For: Bug #355364 sorry but the previous patch was wrong the rules has to match both nagios: and nagios2: (and NOT nagios[...]:) so the pattern is nagios[2]*: (instead of nagios\[[0-9]+\]:) -- Cyril Chaboisseau

Package: logcheck-database Version: 1.2.43a Severity: wishlist when nagios2 is installed logcheck doesn't catch system messages with the existing (nagios) rules please, change "nagios:" to "nagios\[[0-9]+\]:" for all lines thanks -- Cyril Chaboisseau -------------- next part -------------- --- nagios 2005-10-23 06:13:15.000000000 +0200 +++ nagios.new 2006-03-05

Is anyone working on Nagios 3.x RPMs? If not, perhaps I'll whip some up and submit them to some appropriate repository. Geoff Galitz Blankenheim NRW, Deutschland http://www.galitz.org

I''m sure people have hit this problem before. In my nagios module, the nagios command pipe file at /var/lib/nagios3/rw/nagios.cmd is owned by the nagios user, but needs to be written to by the www-data user. Adding the www-user to the nagios group is one solution, but that requires that the nagios module potentially modify the www-data user, which seems bad. What''s the best way

Package: logcheck-database Version: 1.2.54 Severity: normal The included filters for cyrus (/etc/logcheck/ignore.d.server/cyrus) are very minimal. The cyrus-imapd-2.2 has a more extensive ruleset (there's a /etc/logcheck/ignore.d.server/cyrus2_2 file in that package). Please copy over the filters from cyrus-imapd-2.2. I'm running logcheck on a loghost, which doesn't run cyrus

So, my favorite RPM repository (EPEL) only has the ancient nagios-2.12 or so. What's the repo you use for Nagios 3? -- Florin Andrei http://florin.myip.org/

Couple of questions. Firstly, what''s the plugin error about? puppet agent --onetime --test --verbose info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from source(s) puppet://puppet/plugins info: Caching catalog for mon01.ap1.xxx.com info: Applying configuration version ''1346878830'' err:

Hi folks, For the first time since I started playing with puppet I started down the road of using exported resources This was inspired by my reading all of the nagios related recipes that went something along the lines of class nagios { package {nagios: ensure=> latest } service {nagios : ensure => running , enable => true} Nagios_host <<! !>>

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

When an error occurs in prerun_command, puppet continues execution instead of stopping. We can see the error at the log file, but puppet cotinues doing changes: puppetd[18430]: Failed to prepare catalog: Could not run command from prerun_command: Execution of ''/path/to/command'' returned 1: We want to prevent changes when an error occurs in prerun_command. Our puppet.conf:

Dear all, I''m seeing this strange thing: When I run "*puppet agent -td*" on the node (Nagios, in this example case), puppet fails to install Nagios3 (on Debian) with this: Debug: Executing ''/usr/bin/dpkg-query -W --showformat ${Status} ${Package} > ${Version}\n nagios3'' > Debug: Executing ''/usr/bin/apt-get -q -y -o >

I''ve tried to achieve my overall goals with several different features of Puppet, but I''ve hit a bit of a wall here. I think it''s time for me to explain what I''m trying to accomplish: I want the enabling of a service in my manifests to configure the monitoring of that service by a nagios server, without needless repetition. Let me explain how my

Hi folks, I noticed an interesting problem with the nagios_* providers especially in Debian. Besides writing to the wrong file (I fixed that issue) I''ve noticed there is a umask issue where the config files end up being owned by root with perms 0640. This causes nagios to spit milk out of its nose because it cannot read the configuration files. I came up with a kludgey solution to the

I''m very interested in the way that puppet appears to be able to generate nagios configurations though I can''t seem to find any documenation on how it works: http://reductivelabs.com/trac/naginator is clearly a placeholder page... Meanwhile the various pieces of info at links such as: http://reductivelabs.com/trac/puppet/wiki/TypeReference#nagios-host are just teasing me.

I''ve been thinking about how to make Puppet a killer app, and I think there is one specific thing that could be done to help make that happen: People using Puppet now to consistently state what they *really* wish Puppet could do for them -- the recent thread around Puppet on Windows is in that vein, but it''s not specific enough. For example, I''d like to know what

Hello, I've tried many places, finally ending up here to ask my question: why is it so vital that the directory used with the ChrootDirectory directive is root-owned? Like many people I'm trying to use this in a webhosting environment where several users get sftp-only access to some directory, usually something like /home/user/web/part-of-website. I can be sure that there are no setuid

Package: logcheck-database Version: 1.2.26 Severity: normal Hi, the file courier contains the line: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ pop3d-ssl: Unexpected SSL connection shutdown\.$ This triggers the security logcheck section because of the word "shutdown". Quick fix is to move or duplicate this line to violations.ignore.d/logcheck-courier. BTW: It looks like the courier package