Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Note | ||
|---|---|---|
| ||
You can only do this if you're a PerformanceGuard administrator. | ||
| Wiki Markup |
You
can
view
Frontend
server
log
files
through
the
PerformanceGuard
web
interface
by
selecting
*ADMINISTRATION
>
Status
>
System
Status
{*},
then
selecting
the
*Log
Files
* tabtab,
and
then
looking
under
*.../collector/logs
{*}.
Alternatively,
you
can
look
directly
in
the
\[PerformanceGuard
installation
folder
\]\collector\logs
folder.
When you analyze the Frontend server logs you may find it helpful to know some log messages that relate to typical problems—and what you can do to solve those problems:
Read Timed Out
| Info | ||
|---|---|---|
| ||
Example: |
Could not read agent data on Socket \\[addr=/192.168.102.33,port=1060,localport=4003 \\] Created: Fri Jan 23 04:11:30 CET 2015 |
This message appears if an agent didn't reply to the Frontend server within the specified timeout value. If you get many of these warnings, it may indicate that the frontend server is overloaded, or that you have agents at very remote locations. In this case you may want to increase the collector socket timeout value in the PerformanceGuard web interface by selecting ADMINISTRATION > Setup > Parameters, and then selecting the Frontend tab.
Connection Reset
| Info | ||
|---|---|---|
| ||
Example: |
Could not read agent data on Socket \[addr=/85.235.243.208,port=53026,localport=4003 \] Created: Fri Jan 23 20:15:43 CET 2015 |
This message means that an agent has closed the connection when the Frontend server tried to read data from the agent. It may indicate that the frontend server is overloaded or that the agent socket timeout value is too small. You'll typically need to increase the socket timeout value of the agent in the PerformanceGuard web interface: Select ADMINISTRATION > Agent Configuration > Configurations, click the Edit link for the required configuration group, and then scroll down to the Agent Service Parameters.
Unexpected EOF on Input
| Info | ||
|---|---|---|
| ||
Example: | ||
| Wiki Markup | ||
WARNING: Could not read agent data on Socket \[addr=/213.83.130.29,port=2465,localport=4001 \] Created: Fri Jan 23 15:54:52 CET 2015 |
This warning means that some kind of communication error was detected when an agent set up a connection with the Frontend server. EOF means end-of-file.
Could Not Read Report on Socket
| Info | ||
|---|---|---|
| ||
Example: | ||
| Wiki Markup | ||
WARNING: Could not read report on Socket \[addr=/194.239.249.254,port=4870,localport=4001 \] Created: Fri Jan 23 15:54:54 CET 2015 |
This message means that the agent closed the connection when the Frontend server tried to read data from the agent. It may indicate that the Frontend server is overloaded or that the agent socket timeout value is too small. You'll typically need to increase the socket timeout value of the agent in the PerformanceGuard web interface: Select ADMINISTRATION > Agent Configuration > Configurations, click the Edit link for the required configuration group, and then scroll down to the Agent Service Parameters.
Agent: # Not added to Network: 0.0.0.0/0
| Info | ||
|---|---|---|
| ||
Example: |
This message means that the agent reported that its IP address was 0.0.0.0. PerformanceGuard won't create a network group based on this value.
Discarding Line: Timestamp Too Late
| Info | ||
|---|---|---|
| ||
Example: |
AgentReport logDiscard Discarding line: Timestamp too Late \[agent_id=16,sampleTime=1421932140000(Thu Jan 22 14:09:00 CET 2015) |
This message is issued when the Frontend server discards data that's older than five delivery intervals. This primarily serves to prevent an agent from reporting old data from another network if a computer was hibernated and then awakened at new location.
| Panel | ||||||
|---|---|---|---|---|---|---|
Search this documentation
On this page
In this section
|