Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
[image: red] application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM "The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
[image: yellow] application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted "The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
[image: yellow] application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a "An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
There are two ways for clients to do their job. The default and best (IMO) way is to have the server do all of the decisions and parsing through logs. This preferred method is centralized mode. Check to see what yours is doing. I believe bbwin puts this in the registry.
With centralized mode you make changes on the server. The client simply sends the information, the raw data, and the server decides green/yellow red.
With the other mode (maybe client mode?) you make the changes on the client and the client will then send a green/yellow/red.
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Mon, Jul 26, 2010 at 12:42 AM, Vernon Everett <everett.vernon at gmail.com>wrote:
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
[image: red] application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
[image: yellow] application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
[image: yellow] application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
Good day!
I am also trying to make that work for weeks now. I already read a lot of messages in the xymon archive and bbwin forum but still can't make it work.
The log says "[msgs]: will ignore : <entry>" but it still sends the ignored data in the client-local.cfg file.
Is there someone here who has a working ignore function in the bbwin central mode?
Here's my xymon version.
Xymon 4.3.0 beta 2/bbwin 0.12 on CentOS 5-4
Thank in advance!
Ryan
From: Vernon Everett [mailto:everett.vernon at gmail.com] Sent: Monday, July 26, 2010 12:42 PM To: xymon at xymon.com Subject: [xymon] bb-win & client-local.cfg
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
red<http://hobbit/xymon/gifs/red.gif> application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
yellow<http://hobbit/xymon/gifs/yellow.gif> application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available." yellow<http://hobbit/xymon/gifs/yellow.gif> application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
Have you tried LOG?
LOG filename match-pattern [COLOR=color] [IGNORE=ignore-pattern] [TEXT=displaytext]
xymon.com example LOG /var/log/mail.log DB_RUNRECOVERY COLOR=red
Not sure how this would work on Windows. Is there any way to identify what file is being sent without a packet capture?
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Mon, Jul 26, 2010 at 12:56 AM, Lapuz, Ryan Jay < ryanjay.lapuz at tsdp.toshiba.co.jp> wrote:
Good day!
I am also trying to make that work for weeks now. I already read a lot of messages in the xymon archive and bbwin forum but still can’t make it work.
The log says “[msgs]: will ignore : <entry>” but it still sends the ignored data in the client-local.cfg file.
Is there someone here who has a working ignore function in the bbwin central mode?
Here’s my xymon version.
Xymon 4.3.0 beta 2/bbwin 0.12 on CentOS 5-4
Thank in advance!
Ryan
*From:* Vernon Everett [mailto:everett.vernon at gmail.com] *Sent:* Monday, July 26, 2010 12:42 PM *To:* xymon at xymon.com *Subject:* [xymon] bb-win & client-local.cfg
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
[image: red] application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
[image: yellow] application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
[image: yellow] application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver:
()"
On Mon, Jul 26, 2010 at 1:20 PM, Josh Luthman <josh at imaginenetworksllc.com>wrote:
*> Not sure how this would work on Windows.
*I think this statement perfectly encapsulates the problem. :-)
Any Wintendo/bb-win boffins out there?
Cheers Vernon
Have you tried LOG?
LOG filename match-pattern [COLOR=color] [IGNORE=ignore-pattern] [TEXT=displaytext]
xymon.com example LOG /var/log/mail.log DB_RUNRECOVERY COLOR=red
Not sure how this would work on Windows. Is there any way to identify what file is being sent without a packet capture?
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Mon, Jul 26, 2010 at 12:56 AM, Lapuz, Ryan Jay < ryanjay.lapuz at tsdp.toshiba.co.jp> wrote:
Good day!
I am also trying to make that work for weeks now. I already read a lot of messages in the xymon archive and bbwin forum but still can’t make it work.
The log says “[msgs]: will ignore : <entry>” but it still sends the ignored data in the client-local.cfg file.
Is there someone here who has a working ignore function in the bbwin central mode?
Here’s my xymon version.
Xymon 4.3.0 beta 2/bbwin 0.12 on CentOS 5-4
Thank in advance!
Ryan
*From:* Vernon Everett [mailto:everett.vernon at gmail.com] *Sent:* Monday, July 26, 2010 12:42 PM *To:* xymon at xymon.com *Subject:* [xymon] bb-win & client-local.cfg
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
[image: red] application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
[image: yellow] application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
[image: yellow] application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver:
()"
Yes. The syntax for windows client is just similar to unix/linux client.
Ignore pattern is working in the hobbit-clients.cfg file but not in the client-local.cfg file. The problem is that the msgs page is being populated by the event logs.
Thanks,
Ryan
From: Josh Luthman [mailto:josh at imaginenetworksllc.com] Sent: Monday, July 26, 2010 1:21 PM To: xymon at xymon.com Subject: Re: [xymon] bb-win & client-local.cfg
Have you tried LOG?
LOG filename match-pattern [COLOR=color] [IGNORE=ignore-pattern] [TEXT=displaytext]
xymon.com example LOG /var/log/mail.log DB_RUNRECOVERY COLOR=red
Not sure how this would work on Windows. Is there any way to identify what file is being sent without a packet capture?
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Mon, Jul 26, 2010 at 12:56 AM, Lapuz, Ryan Jay <ryanjay.lapuz at tsdp.toshiba.co.jp> wrote:
Good day!
I am also trying to make that work for weeks now. I already read a lot of messages in the xymon archive and bbwin forum but still can't make it work.
The log says "[msgs]: will ignore : <entry>" but it still sends the ignored data in the client-local.cfg file.
Is there someone here who has a working ignore function in the bbwin central mode?
Here's my xymon version.
Xymon 4.3.0 beta 2/bbwin 0.12 on CentOS 5-4
Thank in advance!
Ryan
From: Vernon Everett [mailto:everett.vernon at gmail.com] Sent: Monday, July 26, 2010 12:42 PM To: xymon at xymon.com Subject: [xymon] bb-win & client-local.cfg
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available." application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
Vernon,
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
I grappled with the same problem for ages. My situation was complicated by the fact I have success and failure auditing also enabled, which means the client messages could be huge, and even bumping up MAXMSG_CLIENT to around 15MB was still not enough. I never worked out how to filter a single message out.
My eventual solution was to disable msgs reporting entirely in BBWIN (comment out the BBWIN.CFG line loading the msgs DLL), and set up event log forwarding using SNARE ( http://www.intersectalliance.com/projects/SnareWindows/index.html ) to rsyslog on the logging/monitoring server (running xymon/hobbit) and then write a test to filter the forwarded logs. This also allowed me to filter on severity, error code, etc. so was a better solution due to some of the bizarre errors Windows generates which can be safely ignored (browser service, etc). Been meaning to contribute it and write it up but haven't had time yet.
Note also that the event log reporting in BBWIN doesn't work at all well for Windows 2008/Vista/7 due to the new event log system. The old BBNT client doesn't cut it either.
David.
red application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
yellow application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
yellow application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
-- David Baldwin - IT Unit Australian Sports Commission www.ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
Beginning to sound like BBWin might be in need of an upgrade or refit. Is the project still active? If so, who is the maintainer? If not, where do we go from here?
Cheers Vernon
On Mon, Jul 26, 2010 at 3:54 PM, David Baldwin <david.baldwin at ausport.gov.au
wrote:
Vernon,
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
I grappled with the same problem for ages. My situation was complicated by the fact I have success and failure auditing also enabled, which means the client messages could be huge, and even bumping up MAXMSG_CLIENT to around 15MB was still not enough. I never worked out how to filter a single message out.
My eventual solution was to disable msgs reporting entirely in BBWIN (comment out the BBWIN.CFG line loading the msgs DLL), and set up event log forwarding using SNARE ( http://www.intersectalliance.com/projects/SnareWindows/index.html ) to rsyslog on the logging/monitoring server (running xymon/hobbit) and then write a test to filter the forwarded logs. This also allowed me to filter on severity, error code, etc. so was a better solution due to some of the bizarre errors Windows generates which can be safely ignored (browser service, etc). Been meaning to contribute it and write it up but haven't had time yet.
Note also that the event log reporting in BBWIN doesn't work at all well for Windows 2008/Vista/7 due to the new event log system. The old BBNT client doesn't cut it either.
David.
red application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
yellow application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
yellow application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
-- David Baldwin - IT Unit Australian Sports Commission www.ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
To unsubscribe from the xymon list, send an e-mail to xymon-unsubscribe at xymon.com
Hi Vernon,
The long thread about "Xymon is practically dead" contains a post about BBWin. Basically it has stopped development and apparently can be considered dead. Not sure whether someone else is going to pick it up, or rewrite the program; there was talk of it in the thread.
Cheers, Phil [Hobbitmon-developer] Xymon is practically dead On 26 July 2010 09:05, Vernon Everett <everett.vernon at gmail.com> wrote:
Beginning to sound like BBWin might be in need of an upgrade or refit. Is the project still active? If so, who is the maintainer? If not, where do we go from here?
Cheers Vernon
On Mon, Jul 26, 2010 at 3:54 PM, David Baldwin < david.baldwin at ausport.gov.au> wrote:
Vernon,
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
I grappled with the same problem for ages. My situation was complicated by the fact I have success and failure auditing also enabled, which means the client messages could be huge, and even bumping up MAXMSG_CLIENT to around 15MB was still not enough. I never worked out how to filter a single message out.
My eventual solution was to disable msgs reporting entirely in BBWIN (comment out the BBWIN.CFG line loading the msgs DLL), and set up event log forwarding using SNARE ( http://www.intersectalliance.com/projects/SnareWindows/index.html ) to rsyslog on the logging/monitoring server (running xymon/hobbit) and then write a test to filter the forwarded logs. This also allowed me to filter on severity, error code, etc. so was a better solution due to some of the bizarre errors Windows generates which can be safely ignored (browser service, etc). Been meaning to contribute it and write it up but haven't had time yet.
Note also that the event log reporting in BBWIN doesn't work at all well for Windows 2008/Vista/7 due to the new event log system. The old BBNT client doesn't cut it either.
David.
red application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
yellow application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
yellow application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
-- David Baldwin - IT Unit Australian Sports Commission www.ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
To unsubscribe from the xymon list, send an e-mail to xymon-unsubscribe at xymon.com
Maybe a bit? http://sourceforge.net/project/stats/detail.php?group_id=136450&ugn=bbwin&ty...
There is someone doing a Windows client (XymonWin?) that just started a short while back, I can't recall the details.
As you can tell I'm not too much into Windows servers so I am sorry I can't give you many more details.
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Mon, Jul 26, 2010 at 4:05 AM, Vernon Everett <everett.vernon at gmail.com>wrote:
Beginning to sound like BBWin might be in need of an upgrade or refit. Is the project still active? If so, who is the maintainer? If not, where do we go from here?
Cheers Vernon
On Mon, Jul 26, 2010 at 3:54 PM, David Baldwin < david.baldwin at ausport.gov.au> wrote:
Vernon,
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
I grappled with the same problem for ages. My situation was complicated by the fact I have success and failure auditing also enabled, which means the client messages could be huge, and even bumping up MAXMSG_CLIENT to around 15MB was still not enough. I never worked out how to filter a single message out.
My eventual solution was to disable msgs reporting entirely in BBWIN (comment out the BBWIN.CFG line loading the msgs DLL), and set up event log forwarding using SNARE ( http://www.intersectalliance.com/projects/SnareWindows/index.html ) to rsyslog on the logging/monitoring server (running xymon/hobbit) and then write a test to filter the forwarded logs. This also allowed me to filter on severity, error code, etc. so was a better solution due to some of the bizarre errors Windows generates which can be safely ignored (browser service, etc). Been meaning to contribute it and write it up but haven't had time yet.
Note also that the event log reporting in BBWIN doesn't work at all well for Windows 2008/Vista/7 due to the new event log system. The old BBNT client doesn't cut it either.
David.
red application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
yellow application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
yellow application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
-- David Baldwin - IT Unit Australian Sports Commission www.ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
To unsubscribe from the xymon list, send an e-mail to xymon-unsubscribe at xymon.com
Owner: Oh yes, the, uh, the BBWin Project...What's,uh...What's wrong
with it?
Mr. Praline: I'll tell you what's wrong with it, my lad. 'E's dead,
that's what's wrong with it!
Owner: No, no, 'e's uh,...he's resting.
Mr. Praline: Look, matey, I know a dead project when I see one, and I'm
looking at one right now.
Owner: No no he's not dead, he's, he's restin'! Remarkable project, the
BBWin, idn'it, ay? Beautiful coding!
Mr. Praline: The coding don't enter into it. It's stone dead.
Owner: Nononono, no, no! 'E's resting!
With apologies to Monty Python :-)
I have no idea how things hang together in Wintendo-land, nor am I able to code in anything that could be useful, so I am going to have to sit on the sidelines and cheer for those who do attempt to revive this one.
Cheers Vernon
On Mon, Jul 26, 2010 at 4:22 PM, Josh Luthman <josh at imaginenetworksllc.com>wrote:
Maybe a bit?
http://sourceforge.net/project/stats/detail.php?group_id=136450&ugn=bbwin&ty...
There is someone doing a Windows client (XymonWin?) that just started a short while back, I can't recall the details.
As you can tell I'm not too much into Windows servers so I am sorry I can't give you many more details.
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Mon, Jul 26, 2010 at 4:05 AM, Vernon Everett <everett.vernon at gmail.com>wrote:
Beginning to sound like BBWin might be in need of an upgrade or refit. Is the project still active? If so, who is the maintainer? If not, where do we go from here?
Cheers Vernon
On Mon, Jul 26, 2010 at 3:54 PM, David Baldwin < david.baldwin at ausport.gov.au> wrote:
Vernon,
Hi all
Hoping for a little help on this one. Got a stream of errors coming through from some wintendo clients running bb-win. See example below. We would like to ignore some errors related to certain messages. I was under the impression that the following in client-local.cfg would do it.
[win32] eventlog:Security ignore Success eventlog:System ignore Information *eventlog:Application ignore Citrix System Monitoring ignore MetaFrameEvents*
Appears to not be the case. How do we configure the client-local.cfg to ignore instances of the first and last error, but not instances like the middle one below? (The messages are for illustrative purposes only - their relative importance and why I should or shouldn't ignore them is not under discussion)
Regards Vernon
I grappled with the same problem for ages. My situation was complicated by the fact I have success and failure auditing also enabled, which means the client messages could be huge, and even bumping up MAXMSG_CLIENT to around 15MB was still not enough. I never worked out how to filter a single message out.
My eventual solution was to disable msgs reporting entirely in BBWIN (comment out the BBWIN.CFG line loading the msgs DLL), and set up event log forwarding using SNARE ( http://www.intersectalliance.com/projects/SnareWindows/index.html ) to rsyslog on the logging/monitoring server (running xymon/hobbit) and then write a test to filter the forwarded logs. This also allowed me to filter on severity, error code, etc. so was a better solution due to some of the bizarre errors Windows generates which can be safely ignored (browser service, etc). Been meaning to contribute it and write it up but haven't had time yet.
Note also that the event log reporting in BBWIN doesn't work at all well for Windows 2008/Vista/7 due to the new event log system. The old BBNT client doesn't cut it either.
David.
red application: error - 2010/07/26 11:41:53 - Citrix System Monitoring Agent (37) - NT AUTHORITY\SYSTEM
"The Queue thread stopped responding. The Citrix System Monitoring Agent will shutdown and restart."
yellow application: warning - 2010/07/26 11:40:52 - Citrix-Multimedia-Flash (50) - stuff/deleted
"The client does not support HDX MediaStream for Flash. Server-side Flash rendering will be used if available."
yellow application: warning - 2010/07/26 11:33:59 - MetaFrameEvents (1103) - n/a
"An error occurred while retrieving client printer properties. Default printer properties will be used instead. Client name: (WI_-fCiFejFrIHBbXrfM) Printer: (CompanyName Pull Print PS [UPD:PS] (from WI_-fCiFejFrIHBbXrfM) in session 6) Printer driver: ()"
-- David Baldwin - IT Unit Australian Sports Commission www.ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
To unsubscribe from the xymon list, send an e-mail to xymon-unsubscribe at xymon.com
Beginning to sound like BBWin might be in need of an upgrade or refit. Is the project still active? If so, who is the maintainer? If not, where do we go from here?
If you read the mail archives you'll see that this has been discussed quite recently. BBWin is pretty much dead but may be revivable. Xywin is a new C# based project.
We use BBWin in local mode because that seems to have fewer bugs. We maintain central configuration by periodically downloading the BBWin.cfg files from the server. I have a working dev environment for BBWin and have managed to fix a few bugs - I may have a try at getting it to interpret the event logs in 2008 et al correctly.
Personally I'd much rather the Xywin project successfully replaces it as C# is a much better language (than C++) to use as regards communicating with Windows subsystems.
Malcolm
-- Technical copy-editor & proofreader
KDE Proofreading Team KDE British English Translation Team
http://l10n.kde.org/team-infos.php?teamcode=en_GB
Facebook: http://www.facebook.com/FriendlyAtheist
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
I believe this is it. Anyone know for sure?
http://sourceforge.net/projects/xywinnet/
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Mon, Jul 26, 2010 at 6:50 AM, Malcolm Hunter <malcolm.hunter at gmx.co.uk>wrote:
Beginning to sound like BBWin might be in need of an upgrade or refit. Is the project still active? If so, who is the maintainer? If not, where do we go from here?
If you read the mail archives you'll see that this has been discussed quite recently. BBWin is pretty much dead but may be revivable. Xywin is a new C# based project.
We use BBWin in local mode because that seems to have fewer bugs. We maintain central configuration by periodically downloading the BBWin.cfg files from the server. I have a working dev environment for BBWin and have managed to fix a few bugs - I may have a try at getting it to interpret the event logs in 2008 et al correctly.
Personally I'd much rather the Xywin project successfully replaces it as C# is a much better language (than C++) to use as regards communicating with Windows subsystems.
Malcolm
-- Technical copy-editor & proofreader
KDE Proofreading Team KDE British English Translation Team
http://l10n.kde.org/team-infos.php?teamcode=en_GB
Facebook: http://www.facebook.com/FriendlyAtheist
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
To unsubscribe from the xymon list, send an e-mail to xymon-unsubscribe at xymon.com
I believe this is it. Anyone know for sure? http://sourceforge.net/projects/xywinnet/
I do not see any files to download on this site...
On Mon, Jul 26, 2010 at 6:50 AM, Malcolm Hunter <malcolm.hunter at gmx.co.uk> wrote:
Beginning to sound like BBWin might be in need of an upgrade or refit.
Is the project still active?
If so, who is the maintainer?
If not, where do we go from here?
If you read the mail archives you'll see that this has been discussed quite recently. BBWin is pretty much dead but may be revivable. Xywin is a new C# based project.
We use BBWin in local mode because that seems to have fewer bugs. We maintain central configuration by periodically downloading the BBWin.cfg files from the server. I have a working dev environment for BBWin and have managed to fix a few bugs - I may have a try at getting it to interpret the event logs in 2008 et al correctly.
Personally I'd much rather the Xywin project successfully replaces it as C# is a much better language (than C++) to use as regards communicating with Windows subsystems.
Malcolm
--
Technical copy-editor & proofreader
KDE Proofreading Team
KDE British English Translation Team
http://l10n.kde.org/team-infos.php?teamcode=en_GB
Facebook: http://www.facebook.com/FriendlyAtheist
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
To unsubscribe from the xymon list, send an e-mail to
xymon-unsubscribe at xymon.com
That is the case at this point. Not certain if that's the new Windows client and I was hoping someone could confirm the status of that project.
On Jul 26, 2010 1:01 PM, <wiskbroom at hotmail.com> wrote:
I believe this is it. Anyone know for sure? http://sourceforge.net/projects/xywinnet/ I do not see any files to download on this site...
On Mon, Jul 26, 2010 at 6:50 AM, Malcolm Hunter <malcolm.hunter at gmx.co.uk> wrote:
Beginning...
I downloaded the source and attempted to compile. It did not compile-it complained about some missing DLLs. So, there is probably some other library needed to make it go. Sorry, I do not have time to troubleshoot further right now.
Ray
From: Josh Luthman [mailto:josh at imaginenetworksllc.com] Sent: Monday, July 26, 2010 1:23 PM To: xymon at xymon.com Subject: Re: RE: [xymon] bb-win & client-local.cfg
That is the case at this point. Not certain if that's the new Windows client and I was hoping someone could confirm the status of that project. On Jul 26, 2010 1:01 PM, <wiskbroom at hotmail.com<mailto:wiskbroom at hotmail.com>> wrote:
I believe this is it. Anyone know for sure? http://sourceforge.net/projects/xywinnet/ I do not see any files to download on this site...
On Mon, Jul 26, 2010 at 6:50 AM, Malcolm Hunter <malcolm.hunter at gmx.co.uk<mailto:malcolm.hunter at gmx.co.uk>> wrote:
Beginning...
CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
participants (8)
-
david.baldwin@ausport.gov.au
-
everett.vernon@gmail.com
-
josh@imaginenetworksllc.com
-
malcolm.hunter@gmx.co.uk
-
pmeech@gmail.com
-
ryanjay.lapuz@tsdp.toshiba.co.jp
-
storerr@nibco.com
-
wiskbroom@hotmail.com