Installation guide

Agent Start-Up/Shutdown Issues (Framework Agents Only)
168 Web Agent Installation Guide
Agent Won’t Start Because LLAWP is Already Running or Log Messages not Written
to the Correct Log Files
Valid on UNIX
Symptom:
I'm having one or more of the following problems:
■
My Web Agent won't start because the LLAWP process is already running.
■
My Web Agent starts, however the log messages are being written to the log
files of a second agent instance.
Solution:
This problem may occur when multiple disks on the same computer use the same
mount point. The Web Agent uses the inode of a directory to allocate system
resources, and if the inodes are the same, resource collisions and errors result.
To fix this problem, use the following process:
1. Create a new subdirectory on your web server (this creates a unique inode).
2. Change the path shown in the ServerPath parameter of the Web Agent so it
points to the new subdirectory.
Note: For more information, see the Web Agent Configuration Guide.
Troubleshoot Agent Start-Up/ShutDown with LLAWP
If the Agent is not starting or shutting down properly, you can run the Low Level
Agent Worker Process (LLAWP) from the command line.
The LLAWP handles inter-process Agent management. For IIS 6.0, LLAWP starts
up after the Web Agent receives the first request. For Apache 2.0, the LLAWP
process automatically starts when the Apache web server starts.
By running LLAWP from the command line, you eliminate the web server from
the diagnostic process, which isolates Web Agent issues. Error messages are
written to the Event log for Windows or to the console on UNIX systems.