[hobbit] Duration for one round of server side module
tj_yang at hotmail.com
Fri May 15 02:46:45 CEST 2009
There are a few questions need to be addressed for non-home deployment.
1. Do we want to have xymon clients to query Sun's patch database file ?
The answer should be No for a site have big xymon client installations.
2. the pca xymon client module should query internal solaris patch database server(on xymon server).
3. the pca xymon server side EXT module should in sync with Sun's patch database server and download the zip files for internal installation.
4. pca rely on wget and wget rely on other software also, be prepared to deal with pca xymon module for solaris 2.6 and above that doesn't come with wget.
I don't quite understand why you design pca work as server side module
For me, I did it as a client side module and create another column (pca) for each xymon client.
Here is an example of what it looks like so far
P.S. I interacted with pca author but failed to convince him we (xymon community) can have a "-M" option to send out xymon needed html format.
From: Asif Iqbal
Sent: Thursday, May 14, 2009 1:41 PM
To: hobbit at hswn.dk
Subject: [hobbit] Duration for one round of server side module
I implemented a server side perl script using this http://xymonton.trantor.org/doku.php/tutorials:ssmodule as the template.
I like to run it only once daily, so I put status+1d for the bb command.
But I need help to find out how long it takes for the script to complete for my ~300 hosts.
Currently I have it setup just like the setup in the above url, like the following.
CMD hobbitd_channel --channel=client --log=$BBSERVERLOGS/pca.log $BBHOME
And it is taking tons of resources since it receives all the patch/pkg info from 300 servers through client channel
and generate a patch report using the tool pca (http://www.par.univie.ac.at/solaris/pca/) for each host. It allows us
to find out the patch status for all solaris boxes
Here is an snippet of the top processes sorted by RSS
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
8687 hobbit 2248M 581M run 39 0 0:02:31 1.1% hobbitd_channel/1
8648 hobbit 58M 56M run 39 0 0:07:42 2.5% hobbitd/1
10223 hobbit 21M 20M run 20 0 0:00:03 15% perl5.8.5/1
7115 devmon 11M 11M sleep 59 0 0:00:44 1.5% devmon/1
8689 hobbit 8816K 6968K sleep 59 0 0:07:52 2.7% pca.pl/1
If I can find out how long it takes to run I can then add an INTERVAL accordingly. I do not need to
process the client data more than once a day
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Xymon