- Xymon - Xymon mailman web

Collecting RRD from custom script, but no graph
by Syms.MS＠forces.gc.ca 03 Mar '06

03 Mar '06

Hi, folks- I wrote a custom data collection script to send varying data to hobbit- hobbit receives it ok, displays the status properly and populates an rrd to store the data, but then doesn't graph it. I do get the graph name in a text hyperlink beside the magnifying glass icon, but that's it. I've done a similar thing with hobbit on a debian box before without a problem, but now that I'm running it on an aging Redhat Advanced Server 3 box, it's giving me some trouble. The configuration bits: I'm running rrdtool 1.0.48, gcc 2.3.3 and Hobbit 4.1.2p1. The output line from my script: ${BB} ${BBDISP} "status ${MACHINE}.trackoswex ${COLOR} `date` trackoswex: ${TRACKS} " In hobbitlaunch.cfg, I'ved added [trackoswex] ENVFILE /usr/local/hobbit/client/etc/hobbitclient.cfg NEEDS hobbitd CMD /usr/local/hobbit/server/ext/gccs/trackoswex.sh LOGFILE $BBSERVERLOGS/hobbitclient.log INTERVAL 30m >From hobbitgraph.cfg [trackoswex] TITLE OSWEX Tracks YAXIS Number of tracks DEF:tr=trackoswex.rrd:tracks:AVERAGE AREA:tr#00CCCC:Tracks COMMENT:These are the number of tracks received in the last 120 minutes.\n GPRINT:tr:LAST: \: %5.1lf (cur) GPRINT:tr:MAX: \: %5.1lf (max) GPRINT:tr:MIN: \: %5.1lf (min) GPRINT:tr:AVERAGE: \: %5.1lf (avg)\n >From hobbitserver.cfg TEST2RRD="cpu=la,disk,inode,qtree,memory,$PINGCOLUMN=tcp,http=tcp,dns=tcp,dig=tcp,time=ntpstat,vmstat,iostat,netstat,temperature,apache,bind,sendmail,mailq,nmailq=mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,trackoswex=ncv" # This defines which RRD files to include on the "trends" column webpage, # and the order in which they appear. GRAPHS="la,disk,inode,qtree,memory,users,vmstat,iostat,tcp.http,tcp,netstat,mrtg::1,temperature,ntpstat,apache,bind,sendmail,mailq,socks,bea,iishealth,citrix,bbgen,bbtest,bbproxy,hobbitd,trackoswex" NCV_trackoswex="trackoswex:GAUGE" Any help would be appreciated! tks S

2 1

Hobbit client will no longer start
by Jason.Chambers＠geosoft.com 03 Mar '06

03 Mar '06

I am having a problem getting the hobbit client to start on the hobbit server: - Program crashed Fatal signal caught! Any suggestions? Jason Chambers IT Helpdesk Support <http://www.geosoft.com/> eosoft Inc. 85 Richmond St. West - 8th Floor Toronto, Ontario, Canada M5H 2C9 Tel: 416-369-0111 x344 Fax: 416-369-9599 www.geosoft.com <http://www.geosoft.com/>

2 1

[Hobbit] Order in rules keyword
by plardinois＠be.tiauto.com 03 Mar '06

03 Mar '06

