From: Dan V. M. <bi...@gm...> - 2006-03-02 16:15:09
|
That should work just fine, I understood it. Thanks On 3/2/06, Schwimmer, Eric E *HS <EE...@hs...> wrote: > Okay, I've added this to the top of the "docs/INSTALLATION" file: > > <snip> > A quick Devmon overview > --------------------------------------------------------------------- > The way Devmon works is fairly simple. Here's the gist of it: > 1. An outside process (most likely devmon running with the > --readbbhosts flag) updates the Devmon database from the > Hobbit or BigBrother bb-hosts file. > In a single-node installation, the Devmon database is stored > in the 'hosts.db' file. In a multi-node installation, it > is kept in a MySQL database. > 2. Devmon reads in its templates. A single-node installation > reads the templates from disk at the beginning of every > polling cycle. The multi-node version reads the templates > from the database, but only if they have been updated/changed > since the last time it read them. > 3. Devmon does SNMP queries on all of the devices in its database. > SNMP queries are optimized so that if the same SNMP OID is > specified in multiple tests for a device, it is only queried > once. > 4. Devmon applies template logic against the returned SNMP data. > The involves doing transforms, applying thresholds, and then > finally rendering the message to be sent to the display server. > 5. Devmon sends the rendered messages to the Display server. > 6. Devmon sleeps for any remaining time in the poll cycle. > 7. Return to step #1 (although the interval at which your > external process updates your devmon database might not > be the same as your poll interval, so Devmon might actually > go to step #2 at this point). > </snip> > > And changed the devmon "usage" statement to appear as follows: > > <snip> > Usage: devmon [arguments] > > Arguments: > -c Specify alternate config file (i.e. -c /etc/devmon.cfg) > -f Run in foreground. Prevents running in daemon mode. > -p Print message. Don't send message to display server, instead > print it to stdout > -v Verbose mode. The more v's, the more vebose logging. > > Mutually exclusive arguments: > Note: all of these arguments cause Devmon to exit after > performing the action listed in the argument, without > sending any data to your display server. > > --readbbhosts Read in data from the BigBrother/Hobbit hosts file, > write it to the hosts database. > --syncconfig Update multinode DB with the global config options > configured on this local node. > --synctemplates Update multinode device templates with the template > data on this local node. > --resetowners Reset multinode device ownership data. This will > cause all nodes to recalculate ownership data. > > </snip> > > Let me know if this clears or muddies the water for you. > -Eric > > ________________________________ > > From: dev...@li... on behalf of Dan Vande M= ore > Sent: Thu 3/2/2006 9:29 AM > To: dev...@li... > Subject: Re: [Devmon] problem getting devmon to work > > > > Yes, I think you should explain the purpose of the hosts.db file, and > mention that devmon --readbbhosts's only purpose is to keep this file > up to date. That way, not only will us sysadmins not only have a > better understanding of the fundamentals, there will also be a place > the the docs explaining what bbreadhosts does. > > Thanks > > Dan > > On 3/2/06, Schwimmer, Eric E *HS <EE...@hs...> wrote: > > > > The documentation could be at fault. I don't think I really mention > > anywhere that the --readbbhosts flag causes Devmon to exit after > > reading in the bb-hosts file. Comments? > > > > -Eric > > > > > -----Original Message----- > > > From: dev...@li... > > > [mailto:dev...@li...] On Behalf > > > Of Dan Vande More > > > Sent: Wednesday, March 01, 2006 9:37 PM > > > To: dev...@li... > > > Subject: Re: [Devmon] problem getting devmon to work > > > > > > Holy cow, that was the problem. I can't believe I misinterpreted that= . > > > Everything seems to be working now, thanks. > > > > > > -Dan > > > > > > On 3/1/06, Schwimmer, Eric E *HS > > > <EE...@hs...> wrote: > > > > > > > > Hi Dan, > > > > > > > > I *think* the problem that you are having is that you are > > > > running devmon with the --readbbhosts flag; this flag tells > > > > devmon to read the bbhosts file into the database and then quit, > > > > which I what I think is happening here. > > > > > > > > Try running it like this: > > > > ./devmon -vv -p > > > > (the -p flag implies -f as welli, I should probably document that := ) > > > > > > > > If you've previously run devmon with the --readbbhosts flag, and > > > > devmon has created the hosts.db file in the devmon > > > directory, then it > > > > should read in from that file, poll your hosts, do the > > > logic, and spit > > > > out your message. > > > > > > > > The design reasoning behind the --readbbhosts flag, and why I didnt > > > > just make devmon read the bbhosts file every poll cycle, is twofold > > > > (you can probably skip reading this, I just like typing): > > > > > > > > 1) The fact that running a multi-node cluster, you probably > > > dont want > > > > to run the devmon process on your display machine, but want > > > to farm it > > > > out to dedicated devmon polling servers. The readbbhosts flag make= s > > > > it so that you can import your bb-hosts file into the > > > cluster database, > > > > without having to actually run devmon on the display machine. > > > > > > > > 2) Reading the bb-hosts file and querying the hosts takes a > > > little while, > > > > since devmon queries every host in the bb-hosts file, every > > > time (making > > > > no assumptions as to whether hosts that were there during the last > > > > auto-discovery are the same hosts that are there on this > > > one; people > > > > have been known to swap out devices with different > > > vendor/models and not > > > > change the bb-hosts ip or hostname). So I didnt want this > > > auto-discovery > > > > phase to interfere with polling times. > > > > > > > > -Eric > > > > > > > > -----Original Message----- > > > > From: dev...@li... on behalf > > > of Dan Vande More > > > > Sent: Wed 3/1/2006 4:18 PM > > > > To: dev...@li... > > > > Subject: [Devmon] problem getting devmon to work > > > > > > > > My devmon is close, but still not working. Here's what I've done: > > > > > > > > Made a new template for a cisco 7609, just changed the > > > spec, is about > > > > all - it's just like a 6509. > > > > > > > > Put devmon next to the appropriate line in bb-hosts, like this: > > > > > > > > <ip> gsr-east.domain # ssh !telnet DEVMON > > > > > > > > Configured my devmon.cfg: > > > > > > > > MULTINODE=3DNO > > > > BBHOSTS=3D/home/monitor/server/etc/bb-hosts > > > > BBTAG=3DDEVMON > > > > SNMPCIDS=3Dmycid,public,private > > > > NODENAME=3DHOSTNAME > > > > PIDFILE=3D/var/run/devmon/devmon.pid > > > > LOGFILE=3D/var/log/hobbit/devmon.log > > > > DBHOST=3Dlocalhost > > > > DBNAME=3Ddevmon > > > > DBUSER=3Ddevmon > > > > DBPASS=3Ddevmon > > > > BBTYPE=3Dhobbit > > > > DISPSERV=3Dlocalhost > > > > DISPPORT=3D1984 > > > > MSGSIZE=3D8096 > > > > MSGSLEEP=3D10 > > > > CYCLETIME=3D60 > > > > DEADTIME=3D180 > > > > CLEARTIME=3D180 > > > > NUMFORKS=3D10 > > > > MAXPOLLTIME=3D30 > > > > SNMPTIMEOUT=3D2 > > > > SNMPTRIES=3D5 > > > > > > > > And run this: > > > > > > > > $ sudo -u monitor ./devmon -vvvvv -p -f --readbbhosts > > > > [06-03-01@15:15:32] SNMP querying all hosts in bb-hosts > > > file, please wait... > > > > [06-03-01@15:15:32] Querying pre-existing hosts > > > > [06-03-01@15:15:32] Discovered gsr-east.domain as a cisco 7609 > > > > > > > > And that's all I get. I thought I'd be getting the same > > > messages it's > > > > sending hobbit, but i'm not seeing them. > > > > > > > > What am I doing wrong? > > > > > > > > Thanks > > > > > > > > Dan > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by xPML, a groundbreaking > > > scripting language > > > > that extends applications into web and mobile media. Attend > > > the live webcast > > > > and join the prime developer group breaking into this new > > > coding territory! > > > > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121= 642 > > > > _______________________________________________ > > > > Devmon-support mailing list > > > > Dev...@li... > > > > https://lists.sourceforge.net/lists/listinfo/devmon-support > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking > > > scripting language > > > that extends applications into web and mobile media. Attend > > > the live webcast > > > and join the prime developer group breaking into this new > > > coding territory! > > > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=12164= 2 > > > _______________________________________________ > > > Devmon-support mailing list > > > Dev...@li... > > > https://lists.sourceforge.net/lists/listinfo/devmon-support > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking scripting lang= uage > > that extends applications into web and mobile media. Attend the live we= bcast > > and join the prime developer group breaking into this new coding territ= ory! > > http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642 > > _______________________________________________ > > Devmon-support mailing list > > Dev...@li... > > https://lists.sourceforge.net/lists/listinfo/devmon-support > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Devmon-support mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devmon-support > > > > |