- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Proliant Support Pack on Centos 5.4
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2010 03:00 AM
тАО01-15-2010 03:00 AM
I wanto to install Proliant Support Pack on Centos 5.4 but I have found many difficulty.
The final error is:
Error 5: One or more of the components were not able to install because its
installation requirements were not met.
Please review the hppldu.log file to determine the cause of the
failure. Common causes include: minimum kernel version requirements
were not met; required libraries were missing; kernel source was not
available to build components that are provided as source; and build
tools or environment were not available. Please correct the error
condition and re-run the HP ProLiant Deployment Utility.
Is there a simple guide?
Many thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 07:50 AM
тАО01-18-2010 07:50 AM
Re: Proliant Support Pack on Centos 5.4
I have tried to install hp-healt and hpsmh by rpm but when I do:
/etc/init.d/hp-health status
ERROR: This Server is NOT Supported!
(hpasmd) is stoppen [ OK ]
Why?
Thankx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 08:42 AM
тАО01-18-2010 08:42 AM
Re: Proliant Support Pack on Centos 5.4
[root@serverhost init.d]# service hp-snmp-agents start
ERROR: This Server is NOT Supported!
Starting Proliant System Health Monitor (hpasmd): [ OK ]
Already started Health agent (cmahealthd): [ OK ]
Already started Standard Equipment agent (cmastdeqd): [ OK ]
Already started Host agent (cmahostd): [ OK ]
Already started Threshold agent (cmathreshd): [ OK ]
Already started RIB agent (cmasm2d): [ OK ]
Starting Rack Infrastructure Info Srv (cpqriisd): [ OK ]
Starting Rack agent (cmarackd): [ OK ]
Already started Performance agent (cmaperfd): [ OK ]
Already started SNMP Peer (cmapeerd): [ OK ]
Already started Storage Event Logger (cmaeventd): [ OK ]
Already started FCA agent (cmafcad): [ OK ]
Already started SAS agent (cmasasd): [ OK ]
Already started IDA agent (cmaidad): [ OK ]
Already started IDE agent (cmaided): [ OK ]
Already started SCSI agent (cmascsid): [ OK ]
Already started NIC Agent Daemon (cmanicd): [ OK ]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 09:19 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2010 09:37 AM
тАО01-18-2010 09:37 AM
Re: Proliant Support Pack on Centos 5.4
Now I don't know how to monitorning the server.
Could you indicate me an alternative software (possibly simple) to monitoring server (temperature and fault) and raid status?
Thank you very much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2010 04:18 AM
тАО01-20-2010 04:18 AM
Re: Proliant Support Pack on Centos 5.4
[root@serverhost bus]# yum install lm_sensors
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* addons: centos.intergenia.de
* base: centos.xengage.it
* extras: centos.xengage.it
* updates: centos.intergenia.de
Setting up Install Process
Package lm_sensors-2.10.7-4.el5.x86_64 already installed and latest version
Package lm_sensors-2.10.7-4.el5.i386 already installed and latest version
Nothing to do
[root@serverhost bus]# sensors-detect
# sensors-detect revision 5291 (2008-06-23 23:40:46 -0700)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.
Next adapter: SMBus I801 adapter at 1c00 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel AMB FB-DIMM thermal sensor... No
Sorry, no sensors were detected.
Either your sensors are not supported, or they are connected to an
I2C or SMBus adapter that is not supported. See doc/FAQ,
doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
What do I have to do?
Which is a software to manage this server?