Without resorting to configuration tools, such as Ansible, I wonder if there is an easy way to avoid repeating a list of datasets within a jail configuration. First, some facts: FreeBSD 14.0 I use plain vanilla jails I know this can be easily scripted with a configuration tool; that is out of scope for this […]
Avoiding repetition within jail configurations Read More »
Stuff goes wrong. I like to check. Trust. But. Verify. Skip to the end for the list of useful commands. Here’s some of that verification, as briefly mentioned in FreeBSD 14 upgrade – files not removed by delete-old and Excluding some jails from upgrade. After upgrading all the jails on r730-01, I wanted to make
Post upgrade – checking the jails Read More »
I have some jails already updated to FreeBSD 14 – let’s get a list of what needs to be updated. This cold just as easily be used to get a list of what not to upgrade, if you didn’t want to update all jails right now. These jails are already updated: [15:30 r730-01 dvl ~]
Excluding some jails from upgrade Read More »
I was upgrading a jail (dns1) on r730-01 and I noticed this output from mkjail: In this post: FreeBSD 13.2 (upgrading from) FreeBSD 14.0 (upgrading to) mkjail-0.0.4 (upgrading with) EDIT: 2023-12-05 : This happened again when I updated the tallboy host. Looking at the mkjail source, I realized it had just completed the pkg upgrade
FreeBSD 14 upgrade – files not removed by delete-old Read More »
This post has been replaced by a newer post. For reference, the previous post on this server is still available. Today, the host was updated to FreeBSD 14.0, from FreeBSD 13.2. This is my primary developer server in my basement. gpart zpool list zpool status zfs list dmesg sesutil show jls
These are my notes on figuring out an upgrade path for the FreshPorts PostgreSQL 12.14 database hosted on Amazon RDS. Most of this is based on Upgrading the PostgreSQL DB engine for Amazon RDS The sections of this post relate to the sections found at the above URL. First, I installed the AWS CLI (via
Figuring out the upgrade path for AWS RDS from PostgreSQL 12.14 to PostgreSQL 16.1 Read More »
I have been using Bacula since 2004. It is my backup solution of choice, not only because it has a PostgreSQL backend, but it is flexible, robust, and reliable. I, on the other hand, have long ignored recent releases. I’m using Bacula 9.6.7 (released on 2021-01-26), roughly 3 years ago. Today, I started the upgrade
Bacula: Moving from 9.x to 13.x and upgrading the PostgreSQL database Read More »
In recent blog post, I outlined a problem I hit with pg_dump. Specifically, pg_dump was picking up and using ~/.pgpass with pg_dump from PostgreSQL 12-14, but with PostgreSQL 15-16, it was failing. In this blog post: FreeBSD 13.2 PostgreSQL server 12 / 16 PostgreSQL client 12-16 Bacula 9.6.7 Today we figured out why: $HOME. $HOME
I figured out why pg_dump was failing with PostgreSQL 15-16 Read More »
Lately, I’ve been preparing to move from PostgreSQL 12 to PostgreSQL 16 – my main developement database server at home needs to get updated. The goal: migrate each database from the old host (running PostgreSQL 12) to the new host (running PostgreSQL 16) using pg_dump and pg_restore. Today, I decided to migrate the Bacula database.
FYI, this problem has been solved and described in I figured out why pg_dump was failing with PostgreSQL 15-16. This morning I encountered this error message: In this post: FreeBSD 13.2 PostgreSQL 12.16 (server – pg02) PostgreSQL 16.1 (client – dbclone) See also While restoring my PostgreSQL database to a new FreeBSD server, I discovered
pg_dump: error: connection to server failed: fe_sendauth: no password supplied Read More »