Send Xymon mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
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 <user-c862b499d9fa@xymon.invalid>
To: xymon at xymon.com
Subject: [Xymon] ALERTCOLORS question
Message-ID: <user-7c8920ece467@xymon.invalid>
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 : user-c862b499d9fa@xymon.invalid |
| |
| 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 <user-ce4a2c883f75@xymon.invalid>
To: Xymon mailinglist <xymon at xymon.com>,
user-834d44be5e50@xymon.invalid
Subject: [Xymon] Xymon 4.3.8 available
Message-ID: <user-b137e83d9a04@xymon.invalid>
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" <user-61afc885aa73@xymon.invalid>
To: Henrik St?rner <user-ce4a2c883f75@xymon.invalid>
Cc: Xymon mailinglist <xymon at xymon.com>,
user-834d44be5e50@xymon.invalid
Subject: Re: [Xymon] Xymon 4.3.8 available
Message-ID:
<CAD2GW8pL5JcAy2f+Ozm_CVLfLHTBQP9Cajdrbnztk=
user-aa7926e55d0c@xymon.invalid>
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 <user-ce4a2c883f75@xymon.invalid> 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 <user-ce4a2c883f75@xymon.invalid>
To: "T.J. Yang" <user-61afc885aa73@xymon.invalid>
Cc: Xymon mailinglist <xymon at xymon.com>,
user-834d44be5e50@xymon.invalid
Subject: Re: [Xymon] Xymon 4.3.8 available
Message-ID: <user-ec6a99b08abb@xymon.invalid>
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 <user-eb925835b8b9@xymon.invalid>
To: Xymon mailinglist <xymon at xymon.com>
Subject: [Xymon] alerts.cfg RECOVERED sends 2 emails even with a STOP
Message-ID:
<user-7789f68e8c52@xymon.invalidContent-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 user-43a348f7c9a8@xymon.invalid
<mailto:user-43a348f7c9a8@xymon.invalid> REPEAT=24h RECOVERED FORMAT=SCRIPT
STOP
HOST=*
IGNORE PAGE=%Test_Page
SCRIPT /home/xymon/xymon/server/ext/email_mess_html user-43a348f7c9a8@xymon.invalid
<mailto:user-43a348f7c9a8@xymon.invalid> 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