Overview

This is a development flavour containing rsync and ssh, along with scripts to backup minio buckets, or database servers.

You probably want to adjust this flavour and rebuild your own pot image for your own systems.

Installation

Create a ZFS data set on the parent system beforehand, for example: zfs create -o mountpoint=/mnt/jaildata/remoter zroot/jaildata/remoter
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> -d /mnt/jaildata/remoter -m /mnt
Mandatory copy in SSH authorized_keys file for the SSHUSER: pot copy-in -p <jailname> -s /path/to/authorized_keys -d /root/authorized_keys_in

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 servers>" \
 -E GOSSIPKEY=<32 byte Base64 key from consul keygen> \
 -E SSHUSER=<username to create for ssh access> \
 -E BUCKET=<minio bucket name> \
 -E BUCKETHOST=<minio IP> \
 -E BUCKETUSER=<minio user> \
 -E BUCKETPASS=<minio password> \
 -E DATABASE=<db name> \
 -E DBUSER=<database username> \
 -E DBPASS=<database password> \
 -E DBHOST=<IP database host> \
 [ -E SSHPORT=<change ssh port, default "22022"> ] \
 [ -E DBPORT=<non-standard postgresql port> ] \
 [ -E REMOTELOG=<IP of syslog-ng server> ]

Start the jail

Required Paramaters

The DATACENTER parameter defines a common datacenter.

The NODENAME parameter defines the name of this node.

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

The CONSULSERVERS parameter is a comma-deliminated list of IP addresses for the consul server or cluster. 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.5,10.0.0.6"

The GOSSIPKEY parameter is the gossip encryption key for consul agent. We’re using a default key if you do not set the parameter, do not use the default key for production encryption, instead provide your own.

The SSHUSER parameter is the name of the user to be created for ssh remote access. You must also copy in the user’s authorized_keys file to /root/authorized_keys_in. User scripts are expecting this.

BUCKET is the name of the minio bucket used in scripts.

BUCKETHOST is the hostname or IP of a minio instance.

BUCKETUSER and BUCKETPASS are the credentials for accessing the minio bucket.

DATABASE is the name of a postgresql database to backup.

DBUSER and DBPASS are the credentials for accessing the database.

DBHOST is the IP address of the postgresql host.

Optional Parameters

SSHPORT is for setting a different SSH port to 22022.

DBPORT is for setting a non-standard postgresql port. Default is

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

Usage

TBA

Persistent storage

To use persistent storage make sure to mount-in a pre-configured ZFS dataset to the applicable directory.

Getting Started

How To Use The Ready-Made Image

FreeBSD 14.2:
pot import -p remoter-amd64-14_2 -t 0.0.6 -U https://potluck.honeyguide.net/remoter

With Signify Verification:
fetch https://potluck.honeyguide.net/potluck.pub; pot import -p remoter-amd64-14_2 -t 0.0.6 -C potluck.pub -U https://potluck.honeyguide.net/remoter

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 remoter-amd64-14_2 -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/remoter 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.1) 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.0

Initiate remoter flavour, custom image for internal use
Fix typos
Fix user crontab additions
Adjust .pgpass permissions
Store only 3 days of postgresql backups
Create logs directory and update mirror scripts to log here
Fix consul labels and set IP parameters, set 127.0.0.1 only for consul client_addr
Don’t overwrite existing authorized_keys file if exists These images were built on Sun Feb 16 13:27:36 UTC 2025

Manual Image Download Links

remoter-amd64-14_2_0.0.6.xz ( )
remoter-amd64-14_2_0.0.6.xz.skein ( ) remoter-amd64-14_2_0.0.6.xz.skein.sig ( ) remoter-amd64-14_2_0.0.6.xz.meta ( )

Jenkins Pot Creation Logs

remoter-amd64-14_2_0.0.6:


remoter/remoter:
copy-in -s /usr/local/etc/pot/flavours/remoter.d/local -d /root/.pot_local
remoter/remoter.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 "Enable SSH"
service sshd enable

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

step "Clean freebsd-update"
rm -rf /var/db/freebsd-update
mkdir -p /var/db/freebsd-update

# 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 tmux"
pkg install -y tmux

step "Install package node_exporter"
pkg install -y node_exporter

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

