Overview

This flavour contains a local implementation of parsedmarc.

parsedmarc will produce CSV/JSON output from the relevant mailbox folder in the destination folder selected for /mnt.

This information can be submitted to the local zincsearch instance, a low footprint, non-java, elasticsearch clone.

It is currently expected that this jail will run on an internal IP with no remote access.

The display of the report using zincsearch data is pending, likely local Grafana with imported dashboard.

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.

Warnings

The parsedmarc process can take up to 30min to complete with only a few hundred mails in your dmarc folder on a first run.

There is no progress indicator when complete. When your dmarc folder empties, the initial run is complete, and the messages go to the Archive folder.

Installation

Create your local jail from the image or the flavour files.
Clone the local jail
Mount in persistent storage

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 IMAPSERVER=<mail host> \
  -E IMAPUSER=<imap username> \
  -E IMAPPASS=<imap password> \
  -E IMAPFOLDER=<imap folder with dmarc reports> \
  -E OUTPUTFOLDER=<name of folder to create in /mnt/> \
  -E ZINCUSER=<zincsearch admin user> \
  -E ZINCPASS=<zincsearch admin pass> \
  -E ZINCDATA=<path to store zincsearch files, default /mnt/zinc/data> \
  -E GRAFANAUSER=<username> \
  -E GRAFANAPASSWORD=<password> \
  [ -E ZINCPORT=<zincsearch port, default 4080> ] \
  [ -E REMOTELOG=<IP address> ]

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 IMAPSERVER parameter is the IP address or hostname of the IMAP server. It defaults to port 993 and SSL.

The IMAP user credentials are set with IMAPUSER and IMAPPASS.

The IMAPFOLDER parameter is the mail folder with the DMARC reports as attachments.

The OUTPUTFOLDER parameter is the folder to create in /mnt, which should be mounted in as persistent storage.

The ZINCUSER and ZINCPASS parameters set the zincsearch admin user and password.

The ZINCDATA parameter is the directory to save zincsearch data files. Defaults to /mnt/zinc/data.

The GRAFANAUSER and GRAFANAPASSWORD parameters are for login to the Grafana interface and must be set.

Optional Parameters

The ZINCPORT parameter is the port to make zincsearch available on. Defaults to 4080.

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

We recommend creating a dedicated mailbox folder for DMARC reports and filtering those mails to it. Then configure this image to use that mail folder.

This development version simply sets up parsedmarc and runs the python process to generate JSON and CSV output from a mailbox.

It still needs a way to store the reports long term, and show pretty charts. Possibly elasticsearch and kibana or something lighter.

Note: there is very little feedback that process a mailbox has happened. Check the folders under Archive called Aggregate, Foresic, and Invalid. You might need to subscribe to the folders in an IMAP client to see. When mails are processed from the identified dmarc mail folder, they are transferred to the Archive subfolders.

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 13.2:
pot import -p dmarc-report-amd64-13_2 -t 0.7.1 -U https://potluck.honeyguide.net/dmarc-report

With Signify Verification:
fetch https://potluck.honeyguide.net/potluck.pub; pot import -p dmarc-report-amd64-13_2 -t 0.7.1 -C potluck.pub -U https://potluck.honeyguide.net/dmarc-report

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 dmarc-report-amd64-13_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/dmarc-report 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. 13.2) 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

0.6

Version bump for new base image

0.5

Version bump for new base image
New zincsearch

0.4

Version bump for new base image

0.3

