NRPE - Full Guide to install it offline

[OmarNaji1]

Hello Dears,


I must install Nagios agent ( NRPE ) in the offline server ( no connection to the internet ).

the problem is during NRPE Installation is using the internet to get some package and its return the below error.

Code: Select all

===================
INSTALLATION ERROR!
===================

Installation step failed - exiting.
Check for error messages in the install log (install.log).

If you require assistance in resolving the issue, please include install.log
in your communications with Nagios XI technical support.

The script that failed was: './1-prereqs'

so please support is there any way to install it in offline server with full installation step by step.

INSTALL LOG :

Code: Select all

Nagios Linux Agent Installation Log
===================================
DATE: Thu May 14 19:06:07 GST 2020

DISTRO INFO:
RedHatEnterpriseServer
7.3
x86_64

Configuring Repos...
Enabling EPEL repo...
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
              : manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast
file:///mnt/addons/HighAvailability/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/addons/HighAvailability/repodata/repomd.xml"
Trying other mirror.
file:///mnt/addons/ResilientStorage/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/addons/ResilientStorage/repodata/repomd.xml"
Trying other mirror.
file:///mnt/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/repodata/repomd.xml"
Trying other mirror.
No package epel-release available.
Error: Nothing to do
Installing EPEL PKG: ./packages/epel-release-latest-7.noarch.rpm
warning: ./packages/epel-release-latest-7.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
Preparing...                          ########################################
Updating / installing...
epel-release-7-10                     ########################################
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
              : manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
file:///mnt/addons/HighAvailability/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/addons/HighAvailability/repodata/repomd.xml"
Trying other mirror.
file:///mnt/addons/ResilientStorage/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/addons/ResilientStorage/repodata/repomd.xml"
Trying other mirror.


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
epel-release RPM installed OK
Repos configured OK
Installing prerequisites...
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
              : manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
file:///mnt/addons/HighAvailability/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/addons/HighAvailability/repodata/repomd.xml"
Trying other mirror.
file:///mnt/addons/ResilientStorage/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /mnt/addons/ResilientStorage/repodata/repomd.xml"
Trying other mirror.


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

Best Regards

[jbrunkow]

I believe you will need to download the RPM and all of it's dependencies, and then install it from source.

Please refer to the following documentation for more detailed instructions on how to do this.
https://support.nagios.com/kb/article.php?id=515

[OmarNaji1]

Dear jbrunkow,

Thanks for your reply, already tried to follow that document but my isssue was for first command.

Code: Select all

yum install -y gcc glibc glibc-common openssl openssl-devel perl wget

its return the below output.

Code: Select all

[root@localhost ~]# yum install -y gcc glibc glibc-common openssl openssl-devel                                                                                         perl wget
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-
              : manager
This system is not registered to Red Hat Subscription Management. You can use su                                                                                        bscription-manager to register.
file:///mnt/addons/HighAvailability/repodata/repomd.xml: [Errno 14] curl#37 - "C                                                                                        ouldn't open file /mnt/addons/HighAvailability/repodata/repomd.xml"
Trying other mirror.
file:///mnt/addons/ResilientStorage/repodata/repomd.xml: [Errno 14] curl#37 - "C                                                                                        ouldn't open file /mnt/addons/ResilientStorage/repodata/repomd.xml"
Trying other mirror.


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and                                                                                         try again

do we have this one as package to extract it and install.

Best Regards.

[jbrunkow]

I believe you can download the packages on an internet connected system using the downloadonly plugin or yumdownloader on a system that already has the packages installed.

Code: Select all

yum install yum-plugin-downloadonly
yum install --downloadonly --downloaddir=<[i]directory[/i]> <[i]package[/i]>

link

Then you can move it to the offline system (using scp or similar...), and then run something like the following set of commands.

Code: Select all

yum install --downloadonly --installroot=<[i]directory[/i]> --releasever=<[i]version[/i]> --downloaddir=<[i]directory[/i]> <[i]package[/i]>

As for how you would update the system after that is another matter... Options for that include re-downloading every update using an online machine, setting up a local repository, or setting up a local mirror.
LINK

[OmarNaji1]

Thank you for support and answer.
it was very helpfully to me.


Best regards,

[jbrunkow]

I'm glad to hear that!

Were you able to get it installed offline?

Please let me know if you have any more questions. Otherwise, we can lock this thread for editing so that it can be archived for future reference.

[OmarNaji1]

Hi dear,

I solved this one by below steps.

first, I get the package of below command by yum download-only and take a copy to my Linux host.

Code: Select all

Sudo yum install -y gcc glibc glibc-common openssl openssl-devel perl wget 

and same for

Code: Select all

sudo yum install -y perl-Net-SNMP

then I downloaded epel from below link and take a copy also to Linux host

https://dl.fedoraproject.org/pub/epel/e ... noarch.rpm

then run the below commnad

Code: Select all

sudo rpm -qa | grep -i epel
sudo rpm -qi epel-release-7-12.noarch       //change the name to same file name
sudo rpm -e epel-release-7-12.noarch        //change the name to same file name

that is all requested for NRPE for my case.

Thanks and Best regards.