[Xymon] Xymon Digest, Vol 18, Issue 15

Timothy Myers timcarol at gmail.com
Mon Jul 16 17:20:44 CEST 2012


Ù
On Jul 16, 2012 4: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. ALERTCOLORS question (Torsten Richter)
>    2. Xymon 4.3.8 available (Henrik St?rner)
>    3. Re: Xymon 4.3.8 available (T.J. Yang)
>    4. Re: Xymon 4.3.8 available (Henrik St?rner)
>    5. alerts.cfg RECOVERED sends 2 emails even with a STOP (FORD Alan)
>    6. Missing feature ? (Becker Christian)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 15 Jul 2012 14:44:37 +0200
> From: Torsten Richter <bb4 at richter-it.net>
> To: xymon at xymon.com
> Subject: [Xymon] ALERTCOLORS question
> Message-ID: <5002BB35.9020004 at richter-it.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi XYmonians,
>
> just for my understanding: Is it possible to remove one color from the
> ALERTCOLORS variable in xymonserver.cfg and still trigger an alert for a
> test with this color in alerts.cfg?
>
> Background:
> I want to remove 'yellow' from ALERTCOLORS since our admins only get
> notified for 'red' and 'purple' alerts by our operations center.
> And since I use an initial delay of 6 minutes they will also be notified
> if a test is yellow for, let's say, 10 minutes and then turns red for 2
> or 3 minutes.
>
> But for some tests the "maximum" color is set to yellow since the admins
> do not want to get informed about something that belongs to the
> application development department. So these tests go yellow and an
> email is triggered for the test and sent to our developers.
>
> Thanks
> Torsten
> - --
> +---------------------------------------------------------+
> | E-mail  : bb4 [at] richter-it.net                       |
> |                                                         |
> | Homepage: http://www.richter-it.net/                    |
> +---------------------------------------------------------+
> Download my public key from:
> http://gpg-keyserver.de/pks/lookup?search=0x899093AC&op=get
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
>
> iEYEARECAAYFAlACuzUACgkQ7DlmxomQk6y+zACaAhoK8U/odbgbt9bvZvb2Pbu2
> LhkAnjDWi+wimK0ko+md460DjKOm4H4U
> =IObh
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 15 Jul 2012 17:55:01 +0200
> From: Henrik St?rner <henrik at hswn.dk>
> To: Xymon mailinglist <xymon at xymon.com>,
>         xymon-developer at lists.sourceforge.net
> Subject: [Xymon] Xymon 4.3.8 available
> Message-ID: <5002E7D5.1070203 at hswn.dk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi,
>
> I have uploaded a 4.3.8 maintenance-release of Xymon to Sourceforge. It
> should be available by the time you read this.
>
> This release is an attempt to pick up the various patches and fixes that
> have appeared since the 4.3.7 release. Some issues - especially the
> problem with DNS timeouts - seemed important enough to warrant a
> maintenance release.
>
> This release should also fix some build-problems that have occurred on
> some systems (e.g. newer Ubuntu systems). The build-scripts were
> backported from the current "trunk" version, so they haven't had as much
> testing as the rest of the code - if you run into problems, let me know.
> I know of one issue on older Red Hat Linux versions, where the PCRE
> include-files are not found automatically; adding "--pcreinclude
> /usr/include/pcre" to the configure-command should fix this.
>
> There are also some enhancements, most notably the Enable/Disable page
> now allows you to select a specific time when the disable expires,
> instead of a time-interval; inode-monitoring now works on Linux clients
> (no other platforms, unfortunately); and the SSL certificate checks can
> now check the size of the certificate public key.
>
> Several of these fixes and enhancements were contributed by members of
> the community - I am very pleased to see Xymon development being done by
> others than just myself.
>
> The full list of bugfixes, enhancements and file hashes are below.
>
> Regards,
> Henrik
>
>
> Bugfixes
> * Workaround for DNS timeout handling, now fixed at approximately 25
>    seconds.
> * "hostinfo" command for xymond documented
> * confreport only shows processes that are monitored
> * analysis.cfg parsing of COLOR for UP rules was broken
> * RRD handlers no longer crash after receiving 1 billion updates
> * Using .netrc for authentication could crash xymonnet
> * "directory" includes would report the wrong filename for missing
>    directories.
> * useradm CGI would invoke htpassword twice
> * "include" and "directory" now ignores trailing whitespace
> * SSLv2 support disabled if SSL-library does not support it
> * Minor bugfixes and cleanups of compiler warnings.
>
> Enhancements
> * Service status on info page now links to the detailed status page.
> * Add RRDGRAPHOPTS setting to permit global user-specified RRD options,
>    e.g. for font to showgraph CGI
> * Add check for the size of public keys used in SSL certificates
>    (enabled via --sslkeysize=N option for xymonnet)
> * Optionally disable the display of SSL ciphers in the sslcert status
>    (the --no-cipherlist option for xymonnet)
> * Improved build-scripts works on newer systems with libraries in
>    new and surprising places
> * Reduce xymonnet memory usage and runtime for ping tests when there
>    are multiple hosts.cfg entries with the same IP-address.
> * Add code for inode-monitoring on Linux. Does not currently work on
>    any other client platform.
> * Added the ability to disable tests until a specific time, instead of
>    for some interval. Disabling a test also now computes the expire time
>    for the disable to happen at the next closest minute.
>
>
> SHA1 hashes:
> b9bc428090c53c1938ac965f04affa293917c2ac  xymon-4.3.8.tar.gz
> 9a2ad2ebbed5e6796813810a3650bb5cce739f86  xymon_4.3.8_amd64.deb
> ac1418540c0f45de387b079499b9d8efec234963  xymon-client_4.3.8_amd64.deb
> e68f45327d8682a809cd8c800857b30bbdeb6c60  xymon_4.3.8_i386.deb
> 1e3df6d93747d9a8f87df91c48ab82bc901e775b  xymon-client_4.3.8_i386.deb
>
> MD5 hashes:
> fbd59ca20083a31442f9d1fb37c8c859  xymon-4.3.8.tar.gz
> 92c4297a8f7588ab40240fbc573b721d  xymon_4.3.8_amd64.deb
> 3ac5bbdd997aa449dc8da9b140792e2f  xymon-client_4.3.8_amd64.deb
> 3d74acee2450311445377ad120d31d90  xymon_4.3.8_i386.deb
> 42ef4f5a85460aabc4f2711f1788d24d  xymon-client_4.3.8_i386.deb
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 15 Jul 2012 20:45:53 -0500
> From: "T.J. Yang" <tjyang2001 at gmail.com>
> To: Henrik St?rner <henrik at hswn.dk>
> Cc: Xymon mailinglist <xymon at xymon.com>,
>         xymon-developer at lists.sourceforge.net
> Subject: Re: [Xymon] Xymon 4.3.8 available
> Message-ID:
>         <CAD2GW8pL5JcAy2f+Ozm_CVLfLHTBQP9Cajdrbnztk=
> WNxPAh7g at mail.gmail.com>
> Content-Type: text/plain; charset=windows-1252
>
> Hi, Henrik
>
> Thanks for the new 4.3.8 release.
>
> On Sun, Jul 15, 2012 at 10:55 AM, Henrik St?rner <henrik at hswn.dk> wrote:
> > Hi,
> >
> > I have uploaded a 4.3.8 maintenance-release of Xymon to Sourceforge. It
> > should be available by the time you read this.
> >
> <snipped>
> > * Minor bugfixes and cleanups of compiler warnings.
>
> The compiler warnings are less but there are still 99 compiler
> warnings regarding to "function not checked on returned result"
>
> Example:
> ignoring return value of ?freopen?, declared with attribute
> warn_unused_result [-Wunused-result]
>
>
> See this reference
>
> http://stackoverflow.com/questions/9148134/declared-with-attribute-warn-unused-result-wunused-result
>
>
> Looks like a valid compiler warning need to be addressed, IMHO.
>
>
> tj
> --
> T.J. Yang
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 16 Jul 2012 07:55:51 +0200
> From: Henrik St?rner <henrik at hswn.dk>
> To: "T.J. Yang" <tjyang2001 at gmail.com>
> Cc: Xymon mailinglist <xymon at xymon.com>,
>         xymon-developer at lists.sourceforge.net
> Subject: Re: [Xymon] Xymon 4.3.8 available
> Message-ID: <5003ACE7.4070001 at hswn.dk>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 16-07-2012 03:45, T.J. Yang wrote:
> > The compiler warnings are less but there are still 99 compiler
> > warnings regarding to "function not checked on returned result"
> >
> > Example:
> > ignoring return value of ?freopen?, declared with attribute
> > warn_unused_result [-Wunused-result]
>
> I only get 94, depends on compiler versions I guess. There are some
> valid warnings, but they haven't been blindly ignored.
>
> 52 of those warnings come from re-opening the logfile after a
> log-rotation. If it fails, the only consequence is that logging stops.
> The problem here is: What can you do if you no longer have a logfile ?
> Should xymon abort? That would just be weird, because we cannot tell the
> user why Xymon stopped (there is no logfile, remember?)
>
> 24 are from calls to "fgets". Some of these are valid, but happen only
> in extreme situations - and some are just ignorable, e.g. when scanning
> the history files looking for where to start reading fgets() is used to
> skip to the next line, so we really don't care about the data being read.
>
> And the rest is a mixed bag of calls.
>
>
> I'll work to reduce that number, but it just wasn't a priority right now.
>
>
> Regards,
> Henrik
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 16 Jul 2012 06:14:13 +0000
> From: FORD Alan <Alan.FORD at stanwell.com>
> To: Xymon mailinglist <xymon at xymon.com>
> Subject: [Xymon] alerts.cfg RECOVERED sends 2 emails even with a STOP
> Message-ID:
>         <54CFCF7376079F4D9F7BE49DE3E4FA3B68543085 at DC1EXCMBX01.stanwell.com
> >
> Content-Type: text/plain; charset="us-ascii"
>
> Hi all,
> I am using Xymon 4.3.7 on RHEL5.
> When I get a non-green status for any hosts on "Test_Page" I get one
> email. When it recovers I get 2.
>
> I have my alerts.cfg setup like this
>
> PAGE=%Test_Page
>       SCRIPT /home/xymon/xymon/server/ext/email_mess_html blah at blah.com
> <mailto:blah at blah.com> REPEAT=24h RECOVERED FORMAT=SCRIPT
>       STOP
>
> HOST=*
>       IGNORE PAGE=%Test_Page
>       SCRIPT /home/xymon/xymon/server/ext/email_mess_html blah at blah.com
> <mailto:blah at blah.com> REPEAT=24h RECOVERED FORMAT=SCRIPT
>
> Is this a Bug or am I not understanding something?? :)
>
> Thanks
>
> Alan Ford
> Senior Database Administrator
> Com Serv - Information Communications and Technology
> Stanwell Corporation Limited
> www.stanwell.com<http://www.stanwell.com>
>
>
> This email is to be read subject to the email disclaimer located at
> http://www.stanwell.com/email-disclaimer.aspx
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.xymon.com/pipermail/xymon/attachments/20120716/06f200b7/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 6
> Date: Mon, 16 Jul 2012 09:12:30 +0000
> From: Becker Christian <christian.becker at rhein-zeitung.net>
> To: "xymon at xymon.com" <xymon at xymon.com>
> Subject: [Xymon] Missing feature ?
> Message-ID: <E6B86B09BF9C1E43B3CB4A78CC1BA7B697A55293 at w2k8-ex-mb-2>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello all,
>
> we have Xymon monitoring running on four sites, each site having ~400
> devices to monitor.
> Xymon has replaced our "old" monitoring solution which was CA Unicenter.
>
> Having used CA Unicenter for many years now and now having changed to
> Xymon, I have two things that I cannot find:
>
> a)      In CA Unicenter you can acknowledge an red alert. After having
> acknowledged an red alert, this red alert changes to an orange alert,
> indicating that there is still  a problem.
> The main advantage is, that any "view" on a "higher level" isn't under red
> condition any longer - it becomes yellow. This means, that a new red alert
> coming from the same server could be recognized in a better way.
> This could be useful if in Xymon somebody doesn't like the "All non green
> view" for any reason.
>
>
> b)      The other thing is: for example, in Xymon I have a server on which
> I'm monitoring many services ( ~ 20 services). If one of those services
> fails or is administratively disabled, this service becomes red. Now I have
> the possibility to acknowledge this alert or to disable this test. But, if
> another service on the same server fails, I cannot recognize this, if the
> test is disabled. If it is acknowledged, it isn't clear by 100% which on is
> the most recent one that has failed. This could also affect a server that
> has many disks. If one disk get's filled by 100%, I cannot see if another
> disk get's also filled by 100% (if one doesn't like the "All non green
> view").
>
> Is my thinking wrong?
>
> Regards
> Christian
>
> CHRISTIAN BECKER
> System Engineer
> CSC
>
> August-Horch-Strasse 28, 56070 Koblenz, Germany
> Global Outsourcing Services Central Region
>
>
> ________________________________
>
> CSC * This is a PRIVATE message. If you are not the intended recipient,
> please delete without copying and kindly advise us by e-mail of the mistake
> in delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind CSC to any order or other contract unless pursuant to explicit written
> agreement or government initiative expressly permitting the use of e-mail
> for such purpose * CSC Deutschland Services GmbH * Registered Office:
> Abraham-Lincoln-Park 1, 65189 Wiesbaden, Germany * Board of Directors:
> Gerhard Fercho (Chairman),Thomas Nebe, Peter Schmidt * Registered in
> Germany: HRB 7574, Wiesbaden
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.xymon.com/pipermail/xymon/attachments/20120716/7576e08c/attachment-0001.html
> >
>
> ------------------------------
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
>
> End of Xymon Digest, Vol 18, Issue 15
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20120716/39342966/attachment.html>


More information about the Xymon mailing list