From nobody Thu Aug 19 09:31:15 2021 X-Original-To: ports-bugs@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 5EE7B176DEE4 for ; Thu, 19 Aug 2021 09:31:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GqzzS1wh2z4Vth for ; Thu, 19 Aug 2021 09:31:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 2B6C423289 for ; Thu, 19 Aug 2021 09:31:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 17J9VGU8097920 for ; Thu, 19 Aug 2021 09:31:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 17J9VGL4097919 for ports-bugs@FreeBSD.org; Thu, 19 Aug 2021 09:31:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 257939] databases/mariadb105-server: wsrep_sst_mariabackup broken since 10.5.11 Date: Thu, 19 Aug 2021 09:31:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ltning-freebsd@anduin.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: brnrd@freebsd.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257939 Bug ID: 257939 Summary: databases/mariadb105-server: wsrep_sst_mariabackup broken since 10.5.11 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: brnrd@freebsd.org Reporter: ltning-freebsd@anduin.net Assignee: brnrd@freebsd.org Flags: maintainer-feedback?(brnrd@freebsd.org) We are using MariaDB in a Galera Cluster setup, and the 10.5.10 to=20 10.5.11 upgrade brought huge changes to the wsrep_sst_common and=20 wsrep_sst_mariabackup scripts. These changes make them entirely=20 FreeBSD-incompatible. The most important changes (to us) are - reliance on --tmpdir option to mktemp - is_local_ip always returns true in a jail The former makes the SST script fail because of invalid option.=20 This is easily (and probably compatible with Linux) fixed by removing=20 the --tmpdir option and rather prefixing mktemp with 'TMPDIR=3D$tmpdir ;'=20 inside the same $() around line 935 of wsrep_sst_mariabackup: < xtmpdir=3D$(mktemp '-d' --tmpdir "$tmpdir") > xtmpdir=3D$(TMPDIR=3D"$tmpdir" ; mktemp '-d') The latter I had to hack by removing the commonname option passed to=20 socat on line 387 of the same file: < CN_option=3D'localhost' > CN_option=3D'' This is obviously not a fix, as I don't fully understand what's going on=20 - but I did not have more time to spend on this as our cluster was down :( Anything you can do to help bring attention to this from upstream? It's=20 really broken that they're making linux-ism assumptions all over the=20 place.. And the change set between these two releases seems pretty big=20 in these scripts. Alternatively, patches need to be put in place in the port itself, though I imagine this is a less desirable option long-term. --=20 You are receiving this mail because: You are the assignee for the bug.=