Version bump for new base image
Still WIP image, not working 100% yet for reports
Update to zincsearch 0.4.7
Make nginx fake elasticsearch on ip:9200/_bulk by proxy_pass to ip:4080/api/_bulk
Make parsedmarc send to ip:9200
Adjustments to parsedmarc rc script
Add zinc user/pass to parsedmarc elasticsearch config
Start parsedmarc service last
Increase request entity size for fake elasticsearch to 512MB
Enable prometheus monitoring for zincsearch
Proxy_pass to elasticsearch compatible API bulk endpoint
Adjust proxy_pass to /es/
Fixup changes to parsedmarc ini for fake elasticsearch
Force zincsearch index creation for ‘dmarc_aggregate’ and ‘dmarc_forensic’ before parsedmarc setup
Fix stall in index creation
Create a default index after checking zincsearch is responding. Don’t create ‘dmarc_aggregate’ and ‘dmarc_forensic’.
Bugfixing index creation step
Revert to forcing zincsearch index creation for ‘dmarc_aggregate’ and ‘dmarc_forensic’ before parsedmarc setup
Split index creation to own script before parsedmarc install
Use 127.0.0.1 instead of localhost
Add grafana8 to use with custom dashboard for parsedmarc, suitable dashboard to be tested still
Further adjustments to index creation
Add grafana variables, simplify index creation script
Fix missing grafana.ini
Update to Grafana9
Remove fake elasticsearch proxy_pass for testing direct
Tweaks to parsedmarc elasticsearch config, add back fake elasticsearch for parsedmarc ingestion
Fix Grafana datasource and add first dashboard
Fix syslog-ng problems for 4.2 version, remove stats_freq option
Updates to make Grafana play nice with fake elasticsearch
Create alias for index creation, configure Grafana to use alias
Add cron job to update alias (commented out)
Fix grafana database pattern, separate datasources for aggregate and forensic
Manually set elasticsearch version in zincsearch rc
Add local unbound and consul DNS services
Update README with consul DNS info
fix local_unbound dns resolution with missing parameters for access control
Disable consul DNS option with local_unbound as is only practical in VNET jails with a localhost

0.2

Version bump for new base image
Signified
Fix nologin shell for nodeexport user
Fix nologin shell for zincsearch user

0.1

Rework project to start with parsedmarc python application
Remove serverport parameter
Fix username parsedmarc in user creation
Update checklist for python39 changes
Add parsedmarc.ini with imported parameters
Add outputfolder parameter
Touch log file and set permissions
Add rc script for parsedmarc
Update README
Add zincsearch, an elasticsearch clone
Make parsedmarc log to zincsearch automatically
Remove Elasticsearch and Kibana install
Fix zincsearch download
Add back rust
Fix zincsearch startup

0.0

First bash at a pot jail with automatic dmarc report by accessing IMAP mailbox
Use node pm2 as process manager to background node app

These images were built on Fri Nov 10 21:22:04 UTC 2023

Manual Image Download Links

dmarc-report-amd64-13_2_0.7.1.xz ( )
dmarc-report-amd64-13_2_0.7.1.xz.skein ( ) dmarc-report-amd64-13_2_0.7.1.xz.skein.sig ( ) dmarc-report-amd64-13_2_0.7.1.xz.meta ( )

Jenkins Pot Creation Logs

dmarc-report-amd64-13_2_0.7.1:


dmarc-report/dmarc-report:
copy-in -s /usr/local/etc/pot/flavours/dmarc-report.d/local -d /root/.pot_local
dmarc-report/dmarc-report.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 git-lite"
pkg install -y git-lite

step "Install package node_exporter"
pkg install -y node_exporter

step "Install package nginx"
pkg install -y nginx

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

step "Install package python39"
pkg install -y python39

step "Install package py39-pip"
pkg install -y py39-pip

step "Install package py39-virtualenv"
pkg install -y py39-virtualenv

step "Install package py39-libxml2"
pkg install -y py39-libxml2

step "Install package py39-cryptography"
pkg install -y py39-cryptography

step "Install pckage py39-cryptography-vectors"
pkg install -y py39-cryptography-vectors

step "Install package libxslt"
pkg install -y libxslt

step "Install package rust"
pkg install -y rust

step "Install package grafana9"
pkg install -y grafana9

step "Clean package installation"
pkg clean -y

step "Download and extract zincsearch binary from github"
fetch -qo - \
 https://github.com/zincsearch/zincsearch/releases/download/v0.4.9/zincsearch_0.4.9_freebsd_x86_64.tar.gz | \
 tar xzf - -C /usr/local/bin

step "Testing if zincsearch binary exists"
if [ ! -f /usr/local/bin/zincsearch ]; then
    exit_error "/usr/local/bin/zincsearch is missing"
fi

step "Checksum query for zincsearch"
if [ "$(sha256 -q /usr/local/bin/zincsearch)" != \
  "b2183ac2829847897b837017c4d1828cd66ac655fa0c66c67bbd1237e4faff21" ]; then
  exit_error "/usr/local/bin/zincsearch 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

dmarc-report/dmarc-report+1:
dmarc-report/dmarc-report+1.sh:

dmarc-report/dmarc-report+2:
dmarc-report/dmarc-report+2.sh:

dmarc-report/dmarc-report+3:
dmarc-report/dmarc-report+3.sh:

