Overview
This is a complete jitsi-meet installation in one jail that can be started with pot.
The jail configures itself on the first start for your environment (see notes below), for details about how to run jitsi-meet in a FreeBSD jail in general, see this blog post.
Deploying the image or flavour should be quite straight forward and not take more than a few minutes.
Installation
- Create your local jail from the image or the flavour files.
- This jail does not work with a public bridge, so clone it to use an IP address directly on your host:
sudo pot clone -P <nameofimportedjail> -p <clonejailname> -N alias -i "<interface>|<ipaddress>" - Copy in any supporting files such as image file for customisation
sudo pot copy-in -p <clonejailname> -s <source image> -d /usr/local/www/jitsi-meet/images/<destination filename> - Adjust to your environment:
-E DATACENTER=<datacentername> \ -E IP=<IP address of this nomad instance> \ -E NODENAME=<an internal name for image> \ -E CONSULSERVERS="<comma-deliminated list of consul servers>" \ -E GOSSIPKEY="<32 byte Base64 key from consul keygen>" \ -E DOMAIN=<FQDN for host> \ -E EMAIL=<email address for letsencrypt setup> \ -E RESOLUTION=<one of 180|240|360|480|720> \ -E PUBLICIP=<yourpublicip> \ [ -E IMAGE="filename.svg" ] \ [ -E LINK="https://full.url" ] \ [ -E REMOTELOG="<IP syslog-ng server>" ]``` - Forward the needed ports:
pot export-ports -p <yourjailname> -e 80:80 -e 443:443 -e 10000:10000 -e 4443:4443with <yourjailname> again being the name of your newly created/imported jail. - Start the pot:
pot start <yourjailname>. On the first run the jail will configure itself and start the services. If it would not be for the following one workaround step, you could now use your video conference platform.
Workaround for missing UDP port forwarding:
pot at the moment only forwards TCP ports, not UDP ports. Therefore you need to fix the port forward each time you start the jail manually with a command like this:
echo "
rdr pass on em0 inet proto tcp from any to <yourhostip> port = http -> <yourpotip> port 80
rdr pass on em0 inet proto tcp from any to <yourhostip> port = https -> <yourpotip> port 443
rdr pass on em0 inet proto udp from any to <yourhostip> port = 10000 -> <yourpotip> port 10000
rdr pass on em0 inet proto tcp from any to <yourhostip> port = 4443 -> <yourpotip> port 4443
" | pfctl -a pot-rdr/<yourjailname> -f -
<yourhostip> is the IP address users will connect to, <yourpotip> is the pot generated IP address (e.g. 10.192.0.3), <yourjailname> is the name you have given your jail.
For more details about nomadimages, see about potluck.
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 DOMAIN parameter is the domain name of the jitsi-meet instance.
The EMAIL parameter is the email address to use for letsencrypt registration. SSL certificates are mandatory, modern browsers won’t open camera or microphone unless SSL enabled.
The RESOLUTION parameter is one of the valid jitsi-meet resolution settings such as 180, 240, 360, 480, 720, fullhd etc.
The PUBLIC IP parameter is the public facing IP address which users connect to.
Optional Parameters
The REMOTELOG parameter is the IP address of a destination syslog-ng server, such as with the loki flavour, or beast-of-argh flavour.
The IMAGE parameter is the filename of an image copied in to /usr/local/www/jitsi-meet/images/{filename} if using a custom logo image. You must copy this file in as part of the steps above.
The LINK parameter is the full URL with https://full.url/path which someone will go to when clicking the custom logo image.
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 jitsi-meet-amd64-14_1 -t 0.20.3 -U https://potluck.honeyguide.net/jitsi-meet
With Signify Verification:
fetch https://potluck.honeyguide.net/potluck.pub; pot import -p jitsi-meet-amd64-14_1 -t 0.20.3 -C potluck.pub -U https://potluck.honeyguide.net/jitsi-meet
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 jitsi-meet-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/jitsi-meet 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.20
- 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.19
- Version bump for new base image
0.18
- Version bump for new base image
- Test prosody setting of interfaces = { ‘x.x.x.x’ }
0.17
- Version bump for new base image
- Fix node_exporter zfs issue
- Adjust cert renew script to hardcode domain
- Update certificate renewal script
0.16
- Version bump for new base image
- FBSD14 base image
0.15
- Version bump for new base image
0.14
- Version bump for new base image
0.13
- Version bump for new base image
0.12
- Version bump for new base image
0.11
- Version bump for new base image
- Fix error in ini file
- Fix README
0.10
- Version bump for new base image
- Fix syslog-ng problems for 4.2 version, remove stats_freq option
- 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
- Adjust acme.sh setup and renew scripts for ‘$domain_ecc’ suffix which is default now
- Bug-fixing acme.sh change
- Fix error with prosody setup
- Change password generation for turnserver
- Trim turnadmin output for final line only
- Fix jitsi-videobridge rc script to remove -XX:+UseConcMarkSweepGC
- Make backups of rc scripts if exist
- Use default RC files with user perms instead of custom running services as root
- Prevent jitsi-videobridge from advertising private ranges, set xmpp-domain
0.9
- Version bump for new base image
0.8
- Version bump for new base image
- Signified
- Fix nologin shell for nodeexport user
0.7
- Version increment for new feature
- Pass in consul servers as a comma-deliminated list
- Update nginx for acme challenges
- Fix certificate renewals
0.6
- Version bump for new base image
- Update syslog-ng.conf stats_freq(0); -> stats(freq(0));
0.5
- Major rewrite for testing
- Set ketstore type to jks
- Remove user flag for rc scripts on jicofo and jitsi-videobridge
- Remove prosody localhost virtualhost and cert generation
- Set user jvb instead of user focus
- Simplify many config files
- Add local IP to /etc/hosts
- Fix duplicate ssl_ciphers error
- Add back prosody localhost virtualhost for testing, add nginx-full
- Revert to normal nginx because nginx-full has conflicts which result in removal of nginx
0.4
- Version bump for new base image
0.3
- Version bump for new base image
- Implement websockets and turnserver
- Script error fixes with introduction turnserver
- Adjust config.js and videobridge settings
- Remove no-loopback-peers from turnserver config, bad config option
- Allow setting default resolution as parameter
- Specify turnservers in sip-communicator.properties
- Adjust to use full certificate chain in fullchain.cer so mobile devices work
- Re-enable P2P in config.js
- Set this server as STUN server in config.js
- Add local IP to turnserver allowed-peer-ip
- Include password for prosodyctl mod_roster_command
0.2
- Update prosody and related based on sample prosody config from jitsi-prosody-plugins
- Fix logging to /var/log/prosody
- Update jicofo config
- Update nginx config to match example from jitsi-prosody-plugins
- Bug-fixing and permissions changes
- Working release 0.2.4 with wasm duplication removed from nginx
- Update branding options
- Update README
- Fix branding link
- Add back global modules_enabled to prosody to clear config check
- Update syslog-ng to capture prosody, jicofo, jitsi-videobridge logs
- Comment out focusUserJid from config.js
- Turn off BWE mechanism in sip-communicator.properties
- Fix path for external_api.js in nginx.conf
- Set options in config.js to force video and audio on when joining
- Turn off P2P mode in config.js
- Enable pre-join page
- Prosody needs a localhost virtualhost
- Updates to jicofo, jitsi-videobridge and sip-communicator.properties after bugfixing
0.1
- Creating regular pot jail for jitsi-meet as alternative to jitsi-meet-nomad
- This version includes consul, node_exporter, syslog-ng
- Fix cert renew script name
- Fix jitsi config and typo in service start
- Fix jicofo service start
- Generate keypassword differently as jicofo doesn’t like some characters
- Fix nginx certificate copy
- Adjust jicofo rc script
- Fix logic for certs if already registered domain
- Re-order service config and start
- fix prosody cert location
- fix jicofo rc script with inclusion password
- adjust startup timing
- Adjust startup order
- fix jitsi-videobridge rc script to match earlier blog post
- fix jitsi-videobridge rc script to use org.jitsi.videobridge.MainKt
- create /var/db/prosody/custom_plugins
- fix jicofo start
- revert to simple start of some services
- custom image option added
- adjust prosodyctl legacy command to register for domain not auth.domain
- revert prosodyctl to register with auth.domain, 3rd party docs incorrect
- fix password allocations between first and second
- fix prosodyctl password for auth.domain to second password
- include package jitsi-srtp-native for improved performance
- remove custom settings from rc files (from blog post) to test without
- add back custom parameters to rc files, jicofo doesn’t start otherwise
- tweak startup for jitsi-videobridge
- add jicofostatus script
- fix error with prosody config to update secpassword
- fix source file name for jicofostatus script
- switch to jitsi-full meta package
- redo config files for new format
- Switch to latest package sources, non-layered image
- remove the rc env setting for jicofo and jitsi-videobridge
- Revert to quarterlies and layered image, problem was rc env setting
- Add back rc fix for ’the trustAnchors parameter must be non-empty’ by adding -Djavax.net.ssl.trustStorePassword
- remove internal from bridge stanza
- Synchronise removal internal from jitsi-videobridge, swap password
- Tweak config file for prosody
- Single generated pass for debugging, add back customisations to videobridge rc file
- Cleanup install list
- Revert prosody config to older setup, plug jicofo and videobridge rc files
- Fix config.js for conference muc domain
- Revert to newer prosody setup for focus.auth, this authenticates fine
- Bunch of updates after watching helpful video
- Video link https://youtu.be/LJOpSDcwWIA
- Add extra bits to prosody config
- Tweaks to sip-communicator.properties
- Set jitsi-plugins directory correctly
0.0.1
- Initiate file
These images were built on Wed Nov 6 20:08:38 UTC 2024
Manual Image Download Links
jitsi-meet-amd64-14_1_0.20.3.xz (
)
jitsi-meet-amd64-14_1_0.20.3.xz.skein (
)
jitsi-meet-amd64-14_1_0.20.3.xz.skein.sig (
)
jitsi-meet-amd64-14_1_0.20.3.xz.meta (
)
Jenkins Pot Creation Logs
jitsi-meet-amd64-14_1_0.20.3:
jitsi-meet/jitsi-meet:
copy-in -s /usr/local/etc/pot/flavours/jitsi-meet.d/local -d /root/.pot_local
jitsi-meet/jitsi-meet.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 node_exporter"
pkg install -y node_exporter
# nginx-full has conflicts and will remove any nginx
step "Install package nginx"
pkg install -y nginx
step "Install package syslog-ng"
pkg install -y syslog-ng
step "Install package acme.sh"
pkg install -y acme.sh
step "Install package prosody"
pkg install -y prosody
step "Install package turnserver"
pkg install -y turnserver
# Be aware this installs unbound from ports which overwrites local_unbound
step "Install package jitsi-meet"
pkg install -y jitsi-meet-full
step "Clean package installation"
pkg clean -y
# -------------- 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
jitsi-meet/jitsi-meet+1:
jitsi-meet/jitsi-meet+1.sh:
jitsi-meet/jitsi-meet+2:
jitsi-meet/jitsi-meet+2.sh:
jitsi-meet/jitsi-meet+3:
jitsi-meet/jitsi-meet+3.sh:
jitsi-meet/jitsi-meet+4:
jitsi-meet/jitsi-meet+4.sh:
=====> Create conf dir (/mnt/srv/pot/jails/jitsi-meet-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/jitsi-meet-amd64-14_1/m
=====> Flavour: fbsd-update
=====> Starting jitsi-meet-amd64-14_1 pot for the initial bootstrap
=====> mount /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===> Starting the pot jitsi-meet-amd64-14_1
=====> Pot jitsi-meet-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=jitsi-meet-amd64-14_1 host.hostname=jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net osrelease=14.1-RELEASE-p6 path=/mnt/srv/pot/jails/jitsi-meet-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:8d:1b:1a:20: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:01:55 UTC 2024
/usr/local/etc/pot/flavours/fbsd-update.sh -> /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/tmp/fbsd-update.sh
=====> Executing fbsd-update script on jitsi-meet-amd64-14_1
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching public key from update2.freebsd.org... done.
Fetching metadata signature for 14.1-RELEASE from update2.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 jitsi-meet-amd64-14_1
=====> Remove p4672bcb323f7f epair network interfaces
=====> unmount /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/tmp
=====> unmount /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/dev
=====> Flavour: jitsi-meet
=====> Executing jitsi-meet pot commands on jitsi-meet-amd64-14_1
=====> mount /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/tmp
=====> Source /usr/local/etc/pot/flavours/jitsi-meet.d/local copied in the pot jitsi-meet-amd64-14_1
=====> unmount /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/tmp
=====> /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/dev is already unmounted
=====> Starting jitsi-meet-amd64-14_1 pot for the initial bootstrap
=====> mount /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/tmp
defaultrouter: 10.192.0.1 -> 10.192.0.1
===> Starting the pot jitsi-meet-amd64-14_1
=====> Pot jitsi-meet-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=jitsi-meet-amd64-14_1 host.hostname=jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net osrelease=14.1-RELEASE-p6 path=/mnt/srv/pot/jails/jitsi-meet-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:4f:0b:20:d0: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:02:29 UTC 2024
/usr/local/etc/pot/flavours/jitsi-meet.sh -> /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/tmp/jitsi-meet.sh
=====> Executing jitsi-meet script on jitsi-meet-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: Install package consul
Updating FreeBSD repository catalogue...
[jitsi-meet-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.
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching consul-1.19.2.pkg: .......... done
Checking integrity... done (0 conflicting)
[jitsi-meet-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)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Extracting consul-1.19.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 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.
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Fetching node_exporter-1.8.2.pkg: .......... done
Checking integrity... done (0 conflicting)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/1] Installing node_exporter-1.8.2...
[jitsi-meet-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 17: 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.
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Fetching nginx-1.26.2_5,3.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/2] Fetching pcre2-10.43.pkg: .......... done
Checking integrity... done (0 conflicting)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Installing pcre2-10.43...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Extracting pcre2-10.43: .......... done
[jitsi-meet-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'
[jitsi-meet-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 18: 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.
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/9] Fetching ivykis-0.43.2.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/9] Fetching mpdecimal-4.0.0.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/9] Fetching py311-packaging-24.1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/9] Fetching glib-2.80.5,2.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/9] Fetching syslog-ng-4.8.0_2.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/9] Fetching libffi-3.4.6.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/9] Fetching json-c-0.18.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/9] Fetching e2fsprogs-libuuid-1.47.1.pkg: ....... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/9] Fetching python311-3.11.10.pkg: .......... done
Checking integrity... done (0 conflicting)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/9] Installing mpdecimal-4.0.0...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/9] Extracting mpdecimal-4.0.0: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/9] Installing libffi-3.4.6...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/9] Extracting libffi-3.4.6: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/9] Installing python311-3.11.10...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/9] Extracting python311-3.11.10: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/9] Installing py311-packaging-24.1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/9] Extracting py311-packaging-24.1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/9] Installing ivykis-0.43.2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/9] Extracting ivykis-0.43.2: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/9] Installing glib-2.80.5,2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/9] Extracting glib-2.80.5,2: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/9] Installing json-c-0.18...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/9] Extracting json-c-0.18: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/9] Installing e2fsprogs-libuuid-1.47.1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/9] Extracting e2fsprogs-libuuid-1.47.1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/9] Installing syslog-ng-4.8.0_2...
[jitsi-meet-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 19: Install package acme.sh
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:
acme.sh: 3.0.9
socat: 1.8.0.1
Number of packages to be installed: 2
The process will require 2 MiB more space.
435 KiB to be downloaded.
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Fetching acme.sh-3.0.9.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/2] Fetching socat-1.8.0.1.pkg: .......... done
Checking integrity... done (0 conflicting)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Installing socat-1.8.0.1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/2] Extracting socat-1.8.0.1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/2] Installing acme.sh-3.0.9...
===> Creating groups
Creating group 'acme' with gid '169'
===> Creating users
Creating user 'acme' with uid '169'
===> Creating homedir(s)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/2] Extracting acme.sh-3.0.9: .......... done
=====
Message from acme.sh-3.0.9:
--
This script will create the following directories if they do not exist:
~acme/.acme.sh
~acme/certs
The script will also install ~acme/.acme.sh/account.conf.sample which has
sane defaults. Copy this to ~acme/.acme.sh/account.conf and edit contents
to suit.
If you have EXAMPLES on:
* In the /usr/local/share/examples/acme.sh directory, you can find the dnsapi
scripts which will be useful if you decide to use dns-01 challenges. Also
included are the deploy scripts.
* A newsyslog.conf sample file is installed at
/usr/local/etc/newsyslog.conf.d/acme.sh.conf - you must modify it by
at least uncommenting the line.
* If you run `newsyslog -NC` it will create the required logfiles.
* Please review /usr/local/share/examples/acme.sh/acme.sh-cron.d - instructions are
contained in that file.
Step 20: Install package prosody
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 15 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
expat: 2.6.3
icu: 74.2_1,1
libedit: 3.1.20240808,1
libevent: 2.1.12
libsodium: 1.0.19
lua54: 5.4.7
lua54-bitop: 1.0.2_2
lua54-libevent: 0.4.6_3
lua54-luaexpat: 1.5.2
lua54-luafilesystem: 1.8.0
lua54-luasec: 1.3.2
lua54-luasocket: 3.1.0_1,1
lua54-luaunbound: 1.0.0_5
prosody: 0.12.4_5
unbound: 1.21.1
Number of packages to be installed: 15
The process will require 70 MiB more space.
17 MiB to be downloaded.
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/15] Fetching lua54-libevent-0.4.6_3.pkg: . done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/15] Fetching unbound-1.21.1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/15] Fetching lua54-luasec-1.3.2.pkg: .... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/15] Fetching prosody-0.12.4_5.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/15] Fetching libedit-3.1.20240808,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/15] Fetching icu-74.2_1,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/15] Fetching lua54-luasocket-3.1.0_1,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/15] Fetching lua54-luafilesystem-1.8.0.pkg: ..... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/15] Fetching lua54-bitop-1.0.2_2.pkg: . done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/15] Fetching libsodium-1.0.19.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/15] Fetching lua54-5.4.7.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/15] Fetching lua54-luaunbound-1.0.0_5.pkg: . done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/15] Fetching expat-2.6.3.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/15] Fetching libevent-2.1.12.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/15] Fetching lua54-luaexpat-1.5.2.pkg: ... done
Checking integrity... done (0 conflicting)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/15] Installing libedit-3.1.20240808,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/15] Extracting libedit-3.1.20240808,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/15] Installing libsodium-1.0.19...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/15] Extracting libsodium-1.0.19: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/15] Installing lua54-5.4.7...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/15] Extracting lua54-5.4.7: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/15] Installing expat-2.6.3...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/15] Extracting expat-2.6.3: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/15] Installing libevent-2.1.12...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/15] Extracting libevent-2.1.12: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/15] Installing unbound-1.21.1...
===> Creating groups
Using existing group 'unbound'
===> Creating users
Using existing user 'unbound'
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/15] Extracting unbound-1.21.1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/15] Installing lua54-luasocket-3.1.0_1,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/15] Extracting lua54-luasocket-3.1.0_1,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/15] Installing lua54-libevent-0.4.6_3...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/15] Extracting lua54-libevent-0.4.6_3: ..... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/15] Installing lua54-luasec-1.3.2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/15] Extracting lua54-luasec-1.3.2: ...... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/15] Installing icu-74.2_1,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/15] Extracting icu-74.2_1,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/15] Installing lua54-luafilesystem-1.8.0...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/15] Extracting lua54-luafilesystem-1.8.0: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/15] Installing lua54-bitop-1.0.2_2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/15] Extracting lua54-bitop-1.0.2_2: .... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/15] Installing lua54-luaunbound-1.0.0_5...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/15] Extracting lua54-luaunbound-1.0.0_5: .... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/15] Installing lua54-luaexpat-1.5.2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/15] Extracting lua54-luaexpat-1.5.2: ....... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/15] Installing prosody-0.12.4_5...
===> Creating groups
Creating group 'prosody' with gid '242'
===> Creating users
Creating user 'prosody' with uid '242'
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/15] Extracting prosody-0.12.4_5: .......... done
=====
Message from prosody-0.12.4_5:
--
If you're running Prosody in a jail and experience problems, please add
the following to the global section of your prosody.cfg.lua:
interfaces = { 'x.x.x.x' }
where 'x.x.x.x' is the public IP you wish Prosody to bind to.
Step 21: Install package turnserver
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 17 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
cyrus-sasl: 2.1.28_5
groff: 1.23.0_3
hidapi: 0.14.0
hiredis: 1.2.0.15
libcbor: 0.11.0
libcjson: 1.7.18_2
libfido2: 1.15.0
libpaper: 1.1.28_1
libunwind: 20240221
mysql80-client: 8.0.39
openldap26-client: 2.6.8
perl5: 5.36.3_2
postgresql16-client: 16.4
psutils: 1.17_6
sqlite3: 3.46.1,1
turnserver: 4.6.2_1
uchardet: 0.0.8_1
Number of packages to be installed: 17
The process will require 240 MiB more space.
33 MiB to be downloaded.
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/17] Fetching libcjson-1.7.18_2.pkg: ........ done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/17] Fetching groff-1.23.0_3.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/17] Fetching hidapi-0.14.0.pkg: ...... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/17] Fetching libunwind-20240221.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/17] Fetching mysql80-client-8.0.39.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/17] Fetching libcbor-0.11.0.pkg: ....... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/17] Fetching uchardet-0.0.8_1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/17] Fetching cyrus-sasl-2.1.28_5.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/17] Fetching postgresql16-client-16.4.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/17] Fetching sqlite3-3.46.1,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/17] Fetching psutils-1.17_6.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/17] Fetching libpaper-1.1.28_1.pkg: ..... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/17] Fetching openldap26-client-2.6.8.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/17] Fetching perl5-5.36.3_2.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/17] Fetching hiredis-1.2.0.15.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [16/17] Fetching libfido2-1.15.0.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [17/17] Fetching turnserver-4.6.2_1.pkg: .......... done
Checking integrity... done (0 conflicting)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/17] Installing libcjson-1.7.18_2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/17] Extracting libcjson-1.7.18_2: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/17] Installing libpaper-1.1.28_1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/17] Extracting libpaper-1.1.28_1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/17] Installing libcbor-0.11.0...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/17] Extracting libcbor-0.11.0: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/17] Installing uchardet-0.0.8_1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/17] Extracting uchardet-0.0.8_1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/17] Installing cyrus-sasl-2.1.28_5...
*** Added group `cyrus' (id 60)
*** Added user `cyrus' (id 60)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/17] Extracting cyrus-sasl-2.1.28_5: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/17] Installing psutils-1.17_6...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/17] Extracting psutils-1.17_6: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/17] Installing perl5-5.36.3_2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/17] Extracting perl5-5.36.3_2: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/17] Installing groff-1.23.0_3...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/17] Extracting groff-1.23.0_3: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/17] Installing hidapi-0.14.0...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/17] Extracting hidapi-0.14.0: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/17] Installing libunwind-20240221...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/17] Extracting libunwind-20240221: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/17] Installing openldap26-client-2.6.8...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/17] Extracting openldap26-client-2.6.8: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/17] Installing libfido2-1.15.0...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/17] Extracting libfido2-1.15.0: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/17] Installing mysql80-client-8.0.39...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/17] Extracting mysql80-client-8.0.39: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/17] Installing postgresql16-client-16.4...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/17] Extracting postgresql16-client-16.4: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/17] Installing sqlite3-3.46.1,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/17] Extracting sqlite3-3.46.1,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [16/17] Installing hiredis-1.2.0.15...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [16/17] Extracting hiredis-1.2.0.15: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [17/17] Installing turnserver-4.6.2_1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [17/17] Extracting turnserver-4.6.2_1: .......... done
=====
Message from cyrus-sasl-2.1.28_5:
--
You can use sasldb2 for authentication, to add users use:
saslpasswd2 -c username
If you want to enable SMTP AUTH with the system Sendmail, read
Sendmail.README
NOTE: This port has been compiled with a default pwcheck_method of
auxprop. If you want to authenticate your user by /etc/passwd,
PAM or LDAP, install ports/security/cyrus-sasl2-saslauthd and
set sasl_pwcheck_method to saslauthd after installing the
Cyrus-IMAPd 2.X port. You should also check the
/usr/local/lib/sasl2/*.conf files for the correct
pwcheck_method.
If you want to use GSSAPI mechanism, install
ports/security/cyrus-sasl2-gssapi.
If you want to use SRP mechanism, install
ports/security/cyrus-sasl2-srp.
If you want to use LDAP auxprop plugin, install
ports/security/cyrus-sasl2-ldapdb.
=====
Message from groff-1.23.0_3:
--
In order to be able to use the html driver, you need to install the following
packages:
- ghostscript
- netpbm
=====
Message from openldap26-client-2.6.8:
--
The OpenLDAP client package has been successfully installed.
Edit
/usr/local/etc/openldap/ldap.conf
to change the system-wide client defaults.
Try `man ldap.conf' and visit the OpenLDAP FAQ-O-Matic at
http://www.OpenLDAP.org/faq/index.cgi?file=3
for more information.
=====
Message from mysql80-client-8.0.39:
--
This is the mysql CLIENT without the server.
for complete server and client, please install databases/mysql80-server
=====
Message from postgresql16-client-16.4:
--
The PostgreSQL port has a collection of "side orders":
postgresql-docs
For all of the html documentation
p5-Pg
A perl5 API for client access to PostgreSQL databases.
postgresql-tcltk
If you want tcl/tk client support.
postgresql-jdbc
For Java JDBC support.
postgresql-odbc
For client access from unix applications using ODBC as access
method. Not needed to access unix PostgreSQL servers from Win32
using ODBC. See below.
ruby-postgres, py-psycopg2
For client access to PostgreSQL databases using the ruby & python
languages.
postgresql-plperl, postgresql-pltcl & postgresql-plruby
For using perl5, tcl & ruby as procedural languages.
postgresql-contrib
Lots of contributed utilities, postgresql functions and
datatypes. There you find pg_standby, pgcrypto and many other cool
things.
etc...
=====
Message from turnserver-4.6.2_1:
--
1) You can start and stop the turnserver manually. But, if you want
to enable turnserver as an automatically started system service,
you have to:
a) Create and edit /usr/local/etc/turnserver.conf file.
Use /usr/local/etc/turnserver.conf.default as an example.
b) For user accounts settings: set up SQLite or PostgreSQL or
MySQL or Redis database for user accounts.
Use /usr/local/share/turnserver/schema.sql as an SQL database schema,
or use /usr/local/share/turnserver/schema*redis as Redis database description.
If SQLite is used, then /usr/local/var/db/turndb is the default database
location.
d) add line turnserver_enable="YES" to /etc/rc.conf.
e) If you are using a non-default PREFIX (other than /usr/local),
then edit /usr/local/etc/rc.d/turnserver file, according to
your system settings.
f) Restart the system or run the command:
$ /usr/local/etc/rc.d/turnserver start
2) If you do not want the turnserver to be a system service,
then you can start/stop it "manually", using the "turnserver"
executable with appropriate options (see the documentation).
3) To create database schema, use schema in file /usr/local/share/turnserver/schema.sql.
The TURN Server supports (optionally) SQLite, MySQL, PostgreSQL, Redis.
4) For additional information, run:
$ man turnserver
$ man turnadmin
$ man turnutils
Step 22: Install package jitsi-meet
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 42 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
alsa-lib: 1.2.12
brotli: 1.1.0,1
dejavu: 2.37_3
encodings: 1.1.0,1
font-bh-ttf: 1.0.3_5
font-misc-ethiopic: 1.0.4
font-misc-meltho: 1.0.3_5
fontconfig: 2.15.0_3,1
freetype2: 2.13.3
giflib: 5.2.2
javavmwrapper: 2.7.10
jbigkit: 2.1_3
jicofo: 1.0.1062
jitsi-meet: 1.0.7762
jitsi-meet-full: 2.0.9220_1
jitsi-prosody-plugins: 2.0.9220_1
jitsi-srtp-native: 1.1.8
jitsi-videobridge: 2.3.67
jpeg-turbo: 3.0.4
lcms2: 2.16_2
lerc: 4.0.0
libICE: 1.1.1,1
libSM: 1.2.4,1
libX11: 1.8.9,1
libXau: 1.0.11
libXdmcp: 1.1.5
libXext: 1.3.6,1
libXfixes: 6.0.1
libXi: 1.8.1,1
libXrandr: 1.5.4
libXrender: 0.9.11
libXt: 1.3.0,1
libXtst: 1.2.4
libdeflate: 1.22
libfontenc: 1.1.8
libxcb: 1.17.0
mkfontscale: 1.2.3
openjdk11: 11.0.24+8.1_1
png: 1.6.44
tiff: 4.6.0
xorg-fonts-truetype: 7.7_1
xorgproto: 2024.1
Number of packages to be installed: 42
The process will require 486 MiB more space.
250 MiB to be downloaded.
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/42] Fetching png-1.6.44.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/42] Fetching javavmwrapper-2.7.10.pkg: ... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/42] Fetching libxcb-1.17.0.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/42] Fetching freetype2-2.13.3.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/42] Fetching jpeg-turbo-3.0.4.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/42] Fetching libXt-1.3.0,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/42] Fetching jitsi-meet-full-2.0.9220_1.pkg: . done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/42] Fetching libfontenc-1.1.8.pkg: ..... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/42] Fetching openjdk11-11.0.24+8.1_1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/42] Fetching jitsi-videobridge-2.3.67.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/42] Fetching libXrandr-1.5.4.pkg: ........ done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/42] Fetching lcms2-2.16_2.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/42] Fetching font-bh-ttf-1.0.3_5.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/42] Fetching brotli-1.1.0,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/42] Fetching mkfontscale-1.2.3.pkg: .... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [16/42] Fetching libdeflate-1.22.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [17/42] Fetching libXext-1.3.6,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [18/42] Fetching libXfixes-6.0.1.pkg: ... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [19/42] Fetching libXau-1.0.11.pkg: .. done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [20/42] Fetching libICE-1.1.1,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [21/42] Fetching fontconfig-2.15.0_3,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [22/42] Fetching jitsi-meet-1.0.7762.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [23/42] Fetching jitsi-srtp-native-1.1.8.pkg: .. done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [24/42] Fetching libSM-1.2.4,1.pkg: ..... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [25/42] Fetching font-misc-ethiopic-1.0.4.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [26/42] Fetching libX11-1.8.9,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [27/42] Fetching libXrender-0.9.11.pkg: ....... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [28/42] Fetching giflib-5.2.2.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [29/42] Fetching xorgproto-2024.1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [30/42] Fetching jitsi-prosody-plugins-2.0.9220_1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [31/42] Fetching libXtst-1.2.4.pkg: .... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [32/42] Fetching libXi-1.8.1,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [33/42] Fetching jbigkit-2.1_3.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [34/42] Fetching font-misc-meltho-1.0.3_5.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [35/42] Fetching jicofo-1.0.1062.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [36/42] Fetching libXdmcp-1.1.5.pkg: ..... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [37/42] Fetching tiff-4.6.0.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [38/42] Fetching encodings-1.1.0,1.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [39/42] Fetching alsa-lib-1.2.12.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [40/42] Fetching xorg-fonts-truetype-7.7_1.pkg: . done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [41/42] Fetching dejavu-2.37_3.pkg: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [42/42] Fetching lerc-4.0.0.pkg: .......... done
Checking integrity... done (0 conflicting)
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/42] Installing xorgproto-2024.1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [1/42] Extracting xorgproto-2024.1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/42] Installing libXau-1.0.11...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [2/42] Extracting libXau-1.0.11: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/42] Installing libXdmcp-1.1.5...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [3/42] Extracting libXdmcp-1.1.5: ......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/42] Installing png-1.6.44...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [4/42] Extracting png-1.6.44: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/42] Installing libxcb-1.17.0...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [5/42] Extracting libxcb-1.17.0: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/42] Installing brotli-1.1.0,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [6/42] Extracting brotli-1.1.0,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/42] Installing freetype2-2.13.3...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [7/42] Extracting freetype2-2.13.3: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/42] Installing libfontenc-1.1.8...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [8/42] Extracting libfontenc-1.1.8: ......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/42] Installing libX11-1.8.9,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [9/42] Extracting libX11-1.8.9,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/42] Installing jpeg-turbo-3.0.4...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [10/42] Extracting jpeg-turbo-3.0.4: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/42] Installing mkfontscale-1.2.3...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [11/42] Extracting mkfontscale-1.2.3: ....... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/42] Installing libdeflate-1.22...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [12/42] Extracting libdeflate-1.22: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/42] Installing libXext-1.3.6,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [13/42] Extracting libXext-1.3.6,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/42] Installing libXfixes-6.0.1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [14/42] Extracting libXfixes-6.0.1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/42] Installing libICE-1.1.1,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [15/42] Extracting libICE-1.1.1,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [16/42] Installing fontconfig-2.15.0_3,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [16/42] Extracting fontconfig-2.15.0_3,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [17/42] Installing jbigkit-2.1_3...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [17/42] Extracting jbigkit-2.1_3: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [18/42] Installing lerc-4.0.0...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [18/42] Extracting lerc-4.0.0: ........ done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [19/42] Installing font-bh-ttf-1.0.3_5...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [19/42] Extracting font-bh-ttf-1.0.3_5: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [20/42] Installing libSM-1.2.4,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [20/42] Extracting libSM-1.2.4,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [21/42] Installing font-misc-ethiopic-1.0.4...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [21/42] Extracting font-misc-ethiopic-1.0.4: ...... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [22/42] Installing libXrender-0.9.11...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [22/42] Extracting libXrender-0.9.11: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [23/42] Installing libXi-1.8.1,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [23/42] Extracting libXi-1.8.1,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [24/42] Installing font-misc-meltho-1.0.3_5...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [24/42] Extracting font-misc-meltho-1.0.3_5: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [25/42] Installing tiff-4.6.0...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [25/42] Extracting tiff-4.6.0: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [26/42] Installing encodings-1.1.0,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [26/42] Extracting encodings-1.1.0,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [27/42] Installing dejavu-2.37_3...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [27/42] Extracting dejavu-2.37_3: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [28/42] Installing javavmwrapper-2.7.10...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [28/42] Extracting javavmwrapper-2.7.10: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [29/42] Installing libXt-1.3.0,1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [29/42] Extracting libXt-1.3.0,1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [30/42] Installing libXrandr-1.5.4...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [30/42] Extracting libXrandr-1.5.4: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [31/42] Installing lcms2-2.16_2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [31/42] Extracting lcms2-2.16_2: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [32/42] Installing giflib-5.2.2...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [32/42] Extracting giflib-5.2.2: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [33/42] Installing libXtst-1.2.4...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [33/42] Extracting libXtst-1.2.4: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [34/42] Installing alsa-lib-1.2.12...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [34/42] Extracting alsa-lib-1.2.12: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [35/42] Installing xorg-fonts-truetype-7.7_1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [35/42] Extracting xorg-fonts-truetype-7.7_1: ... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [36/42] Installing openjdk11-11.0.24+8.1_1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [36/42] Extracting openjdk11-11.0.24+8.1_1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [37/42] Installing jitsi-videobridge-2.3.67...
===> Creating groups
Creating group 'jvb' with gid '308'
Creating group 'jitsi' with gid '306'
===> Creating users
Creating user 'jvb' with uid '308'
Creating user 'jitsi' with uid '306'
Adding user 'jitsi' to group 'jvb'
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [37/42] Extracting jitsi-videobridge-2.3.67: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [38/42] Installing jitsi-meet-1.0.7762...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [38/42] Extracting jitsi-meet-1.0.7762: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [39/42] Installing jitsi-srtp-native-1.1.8...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [39/42] Extracting jitsi-srtp-native-1.1.8: .... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [40/42] Installing jitsi-prosody-plugins-2.0.9220_1...
===> Creating groups
Using existing group 'jitsi'
===> Creating users
Using existing user 'jitsi'
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [40/42] Extracting jitsi-prosody-plugins-2.0.9220_1: .......... done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [41/42] Installing jicofo-1.0.1062...
===> Creating groups
Creating group 'jicofo' with gid '307'
Using existing group 'jitsi'
===> Creating users
Creating user 'jicofo' with uid '307'
Using existing user 'jitsi'
Adding user 'jitsi' to group 'jicofo'
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [41/42] Extracting jicofo-1.0.1062: ........ done
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [42/42] Installing jitsi-meet-full-2.0.9220_1...
[jitsi-meet-amd64-14_1.vsf00002.cpt.za.honeyguide.net] [42/42] Extracting jitsi-meet-full-2.0.9220_1: ... done
==> Running trigger: fontconfig.ucl
Running fc-cache to build fontconfig cache...
=====
Message from freetype2-2.13.3:
--
The 2.7.x series now uses the new subpixel hinting mode (V40 port's option) as
the default, emulating a modern version of ClearType. This change inevitably
leads to different rendering results, and you might change port's options to
adapt it to your taste (or use the new "FREETYPE_PROPERTIES" environment
variable).
The environment variable "FREETYPE_PROPERTIES" can be used to control the
driver properties. Example:
FREETYPE_PROPERTIES=truetype:interpreter-version=35 \
cff:no-stem-darkening=1 \
autofitter:warping=1
This allows to select, say, the subpixel hinting mode at runtime for a given
application.
If LONG_PCF_NAMES port's option was enabled, the PCF family names may include
the foundry and information whether they contain wide characters. For example,
"Sony Fixed" or "Misc Fixed Wide", instead of "Fixed". This can be disabled at
run time with using pcf:no-long-family-names property, if needed. Example:
FREETYPE_PROPERTIES=pcf:no-long-family-names=1
How to recreate fontconfig cache with using such environment variable,
if needed:
# env FREETYPE_PROPERTIES=pcf:no-long-family-names=1 fc-cache -fsv
The controllable properties are listed in the section "Controlling FreeType
Modules" in the reference's table of contents
(/usr/local/share/doc/freetype2/reference/index.html, if documentation was installed).
=====
Message from dejavu-2.37_3:
--
Make sure that the freetype module is loaded. If it is not, add the following
line to the "Modules" section of your X Windows configuration file:
Load "freetype"
Add the following line to the "Files" section of X Windows configuration file:
FontPath "/usr/local/share/fonts/dejavu/"
Note: your X Windows configuration file is typically /etc/X11/XF86Config
if you are using XFree86, and /etc/X11/xorg.conf if you are using X.Org.
=====
Message from openjdk11-11.0.24+8.1_1:
--
This OpenJDK implementation requires fdescfs(5) mounted on /dev/fd and
procfs(5) mounted on /proc.
If you have not done it yet, please do the following:
mount -t fdescfs fdesc /dev/fd
mount -t procfs proc /proc
To make it permanent, you need the following lines in /etc/fstab:
fdesc /dev/fd fdescfs rw 0 0
proc /proc procfs rw 0 0
=====
Message from jitsi-videobridge-2.3.67:
--
Jitsi Video Bridge was installed
1) Edit the configuration file located at:
/usr/local/etc/jitsi/videobridge/jitsi-videobridge.conf
2) Enable the service:
# service jitsi-videobridge enable
3) Additional jitsi-videobridge properties to control the TCP-related
functionality can be defined at:
/usr/local/etc/jitsi/videobridge/sip-communicator.properties
4) If jitsi-videobridge server is running behind NAT, you must add the
following lines to the sip-comunnicator.properties file
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=Local_IP_Address
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=Public_IP_Address
Also, you must redirect TCP/4443 and UDP/10000 ports to jitsi-videobridge
server.
5) More about jitsi-videobridge properties at:
https://github.com/jitsi/jitsi-videobridge/blob/master/doc/tcp.md
6) Enjoy it
=====
Message from jitsi-meet-1.0.7762:
--
Jitsi Meet was installed
1) Jitsi Meet needs the following apps as minimal to work
www/nginx
net-im/prosody
net-im/jitsi-prosody-plugins
net-im/jicofo
net-im/jitsi-videobridge
2) You can find a basic configuration example here:
/usr/local/share/examples/jitsi/nginx.conf
3) Configuration and interface options files are installed like
/usr/local/www/jitsi-meet/config.js.sample
/usr/local/www/jitsi-meet/interface_config.js.sample
Copy these files to
/usr/local/www/jitsi-meet/config.js
/usr/local/www/jitsi-meet/interface_config.js
4) Enjoy it
=====
Message from jicofo-1.0.1062:
--
Jitsi Conference Focus was installed
1) Edit the configuration file located at:
/usr/local/etc/jitsi/jicofo/jicofo.conf
2) Enable the service:
# service jicofo enable
3) For use of jicofo with net-im/prosody, you need to import prosody's
auth.jitsi.example.com TLS certificate into a Java truststore.
You should also install net-im/jitsi-prosody-plugins.
The startup rcfile will pass this filename to jicofo:
/usr/local/etc/jitsi/jicofo/truststore.jks - for example:
# prosodyctl cert generate jitsi.example.com
# prosodyctl cert generate auth.jitsi.example.com
# keytool -noprompt -keystore /usr/local/etc/jitsi/jicofo/truststore.jks -importcert \
-alias prosody -file /path/to/prosody/auth.jitsi.example.com.crt
4) Enjoy it
Step 23: Clean package installation
Nothing to do.
Step 24: Clean cook artifacts
Step 25: Install pot local
Step 26: Set file ownership on cook scripts
Step 27: Make cook script executable
setting executable bit on /usr/local/bin/cook
Step 28: Create rc.d script to start cook
creating rc.d script to start cook
Step 29: Make rc.d script to start cook executable
Setting executable bit on cook rc file
Step 30: Enable cook service
enabling cook
cook enabled in /etc/rc.conf
=====> Stop the pot jitsi-meet-amd64-14_1
=====> Remove p4672bcb553f7f epair network interfaces
=====> unmount /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/tmp
=====> unmount /mnt/srv/pot/jails/jitsi-meet-amd64-14_1/m/dev
===> exporting jitsi-meet-amd64-14_1 @ 1730923500 to /tmp/jitsi-meet-amd64-14_1_0.20.3.xz