Overview

This is a flavour containing the mariadb database server with galera clustering solution enabled. It is currently WIP development image and separate from the mariadb image on purpose.

It is assumed that a persistent directory containing the mysql datadir is mounted in to /var/db/mysql, optionally you could copy in your server.cnf configuration if you do have specific needs not covered by the default configuration (see Installation chapter below).

Also, it supports parameters to regularly dump the content of the database into a SQL-file so you can create consistent backups from outside the jail.

To ensure that software and database file versions match, mysql_upgrade is run on startup. That way, you should be able to upgrade your mariadb installation by simply replacing the jail with a newer version as long as the database files are stored outside and mounted in (see above and examples below).

Installation

Create a ZFS data set on the parent system beforehand zfs create -o mountpoint=/mnt/mysqldata zroot/mysqldata
Create your local jail from the image or the flavour files.
Clone the local jail
Mount in the ZFS data set you created pot mount-in -p <jailname> -m /var/db/mysql -d /mnt/mysqldata
Optionally export the ports after creating the jail: pot export-ports -p <jailname> -e 3306:3306 -e 4567:4567 -e 4568:4568 -e 4444:4444 -e 4567:4567 -e 9104:9104

Adjust to your environment:

sudo pot set-env -p <jailname> \
  -E DATACENTER=<datacentername> \
  -E NODENAME=<nodename> \
  -E IP=<IP address of this system> \
  -E CONSULSERVERS="<comma-deliminated list of consul server IP addresses>" \
  -E GOSSIPKEY="<32 byte Base64 key from consul keygen>" \
  -E DBROOTPASS=<database root password> \
  -E DBSCRAPEPASS=<mysqld exporter user password> \
  -E SERVERID=<unique identifier 1,2,3> \
  -E GALERACLUSTER=<comma-deliminated list of all mariadb servers in cluster> \
  [ -E GALERAPRIMARY=<Y> ] \
  [ -E DUMPSCHEDULE="<cronschedule>" -E DUMPUSER=<backupuser> -E DUMPFILE=</insidejail/dumpfile.sql> ] \
  [ -E LOADBALANCER=<IP address of haproxy-sql image> ] \
  [ -E REMOTELOG=<IP address of syslog-ng server> ]

Required Paramaters

DATACENTER defines a common datacenter.

NODENAME defines the name of this node.

IP is the IP address which will be used to access services.

CONSULSERVERS is a comma-deliminated list of consul server instances. Do not include spaces!

e.g. CONSULSERVERS="10.0.0.2" or CONSULSERVERS="10.0.0.2,10.0.0.3,10.0.0.4,10.0.0.6,10.0.0.6"

GOSSIPKEY is the gossip encryption key for consul agent and must be passed in as a parameter.

DBROOTPASS is the root password for the mysql database, which must be passed in even if database exists and configured.

DBSCRAPEPASS is the password for the mysqld_exporter exporter user.

SERVERID is a unique identifier. Set to 1 for first server, 2 for second and so on.

GALERACLUSTER is a comma-deliminated list of all mariadb servers in the cluster.

Optional Parameters

GALERAPRIMARY is set on the first server in the cluster. You’ll launch this node first. Do not set on the others.

DUMPSCHEDULE is a cron schedule is in the scheduling format of crontab, e.g. “*/5 * * * *”. (include quotes)

DUMPUSER defaults to root and DUMPFILE defaults to /var/db/mysql/full_mariadb_backup.sql if you set a DUMPSCHEDULE but do not specify one or both of these parameters.

LOADBALANCER is the IP address of a haproxy-sql instance which will provide loadbalancing between two or three mariadb instances. A user called haproxy is created with no password and no access to databases.

REMOTELOG is the IP address of a destination syslog-ng server, such as with the loki flavour, or beast-of-argh flavour.

Usage

You can connect to the database server with a mariadb client.

Galera Replication

Replication should be automatic between nodes once a database is added to first server.

High Availability