Hello, oh, I forgot to specify something :-( This is about the order in the rules keywords in the hobbit-alerts.cfg. Yesterday, I was doing some tests like this example : # rock-n-roll devices HOST=%(rock|roll).domain.com \ TIME=0123456:0000:2359 \ SERVICE=conn,bbd,bbgen,cpu,disk,hobbitd,http,memory SCRIPT /usr/home/hobbit/server/ext/ti-notify.pl test-email at localhost \ RECOVERED \ DURATION>10m When I put Duration>10m below SERVICE, I received a _lot_ of mails for any devices with a down service. I have also an additional question : the % sign. Does it apply to the whole line or just to the next word. thanks. Regards, Pierre Lardinois -----Original Message----- From: Schwimmer, Eric E *HS [mailto:EES2Y at hscmail.mcc.virginia.edu] Sent: jeudi 2 mars 2006 17:51 To: hobbit at hswn.dk Subject: RE: [hobbit] Order in rules keyword Are you referring to the host tags in the bb-hosts file? like: 10.0.0.1 myhost # badconn1:1:2 NOPROPRED:conn If so, then no, the order of the tags after the '#' doesn't matter. -Eric > -----Original Message----- > From: Lardinois, Pierre [mailto:plardinois at be.tiauto.com] > Sent: Thursday, March 02, 2006 11:43 AM > To: 'hobbit at hswn.dk' > Subject: [hobbit] Order in rules keyword > > > Hi again, > > Is There a specific order in the keywords ? > > Thanks you for your support, > > regards, > > P. Lardinois > > > The information contained in this transmission may contain privileged > and confidential information. It is intended only for the use of the > person(s) named above. If you are not the intended recipient, you are > hereby notified that any review, dissemination, distribution or > duplication of this communication is strictly prohibited. If you are > not the intended recipient, please contact the sender by reply email > and destroy all copies of the original message. > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > > To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

1 0

[hobbit] RE: [SOLVED][hobbit] sshd notification in syslog
by rmcgraw＠purdue.edu 02 Mar '06

02 Mar '06

What ever I did this time seem to work. I used SSH-2.0-Sun_SSH_1.0.1\r\n and this seems to work now. Thanks Robert _____________________________________________________________________ Robert P. McGraw, Jr. Manager, Computer System EMAIL: rmcgraw at purdue.edu Purdue University ROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 > -----Original Message----- > From: Schwimmer, Eric E *HS [mailto:EES2Y at hscmail.mcc.virginia.edu] > Sent: Thursday, March 02, 2006 2:42 PM > To: hobbit at hswn.dk > Subject: RE: [hobbit] RE: [SOLVED][hobbit] sshd notification in syslog > > > > Hrm, the first string (SSH-2.0-Sun_SSH_1.0.1) should > have worked (or at least, it works on my server running the openssh > version of sshd). > > Have you tried telneting into the port and typing the version number > in yourself? If it accepts it, you'll get some crazy diffie-hellman > text, otherwise it will spit a protocol mismatch line back at you. > > Also, silly question, but did you make sure to include to '\r\n' at > the end of the message? If you did, you might want to try messing > with that (changing it to just '\r' or '\n') because the protocol > error in your syslog looks a little weird (extra newline), so I'm > wondering if there isnt something wrong there. > > -Eric > > > -----Original Message----- > > From: McGraw, Robert P. [mailto:rmcgraw at purdue.edu] > > Sent: Thursday, March 02, 2006 2:19 PM > > To: hobbit at hswn.dk > > Subject: RE: [hobbit] RE: [SOLVED][hobbit] sshd notification in syslog > > > > I am having the same problem and trying to follow your instructions. > > > > > > > > I ran > > > > > > > > ##R##-zorn->[227] ##> ssh -V > > > > Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f > > > > > > > > To get the version number. > > > > > > > > I also ran telnet host 22 and got back the following > > > > > > > > SSH-2.0-Sun_SSH_1.0.1 > > > > > > > > I have tried the following > > > > > > > > SSH-2.0-Sun_SSH_1.0.1 > > > > Sun_SSH_1.1 > > > > Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f > > > > > > > > as the version number with no luck. > > > > > > > > I keep getting the following message log. > > > > > > > > Mar 2 14:03:47 zada.math.purdue.edu sshd[29349]: [ID 800047 > > auth.info] Bad protocol version identification 'Sun_SSH_1.1 > > > > Mar 2 14:03:47 zada.math.purdue.edu ' from 128.210.3.176 > > > > > > > > The only change in the log message is the version > > identification string. > > > > > > > > How do I find the right version number to use? > > > > > > > > Thanks > > > > > > > > Robert > > > > > > > > > > > > > > > > _____________________________________________________________________ > > > > Robert P. McGraw, Jr. > > > > Manager, Computer System > > EMAIL: rmcgraw at purdue.edu > > > > Purdue University > > ROOM: MATH-807 > > > > Department of Mathematics > > PHONE: (765) 494-6055 > > > > 150 N. University Street > > FAX: (419) 821-0540 > > > > West Lafayette, IN 47907-2067 > > > > ________________________________ > > > > From: thomas.seglard.enata at cnp.fr > > [mailto:thomas.seglard.enata at cnp.fr] > > Sent: Thursday, March 02, 2006 12:21 PM > > To: hobbit at hswn.dk > > Subject: [hobbit] RE: [SOLVED][hobbit] sshd notification in syslog > > > > > > > > > > Thank you ! > > > > the second option (the one you preferred) was a good bet ! > > I added the lines as you indicate and that's solved my problem. > > > > Best regards, > > > > Thomas Seglard > > > > "Schwimmer, Eric E *HS" <EES2Y at hscmail.mcc.virginia.edu> a > > écrit sur 02/03/2006 17:31:10 : > > > > > > > > Three posibilities, off the top of my head: > > > > > > On the client side: > > > 1. Install syslog-ng instead of ksyslogd, and > > > filter on the ip address of your hobbit server. > > > 2. Call your logrotate script (assuming you use one) > > > more often, and/or make it compress your old syslog > > > messages. > > > > > > On the hobbit server side: > > > (this is my preferred option) > > > 1. change your bb-services file ($HOBBIT/server/etc/bb-services) > > > so that ssh test sends the version string. I think that will > > > stop your sshd from complaining. > > > > > > ie.: > > > > > > [ssh|ssh1|ssh2] > > > send "SSH-2.0-OpenSSH_4.1\r\n" > > > expect "SSH" > > > options banner > > > port 22 > > > > > > > > > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk >

1 0

[hobbit] RE: [SOLVED][hobbit] sshd notification in syslog
by EES2Y＠hscmail.mcc.virginia.edu 02 Mar '06

02 Mar '06

Hrm, the first string (SSH-2.0-Sun_SSH_1.0.1) should have worked (or at least, it works on my server running the openssh version of sshd). Have you tried telneting into the port and typing the version number in yourself? If it accepts it, you'll get some crazy diffie-hellman text, otherwise it will spit a protocol mismatch line back at you. Also, silly question, but did you make sure to include to '\r\n' at the end of the message? If you did, you might want to try messing with that (changing it to just '\r' or '\n') because the protocol error in your syslog looks a little weird (extra newline), so I'm wondering if there isnt something wrong there. -Eric > -----Original Message----- > From: McGraw, Robert P. [mailto:rmcgraw at purdue.edu] > Sent: Thursday, March 02, 2006 2:19 PM > To: hobbit at hswn.dk > Subject: RE: [hobbit] RE: [SOLVED][hobbit] sshd notification in syslog > > I am having the same problem and trying to follow your instructions. > > > > I ran > > > > ##R##-zorn->[227] ##> ssh -V > > Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f > > > > To get the version number. > > > > I also ran telnet host 22 and got back the following > > > > SSH-2.0-Sun_SSH_1.0.1 > > > > I have tried the following > > > > SSH-2.0-Sun_SSH_1.0.1 > > Sun_SSH_1.1 > > Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f > > > > as the version number with no luck. > > > > I keep getting the following message log. > > > > Mar 2 14:03:47 zada.math.purdue.edu sshd[29349]: [ID 800047 > auth.info] Bad protocol version identification 'Sun_SSH_1.1 > > Mar 2 14:03:47 zada.math.purdue.edu ' from 128.210.3.176 > > > > The only change in the log message is the version > identification string. > > > > How do I find the right version number to use? > > > > Thanks > > > > Robert > > > > > > > > _____________________________________________________________________ > > Robert P. McGraw, Jr. > > Manager, Computer System > EMAIL: rmcgraw at purdue.edu > > Purdue University > ROOM: MATH-807 > > Department of Mathematics > PHONE: (765) 494-6055 > > 150 N. University Street > FAX: (419) 821-0540 > > West Lafayette, IN 47907-2067 > > ________________________________ > > From: thomas.seglard.enata at cnp.fr > [mailto:thomas.seglard.enata at cnp.fr] > Sent: Thursday, March 02, 2006 12:21 PM > To: hobbit at hswn.dk > Subject: [hobbit] RE: [SOLVED][hobbit] sshd notification in syslog > > > > > Thank you ! > > the second option (the one you preferred) was a good bet ! > I added the lines as you indicate and that's solved my problem. > > Best regards, > > Thomas Seglard > > "Schwimmer, Eric E *HS" <EES2Y at hscmail.mcc.virginia.edu> a > écrit sur 02/03/2006 17:31:10 : > > > > > Three posibilities, off the top of my head: > > > > On the client side: > > 1. Install syslog-ng instead of ksyslogd, and > > filter on the ip address of your hobbit server. > > 2. Call your logrotate script (assuming you use one) > > more often, and/or make it compress your old syslog > > messages. > > > > On the hobbit server side: > > (this is my preferred option) > > 1. change your bb-services file ($HOBBIT/server/etc/bb-services) > > so that ssh test sends the version string. I think that will > > stop your sshd from complaining. > > > > ie.: > > > > [ssh|ssh1|ssh2] > > send "SSH-2.0-OpenSSH_4.1\r\n" > > expect "SSH" > > options banner > > port 22 > > > >

1 0

[hobbit] RE: [SOLVED][hobbit] sshd notification in syslog
by rmcgraw＠purdue.edu 02 Mar '06

02 Mar '06

I am having the same problem and trying to follow your instructions. I ran ##R##-zorn->[227] ##> ssh -V Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f To get the version number. I also ran telnet host 22 and got back the following SSH-2.0-Sun_SSH_1.0.1 I have tried the following SSH-2.0-Sun_SSH_1.0.1 Sun_SSH_1.1 Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f as the version number with no luck. I keep getting the following message log. Mar 2 14:03:47 zada.math.purdue.edu sshd[29349]: [ID 800047 auth.info] Bad protocol version identification 'Sun_SSH_1.1 Mar 2 14:03:47 zada.math.purdue.edu ' from 128.210.3.176 The only change in the log message is the version identification string. How do I find the right version number to use? Thanks Robert _____________________________________________________________________ Robert P. McGraw, Jr. Manager, Computer System EMAIL: rmcgraw at purdue.edu Purdue University ROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 _____ From: thomas.seglard.enata at cnp.fr [mailto:thomas.seglard.enata at cnp.fr] Sent: Thursday, March 02, 2006 12:21 PM To: hobbit at hswn.dk Subject: [hobbit] RE: [SOLVED][hobbit] sshd notification in syslog Thank you ! the second option (the one you preferred) was a good bet ! I added the lines as you indicate and that's solved my problem. Best regards, Thomas Seglard "Schwimmer, Eric E *HS" <EES2Y at hscmail.mcc.virginia.edu> a écrit sur 02/03/2006 17:31:10 : > > Three posibilities, off the top of my head: > > On the client side: > 1. Install syslog-ng instead of ksyslogd, and > filter on the ip address of your hobbit server. > 2. Call your logrotate script (assuming you use one) > more often, and/or make it compress your old syslog > messages. > > On the hobbit server side: > (this is my preferred option) > 1. change your bb-services file ($HOBBIT/server/etc/bb-services) > so that ssh test sends the version string. I think that will > stop your sshd from complaining. > > ie.: > > [ssh|ssh1|ssh2] > send "SSH-2.0-OpenSSH_4.1\r\n" > expect "SSH" > options banner > port 22

1 0

[hobbit] Order in rules keyword
by EES2Y＠hscmail.mcc.virginia.edu 02 Mar '06

02 Mar '06

Are you referring to the host tags in the bb-hosts file? like: 10.0.0.1 myhost # badconn1:1:2 NOPROPRED:conn If so, then no, the order of the tags after the '#' doesn't matter. -Eric > -----Original Message----- > From: Lardinois, Pierre [mailto:plardinois at be.tiauto.com] > Sent: Thursday, March 02, 2006 11:43 AM > To: 'hobbit at hswn.dk' > Subject: [hobbit] Order in rules keyword > > > Hi again, > > Is There a specific order in the keywords ? > > Thanks you for your support, > > regards, > > P. Lardinois > > > The information contained in this transmission may contain > privileged and > confidential information. It is intended only for the use of the > person(s) named above. If you are not the intended recipient, you are > hereby notified that any review, dissemination, distribution or > duplication of this communication is strictly prohibited. If > you are not > the intended recipient, please contact the sender by reply email and > destroy all copies of the original message. > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > >

1 0

Order in rules keyword
by plardinois＠be.tiauto.com 02 Mar '06

02 Mar '06

Hi again, Is There a specific order in the keywords ? Thanks you for your support, regards, P. Lardinois The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

1 0

RRDTool Upgrade Known Issues?
by Robert.Taylor＠HendrickAuto.com 02 Mar '06

02 Mar '06

All, Has anyone run into issues upgrading from RRDTool 1.0.x to 1.2.x with Hobbit 4.1.1? I am thinking of upgrading on my Hobbit server and just want to see if there are any known issues. Also, is there a need to re-compile Hobbit after the RRDTool upgrade? Robert Taylor

2 1

[hobbit] Question about NOTICE in hobbit-alerts.cfg
by thomas.seglard.enata＠cnp.fr 02 Mar '06

02 Mar '06

Accusé de réception Votre [hobbit] Question about NOTICE in hobbit-alerts.cfg document : a été Thomas SEGLARD/FI6/ANFI/CNP Assurances reçu par : le : 02/03/2006 11:25:58 Ce message (et toutes ses pieces jointes eventuelles) est confidentiel et etabli a l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, CNP Assurances et ses filiales declinent toute responsabilite au titre de ce message, s'il a ete altere, deforme ou falsifie. ***** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither CNP Assurances nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.

1 0