FreeBSD

LibreNMS 26.6.0 & itable cache directories vntl/var/db/

I updated my version of LibreNMS to 26.6.0 and there are “decent sized refactor to the rrd processes” – I’m seeing the following: This is an issue with fontconfig The advice I was given: “XDG_CACHE_HOME might help, but I’m not sure if that is the right fix…” I first created a new directory (I’ve since discovered creating the directory is not necessary, adding the configuration item is sufficient): [12:45 besser dvl /var/db/librenms] % […]

LibreNMS 26.6.0 & itable cache directories vntl/var/db/ Read More »

Getting Victoria Logs running on FreeBSD

This post is only about getting Victoria Logs running on FreeBSD. A future post will go over configuration and getting logs in. I’m hoping Victoria Logs can fill the role which ElasticSearch once tried to fill, but failed; it was too finicky and fragile for my use. In this post: FreeBSD 15.0 victoria-logs-1.50.0_2 mkjail-0.0.8 Jail creation I’m going to run this in a jail, like most things. You don’t have to. I’m using

Getting Victoria Logs running on FreeBSD Read More »

Giving poudriere a jump start

From time to time, I build my ports for a different version of MySQL, or Python, or, as in tonights case, PHP. My usual build command is: [23:43 pkg01 dvl ~] % sudo poudriere bulk -j 150amd64 -p default -z primary -f /usr/local/etc/poudriere.d/buildlists/primary In this post: FreeBSD 15.0 poudriere-3.4.8 For me to build against PHP85, I first created this file: [23:56 pkg01 dvl /usr/local/etc/poudriere.d] % cat 150amd64-default-php85-make.conf DEFAULT_VERSIONS+= php=85 With that file in

Giving poudriere a jump start Read More »

How changes to poudriere.conf affect the build time

NOTE: I was starting my 6th build when I realized the log links are not publicly accessible. Sorry about that: https://pkg02.int.unixathome.org/ should not resolve for you. I have a new server in the basement, known as r7425-01 – it’s beefy. It’s newer than the other hosts I have. Should I retire one of the older servers? First, let’s see if it’s faster. My primary use case: building packages via poudriere. In this post:

How changes to poudriere.conf affect the build time Read More »

/usr/local/sbin/rrsync error: unsafe arg: / [”, ‘/usr/home/rsyncer/backups’]

On Monday morning, I had eight emails each notifying me of a failed rsync attempt. This is one of those messages: Well, that’s a new one to me. This post will eventually show you the solution, and if that’s what you need now, jump to the bottom. If you’re not in a rush, I’m sure the following reading will be funny and a cure for your insomnia. Wow, … that sounds like Michael

/usr/local/sbin/rrsync error: unsafe arg: / [”, ‘/usr/home/rsyncer/backups’] Read More »

newsyslog – telling it not to compress, for anything

In this post, I’m going to show you how I told FreeBSD’s newsyslog to ignore any compression directives and just rotate the file. I will also speculate about some historical items which may be widely incorrect. If you wish to correct any inaccuracies, I will update them here. In this post: FreeBSD 15 wild speculation as to how logging, newsyslog, and compression evovled many paragraphs which aren’t related, but you may find interesting,

newsyslog – telling it not to compress, for anything Read More »

migrating data02/freshports/dev-nginx01 to data04

This post will be short on detail. I’m writing it for myself, to document what I’m doing. I suspect Migrating data02/freshports/dev-ingress01 to another zpool will be more useful to you. In this post: FreeBSD 15.0 I stopped the jail: [15:30 r730-01 dvl ~] % sudo service jail stop dev-nginx01 Stopping jails: dev-nginx01. I took dev.freshports.org offline via: The source Now, you might look at that, and wonder why the filesystems are offline. This

migrating data02/freshports/dev-nginx01 to data04 Read More »

Cleaning up snapshots

Now that I’ve copied two filesets from one zpool to another, let’s delete old snapshots. In this post: FreeBSD 15.0 Freeing up space I’m still hesitant to delete original data, but I’ll delete the snapshots. Here’s my list: [20:25 r730-01 dvl ~] % zfs list -H -o name -r -t snapshot data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15 | grep -v for.data04.0 | less data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-15_00:00:03_daily data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-16_00:00:16_daily data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_00:00:07_daily data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_19:00:02_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_20:00:02_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_21:00:09_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_22:00:09_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_23:00:11_hourly … data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_19:15:13_frequently data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_19:30:02_frequently data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_19:45:11_frequently data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_20:00:01_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_20:00:01_frequently That

Cleaning up snapshots Read More »

after moving datasets, adjust configuration for sanoid and others

Earlier today, I moved two file systems from one zpool to another. I use sysutils/sanoid to take and manage snapshots of the more important data. In this post, I’ll update that configuration. Migrating ZFS filesystems from one zpool to another – same host Migrating data02/freshports/dev-ingress01 to another zpool These are the items which need updates: [20:04 r730-01 dvl ~] % sudo cp -p /usr/local/etc/sanoid/sanoid.conf /usr/local/etc/sanoid/sanoid.conf.backup.2026.04.19 [20:08 r730-01 dvl ~] % sudoedit /usr/local/etc/sanoid/sanoid.conf [20:03

after moving datasets, adjust configuration for sanoid and others Read More »

Migrating data02/freshports/dev-ingress01 to another zpool

I’m going to migrate data02/freshports/dev-ingress01 to the data04 This is before: [13:45 r730-01 dvl ~] % zfs list -r data02/freshports/dev-ingress01 NAME USED AVAIL REFER MOUNTPOINT data02/freshports/dev-ingress01 229G 60.6G 88K none data02/freshports/dev-ingress01/dvl-src 197G 60.6G 197G /jails/dev-ingress01/usr/home/dvl/src data02/freshports/dev-ingress01/freshports 22.9G 60.6G 2.09G /jails/dev-ingress01/var/db/freshports data02/freshports/dev-ingress01/freshports/cache 2.30M 60.6G 132K /jails/dev-ingress01/var/db/freshports/cache data02/freshports/dev-ingress01/freshports/cache/html 2.07M 60.6G 2.07M /jails/dev-ingress01/var/db/freshports/cache/html data02/freshports/dev-ingress01/freshports/cache/spooling 104K 60.6G 104K /jails/dev-ingress01/var/db/freshports/cache/spooling data02/freshports/dev-ingress01/freshports/message-queues 20.8G 60.6G 14.4M /jails/dev-ingress01/var/db/freshports/message-queues data02/freshports/dev-ingress01/freshports/message-queues/archive 20.8G 60.6G 11.7G /jails/dev-ingress01/var/db/freshports/message-queues/archive data02/freshports/dev-ingress01/ingress 5.39G 60.6G 132K /jails/dev-ingress01/var/db/ingress data02/freshports/dev-ingress01/ingress/latest_commits 528K 60.6G

Migrating data02/freshports/dev-ingress01 to another zpool Read More »

Scroll to Top