You can use a loadbalancing/failover TCP proxy such as the haproxy-sql pot image to query all servers in the cluster. Make sure to set the LOADBALANCER variable to the IP of the haproxy-sql image in advance.

Getting Started

Image Readme
How To Use The Ready-Made Image
Alternatively: Create a Jail With This Flavour Yourself
Version History
Manual Image Download Links
Jenkins Pot Creation Logs

How To Use The Ready-Made Image

FreeBSD 14.0:
pot import -p mariadb-galera-amd64-14_0 -t 0.7.1 -U https://potluck.honeyguide.net/mariadb-galera

With Signify Verification:
fetch https://potluck.honeyguide.net/potluck.pub; pot import -p mariadb-galera-amd64-14_0 -t 0.7.1 -C potluck.pub -U https://potluck.honeyguide.net/mariadb-galera

If you don’t want to use the default pot bridged network configuration but instead need an individual network setup (e.g. assign a host IP address), after importing it you can simply clone the jail like that (em0 is the host network adapter in this example):
pot clone -P mariadb-galera-amd64-14_0 -p my-cloned-jail -N alias -i "em0|10.10.10.10"

Note: Some images might require specific network configuration, double check the Overview-chapter at the top.

Alternatively: Create a Jail With This Flavour Yourself

1. Create Flavour Files

Save all files and directories from https://github.com/hny-gd/potluck/tree/master/mariadb-galera to /usr/local/etc/pot/flavours/

2. Create Jail From Flavour

Run
pot create -b <FreeBSD Version> -p <jailname> -t single -N public-bridge -f fbsd-update

with your FreeBSD version (e.g. 14.0) and the name your jail should get.

Note: Some images might require specific network configuration, double check the Overview-chapter at the top.

Version History

0.7

Version bump for new base image
Fix node_exporter zfs issue

0.6

Version bump for new base image
FBSD14 base image

0.5

Version bump for new base image

0.4

Version bump for new base image

0.3

Version bump for new base image

0.2

Version bump for new base image

0.1

Version bump for new base image

0.0

Copy mariadb to mariadb-galera and customise for Galera cluster
Don’t create haproxy user on replicas
Only create mysql_exporter user on primary
mysqld_exporter runs as user nobody but config file with password has restrictive permissions, fixed

These images were built on Mon Apr 22 21:14:43 UTC 2024

Manual Image Download Links

mariadb-galera-amd64-14_0_0.7.1.xz ( )
mariadb-galera-amd64-14_0_0.7.1.xz.skein ( ) mariadb-galera-amd64-14_0_0.7.1.xz.skein.sig ( ) mariadb-galera-amd64-14_0_0.7.1.xz.meta ( )

Jenkins Pot Creation Logs

mariadb-galera-amd64-14_0_0.7.1:


mariadb-galera/mariadb-galera:
copy-in -s /usr/local/etc/pot/flavours/mariadb-galera.d/local -d /root/.pot_local
mariadb-galera/mariadb-galera.sh:
#!/bin/sh

# Based on POTLUCK TEMPLATE v3.0
# Altered by Michael Gmelin
#
# EDIT THE FOLLOWING FOR NEW FLAVOUR:
# 1. RUNS_IN_NOMAD - true or false
# 2. If RUNS_IN_NOMAD is false, can delete the <flavour>+4 file, else
#    make sure pot create command doesn't include it
# 3. Create a matching <flavour> file with this <flavour>.sh file that
#    contains the copy-in commands for the config files from <flavour>.d/
#    Remember that the package directories don't exist yet, so likely copy
#    to /root
# 4. Adjust package installation between BEGIN & END PACKAGE SETUP
# 5. Adjust jail configuration script generation between BEGIN & END COOK
#    Configure the config files that have been copied in where necessary

# Set this to true if this jail flavour is to be created as a nomad
# (i.e. blocking) jail.
# You can then query it in the cook script generation below and the script
# is installed appropriately at the end of this script
RUNS_IN_NOMAD=false

