9 |
|
|
10 |
* The syntax of resource monitoring has changed. "CPUUSAGE", |
* The syntax of resource monitoring has changed. "CPUUSAGE", |
11 |
"MEMUSAGE", "MEMKBYTE" is dropped in favor of the unit based |
"MEMUSAGE", "MEMKBYTE" is dropped in favor of the unit based |
12 |
"MEM" and "CPU" commands. Please consult the manpage for |
"MEM" and "CPU" commands. Please consult the man page for |
13 |
details. |
details. |
14 |
|
|
15 |
* Resource monitoring can be turned off in the configure stage. |
* Resource monitoring can be turned off in the configure stage. |
80 |
start statement was defined for the service. Now it is possible get |
start statement was defined for the service. Now it is possible get |
81 |
notification via email if a service died, even if you did not |
notification via email if a service died, even if you did not |
82 |
include any start statement. For instance, this is now a complete |
include any start statement. For instance, this is now a complete |
83 |
statement and wil, report if the service resin should die: |
statement and will, report if the service apache should die: |
84 |
check process resin with pidfile /usr/local/resin/srun.pid |
check process apache with pidfile /usr/local/apache/logs/httpd.pid |
85 |
|
alert foo@bar.baz |
86 |
|
|
87 |
* Monit now closes all filedescriptors before spawning a child |
* Monit now closes all file descriptors before spawning a child |
88 |
processes. There was a problem with open file descriptors inherited |
processes. There was a problem with open file descriptors inherited |
89 |
by processes started under monit's control. Thanks to Peter |
by processes started under monit's control. Thanks to Peter |
90 |
Holdaway <pholdaway@technocom-wireless.com> for reporting the |
Holdaway <pholdaway@technocom-wireless.com> for reporting the |
98 |
not send alert message with bare line feeds anymore. Thanks to Rail |
not send alert message with bare line feeds anymore. Thanks to Rail |
99 |
Aliev <rail@iqchoice.com> |
Aliev <rail@iqchoice.com> |
100 |
|
|
101 |
* Checksum statement is now restricted to new file monitoring service |
* The checksum statement is now restricted to a check file service |
102 |
type only. Usage of this statements in process check service is |
entry. Usage of this statement in a check process service is |
103 |
obsolete from this release. To test checksum for process asociated |
obsolete from this release. See the documentation and the |
104 |
files, you should use file check service and define dependency of the |
UPGRADE.txt file accompanying the software. |
105 |
process on this check. See documentation and UPGRADE.txt for syntax. |
|
106 |
|
* The timestamp statement is now restricted to a check file service |
107 |
* Timestamp statement is now restricted to new file and directory |
entry. Usage of this statement in a check process service is |
108 |
monitoring services types. Usage of this statement in process check |
obsolete from this release. See the documentation and the |
109 |
service is obsolete from this release. To test timestamp for process |
UPGRADE.txt file accompanying the software. |
110 |
asociated files or directories, you should use file or directory |
|
111 |
check service and define dependency of the process on this check. |
* You do not need to specify the path to the file or directory in a |
112 |
See documentation and UPGRADE.txt for syntax. |
checksum or in a timestamp statements. The path is inherited from |
113 |
|
the parent check service. See the documentation and UPGRADE.txt |
114 |
* You don't need to specify path to the file or directory in checksum |
file. |
|
or timestamp statements. It is inherited from parent check service. |
|
|
See documentation and UPGRADE.txt for syntax. |
|
115 |
|
|
116 |
* The syntax for the checksum statement has changed so the statement |
* The syntax for the checksum statement has changed so the statement |
117 |
is a real IF-THEN statement. An example of a valid checksum statement |
is a real IF-THEN statement. An example of a valid checksum |
118 |
is: |
statement: "if failed checksum then stop". The old syntax version |
119 |
if failed checksum then stop |
is obsolete. |
|
The old syntax version is obsolete. |
|
120 |
|
|
121 |
* The timestamp statement is extended to check for file and directory |
* The timestamp statement is extended to check for file and directory |
122 |
changes. You can now use the timestamp statement to get an alert if |
changes. You can now use the timestamp statement to get an alert if |
123 |
a file was changed. For instance: |
a file was changed. For instance: |
124 |
check file passwd with path /etc/passwd |
check file passwd with path /etc/passwd |
125 |
if timestamp was changed then alert |
if timestamp was changed then alert |
126 |
The timestamp does only test the last modified stamp not if the |
The timestamp does only test the last modified stamp not if the |
127 |
content of the file was changed. Use the checksum statement for |
content of the file was changed. Use the checksum statement for |
128 |
this. |
this. |
129 |
|
|
130 |
* The timestamp, resource and size statement now supports an optional |
* All service tests, such as the timestamp, resource and checksum |
131 |
exec statement. The exec statement is used to execute an arbitrary |
statements now supports an optional exec statement. The exec |
132 |
program as an action for the resource, size or timestamp statement. |
statement is used to execute an arbitrary program as an action if |
133 |
For instance to reload apache if the httpd.conf file was changed: |
the test validates to true. For instance to reload apache if the |
134 |
check file httpd.conf with path /usr/local/apache/conf/httpd.conf |
httpd.conf file was changed: |
135 |
if timestamp was changed then exec "/etc/init.d/apache graceful" |
check file httpd.conf with path /usr/local/apache/conf/httpd.conf |
136 |
|
if timestamp was changed |
137 |
|
then exec "/etc/init.d/apachectl graceful" |
138 |
|
|
139 |
* This release changes the port statement to explicit require an |
* This release changes the port statement to explicit require an |
140 |
action to be executed upon a failed connection test. The port |
action to be executed upon a failed connection test. The port |
141 |
statement has also been extended to include an optional socket |
statement has also been extended to include an optional socket |
142 |
connection timeout. |
connection timeout. |
143 |
|
|
144 |
* Checksum statement bugfix. Previous versions compared only |
* Checksum statement bug fix. Previous versions compared only |
145 |
first 31 characters of 32 possible. |
first 31 characters of 32 possible. |
146 |
|
|
147 |
* The syntax for the timeout statement has changed so the statement |
* The syntax for the timeout statement has changed so the statement |
151 |
The old syntax version, e.g. timeout(2, 3) still works but is |
The old syntax version, e.g. timeout(2, 3) still works but is |
152 |
deprecated and future releases may remove this version. |
deprecated and future releases may remove this version. |
153 |
|
|
154 |
* Monit can be compiled with dietlibc and uClibc from now on. Using |
* Monit can be compiled with dietlibc and uClibc from now on. Using |
155 |
dietlibc it possible to use SSL; SSL support with uClibc is untested. |
dietlibc it possible to use SSL; SSL support with uClibc is |
156 |
For build instructions refer to to the documentation of these |
untested. For build instructions refer to to the documentation of |
157 |
libraries. |
these libraries. |
158 |
|
|
159 |
* New 'monitor' action was added to allow standalone monitoring |
* A new 'monitor' action was added to explicit enable service |
160 |
enabling. It can be used to reenable monitoring of the service |
monitoring. This can be used to re-enable monitoring if a service |
161 |
which timed out, starting monitoring of the service which is in |
timed out or was stopped or start monitoring a service in manual |
162 |
manual mode and is actualy running outside monit control, etc. |
mode. Dependency relationships are also supported - all services |
163 |
Dependency relationships are supported - all services chain which |
which this service depends on are also set in monitored mode before |
164 |
this service depends on are monitoring enabled before starting monitoring |
starting monitoring of this service. You can also enable or disable |
165 |
of this service. You can call monitor action from console or web interface. |
service monitoring from the console or from the web interface. |
166 |
|
|
167 |
* New 'unmonitor' action was added to allow standalone monitoring |
* A new 'unmonitor' action was added to explicit allow monitoring |
168 |
disabling. It can be used to disable monitoring of the service (aka |
disabling. This can be used to disable monitoring of services (aka |
169 |
bring it to maintanance mode), etc. Dependency relationships are supported - |
bring it to maintenance mode), etc. Dependency relationships are |
170 |
all services chain which depends on this service are monitoring disabled |
also supported. |
171 |
before stopping monitoring of this service. You can call unmonitor action |
|
172 |
from console or web interface or use it in tests as action in the case of |
* A new check service entry was added to allow monitoring of remote |
173 |
error. |
host services. Example: |
174 |
|
check host ftp.redhat.com |
175 |
|
if failed port 21 protocol ftp then alert |
176 |
|
alert hauk@tildeslash.com |
177 |
|
|
178 |
|
|
179 |
Version 3.2 |
Version 3.2 |