Agents Stopped working

Kishore_Singamsetty

Hi,

Yesterday I scheduled some webreports to get executed, but today I noticed they didn't get executed, and my Livelink Server service got stopped,

After restart of Server and Admin services as well, my Agent thread is not picking the WebReports Schedule Agent to execute.

Any suggestions appreciated.

Thanks

Kishore

Appu_Nair1

 It looks my elink posts to this thread is not working so I am putting hopefully how to debug your situation

http://appukili.wordpress.com/2012/11/09/agents-agents-everywhere/

If you do not have livelink admin experience or scared to experiment you should work with OT Support
**************************************************************************************************************
This is what I wrote as part of a elink reply which I guess is not working in KB
I think your webreports agents are 20200 & 20201 so maybe concentrate on that



In agent debugging better open a ticket because there is a lot that could happen with that subsystem but from what I am seeing in this thread

I would run this query
Select agentid, enabled,lasttime, nexttime, agentname from agentschedule where agentid <> 9999 order by agentid  (9999 is  harmless personal agent there will be lots of it so don’t crowd the query)

If you see lasttime not getting updated for higher agentids for e.g 1000,2000,2990 has a lasttime,nextime that looks like it is some where in the current times being talked and perhaps 4000
Is not moving what is happening is the agentcontroller the threads that is in your ini like

Loader=sockserv;javaserver;agents;notification  etc etc are trying to run enabled agents in the database .When the thread spawn and after the dbconnection is made it will basically grab a hold of all the agents
And notifications and wfagents and whatever other sched jobs who it thinks should have run. For an enabled agent then it tries to find if the [schedulectivity] lists it as Enabled or not .If it does not find it in scheduleactivity it is assumed run it on this server
This is catually bad because what you think configured running on a server is running elsewhere as well if you did not really disable it in ini.

Then it actually looks in the [agents] section and understands what all should I be running and excluding in this run.
So if it thinks that I have to run

1000,2000,2990,4567  assume 2990 has a problem and is crashing livelink(trace, unhandled exception) well this vicious cycle runs so the lastimes for nobody will change you will be waiting for your agent

Usually OT support will move the offending agent to its own  thread and allow others to run. I am amazed at oscript as I am a developer  and these very simple debugging mechanisms so I Have written it more here

A lot of very intelligent people at OT makes this product and hopefully the newer CS10 has good kewl admin gui’s that pinpoint errors for better debugging