Page 1 of 1

Best Practice for NRPE Agent

Posted: Thu Jan 14, 2016 2:40 pm
by Berto
Hello,

There are servers inside our data center that don't have access to the internet, the vast majority I would say. When testing and installing the NRPE agents, the test servers I used did have access to the net and had no issue installing the EPEL repos.
I'm wondering what is the best practice to get the agents installed on servers that don't have access to the internet. Our environment is mainly made up of RHEL but I do have some Solaris 10 servers and would like to know what's the best way to proceed with my particular situation.

Thanks,

--Berto

Re: Best Practice for NRPE Agent

Posted: Thu Jan 14, 2016 5:25 pm
by lmiltchev
Unfortunately we don't have an "offline" NRPE installer. You can try downloading the Linux agent on the different machine (with Internet access) and moving it over to your server, i.e in the "/tmp/" directory. Next run:

Code: Select all

cd /tmp
tar zxvf linux-nrpe-agent.tar.gz
cd /tmp/linux-nrpe-agent
touch installed.repos
touch installed.prereqs
Find a way to install the prerequisites manually on this machine - autoconf, gcc, glibc, libmcrypt-devel, make, openssl-devel, sudo, sysstat, xinetd, and bc.

Run the fullinstall script:

Code: Select all

./fullinstall
Again, we don't have a "offline" installer. This is just a "workaround" which may or may not work.

Re: Best Practice for NRPE Agent

Posted: Fri Jan 15, 2016 8:12 am
by Berto
Thanks for the suggestion. I have one more question, if I stand up a Linux repo server that the servers could get to and I add an epel channel would that work for installs?

--Berto

Re: Best Practice for NRPE Agent

Posted: Fri Jan 15, 2016 1:09 pm
by hsmith
I can't think of anything else you would need. You may want to check the fullinstall script, but I believe that should work.

Re: Best Practice for NRPE Agent

Posted: Mon Jan 18, 2016 6:09 pm
by Berto
Okay, thanks for the info. This can be closed.

--Berto