Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
cancel
Showing results for 
Search instead for 
Did you mean: 

Nagios not loading

riyan
Frequent Advisor

Nagios not loading

Hi,
I installed ICE-linux in my SLES 10 server and logged in to sim with port 50000 (https://hostname:50000)but when i tried to load Nagios from tools>integrated console>Nagios i am getting following error.

Nagios is not available at this time.

To make Nagios available, use the Options->Configure ICE-Linux Management Services
menu item.

If you have already configured the ICE-Linux management services, log in to the
CMS and enter the following command to verify that the
web server at https://10.10.10.201/nagios is running:

On Red Hat operating systems:

/etc/init.d/httpd status

On SUSE operating systems:

/etc/init.d/apache2 status


If the web server is not running, enter the following command to start it.

On Red Hat operating systems:

/etc/init.d/httpd start

On SUSE operating systems:

/etc/init.d/apache2 startssl

when i try to perform Options->Configure ICE-Linux Management Services i am getting

Using node prefix 'icelx'
Error: /opt/hptc/sbin/create_nodenames --searchall returned: 255
error in stdout

I started apache according to this and checked the https://10.10.10.201/nagios URL.Then i am getting

Secure Connection Failed
An error occurred during a connection to 10.10.10.201.
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)

* The page you are trying to view can not be shown because the authenticity of the received data could not be verified.

* Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.

Can some body please tell me what am i doing wrong and if i have to configure ssl how to do it in SLES 10.thanks in advance.
28 REPLIES
Donna Firkser
Regular Advisor

Re: Nagios not loading

Are you using IC-Linux V2.11?

Let's see if your set up is correct. Before running "Configure ICE-Linux Management Services"

1) Make sure you have managed systems discovered in SIM

2) Make sure the managed systems are installed with a supported Linux OS

3) Make sure all the managed systems you want to monitor with Nagios have an ICE-Linux license assigned to them

4) Make sure you run "Configure or Repair Agents" on all the managed systems to set up the SIM SSH keys.

5) Create a self-signed Apache certificate certificate on the CMS by running /opt/hptc/config/sbin/create_apache_certificate gconfigure.

When your done answering the questions, restart the Apache service

# /etc/init.d/apache2 stop
# /etc/init.d/apache2 startsll

Let us know how this goes.

Donna
riyan
Frequent Advisor

Re: Nagios not loading

Hi Donna,

1) Make sure you have managed systems discovered in SIM
Right now i have installed hpsnmp agents only on 2 servers for the testing.please check the attached screen shot.

2) Make sure the managed systems are installed with a supported Linux OS

OS is SLES 10 SP2 and SP 3

3) Make sure all the managed systems you want to monitor with Nagios have an ICE-Linux license assigned to them

I haven't added the license yet.should i add individual licence to managed systems also or i have add it in the SIM?please advice

4) Make sure you run "Configure or Repair Agents" on all the managed systems to set up the SIM SSH keys.

when i run Configure or Repair Agents in the same cms server following is the out put i got.i am not sure what options i have to select.

Subscribing to WBEM / WMI indications ...
Subscribe to WBEM / WMI Indications (DONE).......................... [FAILED]
Check whether target system met the requirements and all of the software require
d to support indications is installed.
WBEM protocol settings are not valid/enabled for this system in HP SIM. Check yo
ur HP SIM settings.

Send test WBEM/ WMI indication from the system (DONE)............... [FAILED]
CMS has to be subscribed for WBEM / WMI indications before it can receive a test
indication.

Configuring SSH authentication (START)...
Configure SSH for host based authentication (DONE).................. [FAILED]
Configuration failed to complete due to the following exception:
Ssh Operati
on failed for node:cms.cpstl.lk. SSH_BAD_API_USAGEYou must supply a valid userna
me! [Unknown cause]

LINUX configuration command (START)...
Configuring SNMP Settings (START)...
Stopping SNMP daemon...
Shutting down snmpd:..done
Adding read community string cpstl
Adding trap destination address cms.cpstl.lk
Restarting SNMP Daemon...
Starting snmpd..done
Setting SNMP trap destination / SNMP read community string (DONE)....[SUCCESS]

