Date: Tue, 4 Aug 2026 23:00:16 -0400 From: Garrett Wollman <wollman@bimajority.org> To: freebsd-stable@freebsd.org Cc: des@freebsd.org Subject: [MAYBE NOT] Weird breakage on 14.4-p6 to 14.4-p8 upgrade Message-ID: <27250.42816.996405.971780@hergotha.csail.mit.edu> In-Reply-To: <27250.41983.974395.276819@hergotha.csail.mit.edu>
index | next in thread | previous in thread | raw e-mail
<<On Tue, 4 Aug 2026 22:46:23 -0400, I wrote: > On Monday I upgraded one of my servers from 14.4-p6 to 14.4-p8, and > after the reboot, yaf (net-mgmt/yaf) immediately started crashing with > SIGSEGV about once per CPU-minute. The package hasn't changed > (although I did force-reinstall it just to make sure there was no > corruption in the executable). [...] > pid 4650 (yaf), jid 0, uid 65534: exited on signal 11 (no core dump - bad address) It did just occur to me to check whether the package had been updated, and it has; des@ upgraded it to 2.19.3 in late June, and because of the way yaf gets started in my environment, while the binary was silently replaced, the running daemon probably never got restarted until I rebooted the server. So now I've manually backed out the port upgrade to see if that fixes matters. -GAWollmanhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27250.42816.996405.971780>