{"searchBar":{"inputPlaceholder":"Search by keyword or ask a question","searchBtn":"Search","error":"Please enter a keyword to search"}}
{}
{"support":{"yesButton":"yes","noButton":"no","feedback":{"title":"What can we do to improve?"},"submitButton":"Submit","successMessage":"Thank you for your feedback","title":"Was this helpful?","feedbackPercentLabel":"of people found this helpful","captcha":{"error":"Please tick the box"}}}
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.
 
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.
 

Can't find what you are looking for?

Reach out to our Customer Care team to receive information on technical support, assistance for complaints and more.