Search FAQs
PowerChute Business Edition Agent fails to connect using simple signaling on RHEL 5.x due to SELinux access policy
Issue:
PowerChute Business Edition (PowerChute) Agent cannot communicate with UPS using a simple signaling cable. The result is that communication is not established and “Unknown Device” appears in the PowerChute Agent Web UI.
Product Line:
PowerChute Business Edition
Environment:
OS: Red Hat Enterprise Linux (RHEL) 5.x x64, x86
Build: PowerChute Business Edition 9.1.1 and 9.0.3 OEM Basic and 25 Node Deluxe
Cause:
The problem is caused by Security-Enhanced Linux (SELinux) enforcing an access policy. The policy forbids a library used by the PowerChute Agent from running in its current context. RHEL has SELinux set to "Enforcing" mode by default.
Resolution:
1. Change the security context of the PowerChute library file.
2. Restart the PowerChute Agent.
PowerChute Business Edition (PowerChute) Agent cannot communicate with UPS using a simple signaling cable. The result is that communication is not established and “Unknown Device” appears in the PowerChute Agent Web UI.
Product Line:
PowerChute Business Edition
Environment:
OS: Red Hat Enterprise Linux (RHEL) 5.x x64, x86
Build: PowerChute Business Edition 9.1.1 and 9.0.3 OEM Basic and 25 Node Deluxe
Cause:
The problem is caused by Security-Enhanced Linux (SELinux) enforcing an access policy. The policy forbids a library used by the PowerChute Agent from running in its current context. RHEL has SELinux set to "Enforcing" mode by default.
Resolution:
1. Change the security context of the PowerChute library file.
Type the following into the command line:
chcon -t textrel_shlib_t /opt/APC/PowerChuteBusinessEdition/Agent/lib/linux/libNatComm.so
2. Restart the PowerChute Agent.
Released for:APC Lithuania
Did this answer your question?
