From patchwork Sat Sep 18 14:11:10 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Matthias Fischer X-Patchwork-Id: 4720 Return-Path: Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4HBXml1jYMz3xW7 for ; Sat, 18 Sep 2021 14:11:19 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4HBXmj75L4z6cP; Sat, 18 Sep 2021 14:11:17 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4HBXmj2gLWz2xZP; Sat, 18 Sep 2021 14:11:17 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4HBXmg2WsQz2xPC for ; Sat, 18 Sep 2021 14:11:15 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4HBXmf6lYYz2C4 for ; Sat, 18 Sep 2021 14:11:14 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1631974275; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc; bh=Ply0BD745KePya4EEKldQzlQ0qYIIM8IKVHRMUyQsJ4=; b=S6bV/0TagsUOsvuWWjL9cAX2VB6iq4TNWqj6loVaDthRO04k3vCUjxA5YqQ5qLlSPg8om7 Na9QYmjA/S0JVCAg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1631974275; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc; bh=Ply0BD745KePya4EEKldQzlQ0qYIIM8IKVHRMUyQsJ4=; b=BAIf6Mw9M+1H9ggIkx1Ufd60GzXP8FBRj49hXAJIPWKKjmHb4NDl15Ibt5/FxYkweJxEUg m2OoKmgtTme5NU9SlhlN0Q/CVYxhMqrBlXiTAkiTaKbKD6/R4CLErRFOhwNfozIySrBdbf Jd3JxCpohGwsUkR0okC1pQXrTLdDU2Hb7u4zAMaImVr1E34FumXQ+bwQ/XCUtTqiwfmI23 Kn5owCLyHkJ44PcPkTHXK9ihlM2FERyWzBsqSZUtlRER1ToB+hNsZmkBFooqCfoCL96lvA dqhT2/TQPHQbLFrArfp8Rv6PIIBTRfyTOrzeed/A2MajdNAcidECngRJySDCIw== From: Matthias Fischer To: development@lists.ipfire.org Subject: [PATCH] monit: Update to 5.29.0 Date: Sat, 18 Sep 2021 16:11:10 +0200 Message-Id: <20210918141110.24784-1-matthias.fischer@ipfire.org> X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: development-bounces@lists.ipfire.org Sender: "Development" 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 [!]= 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 --- 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)