Sysload: Why Real-Time metrics are not available

Document ID : KB000110542
Last Modified Date : 21/08/2018
Show Technical Document Details
Question:
Why Real-Time metrics from a specific Sysload Agent are not available (greyed out in “Activities” list)?
 
Environment:
Sysload Agents
Answer:
Collector is not started
 
Error(s) / Warning(s)Check(s)Solution
“Stop banner” at the end of the log file - Are the “sldrmd.exe” & “sldrmdhst.exe” (on Windows platform) or the” sldrm_coll“& “sldrm_hist” (on UNIX/Linux platform) processes running?- Start the agent


Collector is unreachable
Error(s) / Warning(s)Check(s)Solution
"Agent is unreachable” pop-up in  the Analyst Rich Client (Console)- Is the socket configured for the Collector listener reachable from the Management Server’s host? (“telnet <Agent_IP_Address> :<Port>”)
- Are they any firewall rules in place preventing the Management Server and the agent to communicate?
-Are the agent properties in the Management Server’s DB consistent with the agent’s actual configuration?
- Modify network configuration and/or firewall rules.
- Update agent’s declaration parameters (In the Analyst Rich Client: right-click on the agent, then select “Update…”)

Perfmon counters are not available (Windows platforms)
Error(s) / Warning(s)Check(s)Solution
Several occurrences of coll - Reallocating 262144 bytes for PerfBuffer at the end of the sldrmd.log file.- Launch Perfmon and check the availability of counters- Rebuild Performance counters (KB000086978).

Information in Management Server DB is not consistent with Collector configuration
Error(s) / Warning(s)Check(s)Solution
 Compare agent’s properties displayed in the Analyst Console Rich Client to the Collector parameters set in the configuration file.- Update agent’s declaration parameters (In the Analyst Rich Client: right-click on the agent, then select “Update…”)
Additional Information:
Things to suspect:
  • Collector is not started
  • Agent (Host itself or Collector only) is unreachable
  • Perfmon counters are corrupted (Windows platforms ONLY)
  • Information in Management Server DB is not consistent with Collector configuration


Files to check:
  • Collector log file (sldrmd.log)
  • Collector configuration file (sldrmd.ini or sldrmd-init)