From owner-freebsd-current@freebsd.org Mon Jun 29 08:03:38 2020 Return-Path: Delivered-To: freebsd-current@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 3F4DE341B71 for ; Mon, 29 Jun 2020 08:03:38 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49wKkK6z6fz4VJC for ; Mon, 29 Jun 2020 08:03:37 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 05T83aNx058932 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 29 Jun 2020 01:03:42 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: "O. Hartmann" In-Reply-To: <20200629090326.63b4830b@freyja> From: Chris Reply-To: bsd-lists@BSDforge.com To: freebsd-current Subject: Re: CURRENT: swap issues and dying jails Date: Mon, 29 Jun 2020 01:03:42 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49wKkK6z6fz4VJC X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2020 08:03:38 -0000 On Mon, 29 Jun 2020 09:03:32 +0200 O=2E Hartmann ohartmann@walstatt=2Eorg said > Due to the circumstance I have no access anymore to the host in question, > I'll > report a problem occured out of the blue around last week's update of > CURRENT > with poudriere and swapspace=2E >=20 > Problem: under heavy load, the host dies - no ssh connection possible > anymore, > all jails are in the state "dead"=2E > The box in question is running CURRENT, most recent, last update yesterda= y > morning (28th of June, around 1400 UTC)=2E Revision numbers are added as so= on > I > have access to the box again=2E >=20 > The host has 16 GB phsyical RAM and 64 GB configured swap - which the ker= nel > complains about to increase swapzone or something similar=2E The host runs > poudriere with both CURRENT and 12-STABLE jails (both recent versions)=2E I= n > the > past 18 months we pushed the box to the limits with poudriere allwoing 4 > poudriere jobs with each 4 threads - never had any problem except slowing > down > the system, but always responsive anyhow and never crashing or loosing > network > connection=2E >=20 > The first time the box died this way was 28th, after the last update of b= oth > host and jails has been performed 26th June, ~ 1400 UTC=2E Jails running > 12-stable are the first poudriere jobs running and that is the state were > the > first crash/hung occured yesterday=2E >=20 > Is this a known problem? There was a situation very similar to yours mentioned over the last week on freebsd-stable@=2E By Donald Wilde, under the title: swap space issues I believe he also used 12=2E There was a great deal of technical advice that appeared to improve his situation=2E Interestingly; he was also experiencing this on his "builder" altho he was using synth as opposed to poudriere=2E Maybe it'll help your situation? --Chris >=20 > Kind regards, >=20 > oliver > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= "