Monitoring VMware With Nagios XI
Re: Monitoring VMware With Nagios XI
root@hpsatvld5302:~ # yum repolist
Loaded plugins: langpacks
UENG.2019.3.0.RHEL | 3.7 kB 00:00:00
nagios-base | 2.9 kB 00:00:00
nagiosxi-deps | 2.9 kB 00:00:00
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
root@hpsatvld5302:~ #
Loaded plugins: langpacks
UENG.2019.3.0.RHEL | 3.7 kB 00:00:00
nagios-base | 2.9 kB 00:00:00
nagiosxi-deps | 2.9 kB 00:00:00
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
root@hpsatvld5302:~ #
Re: Monitoring VMware With Nagios XI
root@hpsatvld5302:~ # yum clean all
Loaded plugins: langpacks
Cleaning repos: UENG.2019.3.0.RHEL epel nagios-base nagiosxi-deps
Other repos take up 2.0 M of disk space (use --verbose for details)
You have new mail in /var/spool/mail/root
root@hpsatvld5302:~ # yum update -y
Loaded plugins: langpacks
UENG.2019.3.0.RHEL | 3.7 kB 00:00:00
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
root@hpsatvld5302:~ #
Loaded plugins: langpacks
Cleaning repos: UENG.2019.3.0.RHEL epel nagios-base nagiosxi-deps
Other repos take up 2.0 M of disk space (use --verbose for details)
You have new mail in /var/spool/mail/root
root@hpsatvld5302:~ # yum update -y
Loaded plugins: langpacks
UENG.2019.3.0.RHEL | 3.7 kB 00:00:00
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
root@hpsatvld5302:~ #
Re: Monitoring VMware With Nagios XI
Again, you will have to talk to your system administrator, and find a way to fix the broken repos, and install all of the required packages. This is out of scope of Nagios support.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Monitoring VMware With Nagios XI
Any suggestions still we are unable to do any task here
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Monitoring VMware With Nagios XI
lmiltchev wrote:Again, you will have to talk to your system administrator, and find a way to fix the broken repos, and install all of the required packages. This is out of scope of Nagios support.
Re: Monitoring VMware With Nagios XI
I am SysAdmin for this server. Any help you can provide to me would be greatly appreciated.
A little history on our proposed (not yet implemented) Nagios environment is this, we are in an offline environment. So either replicate the software repositories using reposync or rsync, or I install stuff 1 package at a time. I know these outside environments get updated often so I sync daily. So I should be up to date.
I am really not sure what the real problem I have tried installing using cpanm and cpan, I was pasting the cpan output:
#cpan
cp[2} install Module::Build Crypt::SSLeay
cpanm (App::cpanminus) 1.7044 on perl 5.016003 built for x86_64-linux-thread-multi
Work directory is /root/.cpanm/work/1573504666.13396
You have make /usr/bin/make
You have LWP 5.837
You have /usr/bin/tar: tar (GNU tar) 1.26
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
You have /usr/bin/unzip
Searching Module::Build () on cpanmetadb ...
-> FAIL Finding Module::Build on cpanmetadb failed.
! Could not find a release matching Module::Build on MetaCPAN.
Searching Module::Build on mirror http://reposerver/repo/cpan/CPAN ...
Downloading index file http://reposerver/repo/cpan/CPAN/module ... ils.txt.gz ...
--> Working on Module::Build
Fetching http://reposerver/repo/cpan/CPAN/author ... 229.tar.gz
-> OK
Unpacking Module-Build-0.4229.tar.gz
Entering Module-Build-0.4229
Checking configure dependencies from META.json
Checking if you have Module::Metadata 1.000002 ... Yes (1.000037)
Checking if you have File::Copy 0 ... Yes (2.23)
Checking if you have version 0.87 ... Yes (0.9907)
Checking if you have File::Spec 0.82 ... Yes (3.40)
Checking if you have CPAN::Meta 2.142060 ... Yes (2.150010)
Checking if you have File::Path 0 ... Yes (2.09)
Checking if you have File::Basename 0 ... Yes (2.84)
Checking if you have Perl::OSType 1 ... Yes (1.003)
Configuring Module-Build-0.4229
Running Build.PL
Checking optional features...
dist_authoring..........disabled
requires:
! Archive::Tar is not installed
recommends:
* Pod::Readme is not installed
inc_bundling_support....disabled
requires:
! inc::latest (0.4005) is installed, but we need version >= 0.5
ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions
of the modules indicated above before proceeding with this installation
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Module-Build' version '0.4229'
-> OK
Checking dependencies from MYMETA.json ...
Checking if you have Module::Metadata 1.000002 ... Yes (1.000037)
Checking if you have File::Spec 0.82 ... Yes (3.40)
Checking if you have ExtUtils::Install 0 ... Yes (1.58)
Checking if you have File::Compare 0 ... Yes (1.1006)
Checking if you have File::Find 0 ... Yes (1.20)
Checking if you have CPAN::Meta 2.142060 ... Yes (2.150010)
Checking if you have File::Path 0 ... Yes (2.09)
Checking if you have Perl::OSType 1 ... Yes (1.003)
Checking if you have ExtUtils::Manifest 0 ... Yes (1.61)
Checking if you have ExtUtils::CBuilder 0.27 ... Yes (0.280206)
Checking if you have Getopt::Long 0 ... Yes (2.4)
Checking if you have File::Copy 0 ... Yes (2.23)
Checking if you have Parse::CPAN::Meta 1.4401 ... Yes (2.150010)
Checking if you have Text::Abbrev 0 ... Yes (1.02)
Checking if you have Pod::Man 2.17 ... Yes (2.27)
Checking if you have Data::Dumper 0 ... Yes (2.145)
Checking if you have version 0.87 ... Yes (0.9907)
Checking if you have ExtUtils::ParseXS 2.21 ... Yes (3.35)
Checking if you have CPAN::Meta::YAML 0.003 ... Yes (0.018)
Checking if you have TAP::Harness 3.29 ... Yes (3.42)
Checking if you have Test::More 0.49 ... Yes (1.302168)
Checking if you have Text::ParseWords 0 ... Yes (3.29)
Checking if you have File::Temp 0.15 ... Yes (0.2301)
Checking if you have File::Basename 0 ... Yes (2.84)
Checking if you have Cwd 0 ... Yes (3.40)
Checking if you have ExtUtils::Mkbootstrap 0 ... Yes (6.68)
Building and testing Module-Build-0.4229
Building Module-Build
t/00-compile.t ................. ok
t/PL_files.t ................... ok
t/actions/installdeps.t ........ ok
t/actions/manifest_skip.t ...... ok
t/add_property.t ............... ok
t/add_property_array.t ......... ok
t/add_property_hash.t .......... ok
t/basic.t ...................... ok
t/bundle_inc.t ................. skipped: $ENV{MB_TEST_EXPERIMENTAL} is not set
t/compat.t ..................... ok
t/compat/exit.t ................ ok
t/debug.t ...................... ok
t/destinations.t ............... ok
t/ext.t ........................ ok
t/extend.t ..................... ok
t/files.t ...................... ok
t/help.t ....................... ok
t/install.t .................... ok
t/install_extra_target.t ....... ok
t/manifypods.t ................. ok
t/manifypods_with_utf8.t ....... ok
t/metadata.t ................... ok
t/metadata2.t .................. ok
t/mymeta.t ..................... ok
t/new_from_context.t ........... ok
t/notes.t ...................... ok
t/par.t ........................ skipped: No compiler found
t/parents.t .................... ok
t/perl_mb_opt.t ................ ok
t/pod_parser.t ................. ok
t/ppm.t ........................ skipped: No compiler found
t/properties/dist_suffix.t ..... ok
t/properties/license.t ......... ok
t/properties/module_name.t ..... ok
t/properties/needs_compiler.t .. ok
t/properties/release_status.t .. ok
t/properties/requires.t ........ ok
t/properties/share_dir.t ....... ok
t/resume.t ..................... ok
t/runthrough.t ................. ok
t/sample.t ..................... ok
t/script_dist.t ................ ok
t/signature.t .................. ok
t/test_file_exts.t ............. ok
t/test_reqs.t .................. ok
t/test_type.t .................. ok
t/test_types.t ................. ok
t/tilde.t ...................... ok
t/unit_run_test_harness.t ...... ok
t/use_tap_harness.t ............ ok
t/versions.t ................... ok
t/write_default_maniskip.t ..... ok
t/xs.t ......................... skipped: No compiler found
All tests successful.
Files=53, Tests=1133, 31 wallclock secs ( 0.26 usr 0.07 sys + 25.28 cusr 5.47 csys = 31.08 CPU)
Result: PASS
Building Module-Build
-> OK
Successfully reinstalled Module-Build-0.4229
Searching Crypt::SSLeay () on cpanmetadb ...
-> FAIL Finding Crypt::SSLeay on cpanmetadb failed.
! Could not find a release matching Crypt::SSLeay on MetaCPAN.
Searching Crypt::SSLeay on mirror http://reposerver/repo/cpan/CPAN ...
--> Working on Crypt::SSLeay
Fetching http://reposerver/repo/cpan/CPAN/author ... .72.tar.gz
-> OK
Unpacking Crypt-SSLeay-0.72.tar.gz
Entering Crypt-SSLeay-0.72
Checking configure dependencies from META.json
Checking if you have Try::Tiny 0.19 ... Yes (0.30)
Checking if you have Getopt::Long 0 ... Yes (2.4)
Checking if you have Path::Class 0.26 ... Yes (0.37)
Checking if you have ExtUtils::CBuilder 0.280205 ... Yes (0.280206)
Configuring Crypt-SSLeay-0.72
Running Makefile.PL
*** THIS IS NOT AN ERROR, JUST A MESSAGE FOR YOUR INFORMATION ***
Do you really need Crypt::SSLeay?
Starting with version 6.02 of LWP, https support was unbundled into
LWP::Protocol::https. This module specifies as one of its prerequisites
IO::Socket::SSL which is automatically used by LWP::UserAgent unless
this preference is overridden separately. IO::Socket::SSL is a more
complete implementation, and, crucially, it allows hostname
verification. Crypt::SSLeay does not support this. At this point,
Crypt::SSLeay is maintained to support existing software that already
depends on it.
However, it is possible that your software does not really depend on
Crypt::SSLeay, only on the ability of LWP::UserAgent class to
communicate with sites over SSL/TLS.
If are using version LWP 6.02 or later, and therefore have installed
LWP::Protocol::https and its dependencies, and do not explicitly use
Net::SSL before loading LWP::UserAgent, or override the default socket
class, you are probably using IO::Socket::SSL and do not really need
Crypt::SSLeay.
Before installing Crypt::SSLeay, you may want to try specifying a
dependency on LWP::Protocol::https.
Failed to build and link a simple executable using OpenSSL
(END)
IROCK@reposerver:~ $ ls -lrt /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay*|sed 's/ed852698/IROCK/g'
-rw-rw-r-- 1 IROCK ueng 129534 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.73_06.tar.gz
-rw-rw-r-- 1 IROCK ueng 129261 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.73_04.tar.gz
-rw-rw-r-- 1 IROCK ueng 129575 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.72.tar.gz
-rw-rw-r-- 1 IROCK ueng 15182 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.72.readme
-rw-rw-r-- 1 IROCK ueng 1505 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.72.meta
-rw-rw-r-- 1 IROCK ueng 121431 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.64.tar.gz
-rw-rw-r-- 1 IROCK ueng 13716 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.64.readme
-rw-rw-r-- 1 IROCK ueng 1014 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.64.meta
A little history on our proposed (not yet implemented) Nagios environment is this, we are in an offline environment. So either replicate the software repositories using reposync or rsync, or I install stuff 1 package at a time. I know these outside environments get updated often so I sync daily. So I should be up to date.
I am really not sure what the real problem I have tried installing using cpanm and cpan, I was pasting the cpan output:
#cpan
cp[2} install Module::Build Crypt::SSLeay
cpanm (App::cpanminus) 1.7044 on perl 5.016003 built for x86_64-linux-thread-multi
Work directory is /root/.cpanm/work/1573504666.13396
You have make /usr/bin/make
You have LWP 5.837
You have /usr/bin/tar: tar (GNU tar) 1.26
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
You have /usr/bin/unzip
Searching Module::Build () on cpanmetadb ...
-> FAIL Finding Module::Build on cpanmetadb failed.
! Could not find a release matching Module::Build on MetaCPAN.
Searching Module::Build on mirror http://reposerver/repo/cpan/CPAN ...
Downloading index file http://reposerver/repo/cpan/CPAN/module ... ils.txt.gz ...
--> Working on Module::Build
Fetching http://reposerver/repo/cpan/CPAN/author ... 229.tar.gz
-> OK
Unpacking Module-Build-0.4229.tar.gz
Entering Module-Build-0.4229
Checking configure dependencies from META.json
Checking if you have Module::Metadata 1.000002 ... Yes (1.000037)
Checking if you have File::Copy 0 ... Yes (2.23)
Checking if you have version 0.87 ... Yes (0.9907)
Checking if you have File::Spec 0.82 ... Yes (3.40)
Checking if you have CPAN::Meta 2.142060 ... Yes (2.150010)
Checking if you have File::Path 0 ... Yes (2.09)
Checking if you have File::Basename 0 ... Yes (2.84)
Checking if you have Perl::OSType 1 ... Yes (1.003)
Configuring Module-Build-0.4229
Running Build.PL
Checking optional features...
dist_authoring..........disabled
requires:
! Archive::Tar is not installed
recommends:
* Pod::Readme is not installed
inc_bundling_support....disabled
requires:
! inc::latest (0.4005) is installed, but we need version >= 0.5
ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions
of the modules indicated above before proceeding with this installation
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Module-Build' version '0.4229'
-> OK
Checking dependencies from MYMETA.json ...
Checking if you have Module::Metadata 1.000002 ... Yes (1.000037)
Checking if you have File::Spec 0.82 ... Yes (3.40)
Checking if you have ExtUtils::Install 0 ... Yes (1.58)
Checking if you have File::Compare 0 ... Yes (1.1006)
Checking if you have File::Find 0 ... Yes (1.20)
Checking if you have CPAN::Meta 2.142060 ... Yes (2.150010)
Checking if you have File::Path 0 ... Yes (2.09)
Checking if you have Perl::OSType 1 ... Yes (1.003)
Checking if you have ExtUtils::Manifest 0 ... Yes (1.61)
Checking if you have ExtUtils::CBuilder 0.27 ... Yes (0.280206)
Checking if you have Getopt::Long 0 ... Yes (2.4)
Checking if you have File::Copy 0 ... Yes (2.23)
Checking if you have Parse::CPAN::Meta 1.4401 ... Yes (2.150010)
Checking if you have Text::Abbrev 0 ... Yes (1.02)
Checking if you have Pod::Man 2.17 ... Yes (2.27)
Checking if you have Data::Dumper 0 ... Yes (2.145)
Checking if you have version 0.87 ... Yes (0.9907)
Checking if you have ExtUtils::ParseXS 2.21 ... Yes (3.35)
Checking if you have CPAN::Meta::YAML 0.003 ... Yes (0.018)
Checking if you have TAP::Harness 3.29 ... Yes (3.42)
Checking if you have Test::More 0.49 ... Yes (1.302168)
Checking if you have Text::ParseWords 0 ... Yes (3.29)
Checking if you have File::Temp 0.15 ... Yes (0.2301)
Checking if you have File::Basename 0 ... Yes (2.84)
Checking if you have Cwd 0 ... Yes (3.40)
Checking if you have ExtUtils::Mkbootstrap 0 ... Yes (6.68)
Building and testing Module-Build-0.4229
Building Module-Build
t/00-compile.t ................. ok
t/PL_files.t ................... ok
t/actions/installdeps.t ........ ok
t/actions/manifest_skip.t ...... ok
t/add_property.t ............... ok
t/add_property_array.t ......... ok
t/add_property_hash.t .......... ok
t/basic.t ...................... ok
t/bundle_inc.t ................. skipped: $ENV{MB_TEST_EXPERIMENTAL} is not set
t/compat.t ..................... ok
t/compat/exit.t ................ ok
t/debug.t ...................... ok
t/destinations.t ............... ok
t/ext.t ........................ ok
t/extend.t ..................... ok
t/files.t ...................... ok
t/help.t ....................... ok
t/install.t .................... ok
t/install_extra_target.t ....... ok
t/manifypods.t ................. ok
t/manifypods_with_utf8.t ....... ok
t/metadata.t ................... ok
t/metadata2.t .................. ok
t/mymeta.t ..................... ok
t/new_from_context.t ........... ok
t/notes.t ...................... ok
t/par.t ........................ skipped: No compiler found
t/parents.t .................... ok
t/perl_mb_opt.t ................ ok
t/pod_parser.t ................. ok
t/ppm.t ........................ skipped: No compiler found
t/properties/dist_suffix.t ..... ok
t/properties/license.t ......... ok
t/properties/module_name.t ..... ok
t/properties/needs_compiler.t .. ok
t/properties/release_status.t .. ok
t/properties/requires.t ........ ok
t/properties/share_dir.t ....... ok
t/resume.t ..................... ok
t/runthrough.t ................. ok
t/sample.t ..................... ok
t/script_dist.t ................ ok
t/signature.t .................. ok
t/test_file_exts.t ............. ok
t/test_reqs.t .................. ok
t/test_type.t .................. ok
t/test_types.t ................. ok
t/tilde.t ...................... ok
t/unit_run_test_harness.t ...... ok
t/use_tap_harness.t ............ ok
t/versions.t ................... ok
t/write_default_maniskip.t ..... ok
t/xs.t ......................... skipped: No compiler found
All tests successful.
Files=53, Tests=1133, 31 wallclock secs ( 0.26 usr 0.07 sys + 25.28 cusr 5.47 csys = 31.08 CPU)
Result: PASS
Building Module-Build
-> OK
Successfully reinstalled Module-Build-0.4229
Searching Crypt::SSLeay () on cpanmetadb ...
-> FAIL Finding Crypt::SSLeay on cpanmetadb failed.
! Could not find a release matching Crypt::SSLeay on MetaCPAN.
Searching Crypt::SSLeay on mirror http://reposerver/repo/cpan/CPAN ...
--> Working on Crypt::SSLeay
Fetching http://reposerver/repo/cpan/CPAN/author ... .72.tar.gz
-> OK
Unpacking Crypt-SSLeay-0.72.tar.gz
Entering Crypt-SSLeay-0.72
Checking configure dependencies from META.json
Checking if you have Try::Tiny 0.19 ... Yes (0.30)
Checking if you have Getopt::Long 0 ... Yes (2.4)
Checking if you have Path::Class 0.26 ... Yes (0.37)
Checking if you have ExtUtils::CBuilder 0.280205 ... Yes (0.280206)
Configuring Crypt-SSLeay-0.72
Running Makefile.PL
*** THIS IS NOT AN ERROR, JUST A MESSAGE FOR YOUR INFORMATION ***
Do you really need Crypt::SSLeay?
Starting with version 6.02 of LWP, https support was unbundled into
LWP::Protocol::https. This module specifies as one of its prerequisites
IO::Socket::SSL which is automatically used by LWP::UserAgent unless
this preference is overridden separately. IO::Socket::SSL is a more
complete implementation, and, crucially, it allows hostname
verification. Crypt::SSLeay does not support this. At this point,
Crypt::SSLeay is maintained to support existing software that already
depends on it.
However, it is possible that your software does not really depend on
Crypt::SSLeay, only on the ability of LWP::UserAgent class to
communicate with sites over SSL/TLS.
If are using version LWP 6.02 or later, and therefore have installed
LWP::Protocol::https and its dependencies, and do not explicitly use
Net::SSL before loading LWP::UserAgent, or override the default socket
class, you are probably using IO::Socket::SSL and do not really need
Crypt::SSLeay.
Before installing Crypt::SSLeay, you may want to try specifying a
dependency on LWP::Protocol::https.
Failed to build and link a simple executable using OpenSSL
(END)
IROCK@reposerver:~ $ ls -lrt /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay*|sed 's/ed852698/IROCK/g'
-rw-rw-r-- 1 IROCK ueng 129534 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.73_06.tar.gz
-rw-rw-r-- 1 IROCK ueng 129261 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.73_04.tar.gz
-rw-rw-r-- 1 IROCK ueng 129575 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.72.tar.gz
-rw-rw-r-- 1 IROCK ueng 15182 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.72.readme
-rw-rw-r-- 1 IROCK ueng 1505 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.72.meta
-rw-rw-r-- 1 IROCK ueng 121431 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.64.tar.gz
-rw-rw-r-- 1 IROCK ueng 13716 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.64.readme
-rw-rw-r-- 1 IROCK ueng 1014 Oct 30 14:08 /ks/run/repo/cpan/CPAN/authors/id/N/NA/NANIS/Crypt-SSLeay-0.64.meta
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Monitoring VMware With Nagios XI
The problem is all starting here
before you are going to be able to build Crypt::SSLeay you need Module::BuildCode: Select all
Searching Module::Build () on cpanmetadb ... -> FAIL Finding Module::Build on cpanmetadb failed. ... Checking optional features... dist_authoring..........disabled requires: ! Archive::Tar is not installed recommends: * Pod::Readme is not installed inc_bundling_support....disabled requires: ! inc::latest (0.4005) is installed, but we need version >= 0.5 ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Monitoring VMware With Nagios XI
One thing to note is it is specifically documented to run the command as
It is possibly this is for a know issue with the tests...
https://assets.nagios.com/downloads/nag ... ios-XI.pdf
Code: Select all
cpanm --notest Module::Build Crypt::SSLeay
https://assets.nagios.com/downloads/nag ... ios-XI.pdf
Re: Monitoring VMware With Nagios XI
That seems to easy, to really be the problem. The only repo I am not yet “able/or sure how” to update is the nagiosxi repo.
root@hpsatvld5302:~ # yum repolist
Loaded plugins: langpacks
repo id repo name status
epel local files for EPEL repo RHEL 7Server-x86_64 13,454
nagios-base Nagios 96
nagiosxi-deps Nagios XI Dependencies 31
repolist: 13,581
You have mail in /var/spool/mail/root
root@hpsatvld5302:~ # yum repolist
Loaded plugins: langpacks
repo id repo name status
epel local files for EPEL repo RHEL 7Server-x86_64 13,454
nagios-base Nagios 96
nagiosxi-deps Nagios XI Dependencies 31
repolist: 13,581
You have mail in /var/spool/mail/root
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Monitoring VMware With Nagios XI
If this is an offline system you aren't going to be able to update it and it should probably be disabled.gary80918 wrote:That seems to easy, to really be the problem. The only repo I am not yet “able/or sure how” to update is the nagiosxi repo.