Sysload: Why Historical metrics are not available

book

Article ID: 110648

calendar_today

Updated On:

Products

CA Automic Sysload

Issue/Introduction



Why Historical metrics from Sysload Agents are not available ?

Environment

Sysload Agents

Resolution

Possible causes are:
  • File Server is not started
  • File Server is unreachable
  • Information in Management Server DB is not consistent with File Server configuration

File Server is not started
Check(s)Solution(s)
- Is the “sldfsd.exe (on Windows platform) or the” sldfs_req (on UNIX/Linux platform) process running?- Start the File Server

File Server is unreachable
Check(s)Solution(s)
- Is the socket configured for the File Server listener reachable from the Management Server’s host? (“telnet <Agent_IP_Address> :<Port>”) [Default value is “9502”]
- Are they any firewall rules in place preventing the Management Server and the agent to communicate?
- Modify network configuration and/or firewall rules.
Information in Management Server DB is not consistent with File Server configuration
Check(s)Solution(s)
Compare agent’s properties displayed in the Analyst Rich Client (Console) to the File Server communication parameter.- Update agent’s declaration parameters (In the Analyst Rich Client: right-click on the agent, then select “Update…”)

Additional Information

Things to suspect:
  • File Server is not started
  • Agent (Host itself or File Server only) is unreachable
  • Information in Management Server DB is not consistent with File Server configuration
 
 
Files to check:
  • File Server log file (sldfsd.log)
  • File Server configuration file (sldfsd.ini or sldfsd-init)