public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 2/2] amazon-ssm-agent: Allow to overcommit memory
Date: Mon, 30 Mar 2020 17:24:42 +0000	[thread overview]
Message-ID: <20200330172442.11391-2-michael.tremer@ipfire.org> (raw)
In-Reply-To: <20200330172442.11391-1-michael.tremer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
---
 lfs/amazon-ssm-agent                      | 2 +-
 src/initscripts/packages/amazon-ssm-agent | 6 ++++++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/lfs/amazon-ssm-agent b/lfs/amazon-ssm-agent
index d4aa3fa90..4b08bd41d 100644
--- a/lfs/amazon-ssm-agent
+++ b/lfs/amazon-ssm-agent
@@ -33,7 +33,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = amazon-ssm-agent
-PAK_VER    = 2
+PAK_VER    = 3
 
 DEPS       =
 
diff --git a/src/initscripts/packages/amazon-ssm-agent b/src/initscripts/packages/amazon-ssm-agent
index c385d890c..eeaa7b7e5 100644
--- a/src/initscripts/packages/amazon-ssm-agent
+++ b/src/initscripts/packages/amazon-ssm-agent
@@ -13,6 +13,12 @@ case "${1}" in
 			exit 0
 		fi
 
+		# Allow the kernel to overcommit memory.
+		# The SSM agent fails to clone() itself when there is
+		# "not enough memory" available. This simply seems to
+		# fail no matter how much free memory is available.
+		echo 1 > /proc/sys/vm/overcommit_memory
+
 		boot_mesg "Starting Amazon SSM Agent..."
 		/usr/bin/amazon-ssm-agent &>/dev/null &
 		evaluate_retval
-- 
2.20.1


      reply	other threads:[~2020-03-30 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 17:24 [PATCH 1/2] amazon-ssm-agent: Update to 2.3.930.0 Michael Tremer
2020-03-30 17:24 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200330172442.11391-2-michael.tremer@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox