Can't help but think that using pnp4nagios would be easier :-) Phil
-- Phil Randal Infrastructure Engineer Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT Tel: 01432 260415 | Email: phil.ran...@hoopleltd.co.uk -----Original Message----- From: nelson [mailto:tnels...@comcast.net] Sent: 20 July 2012 08:30 To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Installing n2rrd with Nagios on Centos 6.2 I am in the process of building a Centos 6.2 system to run Nagios and n2rrd. It is a virtual machine / sandbox. Centos 6.2 is installed as is Nagios 3.4.1 and Nagios Plugins 1.4.15. Nagios and the Nagios Plugins were installed following the Fedora Quick Start instructions at http://nagios.sourceforge.net/docs/3_0/quickstart-fedora.html Nagios was started and I was able to access the Nagios web pages on Apache successfully. It is the basic, just after installation, configuration, but it tells me it is working. The next step was to download and install n2rrd. I downloaded nagios-n2rrd- 1.4.5-1.src.rpm, and started following the instructions at http://n2rrd- wiki.diglinks.com/display/n2rrd/RPM+Source to perform the install. Step 2 rpm -i nagios-n2rrd-1.4.5-1.src.rpm created /root/rpmbuild/SPECS, SOURCES, etc. Step3 and 4 verify the PATHs for ../SPECS/n2rrd.spec and ../SOURCES/... Step 5 executes the rpmbuild -ba /root/rpmbuild/SPECS/n2rrd.spec My first attempt at rpmbuild revealed that I had some problems with some PATHs specified in n2rrd.spec. Nagios is installed entirely in /usr/local/nagios. No problem, now that I know. I made the appropriate (I believe) changes to n2rrd.spec: #nagios related %define nagios_conf_dir /usr/local/nagios/etc %define nagios_data_dir /usr/local/nagios/share %define nagios_lib_dir /usr/local/nagios %define nagios_log_dir /usr/local/nagios/var I'll admit I guessed on the nagios_lib_dir. I fired up a Nagios installation I had on Fedora 14 to compare directory structures and defining it as /usr/local /nagios did not seem unreasonable. I kicked off the rpmbuild -ba /root/rpmbuild/SPECS/n2rrd.spec again and the messages look a bit better. Near the end of the output, I am seeing the following: Processing files: nagios-n2rrd-1.4.5-1.noarch Provides: config(nagios-n2rrd) = 1.4.5-1 Requires(interp): /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires(post): /bin/sh Requires: /usr/bin/perl perl(Getopt::Std) perl(IO::Socket) perl(RRDs) perl(strict) perl(vars) Processing files: nagios-n2rrd-rrd2graph-1.4.5-1.noarch Provides: config(nagios-n2rrd-rrd2graph) = 1.4.5-1 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: /usr/bin/perl perl(CGI) perl(File::Basename) perl(File::Find) perl(File::Temp) perl(RRDs) perl(strict) perl(vars) Checking for unpackaged file(s): /usr/lib/rpm/check-files /root/rpmbuild /BUILDROOT/nagios-n2rrd-1.4.5-1.i386 I believe the above messages are statements produced by the execution rather than errors. These statements are followed by some errors: error: Installed (but unpackaged) file(s) found: /etc/nagios/n2rrd.cfg /usr/share/nagios/css3menu/256base-save-over.png /usr/share/nagios/css3menu/256subdown.png /usr/share/nagios/css3menu/256subdown1.png /usr/share/nagios/css3menu/EPS.png . . . /usr/share/nagios/css3menu/zoom-graph.png /usr/share/nagios/css3menu/zoom.png RPM build errors: Installed (but unpackaged) file(s) found: /etc/nagios/n2rrd.cfg /usr/share/nagios/css3menu/256base-save-over.png /usr/share/nagios/css3menu/256subdown.png . . . /usr/share/nagios/css3menu/zoom-graph.png /usr/share/nagios/css3menu/zoom.png My questions are: 1 - Can someone confirm the above messages (Requires...) are statements rather than errors? 2 - What did I do wrong to generate the 'Installed (but unpackaged) file(s) found:' errors? 3 - Is there some 'big picture' item or bit of knowledge that I am missing that caused me to make these errors? Yes, I am beyond the limit of my expertise here. Any thoughts or comments would be welcomed, even 'this is the wrong place for this message.' Thank you. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null “Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
