From nobody Tue Feb 22 06:58:24 2022 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6B14519E2FDC for ; Tue, 22 Feb 2022 06:58:58 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from smtpg.telissant.net (smtpg.telissant.net [104.225.1.73]) (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 4K2qlP6gCzz3Lms for ; Tue, 22 Feb 2022 06:58:57 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from sacada.3dresearch.com (localhost [127.0.0.1]) by smtpg.telissant.net (Postfix) with ESMTP id 4K2qlP4fhGz6HPl; Tue, 22 Feb 2022 01:58:57 -0500 (EST) X-Virus-Scanned: amavisd-new at telissant.net Received: from smtpg.telissant.net ([127.0.0.1]) by sacada.3dresearch.com (sacada.3dresearch.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UfZhf0dJIpwu; Tue, 22 Feb 2022 01:58:57 -0500 (EST) Received: from elettra.3dresearch.com (unknown [71.112.243.145]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: elettra@sacada.3dresearch.com) by smtpg.telissant.net (Postfix) with ESMTPSA id 4K2qlP1wmkz6HPk; Tue, 22 Feb 2022 01:58:57 -0500 (EST) Received: from elettra.3dresearch.com (localhost [127.0.0.1]) by elettra.3dresearch.com (Postfix) with SMTP id BB48410E7B; Tue, 22 Feb 2022 01:58:56 -0500 (EST) Date: Tue, 22 Feb 2022 01:58:24 -0500 From: Janos Dohanics To: FreeBSD Questions , Paul Procacci Subject: Re: sshd refuses connection Message-Id: <20220222015824.08679774465c2c285fec5e6b@3dresearch.com> In-Reply-To: References: <20220222011846.76558bae4f153f024cae3349@3dresearch.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4K2qlP6gCzz3Lms X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of web@3dresearch.com designates 104.225.1.73 as permitted sender) smtp.mailfrom=web@3dresearch.com X-Spamd-Result: default: False [1.34 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; ENVFROM_SERVICE_ACCT(1.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a:smtpg.telissant.net]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[3dresearch.com]; NEURAL_HAM_LONG(-0.99)[-0.994]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.87)[-0.869]; FROM_SERVICE_ACCT(1.00)[]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-questions]; FREEMAIL_TO(0.00)[freebsd.org,gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:104.225.1.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[71.112.243.145:received] X-ThisMailContainsUnwantedMimeParts: N On Tue, 22 Feb 2022 01:34:07 -0500 Paul Procacci wrote: > Hi Janos, > > The best advice is probably making plans to get a KVM on the machine > ahead of time. > Barring this, if you already installed the world libs/sshd binary ... > keep your current ssh session active and restart the sshd daemon only > to see if that solves your problem. > Also ensure the config is proper and that all referenced paths resolve > correctly and anything referenced has been rebuilt against the new > libs as well. > If that fails, adding -vvv flags to the sshd upon startup would > provide not only you, but us further information as well. > > Ultimately, I believe if you simply restart the daemon, the problem > will resolve itself. > > ~Paul Hi Paul, Thank you for the quick reply. Yes, I did have a KVM ready, and after rebooting sshd(8) is accepting connections again. Whew! -- Janos Dohanics