Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
agent_keepalive alerts not happening
#1
Hello guys - 1st of all want to say thanks for a great bit of software - this does just what I need, and does it well.

The only unsolved problem in my installation is the ability to send an alert when the agent or machine running the agent shuts down. I saw the earlier post about the "bug" where keep alive alerts were being broken by ping alerts - and this is not my situation.

All I have is a handful of proc and data modules assigned to my agent. I created the agent_keepalive alert, and assigned it 0/0 for max/min.

I've turned off the Agent and the server and hoped to receive the alert - but it doesnt happen.

Any ideas what I can look at?
 Reply
#2
Quote:Hello guys - 1st of all want to say thanks for a great bit of software - this does just what I need, and does it well.

Thanks ! Smile. Nice place San Francisco, I was there on holidays !!

Quote:The only unsolved problem in my installation is the ability to send an alert when the agent or machine running the agent shuts down. I saw the earlier post about the "bug" where keep alive alerts were being broken by ping alerts - and this is not my situation.

All I have is a handful of proc and data modules assigned to my agent. I created the agent_keepalive alert, and assigned it 0/0 for max/min.

I've turned off the Agent and the server and hoped to receive the alert - but it doesnt happen.

Any ideas what I can look at?[/quote]

There is a bug there. I'm working on it now, because it was a unfinished bug for release 1.3 and another source of problems. Don't worry, I think this should be easy to fix. I'll post here the solution in a few hours.
 Reply
#3
Thanks for the quick response - im excited to get the fix!
 Reply
#4
Quote:Hello guys - 1st of all want to say thanks for a great bit of software - this does just what I need, and does it well.
Any ideas what I can look at?

I've just uploaded new code about this issue, it affects to SQL data, data server and console as well, so is not a minor or stable change. Works for me now (keepalive is now a "standard" module) and get inputs from agent contact data (from any source, data server or network server) any server could detect a keepalive under it's time limit and raise alerts assigned to this module. Also this module could be deleted from console.

If you want to try it I will please to assist you in every I can. You need to access SVN code, and apply changes manually, is not easy if you dont work before with SVN, but it has no technical dificulties, this is officially code for 1.3.1, a minor fix release scheduled for february.
 Reply
#5
Yes please - can you give the steps involved? I'm no svn expert, but if you give me some pointers I should be fine.
 Reply
#6
well I did a svn checkout. I replaced the console and server code with the new version. Its still not working - I guess I missed something. What is the "sql data and "data server" changes I need to make?

I did notice that the icon for the keepalive monitor is now broken and I had to delete it from my configured agents. So something had changed
 Reply
#7
Quote:well I did a svn checkout. I replaced the console and server code with the new version. Its still not working - I guess I missed something. What is the "sql data and "data server" changes I need to make?

I did notice that the icon for the keepalive monitor is now broken and I had to delete it from my configured agents. So something had changed

I'm working on a tarball for 1.3.1 beta. A minimal upgrade is needed (very simple) and no coding skills required. It takes me one day more. I want to fix several problems detected on 1.3.0 and add some minimal new features.
 Reply
#8
Quote:well I did a svn checkout. I replaced the console and server code with the new version. Its still not working - I guess I missed something. What is the "sql data and "data server" changes I need to make?

I did notice that the icon for the keepalive monitor is now broken and I had to delete it from my configured agents. So something had changed

Last commit for 1.3.1 branch solves all problems with keepalive, and it's very stable (tested several days on several different environments, some of them with huge load). Take a look at project website about that:

http://pandora.sourceforge.net/en/index....=downloads

To "migrate" to 1.3.1 you only need to insert a new data in ttipo_module table as described here:

INSERT INTO `ttipo_modulo` VALUES (100,'keep_alive',-1,'KeepAlive','mod_keepalive.png');
 Reply
#9
Dont forget to take a look on:

http://www.openideas.info/wiki/index.php...tification
 Reply
#10
Thanks - that worked great!
 Reply


Users browsing this thread: 1 Guest(s)


(c) 2006-2018 Artica Soluciones Tecnológicas. Contents of this wiki are under Create Common Attribution v3 licence. | pandorafms.com | pandorafms.org

Theme © MyBB Themes