dmarc-report/dmarc-report+4:
dmarc-report/dmarc-report+4.sh:
=====>  Create conf dir (/mnt/srv/pot/jails/dmarc-report-amd64-13_2/conf)
=====>  Cloning freebsd-potluck-amd64-13_2_0_0_20 with snap 
=====>  clone zroot/srv/pot/jails/freebsd-potluck-amd64-13_2_0_0_20/m@1699635260 into zroot/srv/pot/jails/dmarc-report-amd64-13_2/m
=====>  Flavour: fbsd-update
=====>  Starting dmarc-report-amd64-13_2 pot for the initial bootstrap
=====>  mount /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===>  Starting the pot dmarc-report-amd64-13_2
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=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
	inet 127.0.0.1 netmask 0xff000000
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8<VLAN_MTU>
	ether 02:b8:58:40:59: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 motd:.
Updating /var/run/os-release done.
Creating and/or trimming log files.
Starting syslogd.
Starting cron.
Starting sendmail_outbound.

Fri Nov 10 21:13:13 UTC 2023
/usr/local/etc/pot/flavours/fbsd-update.sh -> /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/tmp/fbsd-update.sh
=====>  Executing fbsd-update script on dmarc-report-amd64-13_2
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 13.2-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 13.2-RELEASE-p5.
No updates are available to install.
=====>  Stop the pot dmarc-report-amd64-13_2
=====>  Remove p4654e9ce5117c1 epair network interfaces
=====>  unmount /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/tmp
=====>  unmount /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/dev
=====>  Flavour: dmarc-report
=====>  Executing dmarc-report pot commands on dmarc-report-amd64-13_2
=====>  mount /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/tmp
=====>  Source /usr/local/etc/pot/flavours/dmarc-report.d/local copied in the pot dmarc-report-amd64-13_2
=====>  unmount /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/tmp
=====>  /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/dev is already unmounted
=====>  Starting dmarc-report-amd64-13_2 pot for the initial bootstrap
=====>  mount /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===>  Starting the pot dmarc-report-amd64-13_2
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=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
	inet 127.0.0.1 netmask 0xff000000
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8<VLAN_MTU>
	ether 02:92:58:29:57: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 motd:.
Updating /var/run/os-release done.
Creating and/or trimming log files.
Starting syslogd.
Starting cron.
Starting sendmail_outbound.

Fri Nov 10 21:13:33 UTC 2023
/usr/local/etc/pot/flavours/dmarc-report.sh -> /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/tmp/dmarc-report.sh
=====>  Executing dmarc-report script on dmarc-report-amd64-13_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_outbound 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...
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.16.2

Number of packages to be installed: 1

The process will require 112 MiB more space.
20 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Fetching consul-1.16.2.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Installing consul-1.16.2...
===> Creating groups.
Creating group 'consul' with gid '469'.
===> Creating users
Creating user 'consul' with uid '469'.
===> Creating homedir(s)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Extracting consul-1.16.2: ..... done
Step 7: 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 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 git-lite
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:
	expat: 2.5.0
	git-lite: 2.42.0
	pcre2: 10.42

Number of packages to be installed: 3

The process will require 41 MiB more space.
7 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Fetching pcre2-10.42.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Fetching expat-2.5.0.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Fetching git-lite-2.42.0.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Installing pcre2-10.42...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Extracting pcre2-10.42: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Installing expat-2.5.0...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Extracting expat-2.5.0: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Installing git-lite-2.42.0...
===> Creating groups.
Creating group 'git_daemon' with gid '964'.
===> Creating users
Creating user 'git_daemon' with uid '964'.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Extracting git-lite-2.42.0: .......... done
=====
Message from git-lite-2.42.0:

--
If you installed the GITWEB option please follow these instructions:

In the directory /usr/local/share/examples/git/gitweb you can find all files to
make gitweb work as a public repository on the web.

All you have to do to make gitweb work is:
1) Please be sure you're able to execute CGI scripts in
   /usr/local/share/examples/git/gitweb.
2) Set the GITWEB_CONFIG variable in your webserver's config to
   /usr/local/etc/git/gitweb.conf. This variable is passed to gitweb.cgi.
3) Restart server.


If you installed the CONTRIB option please note that the scripts are
installed in /usr/local/share/git-core/contrib. Some of them require
other ports to be installed (perl, python, etc), which you may need to
install manually.
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.5.0_7

Number of packages to be installed: 1