# set the cook log path/filename
COOKLOG=/var/log/cook.log

# check if cooklog exists, create it if not
if [ ! -e $COOKLOG ]
then
    echo "Creating $COOKLOG" | tee -a $COOKLOG
else
    echo "WARNING $COOKLOG already exists"  | tee -a $COOKLOG
fi
date >> $COOKLOG

# -------------------- COMMON ---------------

STEPCOUNT=0
step() {
  STEPCOUNT=$(("$STEPCOUNT" + 1))
  STEP="$*"
  echo "Step $STEPCOUNT: $STEP" | tee -a $COOKLOG
}

exit_ok() {
  trap - EXIT
  exit 0
}

FAILED=" failed"
exit_error() {
  STEP="$*"
  FAILED=""
  exit 1
}

set -e
trap 'echo ERROR: $STEP$FAILED | (>&2 tee -a $COOKLOG)' EXIT

# -------------- BEGIN PACKAGE SETUP -------------

step "Bootstrap package repo"
mkdir -p /usr/local/etc/pkg/repos
# only modify repo if not already done in base image
# shellcheck disable=SC2016
test -e /usr/local/etc/pkg/repos/FreeBSD.conf || \
  echo 'FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly" }' \
    >/usr/local/etc/pkg/repos/FreeBSD.conf
ASSUME_ALWAYS_YES=yes pkg bootstrap

step "Touch /etc/rc.conf"
touch /etc/rc.conf

# this is important, otherwise running /etc/rc from cook will
# overwrite the IP address set in tinirc
step "Remove ifconfig_epair0b from config"
# shellcheck disable=SC2015
sysrc -cq ifconfig_epair0b && sysrc -x ifconfig_epair0b || true

step "Disable sendmail"
service sendmail onedisable

step "Create /usr/local/etc/rc.d"
mkdir -p /usr/local/etc/rc.d

# we need consul for consul agent
step "Install package consul"
pkg install -y consul

step "Install package openssl"
pkg install -y openssl

step "Install package sudo"
pkg install -y sudo

# necessary if installing curl now
step "Install package ca_root_nss"
pkg install -y ca_root_nss

step "Install package curl"
pkg install -y curl

step "Install package jq"
pkg install -y jq

step "Install package jo"
pkg install -y jo

step "Install package nano"
pkg install -y nano

step "Install package bash"
pkg install -y bash

step "Install package rsync"
pkg install -y rsync

step "Install package mariadb106-server"
pkg install -y mariadb106-server

step "Install package mariadb106-client"
pkg install -y mariadb106-client

step "Install package galera26"
pkg install -y galera26

step "Install package node_exporter"
pkg install -y node_exporter

step "Install package mysqld_exporter"
pkg install -y mysqld_exporter

step "Install package syslog-ng"
pkg install -y syslog-ng

step "Clean package installation"
pkg clean -y

step "Create mysql directory"
mkdir -p /var/db/mysql

# -------------- END PACKAGE SETUP -------------

#
# Now generate the run command script "cook"
# It configures the system on the first run by creating the config file(s)
# On subsequent runs, it only starts sleeps (if nomad-jail) or simply exits
#

# this runs when image boots
# ----------------- BEGIN COOK ------------------

step "Clean cook artifacts"
rm -rf /usr/local/bin/cook /usr/local/share/cook

step "Install pot local"
tar -C /root/.pot_local -cf - . | tar -C /usr/local -xf -
rm -rf /root/.pot_local

