Jobs hung in launched status

[Bruce Jones]

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

[Joe Fletcher · Accepted solution]

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.

[Bruce Jones]

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

[Jason Javitz]

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

[Joe Fletcher]

I believe they should work adding them to the tagent.ini file the same as on unix.

[Jason Javitz · Accepted solution]

I see the ini, will try that, thanks.