The process will require 11 MiB more space.
3 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Fetching node_exporter-1.5.0_7.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Installing node_exporter-1.5.0_7...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Extracting node_exporter-1.5.0_7: .......... done
=====
Message from node_exporter-1.5.0_7:

--
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 nginx
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:
	nginx: 1.24.0_12,3

Number of packages to be installed: 1

The process will require 1 MiB more space.
463 KiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Fetching nginx-1.24.0_12,3.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Installing nginx-1.24.0_12,3...
===> Creating groups.
Using existing group 'www'.
===> Creating users
Using existing user 'www'.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Extracting nginx-1.24.0_12,3: .......... done
=====
Message from nginx-1.24.0_12,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 19: 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.78.1,2
	ivykis: 0.42.4
	json-c: 0.17
	libffi: 3.4.4
	libxml2: 2.10.4_1
	mpdecimal: 2.5.1
	python39: 3.9.18
	syslog-ng: 4.4.0

Number of packages to be installed: 9

The process will require 158 MiB more space.
24 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/9] Fetching ivykis-0.42.4.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/9] Fetching libxml2-2.10.4_1.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/9] Fetching mpdecimal-2.5.1.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [4/9] Fetching python39-3.9.18.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [5/9] Fetching glib-2.78.1,2.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [6/9] Fetching syslog-ng-4.4.0.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [7/9] Fetching libffi-3.4.4.pkg: ..... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [8/9] Fetching json-c-0.17.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [9/9] Fetching e2fsprogs-libuuid-1.47.0.pkg: ....... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/9] Installing mpdecimal-2.5.1...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/9] Extracting mpdecimal-2.5.1: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/9] Installing libffi-3.4.4...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/9] Extracting libffi-3.4.4: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/9] Installing libxml2-2.10.4_1...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/9] Extracting libxml2-2.10.4_1: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [4/9] Installing python39-3.9.18...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [4/9] Extracting python39-3.9.18: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [5/9] Installing ivykis-0.42.4...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [5/9] Extracting ivykis-0.42.4: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [6/9] Installing glib-2.78.1,2...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [6/9] Extracting glib-2.78.1,2: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [7/9] Installing json-c-0.17...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [7/9] Extracting json-c-0.17: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [8/9] Installing e2fsprogs-libuuid-1.47.0...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [8/9] Extracting e2fsprogs-libuuid-1.47.0: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [9/9] Installing syslog-ng-4.4.0...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [9/9] Extracting syslog-ng-4.4.0: .......... done
==> Running trigger: gio-modules.ucl
Generating GIO modules cache
==> Running trigger: glib-schemas.ucl
Compiling glib schemas
No schema files found: doing nothing.
=====
Message from python39-3.9.18:

--
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.4.0:

--
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 20: Install package python39
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 21: Install package py39-pip
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:
	py39-pip: 23.2.1
	py39-setuptools: 63.1.0_1

Number of packages to be installed: 2

The process will require 27 MiB more space.
4 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/2] Fetching py39-setuptools-63.1.0_1.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/2] Fetching py39-pip-23.2.1.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/2] Installing py39-setuptools-63.1.0_1...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/2] Extracting py39-setuptools-63.1.0_1: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/2] Installing py39-pip-23.2.1...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/2] Extracting py39-pip-23.2.1: .......... done
=====
Message from py39-pip-23.2.1:

--
pip MUST ONLY be used:

 * With the --user flag, OR
 * To install or manage Python packages in virtual environments

Failure to follow this warning can and will result in an inconsistent
system-wide Python environment (LOCALBASE/lib/pythonX.Y/site-packages) and
cause errors.

Avoid using pip as root unless you know what you're doing.
Step 22: Install package py39-virtualenv
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 5 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	py39-distlib: 0.3.7
	py39-filelock: 3.12.3
	py39-platformdirs: 3.10.0
	py39-typing-extensions: 4.8.0
	py39-virtualenv: 20.24.5

Number of packages to be installed: 5

The process will require 8 MiB more space.
4 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/5] Fetching py39-platformdirs-3.10.0.pkg: .... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/5] Fetching py39-virtualenv-20.24.5.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/5] Fetching py39-distlib-0.3.7.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [4/5] Fetching py39-filelock-3.12.3.pkg: .. done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [5/5] Fetching py39-typing-extensions-4.8.0.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/5] Installing py39-typing-extensions-4.8.0...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/5] Extracting py39-typing-extensions-4.8.0: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/5] Installing py39-platformdirs-3.10.0...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/5] Extracting py39-platformdirs-3.10.0: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/5] Installing py39-distlib-0.3.7...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/5] Extracting py39-distlib-0.3.7: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [4/5] Installing py39-filelock-3.12.3...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [4/5] Extracting py39-filelock-3.12.3: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [5/5] Installing py39-virtualenv-20.24.5...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [5/5] Extracting py39-virtualenv-20.24.5: .......... done
Step 23: Install package py39-libxml2
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:
	py39-libxml2: 2.10.4

