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.
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.
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?