Set Trust relationship to "Trust by Certificate" (START) ...
Setting Trust for System Management Home Page.
Stopping System Management Home Page
Shutting down hpsmhd..done
Copying /tmp/hprepair_cms/cms.cpstl.lk.pem to /opt/hp/hpsmh/certs
Restarting System Management Home Page
Starting hpsmhd ....done
Set Trust relationship to "Trust by Certificate" (DONE)............. [SUCCESS]

Setting admin password/Trust for Insight Management Agents 7.1/earlier (START)
Setting admin password/Trust for legacy HP Server Management Agents..[SKIPPED] H
P Server Management Drivers and Agents, is not installed.

Linux configuration commands (DONE)................................. [SUCCESS]

5) Create a self-signed Apache certificate certificate on the CMS by running /opt/hptc/config/sbin/create_apache_certificate gconfigure.

i ran the above script and created a certificate after apache restart checked nagios.still same ssl error

An error occurred during a connection to 10.10.10.201.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)



riyan
Frequent Advisor

Re: Nagios not loading

Yes i am using IC-Linux V2.11

I went through the ICE-Linux user's guide
trouble shoot steps.and it seems i haven't installed nagios properly.does it get installed automatically when im installing ICE-Linux? sorry for the silly questions.this is the first time i am installing sim.please help
Donna Firkser
Regular Advisor

Re: Nagios not loading

You need to first add the IC-Linux license to SIM License Manager and then use SIM license manager to assign the IC-Linux license to your two managed nodes.

Nagios automatically gets installed when you install IC-Linux and Nagios will automatically get configured and started when you run Configure ICE-Linux Management Services (provided you have licensed nodes to monitor).

The instructions for which CRA options to select should be in the Users Guide.

I believe you need to uncheck "Create subscription to WBEM events" and uncheck "Trust by Certificate". "Set read community string", "Set traps to refer...", "Configure SSH access authentication" and "Host based authentication" should all be checked/set.

After you ran CRA, did you re-run Configure Management Services? You'll have to check Stdout and Stderr to see if configure ran properly.

You can also run /etc/init.d/nagios status to see if nagios is running on the CMS.

Donna
riyan
Frequent Advisor

Re: Nagios not loading

Hi,

I got 11 license for.so can i just add one of these SIM license manager and add others to managed servers?

and in the Live monitor also i am getting a plain screen only.

I can see nagios files in the CMS server.but i cannot start the services.when i try to run
/etc/init.d/nagios status i am getting

cms:~ # /etc/init.d/nagios status
NO CACHE FILE! RERUN create_nodenames.
Failure at /opt/hptc/perl/lib/sim/hptc_node.pm line 356.
cms:~ #
I think i made a mistake when initial installation or ssl certificate creation.
I should read the documentations and installation guide again ant try this.
Donna Firkser
Regular Advisor

Re: Nagios not loading

Your installation is correct. Nagios and Live Monitor are not working because "Configure ICE-Linux Management Services" hasn't completed successfully.

You must have servers assigned with an ICE-Linux license for Nagios / Live Monitor to work. If you have no servers with licenses, "Configure Management Services" exits immediately and Nagios doesn't get configured or started.

You need to add the ICE-Linux license keys to SIM License Manager. See Section 6.6 in Installation Guide for instructions on "Adding ICE-Linux license keys" to SIM.

Then you need to assign an ICE-Linux license to each of your managed nodes. See Section 2.2. "Assigning ICE-Linux licenses to discovered systems" in Users Guide.

Once that's done you should be able to re-run "Configure Management Services".

Let me know how this goes.

Donna


riyan
Frequent Advisor

Re: Nagios not loading

Hi
Couldn't do this yet since some issues came up with our storage also :( will do as you suggested and post.Thanks
Donna Firkser
Regular Advisor

Re: Nagios not loading

No problem. I'll be out on vacation 3/25, 3/26, and 3/29 but will reply as soon as I can.

Donna
riyan
Frequent Advisor

Re: Nagios not loading

Hi Donna,
Hope you had a great vacation.I assigned the license for cms server and tried to run Configure ICE-Linux Management Services.But it failed with following error.

Warning: Cannot install ICE-Linux management agents on CMS node icelx1
Error: /opt/hptc/mgmt/bin/setup_management_services --install --verbose returned: 1
Important: Verify that you have run CRA to set up the SIM SSH credentials
on all your managed systems. One you have run CRA, you can run Install Agents
to set up the ICE-Linux management services on your managed systems.


i am unable to run CRA before running the Configure ICE-Linux Management Services as i am getting an error

Configuring SSH authentication (START)...
Configure SSH for host based authentication (DONE).................. [FAILED]
Configuration failed to complete due to the following exception:
Ssh Operati
on failed for node:cms.cpstl.lk. SSH_BAD_API_USAGEYou must supply a valid userna
me! [Unknown cause]

I changed my sshd config file also according to the help page's.please check the attached config file.any idea what is going wrong?
Donna Firkser
Regular Advisor

Re: Nagios not loading

That message during Configure is expected/benign since the CMS is the only node you're monitoring. If you have other managed nodes you want to monitor (besides the CMS), then you need to assign an ICE-Linux license to those target nodes and run CRA on them. If you run Configure, Configure will push out the ICE-Linux management agents to the other target nodes.

When you run CRA you should only check the following 4 options. Everything else should be unchecked.
* Set read community string
* Set traps to refer to this instance...
* Configure SSH access authentication
* Host based authentication

And then select "Use the following credentials for all systems" and enter the root username and password.

I get the same "SSH_BAD_API_USAGE You must supply a valid username!" if I specify the incorrect root username and password for the CMS so please verify that you're using the correct root credentials for the CMS.

You should be able to launch Nagios now and see the CMS (aka nh) in the UI.

What happens when you try to launch Nagios?

If you can't launch Nagios, please send me the output from /etc/init.d/nagios status.

Thanks,
Donna
riyan
Frequent Advisor

Re: Nagios not loading

Hi Donna,

Sorry for the delay.I managed to run CRA successfully after changing the
PasswordAuthentication no to yes in the /etc/ssh/sshd_config file.after this i assigned licenses to 3 nodes (because i didn't get permission to run CRA on all the production servers) and ran Configure ICE-Linux Management Services.in the stdout i got

Collecting configuration information from managed systems ...
write 7986, 1, 4, eth0 to db => icelx1 (cms.cpstl.lk)
check_nrpe error: Connection refused by host => icelx3 (erpap101.cpstl.lk)
write 16054, 1, 4, bond0 to db => icelx2 (erpbk101.cpstl.lk)
Vars Warning - icelx2 vars.ini have been resynchronized Nodes icelx[2-3] did not respond

following is the output from nagios status

cms:/var/log # /etc/init.d/nagios status
Checking for nagios
NAGIOS OK: 1 process, status log updated 21 seconds ago
Checking for supermon: running
Checking for mon: running
Gathering status for nrpe ... icelx[1-3]
Error Connection refused by host - erpap101
Ok NRPE v2.12 - erpbk101,cms
Nagios nsca:
cms: 0 data packet(s) sent to host successfully.

when i tried to load nagios i am still getting same old ssl error.please let me know if you need any logs.

Thanks,
Riyan.
Donna Firkser
Regular Advisor

Re: Nagios not loading

Is apache2 running on your CMS?

# /etc/init.d/apache2 status

Do you see any errors in any of the apache2 log files.

# cd /var/log/apache2

I haven't seen this error before so I did some googling and found the information below. Can you please review this information and make sure your ssl set up is correct.

Please try stopping the firewall on your CMS and see if you are able to launch Nagios.

Can you also send me the contents of iceInstallerAnswers.

# cat /opt/hp/icelx/config/iceInstallerAnswers

Thanks,
Donna


-- INFO FOUND ON GOOGLE --
Error code: ssl_error_rx_record_too_long
Your SSL website may fail to load and display the error

Error code: ssl_error_rx_record_too_long

This usually means the implementation of SSL on your server is not correct. The error is usually caused by a server side problem which the server administrator will need to investigate.

Below are some things we recommend trying.

- Ensure that port 443 is open and enabled on your server. This is the standard port for https communications.

- If SSL is using a non-standard port then FireFox 3 can sometimes give this error. Ensure SSL is running on port 443.

- If using Apache2 check that you are using port 443 for SSL. This can be done by setting the ports.conf file as follows

â clip â
Listen 80
Listen 443 https
â clip â

- Make sure you do not have more than one SSL certificate sharing the same IP. Please ensure that all SSL certificates utilise their own dedicated IP.

- If using Apache2 check your vhost config. Some users have reported changing to _default_ resolved the error.

riyan
Frequent Advisor

Re: Nagios not loading

Hi Donna,

A power reboot to the CMS server and Apache restart sorted the issue :).I think may be some configuration was conflicting prior to the reboot.now nagios is working.But need to have a look and try to integrate other servers too.Will update you once everything is OK.Thanks for all the Patience and support.
Donna Firkser
Regular Advisor

