After encountering a rare instance where processing a FreeBSD commit caused FreshPorts to run low on resources, I want to investigate how limiting a jail might help this situation. I searched for ‘jail limit’ – found sentencing guidelines. I searched for ‘jail limit freebsd’ and found a FreeBSD Forums referring me to rctl(8), which I […]
How to limit a jail Read More »
The FreshPorts dev, test, and stage websites are hosted on a server in my basement. Each instance consists of two jails: an ingress node – for pulling in new commits (and other data) into the database. a webserver node – for displaying the web pages. The new drives: Sometimes the zpool gets too close to
Upgrading an NVMe zpool from 222G to 1TB drives Read More »
This is just rough notes for myself. List the gpart output for each drive in my system. for drive in $(sysctl -n kern.disks) do gpart show $drive done gpart: No such geom: da11. => 40 9767541088 da10 GPT (4.5T) 40 8392664 – free – (4.0G) 8392704 9758048256 3 freebsd-zfs (4.5T) 9766440960 1100168 – free –
Where’s my drives? Read More »
Home Assistant is not friendly for plain installs. It seems designed for containers or running everything out of pip install. That, in itself, is a disturbing trend I’ve seen on several projects (what? you’re not running a git cloned image?). I’ve seen reports of people running containers etc. However, I want to run this on
Getting Home Assistant running in a FreeBSD 13.1 jail Read More »
For years I’ve run the dev, test, and stage nodes for FreshPorts off servers in my basement. This meant that those hostnames have always pointed at my home IP address. I’d like to change that. I first started this using interactive commands (e.g. wg set) but found that approach unsatisfactory. I think directly editing the
Creating a wireguard connection between my home and colo Read More »
NOTE: I wrote this, got stuck, then went a slightly different direction: I stopped using wg set Instead, I updated the configuration files directly I was not satisfied with the wg approach Although it is great for modifying things on the file, I don’t think it helps novices learn Wireguard I’m leaving it here anyway.
Creating a wireguard connection between my home and colo – failed attempt Read More »
Here I am, sitting on a beach, writing a blog post, and sipping a cool adult beverage. Reading email. I see this: I quickly ssh into the host to check zpool status: Lines 15-17 are relevant. There was a resilver event, which completed at 08:49:48 The vdev state changed event occurred at 08:49:34 That all
mps0: IOC Fault 0x40007e23, Resetting Read More »
When updating to FreeBSD 13.1, I started getting these messages from sysutils/logcheck: egrep: trailing backslash (\) This post will document how I tracked down the problem. It is occurring on several hosts. In this post: FreeBSD 13.1 logcheck-1.3.24 Other similar issues I suspect the issue arises because of the change from egrep 2.5.1 under FreeBSD
logcheck – egrep: trailing backslash (\) Read More »
In this post, I will talk about how I modified my pkg configuration so I don’t have to modify it after upgrading a host/jail from one version of FreeBSD to another. You might say that you don’t have to do that. Perhaps you have a different configuration and aren’t doing what I’m doing. HEADS UP:
Making my pkg.conf configuration version independent Read More »
Today I encountered this. [r720-01 dan ~] % sudo freebsd-update fetch install 14:39:01 Looking up update.FreeBSD.org mirrors… 2 mirrors found. Fetching metadata signature for 13.0-RELEASE from update1.freebsd.org… done. Fetching metadata index… done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. I confirmed it was just the
freebsd-update fetch install -> Cowardly refusing to proceed any further. Read More »