Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Nov 2021 11:12:01 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 259795] databases/galera26: cannot initialize new cluster
Message-ID:  <bug-259795-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259795

            Bug ID: 259795
           Summary: databases/galera26: cannot initialize new cluster
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: lapo@lapo.it
                CC: devel@galeracluster.com
             Flags: maintainer-feedback?(devel@galeracluster.com)
                CC: devel@galeracluster.com

Created attachment 229446
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D229446&action=
=3Dedit
complete error log

I have a strange problem: I cannot initialize a new (MAriaDB 10.5) Galera
cluster, doing the same things that I did a few months ago to set-up a simi=
lar
cluster.

# cp /usr/local/etc/mysql/conf.d/wsrep.cnf.sample
/usr/local/etc/mysql/conf.d/wsrep.cnf
# nano /usr/local/etc/mysql/conf.d/wsrep.cnf

and I only changed: wsrep_provider, wsrep_cluster_name, wsrep_cluster_addre=
ss,
wsrep_sst_method, wsrep_sst_auth.

I get this error:

2021-11-12 12:08:37 0 [ERROR] WSREP: exception from gcomm, backend must be
restarted: failed to set FD_CLOEXEC: 9 (Bad file descriptor)
         at
/wrkdirs/usr/ports/databases/galera26/work/galera-release_26.4.9/galerautil=
s/src/gu_asio_socket_util.hpp:set_fd_options():41

Moreover, at the end I get this unexpected behavior that it cannot be stopp=
ed
but there is some lingering process:

# service mysql-server onestop
mysql not running? (check /var/run/mysql/mysqld.pid).
# pgrep maria
73240
57197

Is this a known bug?
Is there a way to debug which socket is not accepting FD_CLOEXEC?
(maybe with truss? but the rc.d startup is a bit complex)

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259795-7788>