Nagios Support Forum

Hello,

I am currently installing Nagios XI on RHEL 6.5, 64-bit, and we are experiencing an install failure during the 'A-subcomponents' script.

The error is:

-----start clip-----
It appears as though Ajaxterm is already configured, so we'll skip that step.
Subcomponent 'ajaxterm' installed OK
Installing wkhtmltopdf and wkhtmltoimage...
--2015-06-03 11:23:08-- http://assets.nagios.com/downloads/nagi ... d64.tar.gz
Resolving wwwXXXcom... 111.222.333.444
Connecting to wwwXXX.com|111.222.333.444|:31060... connected.
Proxy request sent, awaiting response... 301 Moved Permanently
Location: https://assets.nagios.com/downloads/nag ... d64.tar.gz [following]
--2015-06-03 11:23:08-- https://assets.nagios.com/downloads/nag ... d64.tar.gz
Resolving assets.nagios.com... failed: Name or service not known.
wget: unable to resolve host address “assets.nagios.com”
ERROR: Subcomponent 'wkhtmlx' installation failed - exiting.
Subcomponents installation failed - exiting
RESULT=1

===================
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: './A-subcomponents'
-----end clip-----

Our proxy allows the connection to the internet, but 'assets.nagios.com' does not seem to resolve using the wget utility.
Any hints? Can we work around the name resolution with an IP address for the assets server?

gabrotherton wrote:Can we work around the name resolution with an IP address for the assets server?

Yes, you just need to create a hosts entry. Lets get the ip of assets.nagios.com: Alright, now run the following to add the ip <-> hostname assignment to /etc/hosts. Let me know if that works for.

I added the IP address for assets.nagios.com to the /etc/hosts file and ran the ./fullinstall script. It appears the connection is timing out after the proxy connects:

Resolving www-proxyXXX.com... 111.222.333.444
Connecting to wwww-proxyXXX.com|111.222.333.444|:31060... connected.
Proxy request sent, awaiting response... 301 Moved Permanently
Location: https://assets.nagios.com/downloads/nag ... d64.tar.gz [following]
--2015-06-03 13:02:43-- https://assets.nagios.com/downloads/nag ... d64.tar.gz
Resolving assets.nagios.com... 72.14.181.71
Connecting to assets.nagios.com|72.14.181.71|:443... failed: Connection timed out.
Retrying.

--2015-06-03 13:03:47-- (try: 2) https://assets.nagios.com/downloads/nag ... d64.tar.gz
Connecting to assets.nagios.com|72.14.181.71|:443... failed: Connection timed out.
Retrying.

--2015-06-03 13:04:52-- (try: 3) https://assets.nagios.com/downloads/nag ... d64.tar.gz
Connecting to assets.nagios.com|72.14.181.71|:443... failed: Connection timed out.
Retrying.

--2015-06-03 13:05:58-- (try: 4) https://assets.nagios.com/downloads/nag ... d64.tar.gz
Connecting to assets.nagios.com|72.14.181.71|:443... failed: Connection timed out.
Retrying.

--2015-06-03 13:07:05-- (try: 5) https://assets.nagios.com/downloads/nag ... d64.tar.gz
Connecting to assets.nagios.com|72.14.181.71|:443...

Can we get the packages in a tarball and point the installation script to look for those packages on the local server?

Andy,

Just an FYI, we ran this installation before without any issues. This is the first instance where I run into an error with the wget feature. Yum updates from redhat.com are working just fine. I can do a wget google.com and get a response. So I think our proxy is allowing through put. However I did notice when I pointed firefox to https://72.14.181.71:443 I got prompted for a certificate acknowledgement. Could the wget function be timing out because it's waiting for a certificate acknowledgement?

If your Nagios system in behind a proxy server, you will have to edit your /etc/wgetrc file to allow the server access to the internet.
Here is a link to our FAQ explaining how to do that.
http://support.nagios.com/wiki/index.ph ... th_Proxies

that was the problem. The https proxy was not set in the /etc/wgetrc file.

Thanks!

Great! Locking 'er up!