[Xymon] Xymon does not display any information about windows client

Yanni y.goudetsidis at mail.cryst.bbk.ac.uk
Thu Dec 15 13:20:35 CET 2011


Hi everyone

I have setup xymon and I am trying to add a windows XP client.
This client is already monitored by big brother(old version) and it has 
bbwin.exe version 0.12 installed.

How can I make this particular windows XP client to be also monitored by 
xymon?

I have added a second line in the BBWin.cfg inside C:\Program 
Files\BBWin\etc\BBWin.cfg

<setting name="bbdisplay" value="IP_Address" />

but xymon does not display any information.

Could someone please let me know if I am missing something?

Many thanks
Yanni

On 12/15/2011 11:00 AM, xymon-request at xymon.com wrote:
> Send Xymon mailing list submissions to
> 	xymon at xymon.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.xymon.com/mailman/listinfo/xymon
> or, via email, send a message with subject or body 'help' to
> 	xymon-request at xymon.com
>
> You can reach the person managing the list at
> 	xymon-owner at xymon.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xymon digest..."
>
>
> Today's Topics:
>
>     1. delayred and delayyellow do not appear in info page (SebA)
>     2.  logfetch bug or trigger syntax in client-local.cfg?
>        (Gore, David W (David))
>     3. Re: BBwin crashing on one server (Henrik St?rner)
>     4. Re: uninstall Xymon (Henrik St?rner)
>     5. Re: uninstall Xymon (Bill Arlofski)
>     6. Re: uninstall Xymon (White, Bruce)
>     7. Re: Xymon 4.3.7 released (Gore, David W (David))
>     8. DISPLAYGROUP on alert.cfg (John Chen)
>     9. Re: DISPLAYGROUP on alert.cfg (Henrik St?rner)
>    10. Re: DISPLAYGROUP on alert.cfg (John Chen)
>    11. Re: uninstall Xymon (Moodley, Nelandran N)
>    12. Re: DISPLAYGROUP on alert.cfg (Henrik St?rner)
>    13. Re: delayred and delayyellow do not appear in info page
>        (Henrik St?rner)
>    14. RFE: Oracle tests (Colin Coe)
>    15. alerts (Moodley, Nelandran N)
>    16. Current Critical Systems (Mohamed Gabr)
>    17. Alerting - I'm not doing it right... (Carl Inglis)
>    18. Re: Alerting - I'm not doing it right... (Johan Sj?berg)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 14 Dec 2011 13:29:50 -0000
> From: "SebA"<spah at syntec.co.uk>
> To:<xymon at xymon.com>
> Subject: [Xymon] delayred and delayyellow do not appear in info page
> Message-ID:
> 	<!&!AAAAAAAAAAAuAAAAAAAAAL60wriLM9cRsTVojW0AAAABAFEdQVQs6tMRsLEAoMxarIMAAAABk2cAABAAAAC3VWGmB8HVRIYyHePpwKgBAQAAAAA=@syntec.co.uk>
> 	
> Content-Type: text/plain; charset="us-ascii"
>
> delayred and delayyellow do not appear in the info column status page
> (svcstatus.sh?HOST=<hostname>&SERVICE=info).  I would expect them to appear
> perhaps under Other tags, or perhaps at the top of alerting before the table
> of alerts.  This is on 4.3.7.
>
> 192.168.4.56    Db1 # delayred=special:10 delayyellow=special:5
>
> Or does delayred and delayyellow not apply to custom tests?  (If so, the
> docs do not mention this.)
>
> Kind regards,
>
> SebA
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:<http://lists.xymon.com/pipermail/xymon/attachments/20111214/35cfc063/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 14 Dec 2011 08:42:43 -0500
> From: "Gore, David W (David)"<david.gore at verizon.com>
> To: "xymon at xymon.com"<xymon at xymon.com>
> Subject: [Xymon]  logfetch bug or trigger syntax in client-local.cfg?
> Message-ID:
> 	<9E95D92A6FE6D644AD42428C72C4B7C0263F5FDE at FHDP1LUMXC7V42.us.one.verizon.com>
> 	
> Content-Type: text/plain; charset="iso-2022-jp"
>
> We are receiving core dumps of logfetch at irregular times but it is quite persistent.  This is mostly on SunOS 10 SPARC clients with a 4.3.6 Xymon client build.  Any ideas appreciated. Here is the back trace.
>
> [nmsbb at ipgomzspa03 client]$ ./gdb bin/logfetch core
> GNU gdb 6.2.1
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "sparc-sun-solaris2.10"...
> Core was generated by `/export/home/nmsbb/client/bin/logfetch /export/home/nmsbb/client/tmp/logfetch.i'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /lib/librt.so.1...done.
> Loaded symbols for /lib/librt.so.1
> Reading symbols from /lib/libc.so.1...done.
> Loaded symbols for /lib/libc.so.1
> Reading symbols from /lib/libaio.so.1...done.
> Loaded symbols for /lib/libaio.so.1
> Reading symbols from /lib/libmd.so.1...done.
> Loaded symbols for /lib/libmd.so.1
> Reading symbols from /platform/sun4v/lib/libc_psr.so.1...done.
> Loaded symbols for /platform/SUNW,T5240/lib/libc_psr.so.1
> #0  0xff282810 in __regexec_C () from /lib/libc.so.1
> (gdb) bt
> #0  0xff282810 in __regexec_C () from /lib/libc.so.1
> #1  0x00012f5c in logdata (filename=0x3b180 "/var/adm/messages", logdef=0x3b13c)
>      at logfetch.c:252
> #2  0x00014730 in main (argc=1, argv=0x36000) at logfetch.c:963
>
> Relevant portions of code:
>
> Around line 252:
>
>      /* See if this is a trigger line */
>      if (logdef->triggercount) {
>        int i, match = 0;
>
>        for (i=0; ((i<  logdef->ignorecount)&&  !match); i++) {
>          match = (regexec(&trigexpr[i], fillpos, 0, NULL, 0) == 0); ? line 252
>        }
>
>        if (match) {
>          int sidx;
>
>          sidx = lpidx - LINES_AROUND_TRIGGER;
>          if (sidx<  0) sidx += (2*LINES_AROUND_TRIGGER + 1);
>          triggerstartpos = linepos[sidx]; if (!triggerstartpos) triggerstartpos = buf;
>          triggerlinecount = LINES_AROUND_TRIGGER;
>        }
>      }
>
> And line 963:
>
>      switch (walk->checktype) {
>        case C_LOG:
>        data = logdata(walk->filename,&walk->check.logcheck); ? line 963
>        fprintf(stdout, "[msgs:%s]\n", walk->filename);
>        fprintf(stdout, "%s\n", data);
>
>
> Triggers used (piped through cat ?vet):
>
> trigger ERROR
> trigger Error|Segmentation
> trigger Error|Segmentation
> trigger ChannelClosedException|ORA.|Memory|ERROR|FATAL|SQLException|ClassCircularityError|did not respond|CORBA TIMEOUT
> trigger ChannelClosedException|ORA.|Memory|ERROR|FATAL|SQLException|ClassCircularityError|did not respond|CORBA TIMEOUT
> trigger Memory|ERROR|FATAL|ClassCircularityError|did not respond|CORBA TIMEOUT
> trigger ERROR|FATAL|SQLException|(ORA\-)|OutOfMemoryError
> trigger ERROR|FATAL|SQLException|(ORA\-)|OutOfMemoryError
> [nmsbb at ipgomzspa03 tmp]$ grep trigger logfetch.ipgomzspa03.cfg|cat -vet
> trigger ERROR$
> trigger Error|Segmentation$
> trigger Error|Segmentation$
> trigger ChannelClosedException|ORA.|Memory|ERROR|FATAL|SQLException|ClassCircularityError|did not respond|CORBA TIMEOUT$
> trigger ChannelClosedException|ORA.|Memory|ERROR|FATAL|SQLException|ClassCircularityError|did not respond|CORBA TIMEOUT$
> trigger Memory|ERROR|FATAL|ClassCircularityError|did not respond|CORBA TIMEOUT$
> trigger ERROR|FATAL|SQLException|(ORA\-)|OutOfMemoryError$
> trigger ERROR|FATAL|SQLException|(ORA\-)|OutOfMemoryError$
>
>
>
> David Gore (v965-3670)
> Network Management Systems (NMS)
> IMPACT Transport Team Lead - SCSA, SCNA
> Page: 1-800-PAG-eMCI pin 1406090
> Vnet: 965-3676
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 14 Dec 2011 16:04:57 +0100
> From: Henrik St?rner<henrik at hswn.dk>
> To: xymon at xymon.com
> Subject: Re: [Xymon] BBwin crashing on one server
> Message-ID:<4EE8BB19.3040803 at hswn.dk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Johan,
>
> On 14-12-2011 10:38, Johan Sj?berg wrote:
>> No ideas about this?
>>
>> Can I run some debug to try to find out what is causing BBwin to crash?
> I think you should try the BBWin mailing list.
>
>
> Regards,
> Henrik
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 14 Dec 2011 16:06:02 +0100
> From: Henrik St?rner<henrik at hswn.dk>
> To: xymon at xymon.com
> Subject: Re: [Xymon] uninstall Xymon
> Message-ID:<4EE8BB5A.90104 at hswn.dk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 14-12-2011 09:58, Moodley, Nelandran N wrote:
>> How do I uninstall Xymon.
> Delete the directory where you installed it. Remove any startup-scripts
> that you created, and any Apache webserver config you added.
>
> Just like most other software.
>
>
> Regards,
> Henrik
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 14 Dec 2011 09:44:54 -0500
> From: Bill Arlofski<waa-hobbitml at revpol.com>
> To: xymon at xymon.com
> Subject: Re: [Xymon] uninstall Xymon
> Message-ID:<4EE8B666.8060901 at revpol.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 12/14/11 03:58, Moodley, Nelandran N wrote:
>> Hi
>>
>> How do I uninstall Xymon.
>>
>> Newbie
>>
>> Thanks
>
> as root:
>
> root at host # su - xymon<enter>
>
> xymon at host $ ./server/xymon.sh stop<enter>
>
> xymon at host $ exit<enter>
>
> root at host # rm -rf ~xymon
>
> Warning, that will shutdown all Xymon daemons and then will remove ALL traces
> of the Xymon installation from your system. USE IT WITH CARE.
>
> P.S. Any particular reason you want to remove Xymon?  If it is due to
> configuration problems etc there are plenty of nice people in here that would
> be more than willing to help you get through any rough patches and the initial
> learning curve.   Cheers!
>




More information about the Xymon mailing list