From nobody Sat Jan 20 00:39:58 2024 X-Original-To: freebsd-arm@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 4TGyLM6RSkz57mTh for ; Sat, 20 Jan 2024 00:39:55 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TGyLM2d8Jz4S4K for ; Sat, 20 Jan 2024 00:39:55 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 40K0dw7e048979 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 19 Jan 2024 16:39:59 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 40K0dwYX048978; Fri, 19 Jan 2024 16:39:58 -0800 (PST) (envelope-from fbsd) Date: Fri, 19 Jan 2024 16:39:58 -0800 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: sshd signal 11 on -current Message-ID: References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4TGyLM2d8Jz4S4K X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] On Fri, Jan 19, 2024 at 11:40:55AM -0800, Mark Millard wrote: > > You may need to do local experiments where the > dsl_modem is not connected? Or may be move > switchA to the other side of the router temporarily? > > Problem isolation may require things be off the > public WAN some of the time. > In this case, ns2.zefox.net (along with ns1 and www) are at software EOL and need to be updated anyway. I might as well start with ns2 and see what happens. If the problem persists, then there's something to investigate further. A setup similar to pelorus.zefox.org is likely to be used, which communicates via ssh with no trouble over the network as it is. > > in this case > > ns2.zefox.net and ns1.zefox.net seem to be affected. > > No other hosts (so far) have reported that particular > > error. > > If you are unable to isolate the smallest configurations > that fail and which Operating System combinations fail > I do not see how to get evidence for the range of > observed oddities. > At this point the need is for a nameserver that works and is maintainable. 12.4.4 works for now, but isn't maintainable. > > Subject to the proviso that www.zefox.net is headless > > and so must be accessed via ssh from some other host. > > No tip session attached to www.zefox.net ? That > connection type is not via ssh to www.zefox.net . > The serial console server for ns2.zefox.net is nemesis.zefox.com. Ssh to nemesis followed by tip to ns2 works fine, no "Corrupted Mac..."errors even when running grep -i ssh /var/log/messages. > > The choice of host seems to make no difference. > > macOS vs. RasPiOS/Win10 ? But, ns2 needs to communicate with modern hosts, not antiques. All the servers in the trio (ns1, ns2, www) need to update past 12.4.4. Changing ns2 is inevitable. Going to aarch64 seems prudent. At the outset I thought I was seeing something much worse than stale software or maybe hardware. Thanks for reading! bob prohaska