# set to 15 for now to match the postgresql version
step "Install package postgresql15-client"
pkg install -y postgresql15-client

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

step "Clean package installation"
pkg autoremove -y
pkg clean -ay

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

remoter/remoter+1:
remoter/remoter+1.sh:

remoter/remoter+2:
remoter/remoter+2.sh:

remoter/remoter+3:
remoter/remoter+3.sh:

remoter/remoter+4:
remoter/remoter+4.sh:
=====>  Create conf dir (/mnt/srv/pot/jails/remoter-amd64-14_2/conf)
=====>  Cloning freebsd-potluck-amd64-14_2_0_0_35 with snap 
=====>  clone zroot/srv/pot/jails/freebsd-potluck-amd64-14_2_0_0_35/m@1738782968 into zroot/srv/pot/jails/remoter-amd64-14_2/m
=====>  Flavour: fbsd-update
=====>  Starting remoter-amd64-14_2 pot for the initial bootstrap
=====>  mount /mnt/srv/pot/jails/remoter-amd64-14_2/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===>  Starting the pot remoter-amd64-14_2
=====>  Pot remoter-amd64-14_2 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=remoter-amd64-14_2 host.hostname=remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net osrelease=14.2-RELEASE-p1 path=/mnt/srv/pot/jails/remoter-amd64-14_2/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:a4:23:2c:52: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.

Sun Feb 16 13:25:30 UTC 2025
/usr/local/etc/pot/flavours/fbsd-update.sh -> /mnt/srv/pot/jails/remoter-amd64-14_2/m/tmp/fbsd-update.sh
=====>  Executing fbsd-update script on remoter-amd64-14_2
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching public key from update1.freebsd.org... done.
Fetching metadata signature for 14.2-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata files... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 14.2-RELEASE-p1.
No updates are available to install.
=====>  Stop the pot remoter-amd64-14_2
=====>  Remove p467b1e7492b47 epair network interfaces
=====>  unmount /mnt/srv/pot/jails/remoter-amd64-14_2/m/tmp
=====>  unmount /mnt/srv/pot/jails/remoter-amd64-14_2/m/dev
=====>  Flavour: remoter
=====>  Executing remoter pot commands on remoter-amd64-14_2
=====>  mount /mnt/srv/pot/jails/remoter-amd64-14_2/m/tmp
=====>  Source /usr/local/etc/pot/flavours/remoter.d/local copied in the pot remoter-amd64-14_2
=====>  unmount /mnt/srv/pot/jails/remoter-amd64-14_2/m/tmp
=====>  /mnt/srv/pot/jails/remoter-amd64-14_2/m/dev is already unmounted
=====>  Starting remoter-amd64-14_2 pot for the initial bootstrap
=====>  mount /mnt/srv/pot/jails/remoter-amd64-14_2/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===>  Starting the pot remoter-amd64-14_2
=====>  Pot remoter-amd64-14_2 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=remoter-amd64-14_2 host.hostname=remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net osrelease=14.2-RELEASE-p1 path=/mnt/srv/pot/jails/remoter-amd64-14_2/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:96:e2:97:3a: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.

Sun Feb 16 13:25:36 UTC 2025
/usr/local/etc/pot/flavours/remoter.sh -> /mnt/srv/pot/jails/remoter-amd64-14_2/m/tmp/remoter.sh
=====>  Executing remoter script on remoter-amd64-14_2
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: Enable SSH
sshd enabled in /etc/rc.conf
Step 6: Create /usr/local/etc/rc.d
Step 7: Clean freebsd-update
Step 8: Install package consul
Updating FreeBSD repository catalogue...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] Fetching data.pkg: .......... done
Processing entries: .......... done
FreeBSD repository update completed. 35857 packages processed.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	consul: 1.20.1_1

Number of packages to be installed: 1

The process will require 121 MiB more space.
24 MiB to be downloaded.
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching consul-1.20.1_1.pkg: .......... done
Checking integrity... done (0 conflicting)
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Installing consul-1.20.1_1...
===> Creating groups
Creating group 'consul' with gid '469'
===> Creating users
Creating user 'consul' with uid '469'
===> Creating homedir(s)
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting consul-1.20.1_1: ..... done
Step 9: Install package openssl
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 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 11: 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 12: 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 13: 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 14: 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 15: 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 16: 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 17: 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 18: Install package tmux
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 3 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	libevent: 2.1.12
	ncurses: 6.5
	tmux: 3.5a

