search cancel

Sysload Agent for Windows: History not available - sldrmhst process crashes

book

Article ID: 203453

calendar_today

Updated On:

Products

CA Automic Sysload

Issue/Introduction

Some Windows servers having migrated to a different Cloud while having a Windows Agent 5.80 installed are no longer showing metrics available for Long Term History.

The process sldrmhst.exe seems to crash upon Sysload Collector service startup, only process sldrmd.exe remains active.

The following kind of errors may appear in the logs while doing a chart based on Long Term History metrics

 

In sldfsd.log

 fs_treq] ISAM error (-100) Line 709 File fs_trqa.c

[fs_treq] Error, domain (sCPU         v3) not found

In sldrmd.log:

[coll]  (RcvCollMsg) WaitFor Sem_Msg (rc=0) Tm=180000 
[coll] Error RcvCollMsg-4 from HIST 

In sldrmd.log we observe that the following lines having [hist] do not appear during the collector startup:

[Evt] Events history file can be used until the year 2024. 
[hist] Hist - Main Begin 
[hist] Dbg_hist_level = 0 
[hist] Dbg_SldLockFile_level = 0 
[hist] Starting Hist process [LBtreeFile] ... (Apr 19 2017 - 18:33:03) 
[hist] LBtree version : LBtreeFile 1.0 Oct  5 2016 18:56:25 win_x64 40.1 
[hist] Activities history file can be used until the year 2024. 
[hist] INFO : Hist priority 'normal'. 
[hist] INFO : history processing span time defined by user (180 sec.) 
[hist] Init ISAM --> OK ! 
[hist] Processing File : 'D:\SYSLOAD\hom\history\activity' ... 
[hist]  ... Historical Description updated ! 
[hist]  ... Checking Version (2W) --> OK ! 
[hist]  ... Checking Station (DE0-VSIAAS-632) --> OK ! 
[hist] SldLockFile 'D:\SYSLOAD\hom\history\activity.slf' was successfully initialized 
[coll] AutoDeclare - Thread has started (TraceLevel=0). 

 

Environment

Release : 5.8

Component : Sysload Agent for Windows

 

Cause

System issue, probably a Windows / GPO update requiring a Windows Reboot had been applied and the server had not yet been rebooted.

Resolution

Restart the Windows Server hosting the Agent.

Else, as a workaround you can recreate the Windows Service Sysload Collector, to do so:

1. stop sysload collector

2. open again the localsystem cmd on the sldrmd folder

3. launch sldrmd -remove

4. launch sldrmd -install

5. go to the windows services, properties on sysload collector and set it to startup "automatic delayed start" and then Start it
Check if the sldrmhst.exe still crashes when launched via the windows service.

If not, start manually the Sysload Collector via the command sldrmd -start from a Windows command line started as Localsystem

A reboot of the Windows server will probably be necessary after the service is recreated.