step "Set file ownership on cook scripts"
chown -R root:wheel /usr/local/bin/cook /usr/local/share/cook
chmod 755 /usr/local/share/cook/bin/*

# ----------------- END COOK ------------------


# ---------- NO NEED TO EDIT BELOW ------------

step "Make cook script executable"
if [ -e /usr/local/bin/cook ]
then
    echo "setting executable bit on /usr/local/bin/cook" | tee -a $COOKLOG
    chmod u+x /usr/local/bin/cook
else
    exit_error "there is no /usr/local/bin/cook to make executable"
fi

#
# There are two ways of running a pot jail: "Normal", non-blocking mode and
# "Nomad", i.e. blocking mode (the pot start command does not return until
# the jail is stopped).
# For the normal mode, we create a /usr/local/etc/rc.d script that starts
# the "cook" script generated above each time, for the "Nomad" mode, the cook
# script is started by pot (configuration through flavour file), therefore
# we do not need to do anything here.
#

# Create rc.d script for "normal" mode:
step "Create rc.d script to start cook"
echo "creating rc.d script to start cook" | tee -a $COOKLOG

# shellcheck disable=SC2016
echo '#!/bin/sh
#
# PROVIDE: cook
# REQUIRE: LOGIN
# KEYWORD: shutdown
#
. /etc/rc.subr
name="cook"
rcvar="cook_enable"
load_rc_config $name
: ${cook_enable:="NO"}
: ${cook_env:=""}
command="/usr/local/bin/cook"
command_args=""
run_rc_command "$1"
' > /usr/local/etc/rc.d/cook

step "Make rc.d script to start cook executable"
if [ -e /usr/local/etc/rc.d/cook ]
then
  echo "Setting executable bit on cook rc file" | tee -a $COOKLOG
  chmod u+x /usr/local/etc/rc.d/cook
else
  exit_error "/usr/local/etc/rc.d/cook does not exist"
fi

if [ "$RUNS_IN_NOMAD" != "true" ]
then
  step "Enable cook service"
  # This is a non-nomad (non-blocking) jail, so we need to make sure the script
  # gets started when the jail is started:
  # Otherwise, /usr/local/bin/cook will be set as start script by the pot
  # flavour
  echo "enabling cook" | tee -a $COOKLOG
  service cook enable
fi

# -------------------- DONE ---------------
exit_ok

mariadb-galera/mariadb-galera+1:
mariadb-galera/mariadb-galera+1.sh:

mariadb-galera/mariadb-galera+2:
mariadb-galera/mariadb-galera+2.sh:

mariadb-galera/mariadb-galera+3:
mariadb-galera/mariadb-galera+3.sh:

mariadb-galera/mariadb-galera+4:
mariadb-galera/mariadb-galera+4.sh:
=====>  Create conf dir (/mnt/srv/pot/jails/mariadb-galera-amd64-14_0/conf)
=====>  Cloning freebsd-potluck-amd64-14_0_0_0_23 with snap 
=====>  clone zroot/srv/pot/jails/freebsd-potluck-amd64-14_0_0_0_23/m@1713115286 into zroot/srv/pot/jails/mariadb-galera-amd64-14_0/m
=====>  Flavour: fbsd-update
=====>  Starting mariadb-galera-amd64-14_0 pot for the initial bootstrap
=====>  mount /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===>  Starting the pot mariadb-galera-amd64-14_0
=====>  Pot mariadb-galera-amd64-14_0 jail params are: allow.set_hostname=false allow.raw_sockets allow.socket_af allow.chflags exec.clean mount.devfs enforce_statfs=2 sysvshm=new sysvsem=new sysvmsg=new children.max=0 devfs_ruleset=4 stop.timeout=10 name=mariadb-galera-amd64-14_0 host.hostname=mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net osrelease=14.0-RELEASE-p6 path=/mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m persist vnet vnet.interface=epair0b
ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg
32-bit compatibility ldconfig path: /usr/lib32
Starting Network: lo0 epair0b.
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet 127.0.0.1 netmask 0xff000000
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	options=8<VLAN_MTU>
	ether 02:c0:e3:f0:36:0b
	inet 10.192.0.3 netmask 0xffc00000 broadcast 10.255.255.255
	groups: epair
	media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
	status: active
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
add host 127.0.0.1: gateway lo0 fib 0: route already in table
add net default: gateway 10.192.0.1
add host ::1: gateway lo0 fib 0: route already in table
add net fe80::: gateway ::1
add net ff02::: gateway ::1
add net ::ffff:0.0.0.0: gateway ::1
add net ::0.0.0.0: gateway ::1
Clearing /tmp (X related).
Updating /var/run/os-release done.
Creating and/or trimming log files.
Updating motd:.
Starting syslogd.
Starting sendmail_submit.
Starting cron.

Mon Apr 22 21:08:38 UTC 2024
/usr/local/etc/pot/flavours/fbsd-update.sh -> /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/tmp/fbsd-update.sh
=====>  Executing fbsd-update script on mariadb-galera-amd64-14_0
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 14.0-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 14.0-RELEASE-p6.
No updates are available to install.
=====>  Stop the pot mariadb-galera-amd64-14_0
=====>  Remove p46626d1d490 epair network interfaces
=====>  unmount /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/tmp
=====>  unmount /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/dev
=====>  Flavour: mariadb-galera
=====>  Executing mariadb-galera pot commands on mariadb-galera-amd64-14_0
=====>  mount /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/tmp
=====>  Source /usr/local/etc/pot/flavours/mariadb-galera.d/local copied in the pot mariadb-galera-amd64-14_0
=====>  unmount /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/tmp
=====>  /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/dev is already unmounted
=====>  Starting mariadb-galera-amd64-14_0 pot for the initial bootstrap
=====>  mount /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===>  Starting the pot mariadb-galera-amd64-14_0
=====>  Pot mariadb-galera-amd64-14_0 jail params are: allow.set_hostname=false allow.raw_sockets allow.socket_af allow.chflags exec.clean mount.devfs enforce_statfs=2 sysvshm=new sysvsem=new sysvmsg=new children.max=0 devfs_ruleset=4 stop.timeout=10 name=mariadb-galera-amd64-14_0 host.hostname=mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net osrelease=14.0-RELEASE-p6 path=/mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m persist vnet vnet.interface=epair0b
ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg
32-bit compatibility ldconfig path: /usr/lib32
Starting Network: lo0 epair0b.
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet 127.0.0.1 netmask 0xff000000
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	options=8<VLAN_MTU>
	ether 02:0b:72:2e:67:0b
	inet 10.192.0.3 netmask 0xffc00000 broadcast 10.255.255.255
	groups: epair
	media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
	status: active
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
add host 127.0.0.1: gateway lo0 fib 0: route already in table
add net default: gateway 10.192.0.1
add host ::1: gateway lo0 fib 0: route already in table
add net fe80::: gateway ::1
add net ff02::: gateway ::1
add net ::ffff:0.0.0.0: gateway ::1
add net ::0.0.0.0: gateway ::1
Clearing /tmp (X related).
Updating /var/run/os-release done.
Creating and/or trimming log files.
Updating motd:.
Starting syslogd.
Starting sendmail_submit.
Starting cron.

Mon Apr 22 21:09:23 UTC 2024
/usr/local/etc/pot/flavours/mariadb-galera.sh -> /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/tmp/mariadb-galera.sh
=====>  Executing mariadb-galera script on mariadb-galera-amd64-14_0
WARNING /var/log/cook.log already exists
Step 1: Bootstrap package repo
pkg already bootstrapped at /usr/local/sbin/pkg
Step 2: Touch /etc/rc.conf
Step 3: Remove ifconfig_epair0b from config
Step 4: Disable sendmail
sendmail disabled in /etc/rc.conf
sendmail_submit disabled in /etc/rc.conf
sendmail_msp_queue disabled in /etc/rc.conf
Step 5: Create /usr/local/etc/rc.d
Step 6: Install package consul
Updating FreeBSD repository catalogue...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] Fetching data.pkg: .......... done
Processing entries: .......... done
FreeBSD repository update completed. 34050 packages processed.
All repositories are up to date.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pkg: 1.21.1 -> 1.21.2

Number of packages to be upgraded: 1

12 MiB to be downloaded.
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching pkg-1.21.2.pkg: .......... done
Checking integrity... done (0 conflicting)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Upgrading pkg from 1.21.1 to 1.21.2...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting pkg-1.21.2: .......... done
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	consul: 1.18.1_1

Number of packages to be installed: 1

The process will require 121 MiB more space.
24 MiB to be downloaded.
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching consul-1.18.1_1.pkg: .......... done
Checking integrity... done (0 conflicting)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Installing consul-1.18.1_1...
===> Creating groups.
Creating group 'consul' with gid '469'.
===> Creating users
Creating user 'consul' with uid '469'.
===> Creating homedir(s)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting consul-1.18.1_1: ..... done
Step 7: Install package openssl
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	openssl: 3.0.13_2,1 -> 3.0.13_3,1

Number of packages to be upgraded: 1

6 MiB to be downloaded.
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching openssl-3.0.13_3,1.pkg: .......... done
Checking integrity... done (0 conflicting)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Upgrading openssl from 3.0.13_2,1 to 3.0.13_3,1...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting openssl-3.0.13_3,1: .......... done
Step 8: Install package sudo
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 9: Install package ca_root_nss
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 10: Install package curl
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 11: Install package jq
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 12: Install package jo
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 13: Install package nano
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 14: Install package bash
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 15: Install package rsync
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 16: Install package mariadb106-server
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 9 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	boost-libs: 1.84.0
	galera26: 26.4.16_2
	icu: 74.2_1,1
	libedit: 3.1.20230828_1,1
	libxml2: 2.11.7
	mariadb106-client: 10.6.17
	mariadb106-server: 10.6.17
	pcre2: 10.43
	unixODBC: 2.3.12_1

Number of packages to be installed: 9

The process will require 545 MiB more space.
79 MiB to be downloaded.
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/9] Fetching libxml2-2.11.7.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [2/9] Fetching libedit-3.1.20230828_1,1.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [3/9] Fetching icu-74.2_1,1.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [4/9] Fetching galera26-26.4.16_2.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [5/9] Fetching boost-libs-1.84.0.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [6/9] Fetching mariadb106-client-10.6.17.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [7/9] Fetching pcre2-10.43.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [8/9] Fetching mariadb106-server-10.6.17.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [9/9] Fetching unixODBC-2.3.12_1.pkg: .......... done
Checking integrity... done (0 conflicting)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/9] Installing icu-74.2_1,1...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/9] Extracting icu-74.2_1,1: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [2/9] Installing libedit-3.1.20230828_1,1...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [2/9] Extracting libedit-3.1.20230828_1,1: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [3/9] Installing boost-libs-1.84.0...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [3/9] Extracting boost-libs-1.84.0: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [4/9] Installing pcre2-10.43...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [4/9] Extracting pcre2-10.43: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [5/9] Installing libxml2-2.11.7...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [5/9] Extracting libxml2-2.11.7: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [6/9] Installing galera26-26.4.16_2...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [6/9] Extracting galera26-26.4.16_2: ....... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [7/9] Installing mariadb106-client-10.6.17...
===> Creating groups.
Creating group 'mysql' with gid '88'.
===> Creating users
Creating user 'mysql' with uid '88'.
===> Creating homedir(s)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [7/9] Extracting mariadb106-client-10.6.17: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [8/9] Installing unixODBC-2.3.12_1...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [8/9] Extracting unixODBC-2.3.12_1: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [9/9] Installing mariadb106-server-10.6.17...
===> Creating groups.
Using existing group 'mysql'.
===> Creating users
Using existing user 'mysql'.
===> Creating homedir(s)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [9/9] Extracting mariadb106-server-10.6.17: .......... done
=====
Message from boost-libs-1.84.0:

--
You have built the Boost library with thread support.

Don't forget to add -pthread to your linker options when
linking your code.
=====
Message from galera26-26.4.16_2:

--
Find the Galera Cluster documentation at
https://galeracluster.com/library/documentation/index.html
=====
Message from mariadb106-client-10.6.17:

--
MariaDB respects hier(7) and doesn't check /etc and /etc/mysql for
my.cnf. Please move existing my.cnf files from those paths to
/usr/local/etc/mysql or /usr/local/etc. Sample
configuration files are provided in /usr/local/etc/mysql
and /usr/local/etc/mysql/conf.d.
The rc(8) script no longer uses /var/db/mysql/my.cnf for configuration
nor /var/db/mysql for logs and PID-file.

This port does NOT include the mytop perl script, this is included in
the MariaDB tarball but the most recent version can be found in the
databases/mytop port

%%WSREP%%Using wsrep clustering requires adding a configuration file.
%%WSREP%%Copy /usr/local/etc/mysql/conf.d/wsrep.conf.sample to
%%WSREP%%/usr/local/etc/mysql/conf.d/wsrep.conf and change what you need there.
=====
Message from mariadb106-server-10.6.17:

--
MariaDB respects hier(7) and doesn't check /etc and /etc/mysql for
my.cnf. Please move existing my.cnf files from those paths to
/usr/local/etc/mysql or /usr/local/etc. Sample
configuration files are provided in /usr/local/etc/mysql
and /usr/local/etc/mysql/conf.d.
The rc(8) script no longer uses /var/db/mysql/my.cnf for configuration
nor /var/db/mysql for logs and PID-file.

This port does NOT include the mytop perl script, this is included in
the MariaDB tarball but the most recent version can be found in the
databases/mytop port

Using wsrep clustering requires adding a configuration file.
Copy /usr/local/etc/mysql/conf.d/wsrep.conf.sample to
/usr/local/etc/mysql/conf.d/wsrep.conf and change what you need there.
Step 17: Install package mariadb106-client
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 18: Install package galera26
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
Step 19: Install package node_exporter
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	node_exporter: 1.6.1_4

Number of packages to be installed: 1

The process will require 11 MiB more space.
4 MiB to be downloaded.
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching node_exporter-1.6.1_4.pkg: .......... done
Checking integrity... done (0 conflicting)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Installing node_exporter-1.6.1_4...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting node_exporter-1.6.1_4: .......... done
=====
Message from node_exporter-1.6.1_4:

--
If upgrading from a version of node_exporter <0.15.0 you'll need to update any
custom command line flags that you may have set as it now requires a
double-dash (--flag) instead of a single dash (-flag).
The collector flags in 0.15.0 have now been replaced with individual boolean
flags and the -collector.procfs` and -collector.sysfs` flags have been renamed
to --path.procfs and --path.sysfs respectively.
Step 20: Install package mysqld_exporter
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	mysqld_exporter: 0.12.1_19

Number of packages to be installed: 1

The process will require 9 MiB more space.
3 MiB to be downloaded.
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching mysqld_exporter-0.12.1_19.pkg: .......... done
Checking integrity... done (0 conflicting)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Installing mysqld_exporter-0.12.1_19...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting mysqld_exporter-0.12.1_19: ..... done
Step 21: Install package syslog-ng
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 9 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	e2fsprogs-libuuid: 1.47.0
	glib: 2.80.0,2
	ivykis: 0.43_1
	json-c: 0.17
	libffi: 3.4.4_1
	mpdecimal: 4.0.0
	py39-packaging: 23.2
	python39: 3.9.18_2
	syslog-ng: 4.6.0_2

Number of packages to be installed: 9

The process will require 151 MiB more space.
24 MiB to be downloaded.
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/9] Fetching ivykis-0.43_1.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [2/9] Fetching mpdecimal-4.0.0.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [3/9] Fetching python39-3.9.18_2.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [4/9] Fetching glib-2.80.0,2.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [5/9] Fetching syslog-ng-4.6.0_2.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [6/9] Fetching libffi-3.4.4_1.pkg: ......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [7/9] Fetching py39-packaging-23.2.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [8/9] Fetching json-c-0.17.pkg: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [9/9] Fetching e2fsprogs-libuuid-1.47.0.pkg: ....... done
Checking integrity... done (0 conflicting)
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/9] Installing mpdecimal-4.0.0...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [1/9] Extracting mpdecimal-4.0.0: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [2/9] Installing libffi-3.4.4_1...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [2/9] Extracting libffi-3.4.4_1: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [3/9] Installing python39-3.9.18_2...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [3/9] Extracting python39-3.9.18_2: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [4/9] Installing py39-packaging-23.2...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [4/9] Extracting py39-packaging-23.2: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [5/9] Installing ivykis-0.43_1...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [5/9] Extracting ivykis-0.43_1: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [6/9] Installing glib-2.80.0,2...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [6/9] Extracting glib-2.80.0,2: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [7/9] Installing json-c-0.17...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [7/9] Extracting json-c-0.17: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [8/9] Installing e2fsprogs-libuuid-1.47.0...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [8/9] Extracting e2fsprogs-libuuid-1.47.0: .......... done
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [9/9] Installing syslog-ng-4.6.0_2...
[mariadb-galera-amd64-14_0.vsf00002.cpt.za.honeyguide.net] [9/9] Extracting syslog-ng-4.6.0_2: .......... done
==> Running trigger: glib-schemas.ucl
Compiling glib schemas
No schema files found: doing nothing.
==> Running trigger: gio-modules.ucl
Generating GIO modules cache
=====
Message from python39-3.9.18_2:

--
Note that some standard Python modules are provided as separate ports
as they require additional dependencies. They are available as:

py39-gdbm       databases/py-gdbm@py39
py39-sqlite3    databases/py-sqlite3@py39
py39-tkinter    x11-toolkits/py-tkinter@py39
=====
Message from syslog-ng-4.6.0_2:

--
syslog-ng is now installed!  To replace FreeBSD's standard syslogd
(/usr/sbin/syslogd), complete these steps:

1. Create a configuration file named /usr/local/etc/syslog-ng.conf
   (a sample named syslog-ng.conf.sample has been included in
   /usr/local/etc). Note that this is a change in 2.0.2
   version, previous ones put the config file in
   /usr/local/etc/syslog-ng/syslog-ng.conf, so if this is an update
   move that file in the right place

2. Configure syslog-ng to start automatically by adding the following
   to /etc/rc.conf:

        syslog_ng_enable="YES"

3. Prevent the standard FreeBSD syslogd from starting automatically by
   adding a line to the end of your /etc/rc.conf file that reads:

        syslogd_enable="NO"

4. Shut down the standard FreeBSD syslogd:

     kill `cat /var/run/syslog.pid`

5. Start syslog-ng:

     /usr/local/etc/rc.d/syslog-ng start
Step 22: Clean package installation
The following package files will be deleted:
	/var/cache/pkg/openssl-3.0.13_2,1.pkg
	/var/cache/pkg/openssl-3.0.13_2,1~9d9aca70ca.pkg
The cleanup will free 6 MiB
Deleting files: .. done
Step 23: Create mysql directory
Step 24: Clean cook artifacts
Step 25: Install pot local
Step 26: Set file ownership on cook scripts
Step 27: Make cook script executable
setting executable bit on /usr/local/bin/cook
Step 28: Create rc.d script to start cook
creating rc.d script to start cook
Step 29: Make rc.d script to start cook executable
Setting executable bit on cook rc file
Step 30: Enable cook service
enabling cook
cook enabled in /etc/rc.conf
=====>  Stop the pot mariadb-galera-amd64-14_0
=====>  Remove p46626d20290 epair network interfaces
=====>  unmount /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/tmp
=====>  unmount /mnt/srv/pot/jails/mariadb-galera-amd64-14_0/m/dev
===>  exporting mariadb-galera-amd64-14_0 @ 1713820266 to /tmp/mariadb-galera-amd64-14_0_0.7.1.xz

MariaDB (Galera Cluster)