Hello. If anybody has a minute, I noticed a scheduled agent did not run to completion (with no errors) in a single database around 5 AM the other day. There is a print statement saying it started and a print saying it ended but the end never printed. Ever since then, none of the other scheduled agents within this database run. I’ve put a simple scheduled agent into this database and it fails to run, yet I paste the same agent into another database and it runs.
Does anybody know what might be occurring between agent manager and this single database? Will a server reboot resolve it? Is it a cache problem? Thank you very much for reading this.
Subject: agent stuck?
sounds like the agent may be stuck in memory. Issue “show task” at the server console and see if it shows as still running. Only 1 agent can run in a db at any time so if the agent is stuck this would explain why no other agents in that db have run. Also try “tell amgr sched” and see if this agent appears at the top of the list. This would indicate that the agent manager still has a hold of the agent. Try stopping the agent manager and see if it clears but be prepared that the agent manager may not shut down and a server reboot may be necessary.
Subject: Hung agent
It appears that you agent is hung, until it ends other agents will not run.I would add print statement to help diagnose where the logic is hung.
What is the time out for your agent manager? In should have terminated
the agent after the time has been exceeded.
Is this LotusScript or Java agent?