5 |
Version 4.6.1 |
Version 4.6.1 |
6 |
|
|
7 |
BUGFIXES: |
BUGFIXES: |
8 |
* When file content test matched, send alert each time (though the |
* If a file content test evaluate to true, monit will now send an |
9 |
action was evaluated each time the test matched, monit sent |
alert each time. In previous versions, monit only sent one alert |
10 |
just one alert on first occurence by default). Thanks to Peter |
on the first occurence. Thanks to Peter Holik (peter AT holik!at) |
11 |
Holik ( peter AT holik!at ) for reporting the problem. |
for reporting the problem. |
12 |
|
|
13 |
* Add client_name field to the postfix-policy protocol test to |
* Added client_name field to the postfix-policy protocol test to |
14 |
support more policy server implementations. Thanks to Scott |
support more policy server implementations. Thanks to Scott |
15 |
Storck < scott ; storck topdeq ; com > for the patch. |
Storck < scott ; storck topdeq ; com > for the patch. |
16 |
|
|
26 |
Version 4.6 |
Version 4.6 |
27 |
|
|
28 |
NEW FEATURES AND FUNCTIONS: |
NEW FEATURES AND FUNCTIONS: |
29 |
* Add support for Postfix SMTP access policy delegation protocol |
* Added support for a Postfix SMTP access policy delegation |
30 |
test. Example usage: |
protocol test. Example of usage: |
31 |
check host policyd with address 192.168.1.5 |
check host policyd with address 192.168.1.5 |
32 |
if failed port 10031 protocol postfix-policy then alert |
if failed port 10031 protocol postfix-policy then alert |
33 |
|
|
34 |
* Support to check lines appended to files added. The feature |
* Support for performing regular expression tests in text files |
35 |
is usable with the following statements: |
where added. Here's a teaser example showing how this feature |
36 |
IF [NOT] MATCH {regex|path} THEN action |
can be used to scan syslog: |
37 |
IGNORE [NOT] MATCH {regex|path} |
check file syslog with path /var/log/syslog |
38 |
Lines matching the IGNORE MATCH are not examined with further |
if match |
39 |
IF MATCH tests. Single extended regular expression or files |
"^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mrcoffee\[[0-9]+\]:" |
40 |
containing extended regular expression can be used. In case |
# You can also collect regexs in a file |
41 |
regular expression support is not available simple substring |
if match /etc/monit/active.regex then alert |
42 |
matching is being used. |
As shown, regex can be written directly in the control file or |
43 |
|
collected in a separat file which monit will use. This feature |
44 |
|
depends on regex(7) and if not installed on the system, monit |
45 |
|
reverts to plain substring matching. The matching engine is |
46 |
|
fast and on par with more specialized log-scanning tools. |
47 |
|
|
48 |
* Monit now sends three icmp echo requests in one cycle by default. |
* Monit now sends three icmp echo requests in one cycle by default. |
49 |
It is also possible to customize the echo requests count using |
It is also possible to customize the echo requests count using |
52 |
if failed icmp type echo count 5 with timeout 3 seconds |
if failed icmp type echo count 5 with timeout 3 seconds |
53 |
then alert |
then alert |
54 |
|
|
55 |
* Monit now supports optional error notification reminder. For those |
* Support for optional error notification reminders. For those |
56 |
who want to be notified several times that the service is still |
who wants to be notified several times that the service is still |
57 |
down, it is possible to specify the count of service failed cycles |
down, it is possible to specify the count of service failed cycles |
58 |
after which monit will send another notification. The 'reminder' |
after which monit will send another notification. The 'reminder' |
59 |
option was added to local and global alert definition - example: |
option was added to both local and global alert definitions - example: |
60 |
set alert foo@bar with reminder on 10 cycles |
set alert foo@bar with reminder on 10 cycles |
61 |
will send the error notification each tenth cycle when the service |
will send error notification each tenth cycle when the service |
62 |
remains down. If you want to be notified each cycle, then use reminder |
remains down. If you want to be notified on each cycle, use reminder |
63 |
on 1 cycle. Thanks to Pavel Urban <urbanp at mlp!cz> for suggesting |
on 1 cycle. Thanks to Pavel Urban <urbanp at mlp!cz> for suggesting |
64 |
the feature. |
the feature. |
65 |
|
|
66 |
* It is now possible to use the 'passed' word as alternative to the |
* It is now possible to use the 'passed' keyword as alternative to the |
67 |
'recovered' in recovery action section. |
'recovered' keyword in a recovery action section. |
68 |
|
|
69 |
* Support for event ratio dependant actions added. It is now possible |
* Support for fault tolerant monitoring added. You can now specify |
70 |
to specify how many events during how many cycles are needed |
the event frequency before an action is conducted by monit. |
71 |
to trigger the action. Both failed and passed actions may be |
In some cases you will want to allow a certain level of events to |
72 |
restricted this way. The part 'X times within Y cycles' is |
occur before an error is raised. This feature is optional and if |
73 |
optional - when not used, monit will act on first event (equals |
not used, monit defaults to act on the first event as usually. Both |
74 |
to '1 times within 1 cycle'). It is also possible to specify just |
failed and passed actions may be restricted this way. Here's an |
75 |
consecutive cycles count. Example: |
example: |
76 |
check host foo.bar with address 192.168.1.1 |
check host foo.bar with address 192.168.1.1 |
77 |
if failed port 80 for 5 times within 8 cycles then exec '/my/script' |
if failed port 80 for 5 times within 8 cycles |
78 |
|
then exec '/my/script' |
79 |
else if passed for 10 cycles then alert |
else if passed for 10 cycles then alert |
80 |
|
|
81 |
BUGFIXES: |
BUGFIXES: |
82 |
* In the case that kvm access on FreeBSD failed (for example |
* If kvm access on FreeBSD failed (for example because of environment |
83 |
because of environment restricted by virtual server), process |
restricted by virtual server), monit's process resource monitoring |
84 |
resource monitoring will be disabled. Thanks to Mike Jackson |
will automatically be disabled. Thanks to Mike Jackson <mjackson at |
85 |
<mjackson at datahost!com> for reporting the problem. |
datahost!com> for reporting the problem. |
86 |
|
|
87 |
* Fixed URL connection test. Monit now really tries to download |
* Fixed the URL connection test. Monit now really tries to download |
88 |
content length data from the HTTP server or if not set, up to 1 MB. |
content length data from the HTTP server or if the content-length |
89 |
Previous versions could fail to read all the data provided by |
header is not provided, up to 1 MB. Previous versions could fail |
90 |
the server. Thanks to Ben Hartshorne <ben at hartshorne!net> for |
to read all the data provided by the server. Thanks to Ben |
91 |
reporting the problem. |
Hartshorne <ben at hartshorne!net> for reporting the problem. |
92 |
|
|
93 |
* Fixed CIDR notation of monit http interface net allow option on |
* Fixed CIDR notation of monit http interface net allow option on |
94 |
little endian architectures. Thanks to Ben Hartshorne <ben at |
little endian architectures. Thanks to Ben Hartshorne <ben at |
95 |
hartshorne!net> for reporting the problem. |
hartshorne!net> for reporting the problem. |
96 |
|
|
97 |
* Retry the service restart in the next cycle even in the case that |
* Retry service restart in the next cycle even if the stop method |
98 |
the stop method failed, until restart timeout limit is reached. |
failed. Restart is now tried until the timeout limit is reached. |
99 |
Monit silently timeouted the service in the case that the stop |
Monit silently timed out the service if the stop method failed |
100 |
method failed (just exec failed notification was send). Thanks |
(only an exec failed notification was sent). Thanks to Pavel Urban |
101 |
to Pavel Urban <urbanp at mlp ! cz> for reporting the problem. |
<urbanp at mlp ! cz> for reporting the problem. |
102 |
|
|
103 |
* Close included config files after parsing. Previous versions of |
* Close included config files after parsing. Previous versions of |
104 |
monit kept parsed include files open, which could create a problem |
monit kept parsed include files open, which could create a problem |
126 |
is defined for the host and it fails we simply do not continue with testing |
is defined for the host and it fails we simply do not continue with testing |
127 |
any port connection tests because we assume the line is down. |
any port connection tests because we assume the line is down. |
128 |
|
|
129 |
* Fixed the echo request identification in ping test when more hosts were tested |
* Fixed the echo request identification in ping test when more hosts were |
130 |
using ping test. Thanks to Peter Holik ( peter AT holik!at ) |
tested using the ping test. Thanks to Peter Holik ( peter AT holik!at ) |
131 |
|
|
132 |
|
|
133 |
Version 4.5.1 |
Version 4.5.1 |
134 |
|
|
135 |
NEW FEATURES AND FUNCTIONS: |
NEW FEATURES AND FUNCTIONS: |
136 |
* Support for native MySQL protocol test added. The test can be |
* Support for native MySQL protocol test was added. The test can be |
137 |
used with unixsocket and port testing rules. Example: |
used with unixsocket and port testing rules. Example: |
138 |
check host FOO with address db.foo.bar |
check host FOO with address db.foo.bar |
139 |
if failed port 3306 protocol mysql then alert |
if failed port 3306 protocol mysql then alert |