Re: Nagios not loading

Good news. Let me know if you need help with anything else.

Thanks,
Donna
riyan
Frequent Advisor

Re: Nagios not loading

Hi Donna,
Problem again :(
any idea why i am getting this

cms:/opt/hptc/nagios/var # /opt/hptc/nagios/libexec/gather_all_data --verbose
write 7986, 1, 4, eth0 to db => icelx1 (cms.cpstl.lk)
check_nrpe error: Connection refused by host => icelx3 (erpap101.cpstl.lk)
write 16054, 1, 4, bond0 to db => icelx2 (erpbk101.cpstl.lk)




cms:/opt/hptc/nagios/var # /etc/init.d/nagios status
Checking for nagios
NAGIOS OK: 1 process, status log updated 34 seconds ago
Checking for supermon: running
Checking for mon: running
Gathering status for nrpe ... icelx[1-3]
Error Connection refused by host - erpap101
Ok NRPE v2.12 - erpbk101,cms
Nagios nsca:
cms: 0 data packet(s) sent to host successfully.
Donna Firkser
Regular Advisor

Re: Nagios not loading

It looks like you may have not run "Configure or Repair Agents" on icelx3 (erpap101.cpstl.lk) and therefore the ICE-Linux management agents didn't get pushed out to erpap101.

Check /var/log/mgmt.log on the CMS to see if you see any messages like "Warning: Cannot distribute pdsh keys to ...".

If you see this message, then you need to run Configure or Repair Agents on the target node and re-run Configure ICE-Linux Management Services.

Let me know how it goes.

Donna
riyan
Frequent Advisor

Re: Nagios not loading

CRA ran successfully.following is the stdout output for configure ICE-LX management services.I have attached mgmt log here.I don't see any error except some proxy connection.

Using node prefix 'icelx'
Reading cached number file /opt/hptc/database/etc/icelx/nodenumbers
Assigning node numbers
Rewriting cached number file /opt/hptc/database/etc/icelx/nodenumbers
Repopulating icelx_Servers
Repopulating icelx_Console_ports
Repopulating icelx_Enclosures
Adding ICE-Linux attributes to objects in
icelx_Servers
icelx_Console_ports
icelx_Enclosures
Creating /opt/hptc/etc/sysconfig/managementData.ini ...
Creating /etc/powerd.conf
Cluster Configuration - ICELX Cluster version HP icelx 2.11 20090610 r15422


Configuring system wide functions / policies / behaviors
Executing C02hptc_cluster_sfs sconfigure
Executing C02ssh_config sconfigure
Executing C10cluster_fstab sconfigure
Executing C20sysparams sconfigure
Executing C25syslimits sconfigure
Executing C66ibbond sconfigure
Executing C75mpiic sconfigure

Configuring service specific functions
Executing C05pdsh gconfigure
Executing C10hptc_cluster_fs gconfigure
Executing C30syslogng_forward gconfigure
Executing C50cmf gconfigure
Executing C50nagios gconfigure
You can create or modify nagios web accounts using the command:
# /usr/sbin/htpasswd2 /opt/hptc/nagios/etc/htpasswd.users nagiosadmin

Creating /opt/hptc/etc/sysconfig/managementData.ini ...
Executing C50supermond gconfigure
Executing C51nagios_monitor gconfigure
info: nconfig started
info: Executing on head node

info: Executing C10hptc_cluster_fs nconfigure
info: Executing C10hptc_cluster_fs_client nconfigure
info: Executing C30syslogng_forward nconfigure
info: Executing C50cmf nconfigure
info: Executing C50gather_data nconfigure
info: Executing C50nagios nconfigure
info: Executing C50supermond nconfigure
info: Executing C51nagios_monitor nconfigure
info: Executing C51nrpe nconfigure
info: Executing C30syslogng_forward cconfigure
info: Executing C50cmf cconfigure
info: Executing C50supermond cconfigure
info: nconfig shut down
info: nconfig started
info: Executing on head node

info: Executing C10hptc_cluster_fs nrestart
info: Executing C10hptc_cluster_fs_client nrestart
info: Executing C30syslogng_forward nrestart
info: Executing C50cmf nrestart
info: Executing C50gather_data nrestart
info: Executing C50nagios nrestart
info: Executing C50supermond nrestart
info: Executing C51nagios_monitor nrestart
info: Executing C51nrpe nrestart
info: Executing C30syslogng_forward crestart
info: Executing C50cmf crestart
info: Executing C50supermond crestart
info: nconfig shut down


setup_management_services started at - Apr 5 18:51:57


Create /opt/hptc/etc/sysconfig/managementData.ini ...

Create /opt/hptc/etc/sysconfig/vars.ini ...

Distribute ssh keys for pdsh...


Installing ICE-Linux Management Agents on nodes:
erpap101,erpbk101,cms

Build ID files ...
erpbk101: Warning: Permanently added 'erpbk101,10.10.10.41' (RSA) to the list of known hosts.
erpap101: Warning: Permanently added 'erpap101,10.10.10.21' (RSA) to the list of known hosts.
erpbk101: Warning: Permanently added 'erpbk101.cpstl.lk' (RSA) to the list of known hosts.
erpap101: Warning: Permanently added 'erpap101.cpstl.lk' (RSA) to the list of known hosts.
Building ID file for icelx1 (cms)
Building ID file for icelx2 (erpbk101)
Building ID file for icelx3 (erpap101)

Create /opt/hptc/supermon/etc/mon.conf ...

Create /opt/hptc/mgmt/tar/mgmt.tar ...

Push out install.sh...
Running tool cp_install_sh with job id 1758.
Task Name :defRunNowTaskId_1270473723916_78
Job ID :1758
Tool Name :cp_install_sh
Job State :Complete
User Name :root
Execute As User :root
Start Time :Monday, April 5, 2010 6:52:03 PM LKT
End Time :Monday, April 5, 2010 6:52:04 PM LKT
Elapsed Time : 118 milliseconds
Node :erpbk101.cpstl.lk
Status :Complete
Exit Code :-1
Files copied :2/2
Source :cms.cpstl.lk:/opt/hptc/mgmt/bin/install.sh
Destination :erpbk101.cpstl.lk:/opt/hptc/mgmt/bin/install.sh
Source :cms.cpstl.lk:/opt/mx/icle/icle.properties
Destination :erpbk101.cpstl.lk:/opt/hptc/mgmt/bin/icle.properties
STDOUT :


Node :erpap101.cpstl.lk
Status :Complete
Exit Code :-1
Files copied :2/2
Source :cms.cpstl.lk:/opt/hptc/mgmt/bin/install.sh
Destination :erpap101.cpstl.lk:/opt/hptc/mgmt/bin/install.sh
Source :cms.cpstl.lk:/opt/mx/icle/icle.properties
Destination :erpap101.cpstl.lk:/opt/hptc/mgmt/bin/icle.properties
STDOUT :



Run install.sh on managed systems ...
erpbk101: --18:53:55-- http://10.10.10.201:60000/management_data/vars.ini
erpbk101: => `/opt/hptc/etc/sysconfig/vars.ini'
erpap101: --18:53:38-- http://10.10.10.201:60000/management_data/vars.ini
erpap101: => `/opt/hptc/etc/sysconfig/vars.ini'
erpbk101: Connecting to 10.10.10.201:60000... connected.
erpbk101: HTTP request sent, awaiting response... 200 OK
erpbk101: Length: 3,515 (3.4K)
erpbk101:
erpap101: Connecting to 10.10.14.2:3128... connected.
erpbk101: 0K ... 100% 335.22 MB/s
erpbk101:
erpbk101: 18:53:55 (335.22 MB/s) - `/opt/hptc/etc/sysconfig/vars.ini' saved [3515/3515]
erpbk101:
erpbk101: --18:53:55-- http://10.10.10.201:60000/management_data/managementData.ini
erpbk101: => `/opt/hptc/etc/sysconfig/managementData.ini'
erpbk101: Connecting to 10.10.10.201:60000... connected.
erpap101: Proxy request sent, awaiting response... 407 Proxy Authentication Required
erpbk101: HTTP request sent, awaiting response... 200 OK
erpap101: 18:53:38 ERROR 407: Proxy Authentication Required.
erpap101:
erpbk101: Length: 452
erpbk101:
erpbk101: 0K 100% 71.84 MB/s
erpbk101:
erpbk101: 18:53:55 (71.84 MB/s) - `/opt/hptc/etc/sysconfig/managementData.ini' saved [452/452]
erpbk101:
erpap101: --18:53:38-- http://10.10.10.201:60000/management_data/managementData.ini
erpap101: => `/opt/hptc/etc/sysconfig/managementData.ini'
erpap101: Connecting to 10.10.14.2:3128... connected.
erpbk101: --18:53:55-- http://10.10.10.201:60000/management_data/mon.conf
erpbk101: => `/opt/hptc/supermon/etc/mon.conf'
erpbk101: Connecting to 10.10.10.201:60000... connected.
erpbk101: HTTP request sent, awaiting response... 200 OK
erpbk101: Length: 783
erpbk101:
erpbk101: 0K 100% 39.30 MB/s
erpbk101:
erpbk101: 18:53:55 (39.30 MB/s) - `/opt/hptc/supermon/etc/mon.conf' saved [783/783]
erpbk101:
erpap101: Proxy request sent, awaiting response... 407 Proxy Authentication Required
erpap101: 18:53:38 ERROR 407: Proxy Authentication Required.
erpap101:
erpap101: --18:53:38-- http://10.10.10.201:60000/management_data/mon.conf
erpap101: => `/opt/hptc/supermon/etc/mon.conf'
erpap101: Connecting to 10.10.14.2:3128... connected.
erpap101: Proxy request sent, awaiting response... 407 Proxy Authentication Required
erpap101: 18:53:38 ERROR 407: Proxy Authentication Required.
erpap101:
erpap101: /opt/hptc/mgmt/bin/install.sh: line 254: /etc/init.d/nrpe: No such file or directory
erpap101: /opt/hptc/mgmt/bin/install.sh: line 258: /opt/hptc/syslog-ng/etc/gconfig.d/syslog-setup: No such file or directory
erpap101: /opt/hptc/mgmt/bin/install.sh: line 259: /opt/hptc/syslog-ng/etc/gconfig.d/syslog-setup: No such file or directory
erpap101: /opt/hptc/mgmt/bin/install.sh: line 262: /opt/hptc/supermon/etc/init.d/mond-setup: No such file or directory
erpap101: /opt/hptc/mgmt/bin/install.sh: line 265: /etc/init.d/mond: No such file or directory
erpbk101: insserv: script ipmi.hp: service ipmidrv already provided!
erpbk101: MOND: Bound to socket 38154
----------------
erpap101
----------------

Configure and start management services ...

----------------
erpbk101
----------------

Configure and start management services ...

Shutting down NRPE service
Configuring NRPE
nrpe 0:off 1:off 2:off 3:on 4:off 5:on 6:off
Starting NRPE service
Configuring syslog-ng to forward events to syslog-ng aggregator
Shutting down syslog services..done
Starting syslog services..done
Starting the MON service: ..done

Collecting configuration information from managed systems ...
write 7986, 1, 4, eth0 to db => icelx1 (cms.cpstl.lk)
check_nrpe error: Connection refused by host => icelx3 (erpap101.cpstl.lk)
write 16054, 1, 4, bond0 to db => icelx2 (erpbk101.cpstl.lk)
Vars Warning - icelx2 vars.ini have been resynchronized Nodes icelx3 did not respond

Install Agents Done

Done
Donna Firkser
Regular Advisor

Re: Nagios not loading

What OS do you have installed on
erpap101.cpstl.lk?

e.g.
# cat /etc/redhat-release
OR
# cat /etc/SuSE-release

Can you log in to erpap101.cpstl.lk and send me the output from the install.sh command. Make sure you do this on erpap101 and not the CMS.

# cd /opt/hptc/mgmt/bin
# ./install.sh

Thanks,
Donna
riyan
Frequent Advisor

Re: Nagios not loading

OS is SLES 10 SP 3

Output from
erpap101# cat /etc/SuSE-release
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 3
erpap101:/opt/hptc/mgmt/bin #

Output from .install.sh

erpap101:/opt/hptc/mgmt/bin # ./install.sh
--09:09:07-- http://10.10.10.201:60000/management_data/vars.ini
=> `/opt/hptc/etc/sysconfig/vars.ini'
Connecting to 10.10.14.2:3128... connected.
Proxy request sent, awaiting response... 407 Proxy Authentication Required
09:09:07 ERROR 407: Proxy Authentication Required.

--09:09:07-- http://10.10.10.201:60000/management_data/managementData.ini
=> `/opt/hptc/etc/sysconfig/managementData.ini'
Connecting to 10.10.14.2:3128... connected.
Proxy request sent, awaiting response... 407 Proxy Authentication Required
09:09:07 ERROR 407: Proxy Authentication Required.

--09:09:07-- http://10.10.10.201:60000/management_data/mon.conf
=> `/opt/hptc/supermon/etc/mon.conf'
Connecting to 10.10.14.2:3128... connected.
Proxy request sent, awaiting response... 407 Proxy Authentication Required
09:09:07 ERROR 407: Proxy Authentication Required.


Configure and start management services ...

./install.sh: line 254: /etc/init.d/nrpe: No such file or directory
./install.sh: line 258: /opt/hptc/syslog-ng/etc/gconfig.d/syslog-setup: No such file or directory
./install.sh: line 259: /opt/hptc/syslog-ng/etc/gconfig.d/syslog-setup: No such file or directory
./install.sh: line 262: /opt/hptc/supermon/etc/init.d/mond-setup: No such file or directory
./install.sh: line 265: /etc/init.d/mond: No such file or directory
erpap101:/opt/hptc/mgmt/bin #

is this something to do with the proxy configuration?

Thanks,
Riyan.
Donna Firkser
Regular Advisor

Re: Nagios not loading

Yes. This error looks like it's related to the proxy server. ICE-Linux/SIM does not have proxy server support. Do you know how to disable the proxy server? It may be as simple as making sure you don't have any proxy variables set in /etc/wgetrc and in your environment(env command) but I will need to confirm this.

Once you get rid of the proxy server, you should be able to delete the /opt/hptc/nagios directory on the target node where the wget is failing (NOT on the CMS) and re-run /opt/hptc/mgmt/bin/install.sh on the target node.

Donna
riyan
Frequent Advisor

Re: Nagios not loading

Hi Donna,

Yes.erpap101 is configured with proxy and erpbk101 is not.most probably this must be the issue.But our SAP consultants doesn't want to remove the proxy since the system just went live :( anyway in nagios web page it is showing all 3 servers.I will wait for some time and give it a try again.Thanks a lot for all the help and quick response.

Thanks,
Riyan.
Donna Firkser
Regular Advisor

Re: Nagios not loading

As an FYI, even though the server is showing up in Nagios some of the Nagios services will remain in the PENDING state since the monitoring daemons for the target node with the proxy issue didn't get configured properly.

You basically need to figure out how to get the following wget command to succeed on erpap101 if you want to configure ICE-Linux monitoring for this target node.

# wget http://10.10.10.201:60000/management_data/vars.ini

One of the other ICE-Linux developers suggested you try to enhance the proxy to exclude systems on your 10 network.

Thanks,
Donna
riyan
Frequent Advisor

Re: Nagios not loading

Hi Donna,

Yes i agree with you.I will try to find out a way to add the proxy exception to internal systems.But I just want to know

If the wget works on the erpap101 server will i be able to run the install.sh successfully?

or what if i copy that file manually to erpap101?

if i run the install.sh manually from server what will happen?

Thanks,
Riyan.
Donna Firkser
Regular Advisor

Re: Nagios not loading

If you can run the wget manually on the target server, you should be able to re-run Configure ICE-Linux Management Services so the IC-Linux monitoring agents get set up correctly on this node.

The one caveat is that you should remove the "opt/hptc" directory on erpap101 before you re-run Configure ICE-Linux Management Services since this node is in a funky state.

Donna