Overview
This is a mega-flavour containing the prometheus
time series database, alertmanager
alert notification queue, loki
log monitoring, promtail
log ingestor, and grafana
viewer with custom dashboards.
The flavour includes a local consul
agent instance to be available that it can connect to (see configuration below). You can e.g. use the consul pot
flavour on this site to run consul
. You can also connect to this host and service consul restart
manually.
Installation
- Create a ZFS data set on the parent system beforehand
zfs create -o mountpoint=/mnt/beastdata zroot/beastdata
- 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 /mnt -d /mnt/beastdata
- Optionally export the ports after creating the jail:
pot export-ports -p <jailname> -e 3100:3100 -e 3000:3000
- 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=<consul IP address(es) in comma-deliminated format> \ -E GOSSIPKEY=<32 byte Base64 key from consul keygen>] \ -E GRAFANAUSER=<grafana username> \ -E GRAFANAPASSWORD=<grafana password> \ -E SCRAPECONSUL=<consul IP address(es) in comma-deliminated format> \ -E SCRAPENOMAD=<nomad IP address(es) in comma-deliminated format> \ -E TRAEFIKSERVER=<ip:port of traefik-consul instances in comma-deliminated format> \ -E SMTPHOSTPORT="10.0.0.2:25" \ -E SMTPFROM=<from email address> \ -E ALERTADDRESS=<to email address> \ [ -E SMTPUSER=<smtp auth username> -E SMTPPASS=<smtp auth password> ]
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 defines the consul server instances, from one to five IP addresses in comma-deliminated format and no spaces.
-E CONSULSERVERS="10.0.0.1,10.0.0.2,10.0.0.3,10.0.0.4,10.0.0.5"
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 GRAFANAUSER and GRAFANAPASSWORD parameters are to set a custom user/pass for Grafana.
The SCRAPECONSUL parameter is a comma-deliminated list of consul servers to scrape data from. Metrics must be configured in consul.
-E SCRAPECONSUL="10.0.0.1,10.0.0.2,10.0.0.3,10.0.0.4,10.0.0.5"
The SCRAPENOMAD parameter is a comma-deliminated list of nomad servers to scrape data from. Metrics must be configured in nomad.
-E SCRAPENOMAD="10.0.0.1,10.0.0.2,10.0.0.3,10.0.0.4,10.0.0.5"
The TRAEFIKSERVER parameter is comma-deliminated list of IP:port of traefik-consul
instances to scrape metrics from. They must be setup with a metrics endpoint.
-E TRAEFIKSERVER="10.0.0.1:8082,10.0.0.2:8082"
The SMTPHOSTPORT parameter is the IP address and port of the mail server to use when sending alerts.
The SMTPFROM parameter is the from address of the account sending alerts via mail.
The ALERTADDRESS parameter is the destination address for alerts.
Optional Parameters
The SMTPUSER and SMTPPASS parameters are credentials for smtp auth.
Loki Explanation
There are several components to having a searchable log-ingestor:
1. Remote syslog server accepting incoming logs
syslogd
is configured to accept syslog on UDP port 514 from hosts in the specified subnet, and save all to /mnt/logs/central.log
.
Remote hosts have their syslog.conf configured to send logs to this host.
This is a very broad and blunt approach, where syslog-ng
may be a preferred approach with wildcard capabilities and multiple files.
2. Promtail log parsing and labelling
promtail
is configured as a service and monitors /mnt/logs/central.log
for data to ingest and label, before submitting to loki
.
3. Loki data source
loki
is configured as a service and ingests data-with-labels, and makes available for query purposes.
4. Grafana with “search logs” dashboard
grafana
is a viewer for the data in the loki
data source. A separate grafana
flavour must be configured with loki
as a data source to view captured logs.
Usage
Access grafana dashboards at http://yourhost:3000
and choose from various dashboards, or access loki
logs via the search logs
dashboard.
Access prometheus
at http://yourhost:9090
.
Access alertmanager
at http://yourhost:9093
.
Dynamic inventory for scrape targets
File-based scrape targets are configured for the following files, which you can copy in replacements for, or update on the system.
(assumes persistent storage mounted in)
- /mnt/prometheus/targets.d/blackboxhttpget.yml
- /mnt/prometheus/targets.d/blackboxicmp.yml
- /mnt/prometheus/targets.d/blackboxtcpconnect.yml
- /mnt/prometheus/targets.d/mytargets.yml
- /mnt/prometheus/targets.d/postgres.yml
- /mnt/prometheus/targets.d/minio.yml
- /mnt/prometheus/targets.d/redis.yml
These files need to in the format:
- targets:
- <ip>:<port>
labels:
job: jobtype1
Reload prometheus when changing the files in /mnt/prometheus/targets.d/ for targets to take effect.
Scaping blackbox_exporter hosts
The targets files for blackbox_exporter
hosts has a slightly different format, for example http_2xx
hosts can be added to blackboxhttpget.yml
in the following format
########################################################
# <BLACKBOX_EXPORTER_IP_PORT>:_:<JOB>:_:<TARGET_URL> #
########################################################
# Only one destination per target
- targets:
- 1.2.3.4:9115:_:prometheusio:_:https://prometheus.io
Whereas ICMP monitoring can be done in blackboxicmp.yml
in the format
########################################################
# <BLACKBOX_EXPORTER_IP_PORT>:_:<JOB>:_:<TARGET_URL> #
########################################################
# Only one destination per target
- targets:
- 1.2.3.4:9115:_:icmp-10-0-0-1:_:10.0.0.1
Reload prometheus when changing the files in /mnt/prometheus/targets.d/ for targets to take effect.
Note: for every target only a single test can be performed. This is split over multiple jobs for http_2xx
, icmp
and tcp_connect
. WIP for others.
Scraping minio metrics
This image is setup with the assumption of a self-signed certificate for minio, and env MINIO_PROMETHEUS_AUTH_TYPE=public
configured on minio start.
Test metrics scraping with curl -k https://your-minio-host:9000/minio/v2/metrics/cluster
and if successful, add targets to the file /mnt/prometheus/targets.d/minio.yml
in the format:
- targets:
- your-minio-host:9000
- your-other-minio:9000
labels:
job: minio
If you require authentication, you can adjust the minio
scrape job in the file /usr/local/etc/prometheus.yml
, via external script, after image boot and with a reload of prometheus
, to include the relevant token option and optional SSL config.
Persistent storage
Persistent storage will be in the ZFS dataset zroot/beastdata, available inside the image at /mnt
If you stop the image, the data will still exist, and a new image can be started up and still use it.
If you need to change the directory parameters for the ZFS dataset, adjust the mount-in
command accordingly for the source directory as mounted by the parent OS.
Do not adjust the image destination mount point at /mnt because the included applications are configured to use this directory for data.
Client-side syslog-ng configuration
Please see the included file client-syslog-ng.conf.sample
and configure:
%%config_version%%
is the syslog-ng config version in X.YY (not X.YY.Z). You can extract a suitable value to update in scripts using:
/usr/local/sbin/syslog-ng --version | grep '^Config version:' | awk -F: '{ print \$2 }' | xargs
%%remotelogip%%
is the IP address of the Beast of Argh pot jail.
Update manually or via sed
in scripts.
Alertmanager Silences
Some alerts will trigger automatically.
For example, if there is no Mariadb Galera cluster, there will be an alert about the Galera cluster not being ready.
Add a silence to this alert with an expiry of 52 weeks, and leave a comment of 52 weeks. Then do it again in a year.
There is also a Dead Man’s Switch alert, which needs to be silenced in a similar manner.
The purpose of this alert is to verify processes are functioning correctly for alerting and response.
Out of memory alerts may also crop up and can be silenced for a few weeks. Pot jails can utilise most of the memory allocated to them, and this will trigger an alert. However everything will be functioning normally.
It’s useful to leave a comment with the delay time set.
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.1:
pot import -p beast-of-argh-amd64-14_1 -t 0.22.3 -U https://potluck.honeyguide.net/beast-of-argh
With Signify Verification:
fetch https://potluck.honeyguide.net/potluck.pub; pot import -p beast-of-argh-amd64-14_1 -t 0.22.3 -C potluck.pub -U https://potluck.honeyguide.net/beast-of-argh
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 beast-of-argh-amd64-14_1 -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/beast-of-argh 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.22
- Version bump for new base image
- Enable milliseconds in syslog-ng for all log timestamps
- Update syslog-ng config to use modern config options
0.21
- Version bump for new base image
- Adjust grafana cookie samesite parameter from none to disabled to avoid login loop
0.20
- Version bump for new base image
0.19
- Version bump for new base image
0.18
- Version bump for new base image
0.17
- Version bump for new base image
- Minor updates to match loki updates
0.16
- Switch to using pkg sources for grafana loki and promtail install
- Update loki config
- Add directory for promtail positions
- Adjust syslog-ng to save remote log files with group read permissions
- Remove invalid loki and promtail sysrc entries not present in pkg install grafana-loki
- Change syslog-ng file save perms under options not destination
- Correctly set syslog-ng remote logs permissions instead of global option
- Even more correctly set permissions 0644 on remote logs files
0.15
- Version bump for new base image
- Implement grafana change to unset timezone value, from PR45
0.14
- Version bump for new base image
- Loki 2.9.7, Promtail 2.9.7
- Fix node_exporter zfs issue
- Fix copy-in missing vault dashboard, not in use here
- Adjust prometheus memory alert to less than 1% only
- Loki 2.9.8, Promtail 2.9.8
- Add blackbox scraper to prometheus
- Adjust json files for grafana charts to set null id
- Adjust blackbox exporter config and sample targets file
- Split blackbox exporter into multiple jobs for http_2xx, icmp and tcp_connect
- Switch to grafana10 in the grafana package
0.13
- Version bump for new base image
- FBSD14 base image
- Loki 2.9.5, Promtail 2.9.5
- Adjust install method for loki and promtail due to errors with old way
- Add unzip to packages
0.12
- Version bump for new base image
- Update loki and promtail versions
- Specify port in postgres.yml for prometheus monitoring
- Remove noisy low usage postgres alerts
- Add redis config to prometheus
- Update loki and promtail version to latest
- Add redis dashboard
- Fix alert metric and loki path
- Update loki and promtail versions
0.11
- Version bump for new base image
0.10
- Version bump for new base image
- New loki and promtail versions 2.9.1
0.9
- Version bump for new base image
- New loki and promtail
- Start syslog-ng last
- Add SVG logo
- Link to PNG logo in README as SVG not working
0.8
- Version bump for new base image
0.7
- Version bump for new base image
- Upgrade to grafana9
- Remove old nomad dashboards, replace with hashicorp one
- Tweak titles in dashboards
- Fixup nomad dashboard
- Fix syslog-ng problems for 4.2 version, remove stats_freq option
- Add local unbound for consul DNS resolution
- Update to Loki 2.8.3 and Promtail 2.8.3
- Add services to consul setup
- Fix addition of services
- Add consul DNS info to README
- Fix JSON consul agent config for multiple services
- Adjust local_unbound resolution problems
- Another approach to local_unbound resolution problems
- Disable consul DNS option with local_unbound as is only practical in VNET jails with a localhost
- Loki config updates, set localhost options to jail IP, as failing in VNET jails
- Set prometheus consul sd config to use 127.0.0.1
- Update prometheus alerts to fix broken alerts
- Update README with info on silences
- Adjust out of memory alert to trigger if less than 5% available
- Update Loki and Promtail to 2.8.4 versions
- Addressing potential errors causing hangs during orchestration scripts, start syslog-ng later
0.6
- Version bump for new base image
- New versions of loki and promtail
- Update checklist
0.5
- Version bump for new base image
- Signified
- Fix nologin shell for nodeexport user
- Fix nologin shell for loki user
0.4
- Version bump for new feature
- Pass in consul servers and scrape lists in comma-deliminated format
- Update logo
0.3
- Version bump for new base image
- Update syslog-ng.conf stats_freq(0); -> stats(freq(0));
- Tweak consul agent json to remove quotes for consul servers list
0.2
- Version bump for new base image
- Update loki and promtail to 2.7.3
- Set consul options for bind address
- Revert to consul json config file until consul fixed start with hcl
- Update loki and promtail to 2.7.5
- Update loki configuration file, permissions, sysrc entries
- Update grafana for grafana.ini and copy provisions dir from /usr/local/etc/grafana now
- Fix permissions on grafana.ini
- Update logs dashboard, replace nomad dashboards with newer ones
0.1
- Version bump for new base image
- New changelog format
- Grafana8 instead of Grafana7
0.0.29
- Fix consul client hcl for new format
0.0.28
- Version bump for rebuild to fix missing images on potluck site
0.0.27
- Version bump for p3 rebuild
0.0.26
- Adjusting minio dashboard in grafana to better working one
- Minio-supplied one is out of date
0.0.25
- Add minio.json to dashboards
0.0.24
- Version bump for rebuild and new version syslog-ng
- Added checklist
0.0.23
- Version bump for rebuild
0.0.22
- Updated to match cook changes and check for .env.cook
- Removed artifacts from combining several images into Beast
0.0.21
- Version bump for rebuild with new base image
0.0.20
- Version bump to build for FreeBSD-13.1
- Various formatting adjustments in earlier git PR but not version-bumped
0.0.19
- Add support for json logs, nginx, others
- Create /var/log/syslog-ng-disk-buffer/
- loki and promtail upgrade from 2.2.1 to 2.6.1 with adjusted config files
- Added a better all-in-one loki logs dashboard
0.0.18
- Added updated mysql dashboard to grafana default dashboards
0.0.17
- Added mysql dashboard to grafana default dashboards
0.0.16
- Scrape config for mysql/mariadb file-based-targets
0.0.15
- Minio additions for file-based-targets and documentation to enable metrics
0.0.14
- Avoid copying over existing files for file-based-targets
0.0.13
- Fixing broken indentation in prometheus.yml.in
0.0.12
- Adding scrape job for file-based targets in persistent storage to enable dynamic configuration
- Moved postgres scrape job to file-based target in persistent storage, and removed dbserver parameter
- Removed influxdb datasource from grafana for now
0.0.11
- Full path required for alert rules directory in prometheus.yml
- Using hard-coded mount-in persistant storage at /mnt
0.0.10
- Using different approach to disable syslogd
0.0.9
- Cleanup lingering artifacts from proxy services for TLS versions of images
0.0.8
- Removing syslogd central.log from loki, syslog-ng changes to promtail config weren’t updated
- Adding note that syslog-ng version must be 3.36 not 3.36.1
0.0.7
- Missing dashboards for grafana fail in running image, fixed by adding back
0.0.6
- Version increment for potbuilder build failure, retry
0.0.5
- Fixing grafana missing IP changes, failed to start
0.0.4
- Fixing formatting typo in README
0.0.3
- Switch to syslog-ng
0.0.2
- Updated to scrape traefik source
0.0.1
- First bash at the ‘Beast of Argh’, a single pot image with prometheus, alertmanager, loki, grafana, syslog server and more
These images were built on Wed Nov 6 20:56:35 UTC 2024
Manual Image Download Links
beast-of-argh-amd64-14_1_0.22.3.xz (
)
beast-of-argh-amd64-14_1_0.22.3.xz.skein (
)
beast-of-argh-amd64-14_1_0.22.3.xz.skein.sig (
)
beast-of-argh-amd64-14_1_0.22.3.xz.meta (
)
Jenkins Pot Creation Logs
beast-of-argh-amd64-14_1_0.22.3:
beast-of-argh/beast-of-argh:
copy-in -s /usr/local/etc/pot/flavours/beast-of-argh.d/local -d /root/.pot_local
beast-of-argh/beast-of-argh.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
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 node_exporter"
pkg install -y node_exporter
step "Install package prometheus"
pkg install -y prometheus
step "Install package alertmanager"
pkg install -y alertmanager
step "Install package grafana"
pkg install -y grafana
step "Install package grafana-loki"
pkg install -y grafana-loki
step "Install package nginx"
pkg install -y nginx
step "Install package syslog-ng"
pkg install -y syslog-ng
step "Install package unzip"
pkg install -y unzip
step "Clean package installation"
pkg clean -ay
### removed in favour of pkg install (2024-07-08)
## alternative approach as temporary measure (2024-03-03)
#step "Download loki release from github"
#fetch -qo /tmp/loki-freebsd-amd64.zip https://github.com/grafana/loki/releases/download/v2.9.8/loki-freebsd-amd64.zip
#
#step "Unzip loki"
#unzip -o -d /tmp /tmp/loki-freebsd-amd64.zip
#
#step "Validate loki checksum and install if valid"
#if [ "$(sha256 -q /tmp/loki-freebsd-amd64)" == "f4dc39f6eada4fde16617e1d9372c897d16cbbe136401732fb644fb8033278a6" ]; then
# cp -f /tmp/loki-freebsd-amd64 /usr/local/bin/loki
# chmod 755 /usr/local/bin/loki
# rm -rf /tmp/loki-freebsd-amd64.zip /tmp/loki-freebsd-amd64
#else
# exit_error "loki checksum mismatch!"
#fi
#
#step "Download promtail release from github"
#fetch -qo /tmp/promtail-freebsd-amd64.zip https://github.com/grafana/loki/releases/download/v2.9.8/promtail-freebsd-amd64.zip
#
#step "Unzip promtail"
#unzip -o -d /tmp /tmp/promtail-freebsd-amd64.zip
#
#step "Validate promtail checksum and install if valid"
#if [ "$(sha256 -q /tmp/promtail-freebsd-amd64)" == "9dcd257be09e4ab22208c819abbaa74782ddcb5cde1f5fbb4fabff938230eeca" ]; then
# cp -f /tmp/promtail-freebsd-amd64 /usr/local/bin/promtail
# chmod 755 /usr/local/bin/promtail
# rm -rf /tmp/promtail-freebsd-amd64.zip /tmp/promtail-freebsd-amd64
#else
# exit_error "promtail checksum mismatch!"
#fi
###
# -------------- 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
beast-of-argh/beast-of-argh+1:
beast-of-argh/beast-of-argh+1.sh:
beast-of-argh/beast-of-argh+2:
beast-of-argh/beast-of-argh+2.sh:
beast-of-argh/beast-of-argh+3:
beast-of-argh/beast-of-argh+3.sh:
beast-of-argh/beast-of-argh+4:
beast-of-argh/beast-of-argh+4.sh:
=====> Create conf dir (/mnt/srv/pot/jails/beast-of-argh-amd64-14_1/conf)
=====> Cloning freebsd-potluck-amd64-14_1_0_0_31 with snap
=====> clone zroot/srv/pot/jails/freebsd-potluck-amd64-14_1_0_0_31/m@1730306249 into zroot/srv/pot/jails/beast-of-argh-amd64-14_1/m
=====> Flavour: fbsd-update
=====> Starting beast-of-argh-amd64-14_1 pot for the initial bootstrap
=====> mount /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===> Starting the pot beast-of-argh-amd64-14_1
=====> Pot beast-of-argh-amd64-14_1 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=beast-of-argh-amd64-14_1 host.hostname=beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net osrelease=14.1-RELEASE-p6 path=/mnt/srv/pot/jails/beast-of-argh-amd64-14_1/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 /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:83:a8:6d:4e: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.
Wed Nov 6 20:51:22 UTC 2024
/usr/local/etc/pot/flavours/fbsd-update.sh -> /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/tmp/fbsd-update.sh
=====> Executing fbsd-update script on beast-of-argh-amd64-14_1
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.1-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.1-RELEASE-p6.
No updates are available to install.
=====> Stop the pot beast-of-argh-amd64-14_1
=====> Remove p4672bd6c916e0f epair network interfaces
=====> unmount /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/tmp
=====> unmount /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/dev
=====> Flavour: beast-of-argh
=====> Executing beast-of-argh pot commands on beast-of-argh-amd64-14_1
=====> mount /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/tmp
=====> Source /usr/local/etc/pot/flavours/beast-of-argh.d/local copied in the pot beast-of-argh-amd64-14_1
=====> unmount /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/tmp
=====> /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/dev is already unmounted
=====> Starting beast-of-argh-amd64-14_1 pot for the initial bootstrap
=====> mount /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===> Starting the pot beast-of-argh-amd64-14_1
=====> Pot beast-of-argh-amd64-14_1 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=beast-of-argh-amd64-14_1 host.hostname=beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net osrelease=14.1-RELEASE-p6 path=/mnt/srv/pot/jails/beast-of-argh-amd64-14_1/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 /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:a3:5c:e6:fa: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.
Wed Nov 6 20:51:55 UTC 2024
/usr/local/etc/pot/flavours/beast-of-argh.sh -> /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/tmp/beast-of-argh.sh
=====> Executing beast-of-argh script on beast-of-argh-amd64-14_1
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: Clean freebsd-update
Step 7: Install package consul
Updating FreeBSD repository catalogue...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] Fetching data.pkg: .......... done
Processing entries: .......... done
FreeBSD repository update completed. 35518 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.19.2
Number of packages to be installed: 1
The process will require 124 MiB more space.
24 MiB to be downloaded.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching consul-1.19.2.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Installing consul-1.19.2...
===> Creating groups
Creating group 'consul' with gid '469'
===> Creating users
Creating user 'consul' with uid '469'
===> Creating homedir(s)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting consul-1.19.2: ..... done
Step 8: 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 9: 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 10: 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 11: 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 12: 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 13: 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 14: 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 15: 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 16: 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 17: 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.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching node_exporter-1.8.2.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Installing node_exporter-1.8.2...
[beast-of-argh-amd64-14_1.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 18: Install package prometheus
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:
prometheus: 2.49.1_6
Number of packages to be installed: 1
The process will require 170 MiB more space.
36 MiB to be downloaded.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching prometheus-2.49.1_6.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Installing prometheus-2.49.1_6...
===> Creating groups
Creating group 'prometheus' with gid '478'
===> Creating users
Creating user 'prometheus' with uid '478'
===> Creating homedir(s)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting prometheus-2.49.1_6: .......... done
Step 19: Install package alertmanager
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:
alertmanager: 0.26.0_7
Number of packages to be installed: 1
The process will require 46 MiB more space.
13 MiB to be downloaded.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching alertmanager-0.26.0_7.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Installing alertmanager-0.26.0_7...
===> Creating groups
Creating group 'alertmanager' with gid '479'
===> Creating users
Creating user 'alertmanager' with uid '479'
===> Creating homedir(s)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting alertmanager-0.26.0_7: ....... done
Step 20: Install package grafana
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:
grafana: 10.4.5_1
Number of packages to be installed: 1
The process will require 356 MiB more space.
73 MiB to be downloaded.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching grafana-10.4.5_1.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Installing grafana-10.4.5_1...
===> Creating groups
Creating group 'grafana' with gid '904'
===> Creating users
Creating user 'grafana' with uid '904'
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting grafana-10.4.5_1: .......... done
Step 21: Install package grafana-loki
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:
grafana-loki: 2.9.2_9
Number of packages to be installed: 1
The process will require 237 MiB more space.
55 MiB to be downloaded.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching grafana-loki-2.9.2_9.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Installing grafana-loki-2.9.2_9...
===> Creating groups
Creating group 'loki' with gid '967'
Creating group 'promtail' with gid '968'
===> Creating users
Creating user 'loki' with uid '916'
===> Creating homedir(s)
Creating user 'promtail' with uid '816'
===> Creating homedir(s)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting grafana-loki-2.9.2_9: ........ done
Step 22: Install package nginx
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 2 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
nginx: 1.26.2_5,3
pcre2: 10.43
Number of packages to be installed: 2
The process will require 9 MiB more space.
2 MiB to be downloaded.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Fetching nginx-1.26.2_5,3.pkg: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/2] Fetching pcre2-10.43.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Installing pcre2-10.43...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Extracting pcre2-10.43: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/2] Installing nginx-1.26.2_5,3...
===> Creating groups
Using existing group 'www'
===> Creating users
Using existing user 'www'
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/2] Extracting nginx-1.26.2_5,3: .......... done
=====
Message from nginx-1.26.2_5,3:
--
Recent version of the NGINX introduces dynamic modules support. In
FreeBSD ports tree this feature was enabled by default with the DSO
knob. Several vendor's and third-party modules have been converted
to dynamic modules. Unset the DSO knob builds an NGINX without
dynamic modules support.
To load a module at runtime, include the new `load_module'
directive in the main context, specifying the path to the shared
object file for the module, enclosed in quotation marks. When you
reload the configuration or restart NGINX, the module is loaded in.
It is possible to specify a path relative to the source directory,
or a full path, please see
https://www.nginx.com/blog/dynamic-modules-nginx-1-9-11/ and
http://nginx.org/en/docs/ngx_core_module.html#load_module for
details.
Default path for the NGINX dynamic modules is
/usr/local/libexec/nginx.
Step 23: 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.1
glib: 2.80.5,2
ivykis: 0.43.2
json-c: 0.18
libffi: 3.4.6
mpdecimal: 4.0.0
py311-packaging: 24.1
python311: 3.11.10
syslog-ng: 4.8.0_2
Number of packages to be installed: 9
The process will require 234 MiB more space.
32 MiB to be downloaded.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/9] Fetching ivykis-0.43.2.pkg: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/9] Fetching mpdecimal-4.0.0.pkg: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/9] Fetching py311-packaging-24.1.pkg: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/9] Fetching glib-2.80.5,2.pkg: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/9] Fetching syslog-ng-4.8.0_2.pkg: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/9] Fetching libffi-3.4.6.pkg: ........ done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/9] Fetching json-c-0.18.pkg: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/9] Fetching e2fsprogs-libuuid-1.47.1.pkg: ....... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/9] Fetching python311-3.11.10.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/9] Installing mpdecimal-4.0.0...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/9] Extracting mpdecimal-4.0.0: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/9] Installing libffi-3.4.6...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/9] Extracting libffi-3.4.6: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/9] Installing python311-3.11.10...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/9] Extracting python311-3.11.10: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/9] Installing py311-packaging-24.1...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/9] Extracting py311-packaging-24.1: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/9] Installing ivykis-0.43.2...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/9] Extracting ivykis-0.43.2: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/9] Installing glib-2.80.5,2...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/9] Extracting glib-2.80.5,2: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/9] Installing json-c-0.18...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/9] Extracting json-c-0.18: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/9] Installing e2fsprogs-libuuid-1.47.1...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/9] Extracting e2fsprogs-libuuid-1.47.1: .......... done
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/9] Installing syslog-ng-4.8.0_2...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/9] Extracting syslog-ng-4.8.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 python311-3.11.10:
--
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.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 24: Install package unzip
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:
unzip: 6.0_8
Number of packages to be installed: 1
140 KiB to be downloaded.
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching unzip-6.0_8.pkg: .......... done
Checking integrity... done (0 conflicting)
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Installing unzip-6.0_8...
[beast-of-argh-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting unzip-6.0_8: .......... done
Step 25: Clean package installation
The following package files will be deleted:
/var/cache/pkg/unzip-6.0_8.pkg
/var/cache/pkg/alertmanager-0.26.0_7~95686b5f4d.pkg
/var/cache/pkg/e2fsprogs-libuuid-1.47.1~362f74ac69.pkg
/var/cache/pkg/grafana-loki-2.9.2_9.pkg
/var/cache/pkg/consul-1.19.2.pkg
/var/cache/pkg/py311-packaging-24.1.pkg
/var/cache/pkg/python311-3.11.10~286ca605ff.pkg
/var/cache/pkg/mpdecimal-4.0.0~355dbb0218.pkg
/var/cache/pkg/syslog-ng-4.8.0_2~cf5f9ee289.pkg
/var/cache/pkg/grafana-loki-2.9.2_9~4a476b1667.pkg
/var/cache/pkg/alertmanager-0.26.0_7.pkg
/var/cache/pkg/pcre2-10.43.pkg
/var/cache/pkg/grafana-10.4.5_1.pkg
/var/cache/pkg/json-c-0.18.pkg
/var/cache/pkg/prometheus-2.49.1_6~80fedc2edd.pkg
/var/cache/pkg/glib-2.80.5,2.pkg
/var/cache/pkg/node_exporter-1.8.2.pkg
/var/cache/pkg/nginx-1.26.2_5,3~339c37ca93.pkg
/var/cache/pkg/syslog-ng-4.8.0_2.pkg
/var/cache/pkg/json-c-0.18~4c2b04b9f9.pkg
/var/cache/pkg/unzip-6.0_8~deefcde1de.pkg
/var/cache/pkg/e2fsprogs-libuuid-1.47.1.pkg
/var/cache/pkg/pcre2-10.43~d476f63222.pkg
/var/cache/pkg/python311-3.11.10.pkg
/var/cache/pkg/ivykis-0.43.2.pkg
/var/cache/pkg/glib-2.80.5,2~909ca79520.pkg
/var/cache/pkg/prometheus-2.49.1_6.pkg
/var/cache/pkg/ivykis-0.43.2~07934ae53e.pkg
/var/cache/pkg/node_exporter-1.8.2~d3c8df78fe.pkg
/var/cache/pkg/libffi-3.4.6~e038c4b1cf.pkg
/var/cache/pkg/grafana-10.4.5_1~63685caf5e.pkg
/var/cache/pkg/mpdecimal-4.0.0.pkg
/var/cache/pkg/nginx-1.26.2_5,3.pkg
/var/cache/pkg/py311-packaging-24.1~b3b408ec53.pkg
/var/cache/pkg/libffi-3.4.6.pkg
/var/cache/pkg/consul-1.19.2~ffcc2d4893.pkg
The cleanup will free 239 MiB
Deleting files: .......... done
Step 26: Clean cook artifacts
Step 27: Install pot local
Step 28: Set file ownership on cook scripts
Step 29: Make cook script executable
setting executable bit on /usr/local/bin/cook
Step 30: Create rc.d script to start cook
creating rc.d script to start cook
Step 31: Make rc.d script to start cook executable
Setting executable bit on cook rc file
Step 32: Enable cook service
enabling cook
cook enabled in /etc/rc.conf
=====> Stop the pot beast-of-argh-amd64-14_1
=====> Remove p4672bd6eb16e0f epair network interfaces
=====> unmount /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/tmp
=====> unmount /mnt/srv/pot/jails/beast-of-argh-amd64-14_1/m/dev
===> exporting beast-of-argh-amd64-14_1 @ 1730926416 to /tmp/beast-of-argh-amd64-14_1_0.22.3.xz