Number of packages to be installed: 3

The process will require 7 MiB more space.
2 MiB to be downloaded.
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/3] Fetching ncurses-6.5.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [2/3] Fetching libevent-2.1.12.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [3/3] Fetching tmux-3.5a.pkg: .......... done
Checking integrity... done (0 conflicting)
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/3] Installing ncurses-6.5...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/3] Extracting ncurses-6.5: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [2/3] Installing libevent-2.1.12...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [2/3] Extracting libevent-2.1.12: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [3/3] Installing tmux-3.5a...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [3/3] Extracting tmux-3.5a: .......... done
=====
Message from ncurses-6.5:

--
To get the terminfo database please install the terminfo-db package:
pkg install terminfo-db
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.8.2

Number of packages to be installed: 1

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

--
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 minio-client
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:
	minio-client: 2024.01.31.08.59.40_1

Number of packages to be installed: 1

The process will require 26 MiB more space.
8 MiB to be downloaded.
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching minio-client-2024.01.31.08.59.40_1.pkg: .......... done
Checking integrity... done (0 conflicting)
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Installing minio-client-2024.01.31.08.59.40_1...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting minio-client-2024.01.31.08.59.40_1: .... done
Step 21: Install package postgresql15-client
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:
	postgresql15-client: 15.10

Number of packages to be installed: 1

The process will require 14 MiB more space.
3 MiB to be downloaded.
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching postgresql15-client-15.10.pkg: .......... done
Checking integrity... done (0 conflicting)
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Installing postgresql15-client-15.10...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting postgresql15-client-15.10: .......... done
=====
Message from postgresql15-client-15.10:

--
The PostgreSQL port has a collection of "side orders":

postgresql-docs
  For all of the html documentation

p5-Pg
  A perl5 API for client access to PostgreSQL databases.

postgresql-tcltk
  If you want tcl/tk client support.

postgresql-jdbc
  For Java JDBC support.

postgresql-odbc
  For client access from unix applications using ODBC as access
  method. Not needed to access unix PostgreSQL servers from Win32
  using ODBC. See below.

ruby-postgres, py-psycopg2
  For client access to PostgreSQL databases using the ruby & python
  languages.

postgresql-plperl, postgresql-pltcl & postgresql-plruby
  For using perl5, tcl & ruby as procedural languages.

postgresql-contrib
  Lots of contributed utilities, postgresql functions and
  datatypes. There you find pg_standby, pgcrypto and many other cool
  things.

etc...
Step 22: Install package syslog-ng
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 10 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	e2fsprogs-libuuid: 1.47.1
	glib: 2.80.5_1,2
	ivykis: 0.43.2
	json-c: 0.18
	libffi: 3.4.6
	mpdecimal: 4.0.0
	pcre2: 10.43
	py311-packaging: 24.2
	python311: 3.11.11
	syslog-ng: 4.8.1_3

Number of packages to be installed: 10

The process will require 242 MiB more space.
34 MiB to be downloaded.
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/10] Fetching ivykis-0.43.2.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [2/10] Fetching mpdecimal-4.0.0.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [3/10] Fetching py311-packaging-24.2.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [4/10] Fetching glib-2.80.5_1,2.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [5/10] Fetching syslog-ng-4.8.1_3.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [6/10] Fetching pcre2-10.43.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [7/10] Fetching libffi-3.4.6.pkg: ........ done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [8/10] Fetching json-c-0.18.pkg: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [9/10] Fetching e2fsprogs-libuuid-1.47.1.pkg: ...... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [10/10] Fetching python311-3.11.11.pkg: .......... done
Checking integrity... done (0 conflicting)
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/10] Installing mpdecimal-4.0.0...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [1/10] Extracting mpdecimal-4.0.0: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [2/10] Installing libffi-3.4.6...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [2/10] Extracting libffi-3.4.6: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [3/10] Installing python311-3.11.11...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [3/10] Extracting python311-3.11.11: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [4/10] Installing py311-packaging-24.2...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [4/10] Extracting py311-packaging-24.2: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [5/10] Installing pcre2-10.43...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [5/10] Extracting pcre2-10.43: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [6/10] Installing ivykis-0.43.2...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [6/10] Extracting ivykis-0.43.2: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [7/10] Installing glib-2.80.5_1,2...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [7/10] Extracting glib-2.80.5_1,2: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [8/10] Installing json-c-0.18...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [8/10] Extracting json-c-0.18: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [9/10] Installing e2fsprogs-libuuid-1.47.1...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [9/10] Extracting e2fsprogs-libuuid-1.47.1: .......... done
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [10/10] Installing syslog-ng-4.8.1_3...
[remoter-amd64-14_2.vsf00002.cpt.za.honeyguide.net] [10/10] Extracting syslog-ng-4.8.1_3: .......... 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 python311-3.11.11:

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

