KBI 311659 Missing Heartbeat Email From One Daughter Engine
Version
Argent Advanced Technology – All Versions
Date
Thursday, 17 May 2018
Summary
Customer noticed missing heartbeat email from one of the multiple Daughter Engines
‘Last Contact Time’ for all Daughter Engine appeared current on Supervising Engine
Trace Log of internal heartbeat Relator contained ongoing errors, for example,
~REL_HEARTBEAT_DAUGHTER_ENGINE_NAME.TXT
Mon Apr 23 17:00:03.393 DaughterEngine ArgentService Could not spawn shared monitor engine process
Tue Apr 24 01:00:06.031 DaughterEngine ArgentService Could not spawn shared monitor engine process
Tue Apr 24 09:00:04.486 DaughterEngine ArgentService Could not spawn shared monitor engine process
Tue Apr 24 17:00:04.430 DaughterEngine ArgentService Could not spawn shared monitor engine process
Wed Apr 25 01:00:06.356 DaughterEngine ArgentService Could not spawn shared monitor engine process
Wed Apr 25 09:00:04.073 DaughterEngine ArgentService Could not spawn shared monitor engine process
Wed Apr 25 17:00:05.212 DaughterEngine ArgentService Could not spawn shared monitor engine process
Thu Apr 26 01:00:05.049 DaughterEngine ArgentService Could not spawn shared monitor engine process
Thu Apr 26 09:00:05.099 DaughterEngine ArgentService Could not spawn shared monitor engine process
Thu Apr 26 17:00:04.341 DaughterEngine ArgentService Could not spawn shared monitor engine process
Fri Apr 27 01:00:06.638 DaughterEngine ArgentService Could not spawn shared monitor engine process
Fri Apr 27 09:00:04.086 DaughterEngine ArgentService Could not spawn shared monitor engine process
Fri Apr 27 17:00:06.601 DaughterEngine ArgentService Could not spawn shared monitor engine process
Technical Background
Error message issue of ‘Could not spawn…’ can be a result of low system resource
Windows resource is more than just CPU, memory & disk space
There is internal resource such as ‘heap’ and more which was uncommonly discussed
There was case study showing VM Guest Tool not up-to-date caused network driver leaks on system resource under no CPU and memory stress
It is completely a Windows behavior
Resolution
Plan for server restart
If issue persists, contact Argent support