07-20-2017 06:46 AM - edited 03-01-2019 09:26 AM
What would cause jobs to hang in launched status. Had this issue this morning, logs didn't show any errors. Unix admin stopped and started the agent and all is working again. Currently on Tidal 6.2 agent is 3.0.1.09
Solved! Go to Solution.
07-21-2017 03:29 AM
Hi,
For one thing that is a fairly old agent version. The problem is usually insufficient memory assigned to the agent at startup. You might want to add something like
minmem=512
maxmem=1024
to your tagent.ini file.
07-27-2017 08:21 AM
I see the ini, will try that, thanks.
07-21-2017 03:29 AM
Hi,
For one thing that is a fairly old agent version. The problem is usually insufficient memory assigned to the agent at startup. You might want to add something like
minmem=512
maxmem=1024
to your tagent.ini file.
07-21-2017 06:16 AM
Joe, thanks for the information, yes it is an old agent, we are in the process is installing the newest agents on the servers as part of a migration to new Linux servers. I will pass the information along to the Unix/Linux team about adding the minmem and maxmem to the ini file.
Thanks
07-27-2017 08:00 AM
Hi Joe,
We have seen this issue many times over the years, on Windows as well as Unix agents. For Windows, would we just add these values to the Parameters field in agent service configuration?
Thanks
07-27-2017 08:18 AM
I believe they should work adding them to the tagent.ini file the same as on unix.
07-27-2017 08:21 AM
I see the ini, will try that, thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide