For details see: https://mmonit.com/monit/changes/
New: Issue #715: The PostgreSQL protocol test has been improved and now supports authentication with username, password and database when testing connection. Example:
if failed port 5432 protocol pgsql username "username" password "12345" database "test" then alert
Previous Monit versions used hardcoded credentials when testing connection to postgresql (user=root and database=root). This could trigger thousands of messages like this in the postgresql log:
root@root FATAL: password authentication failed for user "root" root@root DETAIL: Role "root" does not exist.
Note: Monit will continue to use the hardcoded credentials (for backward compatibility) unless username and password are set. New: Issue #973: You can now test program output using a regular expression. Syntax:
IF CONTENT [!]= <regex> THEN action
Example:
check program disk0_smart with path "/usr/sbin/nvme smart-log /dev/nvme0" if content != "critical_warning[ ]+: 0" then alert
New: Issue #974: Monit CLI: Added support for the -g (group) option to the report command. Example:
monit -g database report
Fixed: Issue #991 (Monit 5.28.1 regression): MacOS: Monit didn't compile on MacOS 10.13 or older. Thanks to Lutz Mader.
Fixed: Issue #994 (Monit 5.28.1 regression): The check program statement with every did not work properly.
Fixed: Issue #995: Monit start delay was vulnerable to time jumps when Monit is waiting for the delay to pass. Thanks to Daniel Crowe.
Fixed: Issue #975: Monit CLI: Monit did not report a warning if -s, -p, -l, -g or -c command-line options were specified multiple times and silently used the last value only. Monit will generate a warning now.
Fixed: Issue #972: Monit GUI: The log view had no size limit when reading the Monit log file and could block the browser if the log file was large.
Fixed: Issue #955: If more than one every statement is used in a check-service context only the last value is (silently) used. We now report a warning in this case.
Signed-off-by: Matthias Fischer matthias.fischer@ipfire.org --- lfs/monit | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/monit b/lfs/monit index 06306eb8f..c01e5bab0 100644 --- a/lfs/monit +++ b/lfs/monit @@ -24,7 +24,7 @@
include Config
-VER = 5.28.1 +VER = 5.29.0
THISAPP = monit-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 832783145cbd523bd6bc2c36e0e5c052 +$(DL_FILE)_MD5 = 8a0546d0d52216b22ebd57acc0bb1e03
install : $(TARGET)
Hi Matthias,
You missed the increment of the PAK_VER number.
Regards,
Adolf.
On 18/09/2021 16:11, Matthias Fischer wrote:
For details see: https://mmonit.com/monit/changes/
New: Issue #715: The PostgreSQL protocol test has been improved and now supports authentication with username, password and database when testing connection. Example: if failed port 5432 protocol pgsql username "username" password "12345" database "test" then alert Previous Monit versions used hardcoded credentials when testing connection to postgresql (user=root and database=root). This could trigger thousands of messages like this in the postgresql log: root@root FATAL: password authentication failed for user "root" root@root DETAIL: Role "root" does not exist. Note: Monit will continue to use the hardcoded credentials (for backward compatibility) unless username and password are set. New: Issue #973: You can now test program output using a regular expression. Syntax: IF CONTENT [!]= <regex> THEN action Example: check program disk0_smart with path "/usr/sbin/nvme smart-log /dev/nvme0" if content != "critical_warning[ ]+: 0" then alert New: Issue #974: Monit CLI: Added support for the -g (group) option to the report command. Example: monit -g database report Fixed: Issue #991 (Monit 5.28.1 regression): MacOS: Monit didn't compile on MacOS 10.13 or older. Thanks to Lutz Mader. Fixed: Issue #994 (Monit 5.28.1 regression): The check program statement with every did not work properly. Fixed: Issue #995: Monit start delay was vulnerable to time jumps when Monit is waiting for the delay to pass. Thanks to Daniel Crowe. Fixed: Issue #975: Monit CLI: Monit did not report a warning if -s, -p, -l, -g or -c command-line options were specified multiple times and silently used the last value only. Monit will generate a warning now. Fixed: Issue #972: Monit GUI: The log view had no size limit when reading the Monit log file and could block the browser if the log file was large. Fixed: Issue #955: If more than one every statement is used in a check-service context only the last value is (silently) used. We now report a warning in this case.Signed-off-by: Matthias Fischer matthias.fischer@ipfire.org
lfs/monit | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/monit b/lfs/monit index 06306eb8f..c01e5bab0 100644 --- a/lfs/monit +++ b/lfs/monit @@ -24,7 +24,7 @@
include Config
-VER = 5.28.1 +VER = 5.29.0
THISAPP = monit-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 832783145cbd523bd6bc2c36e0e5c052 +$(DL_FILE)_MD5 = 8a0546d0d52216b22ebd57acc0bb1e03
install : $(TARGET)
On 20.09.2021 15:45, Adolf Belka wrote:
Hi Matthias,
Hi Adolf,
You missed the increment of the PAK_VER number.
Erm...DOH!...Done.
I've sent a fix - hoping this will be enough,
Best, Matthias
Regards,
Adolf.
On 18/09/2021 16:11, Matthias Fischer wrote:
For details see: https://mmonit.com/monit/changes/
New: Issue #715: The PostgreSQL protocol test has been improved and now supports authentication with username, password and database when testing connection. Example: if failed port 5432 protocol pgsql username "username" password "12345" database "test" then alert Previous Monit versions used hardcoded credentials when testing connection to postgresql (user=root and database=root). This could trigger thousands of messages like this in the postgresql log: root@root FATAL: password authentication failed for user "root" root@root DETAIL: Role "root" does not exist. Note: Monit will continue to use the hardcoded credentials (for backward compatibility) unless username and password are set. New: Issue #973: You can now test program output using a regular expression. Syntax: IF CONTENT [!]= <regex> THEN action Example: check program disk0_smart with path "/usr/sbin/nvme smart-log /dev/nvme0" if content != "critical_warning[ ]+: 0" then alert New: Issue #974: Monit CLI: Added support for the -g (group) option to the report command. Example: monit -g database report Fixed: Issue #991 (Monit 5.28.1 regression): MacOS: Monit didn't compile on MacOS 10.13 or older. Thanks to Lutz Mader. Fixed: Issue #994 (Monit 5.28.1 regression): The check program statement with every did not work properly. Fixed: Issue #995: Monit start delay was vulnerable to time jumps when Monit is waiting for the delay to pass. Thanks to Daniel Crowe. Fixed: Issue #975: Monit CLI: Monit did not report a warning if -s, -p, -l, -g or -c command-line options were specified multiple times and silently used the last value only. Monit will generate a warning now. Fixed: Issue #972: Monit GUI: The log view had no size limit when reading the Monit log file and could block the browser if the log file was large. Fixed: Issue #955: If more than one every statement is used in a check-service context only the last value is (silently) used. We now report a warning in this case.Signed-off-by: Matthias Fischer matthias.fischer@ipfire.org
lfs/monit | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/monit b/lfs/monit index 06306eb8f..c01e5bab0 100644 --- a/lfs/monit +++ b/lfs/monit @@ -24,7 +24,7 @@
include Config
-VER = 5.28.1 +VER = 5.29.0
THISAPP = monit-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 832783145cbd523bd6bc2c36e0e5c052 +$(DL_FILE)_MD5 = 8a0546d0d52216b22ebd57acc0bb1e03
install : $(TARGET)
-
Adolf Belka -
Matthias Fischer