LLAWP consumes almost 100% of the CPU in Web Agent
Article ID: 217554
Updated On:
Products
CA Single Sign On Agents (SiteMinder)
SITEMINDER
Issue/Introduction
A SiteMinder Web Agent was installed and configured on an RHEL 7.9 server.
The Web Agent version is 12.52 SP01 CR09.
There are two issues with this system.
- When the Web Server is started, the LLAWP immediately consumes 99.x% of the CPU.
- After a few hours, the semaphore used by the agent seems to be deleted, so the agent cannot communicate with the LLAWP process.
Since there is one LLAWP instance running, it cannot start another one.
The user will get an internal server error.
The instruction described to avoid that situation didn't work (1).
Uncommenting the line "RemoveIPC=no" in /etc/systemd/logind.conf file and restarting systemd-logind didn't work either.
Cause
The Web Agent is configured to write its logfiles to the Apache httpd/logs directory, however, the permissions on the directory were not correct to allow the Web Agent access to its logfiles.
Resolution
Permissions on the Apache logs directory had been misconfigured preventing the Web Agent from accessing its logs.
Once the permissions were corrected, the Agent is running fine without consuming a high CPU.
Additional Information
Feedback
Yes
No
Powered by