Number of packages to be installed: 1

The process will require 2 MiB more space.
173 KiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Fetching py39-libxml2-2.10.4.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Installing py39-libxml2-2.10.4...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Extracting py39-libxml2-2.10.4: .......... done
Step 24: Install package py39-cryptography
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:
	py39-cffi: 1.16.0
	py39-cryptography: 41.0.4,1
	py39-pycparser: 2.21

Number of packages to be installed: 3

The process will require 7 MiB more space.
1 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Fetching py39-cryptography-41.0.4,1.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Fetching py39-pycparser-2.21.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Fetching py39-cffi-1.16.0.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Installing py39-pycparser-2.21...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Extracting py39-pycparser-2.21: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Installing py39-cffi-1.16.0...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Extracting py39-cffi-1.16.0: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Installing py39-cryptography-41.0.4,1...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Extracting py39-cryptography-41.0.4,1: .......... done
Step 25: Install pckage py39-cryptography-vectors
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:
	py39-cryptography-vectors: 41.0.4

Number of packages to be installed: 1

The process will require 72 MiB more space.
28 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Fetching py39-cryptography-vectors-41.0.4.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Installing py39-cryptography-vectors-41.0.4...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Extracting py39-cryptography-vectors-41.0.4: .......... done
Step 26: Install package libxslt
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:
	libgcrypt: 1.10.2
	libgpg-error: 1.47
	libxslt: 1.1.37

Number of packages to be installed: 3

The process will require 8 MiB more space.
1 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Fetching libgcrypt-1.10.2.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Fetching libxslt-1.1.37.pkg: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Fetching libgpg-error-1.47.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Installing libgpg-error-1.47...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/3] Extracting libgpg-error-1.47: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Installing libgcrypt-1.10.2...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [2/3] Extracting libgcrypt-1.10.2: .......... done
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Installing libxslt-1.1.37...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [3/3] Extracting libxslt-1.1.37: .......... done
Step 27: Install package rust
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:
	rust: 1.72.0

Number of packages to be installed: 1

The process will require 1 GiB more space.
130 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Fetching rust-1.72.0.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Installing rust-1.72.0...
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Extracting rust-1.72.0: .......... done
Step 28: Install package grafana9
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:
	grafana9: 9.5.7_2

Number of packages to be installed: 1

The process will require 262 MiB more space.
52 MiB to be downloaded.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Fetching grafana9-9.5.7_2.pkg: .......... done
Checking integrity... done (0 conflicting)
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Installing grafana9-9.5.7_2...
===> Creating groups.
Creating group 'grafana' with gid '904'.
===> Creating users
Creating user 'grafana' with uid '904'.
[dmarc-report-amd64-13_2.vsf00001.cpt.za.honeyguide.net] [1/1] Extracting grafana9-9.5.7_2: .......... done
Step 29: Clean package installation
Nothing to do.
Step 30: Download and extract zincsearch binary from github
Step 31: Testing if zincsearch binary exists
Step 32: Checksum query for zincsearch
Step 33: Clean cook artifacts
Step 34: Install pot local
Step 35: Set file ownership on cook scripts
Step 36: Make cook script executable
setting executable bit on /usr/local/bin/cook
Step 37: Create rc.d script to start cook
creating rc.d script to start cook
Step 38: Make rc.d script to start cook executable
Setting executable bit on cook rc file
Step 39: Enable cook service
enabling cook
cook enabled in /etc/rc.conf
=====>  Stop the pot dmarc-report-amd64-13_2
=====>  Remove p4654e9cfa117c1 epair network interfaces
=====>  unmount /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/tmp
=====>  unmount /mnt/srv/pot/jails/dmarc-report-amd64-13_2/m/dev
===>  exporting dmarc-report-amd64-13_2 @ 1699650959 to /tmp/dmarc-report-amd64-13_2_0.7.1.xz
xz: Reduced the number of threads from 4 to 3 to not exceed the memory usage limit of 503 MiB

DMARC-report