Agents stay frozen

4 views
Skip to first unread message

Phil -- wbtc.fr --

unread,
Sep 26, 2011, 3:08:02 PM9/26/11
to in-port...@googlegroups.com
Hi,

I had many times the case where an agent stay frozen (for monthes).

There are several causes for an agent to freeze, and I'd to add inside the cron task for agents a check: if any of them is frozen, reset it.

How to check if an agent is frozen? My proposal: the difference between "last run on" timestamp and actual time is greater than "run interval".

p

Alexander Obuhovich

unread,
Sep 26, 2011, 4:31:26 PM9/26/11
to in-port...@googlegroups.com
Interesting formula. I never thought about fact, that "run interval" is maximal time a particular agent could normally run.

New agent to look to dead agents. Interesting concept. What if watchman agent dies. Let's hope, that this won't be happening soon.



--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.



--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

Phil -- wbtc.fr --

unread,
Sep 26, 2011, 4:41:22 PM9/26/11
to in-port...@googlegroups.com
the only exception is process-mailing-queue agent. It's set to be ran each minute, but it could take more than 1 minute to send all emails...

The idea is not to create a new agent, but as posted, to include this as a watchdog in cron task responsible for agents starting, or somewhere else, but not at agent level.

2011/9/26 Alexander Obuhovich <aik....@gmail.com>

Dmitry Andrejev

unread,
Sep 26, 2011, 4:50:23 PM9/26/11
to in-port...@googlegroups.com
I have already created similar functionality before, but I had specified Timeout for each Agent which allows system to reset it! Why do we need another agent for that?


DA
Best regards,

Dmitry A.

Phil -- wbtc.fr --

unread,
Sep 26, 2011, 5:06:28 PM9/26/11
to in-port...@googlegroups.com
I just gave a way to calculate timeout. yes, no other agent is needed.

2011/9/26 Dmitry Andrejev <dand...@gmail.com>

Alexander Obuhovich

unread,
Sep 26, 2011, 5:13:33 PM9/26/11
to in-port...@googlegroups.com
I see. When you plan to run an agent you check if it's not running OR is running more then allowed, then reset it and run now.

Phil -- wbtc.fr --

unread,
Sep 27, 2011, 2:31:09 AM9/27/11
to in-port...@googlegroups.com
it's nearly that. Just that you don't plan to run the agent, because it appears to be already running... I don't know how agents schedules are made, but you got the main idea : monitor agents and reset them if needed - and why not sending an email to admin when an agent needed to be reset.

2011/9/26 Alexander Obuhovich <aik....@gmail.com>

Dmitry A.

unread,
Oct 15, 2011, 10:36:34 PM10/15/11
to in-port...@googlegroups.com
Hi guys,


Do we really need to send out any email notifications at this point?

I would think that Agent Timeout functionality would be enough at this point, don't you agree?


Also, question to the Alex about implementation of this in 5.2.0:

Currently there is public function getAll($from_cache = false) method which gets ALL, but running Agents. Do you I create a different method for Resetting running Agents based on their Timeout or adjust this one? What's you thoughts on this?


DA

Phil -- wbtc.fr --

unread,
Oct 16, 2011, 4:02:29 AM10/16/11
to in-port...@googlegroups.com
Hi Dmitry,

well, if a frozen agent doesn't need further inspection to find the cause, then yes, email isn't necessary at all :)

p

2011/10/16 Dmitry A. <dand...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/rZM4IaxoVfYJ.

Alexander Obuhovich

unread,
Oct 16, 2011, 8:44:29 AM10/16/11
to in-port...@googlegroups.com
Currently there is public function getAll($from_cache = false) method which gets ALL, but running Agents. Do you I create a different method for Resetting running Agents based on their Timeout or adjust this one? What's you thoughts on this?

No problems with that, since we can get:
  • agents, who are not running
  • agents, who are running longer, then allowed
at the same time in that method.


well, if a frozen agent doesn't need further inspection to find the cause, then yes, email isn't necessary at all :)

Usually agents got frozen due some Fatal Error, which we can't catch. However we can remember the fact, what we automatically restarted frozen agent somewhere in agent record.

Dmitry A.

unread,
Oct 16, 2011, 2:26:10 PM10/16/11
to in-port...@googlegroups.com
Here is a task and patch for 5.2.0 - please test when you have a chance:


1140: Ability to specify Timeout for Agents



DA
Ability-to-specify-Timeout-for-Agents.patch

Phil -- wbtc.fr --

unread,
Oct 16, 2011, 3:24:33 PM10/16/11
to in-port...@googlegroups.com
I'll install on websites where I encounter frequent freezes and let you know. Thanks for fast release :)

2011/10/16 Dmitry A. <dand...@gmail.com>
--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/KT6trZMhGRIJ.
Reply all
Reply to author
Forward
0 new messages