py311-gdbm       databases/py-gdbm@py311
py311-sqlite3    databases/py-sqlite3@py311
py311-tkinter    x11-toolkits/py-tkinter@py311
=====
Message from syslog-ng-4.8.1_3:

--
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 23: Clean package installation
Checking integrity... done (0 conflicting)
Nothing to do.
The following package files will be deleted:
	/var/cache/pkg/ncurses-6.5~5a359a830a.pkg
	/var/cache/pkg/ivykis-0.43.2~e381e68815.pkg
	/var/cache/pkg/tmux-3.5a~674adee29b.pkg
	/var/cache/pkg/pcre2-10.43~e5653d2442.pkg
	/var/cache/pkg/postgresql15-client-15.10~70f3271a9d.pkg
	/var/cache/pkg/libffi-3.4.6~d0bebafdbe.pkg
	/var/cache/pkg/glib-2.80.5_1,2.pkg
	/var/cache/pkg/py311-packaging-24.2~049f6d278b.pkg
	/var/cache/pkg/minio-client-2024.01.31.08.59.40_1.pkg
	/var/cache/pkg/pcre2-10.43.pkg
	/var/cache/pkg/consul-1.20.1_1~dd20a71df2.pkg
	/var/cache/pkg/postgresql15-client-15.10.pkg
	/var/cache/pkg/node_exporter-1.8.2.pkg
	/var/cache/pkg/json-c-0.18.pkg
	/var/cache/pkg/libffi-3.4.6.pkg
	/var/cache/pkg/json-c-0.18~e0185782a1.pkg
	/var/cache/pkg/python311-3.11.11~cf05ce6c94.pkg
	/var/cache/pkg/e2fsprogs-libuuid-1.47.1~54f5a5cbea.pkg
	/var/cache/pkg/syslog-ng-4.8.1_3.pkg
	/var/cache/pkg/python311-3.11.11.pkg
	/var/cache/pkg/tmux-3.5a.pkg
	/var/cache/pkg/syslog-ng-4.8.1_3~fdb5fe92df.pkg
	/var/cache/pkg/consul-1.20.1_1.pkg
	/var/cache/pkg/libevent-2.1.12~040769e3d0.pkg
	/var/cache/pkg/libevent-2.1.12.pkg
	/var/cache/pkg/mpdecimal-4.0.0~c4b382f64c.pkg
	/var/cache/pkg/ivykis-0.43.2.pkg
	/var/cache/pkg/node_exporter-1.8.2~65f7bfe5a8.pkg
	/var/cache/pkg/ncurses-6.5.pkg
	/var/cache/pkg/py311-packaging-24.2.pkg
	/var/cache/pkg/glib-2.80.5_1,2~da836b96ab.pkg
	/var/cache/pkg/e2fsprogs-libuuid-1.47.1.pkg
	/var/cache/pkg/mpdecimal-4.0.0.pkg
	/var/cache/pkg/minio-client-2024.01.31.08.59.40_1~0dd75d7736.pkg
The cleanup will free 74 MiB
Deleting files: .......... done
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 remoter-amd64-14_2
=====>  Remove p467b1e74f2b47 epair network interfaces
=====>  unmount /mnt/srv/pot/jails/remoter-amd64-14_2/m/tmp
=====>  unmount /mnt/srv/pot/jails/remoter-amd64-14_2/m/dev
===>  exporting remoter-amd64-14_2 @ 1739712383 to /tmp/remoter-amd64-14_2_0.0.6.xz

Remoter