- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Re: hpasm on rhel 5
ProLiant Servers - Netservers
1752802
Members
5410
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-16-2007 08:02 PM
07-16-2007 08:02 PM
hpasm on rhel 5
Hi,
I have i problem on a prolian DL360 G5 whith rhel5
I try to install hpasmcli whith this rpm:
hpasm-7.8.0-88.rhel5.i386.rpm
It install the package, but on configuration give me this warning:
==============================================================================
The selinux boolean 'allow_ypbind' was enabled.
==============================================================================
==============================================================================
Text relocation was allowed for libcpqci.s0.1.
==============================================================================
==============================================================================
NOTE: selinux configuration in file_contexts was amended.
==============================================================================
==============================================================================
NOTE: Your SNMP stack can load the 32-bit hp ProLiant Management Extension.
Problems may result from using your distribution's SNMP stack.
See hp Documentation (HOWTO, agent manual) for more details.
==============================================================================
and when I try to start hpasm this say to me:
/etc/init.d/hpasm start
sed: can't read /etc/init.d/ipmi: No such file or directory
Using standard Linux IPMI device driver and hpasm-lite
Starting Proliant Standard IPMI based System Health Monismlited):
Starting Foundation Agents (cmafdtn):
Starting Server Agents (cmasvr):
Starting Storage Agents (cmastor):
hpasm: Server Management is enabled
----------------
And the file /etc/init.d/ipmi don't exist.
I hope this problem is generated by selinux.
Someone have some solution for this?
Regards
I have i problem on a prolian DL360 G5 whith rhel5
I try to install hpasmcli whith this rpm:
hpasm-7.8.0-88.rhel5.i386.rpm
It install the package, but on configuration give me this warning:
==============================================================================
The selinux boolean 'allow_ypbind' was enabled.
==============================================================================
==============================================================================
Text relocation was allowed for libcpqci.s0.1.
==============================================================================
==============================================================================
NOTE: selinux configuration in file_contexts was amended.
==============================================================================
==============================================================================
NOTE: Your SNMP stack can load the 32-bit hp ProLiant Management Extension.
Problems may result from using your distribution's SNMP stack.
See hp Documentation (HOWTO, agent manual) for more details.
==============================================================================
and when I try to start hpasm this say to me:
/etc/init.d/hpasm start
sed: can't read /etc/init.d/ipmi: No such file or directory
Using standard Linux IPMI device driver and hpasm-lite
Starting Proliant Standard IPMI based System Health Monismlited):
Starting Foundation Agents (cmafdtn):
Starting Server Agents (cmasvr):
Starting Storage Agents (cmastor):
hpasm: Server Management is enabled
----------------
And the file /etc/init.d/ipmi don't exist.
I hope this problem is generated by selinux.
Someone have some solution for this?
Regards
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2007 01:05 AM
07-18-2007 01:05 AM
Re: hpasm on rhel 5
My solution=turn off selinux.
More:
Is your server facing the public internet? If not, unless you have a lot of highly skilled staff that you wouldn't trust with your coffee cup, i don't see the need for it.
You can set it to "warn" rather than "block". This way you can ascertain if it will cause problems on your systems. I did this with my first RHEL4 box that has it, and it "warned" me so much i had to turn the warning off.
Unless you're defence CIA or MAJOR finance (in which case i don't know that you'd be on here) i don't see a need for it.
From memory you can turn it off through "system-config-security-level" or something similar. That was on RHEL4 though, i'm not sure of RH5, haven't used it yet but it can't be that hard.
More:
Is your server facing the public internet? If not, unless you have a lot of highly skilled staff that you wouldn't trust with your coffee cup, i don't see the need for it.
You can set it to "warn" rather than "block". This way you can ascertain if it will cause problems on your systems. I did this with my first RHEL4 box that has it, and it "warned" me so much i had to turn the warning off.
Unless you're defence CIA or MAJOR finance (in which case i don't know that you'd be on here) i don't see a need for it.
From memory you can turn it off through "system-config-security-level" or something similar. That was on RHEL4 though, i'm not sure of RH5, haven't used it yet but it can't be that hard.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP