1. Forum
  2. USENET
  3. muc.lists.freebsd.stable

  • Weird breakage on 14.4-p6 to 14.4-p8 upgrade

    From Garrett Wollman@wollman@bimajority.org to muc.lists.freebsd.stable on Tue Aug 4 22:46:23 2026
    From Newsgroup: muc.lists.freebsd.stable

    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). I was able to attach to a running in
    lldb before it crashed, and the crash appears to be a null-pointer
    dereference, but obviously *this wasn't happening before*, and I don't
    see anything in UPDATING for -p7 or -p8 that looks like it could be
    remotely relevant.

    There's no core dump; the kernel logs:

    pid 4650 (yaf), jid 0, uid 65534: exited on signal 11 (no core dump - bad address)

    Anyone have any clues?

    -GAWollman



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Garrett Wollman@wollman@bimajority.org to muc.lists.freebsd.stable on Tue Aug 4 23:00:16 2026
    From Newsgroup: muc.lists.freebsd.stable

    <<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.

    -GAWollman



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Garrett Wollman@wollman@bimajority.org to muc.lists.freebsd.stable on Fri Aug 7 11:50:20 2026
    From Newsgroup: muc.lists.freebsd.stable

    <<On Tue, 4 Aug 2026 23:00:16 -0400, Garrett Wollman <wollman@bimajority.org> said:

    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.

    And I'm not pretty certain that the upgrade of yaf is the actual
    source of the problem, and the security patches were unrelated other
    than forcing a reboot. Sorry for the false alarm; I'll be filing a
    bug on the yaf package.

    -GAWollman



    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2