File Release Notes and Changelog
Release Name: 1.2.0
Notes:
Changes:
$Id: CHANGES,v 1.3.2.12 2007/06/06 11:46:17 trockij Exp $
Changes between mon-1.2.0- and mon-1.2.0-release
Wed Jun 6 07:45:35 EDT 2007
-----------------------------------------------
-Bunch of fixes from Augie Schwer:
Added RPM spec update to do a "chkconfig on" in the post install, and fixed a path bug in S99mon
Fix config parsing of unack_summary, added docs for the option in the man page
Fix display of ack'd services in mon.cgi
Fix -p/-P option problem in mon.monitor
Fix nntp.monitor "-f" option
Allow snpp.alert to "use strict"
-added "-m" to http.monitor to match header/content with regex
by Jim Trocki
-added hard timeout patch to msql-mysql.monitor
by Arkadiusz Miskiewicz
-added fix to ftp.monitor to handle multiline reply after quit command
by Arkadiusz Miskiewicz
-fix to fping.monitor to correct parsing of fping 2.2b1 output. It prints
lines like "ICMP Host Unreachable from" to stderr, but to stdout it
prints "(host) is unreachable", and the regex was matching both, which
is wrong.
by Tim Berger
-added -u option, "UnexpectedHop", "AlertMessage", to traceroute.monitor
by Jon Meek
-updated output formatting in ntpdate.monitor
by Jon Meek
-added local-syslog.monitor
by Jon Meek
-added --okstring, Cache-Control http header, --debuglog, to http_tppnp.monitor
by Jon Meek
-updates to smtp3.monitor, --alarmtime, --maxfailtime
by Jon Meek
-fixed "disable host" behavior. if a host was the only member of a hostgroup,
that watch would be disabled, but that host would not be disabled in other
hostgroups. the correct behavior is that a host will be disabled individually
in all hostgroups, and if it is the only memeber of a hostgroup, the watch
associated with that hostgroup will be disabled. enabling the host again undoes
all of that. the behavior of disabling the watch is useful so that disabling a
host in a single-hosted hostgroup does not inadvertently leave an empty
hostgroup, which will generate log warnings when services are run against it.
reported by Ed Ravin
Changes between mon-1.0.0pre3 and mon-1.0.0pre4
Tue Aug 3 08:02:35 EDT 2004
-----------------------------------------------
-when allow_empty_group is not set and no host arguments
to pass to a monitor, the interval wasn't being reset so
it would spam the syslog with lots of "no host arguments"
messages. this is fixed.
-in reset_timer, there was a chance that _timer could get
set to a negative value, which is not right. fixed it.
-fixed the bug where lots of mon processes could accumulate if the
exec of an alert failed. also fixed error handling of failed
alerts.
-added "show failures only" button to mon.cgi to speed it up.
by Ed Ravin <eravin@panix.com>
-small permissions fix to rpm spec file
-added MON_CFBASEDIR variable to monitor and alert
environment, which is set to the value of "cfbasedir" in the
config file.
-removed unfinished snmp trap handling stuff. it doesn't work at all,
and it's misleading to people even though the man page says it doesn't
work.
-added monitor_duration and monitor_running output to opstatus detail
in monshow
Changes between mon-1.0.0pre1 and mon-1.0.0pre3
Mon Jul 12 09:12:29 EDT 2004
-----------------------------------------------
-changed README to refer to the new, more sensible name for the perl module
client, which is mon-client
-applied eric's updates to INSTALL and added a mention of monshow and mon.cgi as
the web interfaces
-added eric's rpm spec file (i removed the patches because they are no longer
needed)
-added lmb's syslog.monitor (a nifty hack)
-added 'alertevery strict' code and docs, updated the README and INSTALL to
mention CVS, updated CREDITS
-incorporated mon.cgi 1.52
-minor addition to alert behavior explanation in mon.8
-in dialin.monitor.wrap.c, return the exit status of execv (if it fails, that is)
-fixed path to perl in file_change.monitor and smtp3.monitor
-added some rcs tags to identify the file versions
-handle_trap_timeout now calls process_event, and it works fine with
alert/upalert/alertevery/etc. as shown by my testing
-received traps now reset the trap timeout counter, and fixed some
other stuff wrt trap timeouts
-added sub process_event and made proc_cleanup and handle_trap use it
so that the alert mgmt code is shared rather than in two places. i tested
as much of it as i could and all seems to work well now, especially
upalert, alertafter, alertevery with traps.
-added per-service "_monitor_duration" variable which records how many
seconds the previous monitor took to execute. this is available via
"list opstatus". if no monitor has executed yet then the value is -1.
-added per-service "_monitor_running" variable whose value is 0 or 1
depending on whether the monitor is currently running for that service.
-removed gunk from handle_trap regarding the various TRAP_COLDSTART, etc.
processing, since most of it was a bad idea anyway, or at least as far as
i could tell. traps and their exit values are now processed exactly as
monitors are, which simplifies things greatly and adds to more intuitive
functionality. this means the "spc" value in a trap is now ignored.
-fixed some args processing in call_alert
-fixed a bug which would prevent alerts or upalerts
from being sent when call alerts is passed the "output"
argument whose value is undef
-remove usage of parse_line in trap processing
(backported from mon 1.1 code)
-make esc_str escape spaces in order to be compatible with monperl-1-0-0pre1
-added list of all possible client commands to moncmd
-added --community to set the snmp community in reboot.monitor
-patch to traceroute.monitor from meekj
added StateDir, TracerouteOptions, StopAt config options
some bugfixes to config file parsing
reap children to avoid defunct processes
added timeout alarm
-up_rtt.monitor
added -r to log individual rtts, better error reporting for tcp and udp check