Nagios Support Forum

Thanks a bunch. I have just let Eric (one of our core devs) know about the core spec issues (he probably already knows if you posted to tracker). I will look over the nagios-plugins spec file issues - I just took over the plugins project so fixing up the spec file will be a priority, but I cannot d...

I tried yours for nrpe, but you still need to be root for the permission change, right? Isn't there a way around that? The 2.12 tarball builds fine. Yes, I believe at least one of the packages requires root while compiling / building. The way I see it, it seems more like something the software does...

Done:

http://tracker.nagios.org/view.php?id=530

Thanks!

The spec file in 4.0.1 is greatly improved over 4.0.0, thank you. There's still one left-over issue - the permissions on the plugins directory. Think about it: it's a directory, you don't want to set 0644 permissions on it unless you have a very good reason, otherwise many things will stop working m...

I'm preparing for the upgrade to Nagios v4 on a Red Hat 5 compatible server. I am building RPM packages out of the tarballs for nagios-core, nagios-plugins, and nrpe. It's pretty messy. Out the box, the packages are incompatible with each other. For most, the build process exits with errors. Nagios ...

No, it's multiple plugins. Meanwhile, I think I've found the problem. The spec files for the RPM packages, contained in the tarballs, are woefully out of date, and incompatible between nagios, nagios-plugins, and nrpe-plugin. Also, there are things such as 644 permissions on directories, etc. It's u...

After quite a bit of difficulties (spec file is broken, there are many things not right about the whole package compiling here), I've managed to build an RPM package out of nagios-plugins-1.5. I've upgraded that package on the test server, restarted the nagios service, and I'm getting the same error...

I've built RPM packages from 4.0.0 for core, plugins and NRPE, and I've installed them on Red Hat 5. I'm using a simple test configuration with a few hosts and services. This stuff used to work on 3.x. Now I get a whole lot of: [1381794997] Warning: Return code of 13 for check of host 'foo' was out ...

You could do this a couple ways, One would be setting up notification_options, in your service .cfg files like so: notification_options w,c,u In this example, the service will only send out an alert if it reaches a warning, critical, or unknown state. Nothing else, if you wanted recovery alerts for...