From owner-freebsd-questions@freebsd.org Thu Sep 2 08:10:14 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9C56C67B149 for ; Thu, 2 Sep 2021 08:10:14 +0000 (UTC) (envelope-from mark.tinka@seacom.com) Received: from the-host.tinka.africa (ge-1.ln-01-jnb.za.seacomnet.com [105.28.96.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H0YWT5NKsz3t33 for ; Thu, 2 Sep 2021 08:10:13 +0000 (UTC) (envelope-from mark.tinka@seacom.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tinka.africa; s=tinka; h=Content-Type:MIME-Version:Date:Message-ID:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=N8FG/QDSGAetcdNCIgPU9YeBqv9LQMJkOFjN5HOcgxQ=; b=Vlkb/FNec/6o0M6EggsB0Sk2Qr 5OoZlssaq/wieI/M2T+BDLWuyV+vWiHxduEuHA2KMrCQ7SoZLxXMyxWsvFVb9dz/etL9MZLTvAdB4 NmrJvDFuAmlnYtvGUBbyKODc0HowpTtxLGQ2yqCqZlFduOOVhqoc+iEky68cID0SoYAS0t7tBZfBL IqxDhK24N/MDVDPopCIYl8A5fW8r0whMWbgPJV3IBGYSQvwSG/qJ4rtJZLC1etiehIVjPQx26FCzZ EjT34LZpEbu0iBcpDlRqRtIcHg5cJhBSF+1ANoh53L1iXiOwPk+cdgevgUaxFUMvfWP7L2yYdoG1S alHdsTsQ==; Received: from [127.0.0.1] (helo=Marks-MacBook-Pro.local) by the-host.tinka.africa with esmtp (Exim 4.94) (envelope-from ) id QYSS0R-0009EL-ED for freebsd-questions@freebsd.org; Thu, 02 Sep 2021 10:10:03 +0200 To: freebsd-questions@freebsd.org From: Mark Tinka Subject: BIND 'max-cache-size' Value on FreeBSD-13.0 Organization: SEACOM Message-ID: Date: Thu, 2 Sep 2021 10:10:03 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 Content-Language: en-US X-Rspamd-Queue-Id: 4H0YWT5NKsz3t33 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tinka.africa header.s=tinka header.b="Vlkb/FNe"; dmarc=pass (policy=none) header.from=seacom.com; spf=pass (mx1.freebsd.org: domain of mark.tinka@seacom.com designates 105.28.96.5 as permitted sender) smtp.mailfrom=mark.tinka@seacom.com X-Spamd-Result: default: False [-3.00 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[tinka.africa:s=tinka]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:105.28.96.5]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; HAS_ORG_HEADER(0.00)[]; DKIM_TRACE(0.00)[tinka.africa:+]; HFILTER_HELO_2(1.00)[the-host.tinka.africa]; DMARC_POLICY_ALLOW(-0.50)[seacom.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:37100, ipnet:105.16.0.0/12, country:MU]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-questions] X-Mailman-Approved-At: Sat, 04 Sep 2021 20:47:48 +0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2021 08:10:14 -0000 Hi all. Ever since we moved from BIND-9.11 to BIND-9.16, we've been experiencing 'named' crashing after 24hrs - 36hrs on high-load resolver-only servers, running on FreeBSD-13.0. We found that the reason for this was due to BIND running out of swap space. An increase in swap space by creating a 4GB swap file did not help. So we are now playing with the 'max-cache-size' value in BIND. The system has 15GB of physical RAM. Limiting BIND to 13GB of memory does not work; 'named' still crashes due to a lack of swap space. We have then switched to % values, and it's still crashing for the same reason at 90% and now 80%. We are now testing 70%. Anyone have some idea of how we can get this under control? Is there a possibility that BIND is not properly understanding how much physical RAM is available to FreeBSD, and just burns through it anyway, tripping swap space in the process? I can't think of any reason why BIND would keep burning RAM if it has been told to limit its demand to a certain value or %. All help appreciated. Thanks. Mark.