Search Results for: bacula

r730-01

This is the Dell R730 host known as r730-01. For reference, the previous post on this server is still available. A few days ago, this host had a change in CPU and RAM. This is my primary developer server in my basement. gpart zpool list zpool status zfs list dmesg sesutil show jls pciconf (added 2025-09-27)

r730-01 Read More »

Post upgrade – checking the jails

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 sure that all the binaries had been updated from FreeBSD 13. Here’s what I did. This tells me

Post upgrade – checking the jails Read More »

Excluding some jails from upgrade

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 ~] % file /jails/*/bin/sh | grep 14 /jails/bacula/bin/sh: ELF 64-bit LSB pie executable, x86-64, version 1 (FreeBSD), dynamically linked,

Excluding some jails from upgrade Read More »

I figured out why pg_dump was failing with PostgreSQL 15-16

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 for the script was set to / In PostgreSQL < 15, the code used the database to determine

I figured out why pg_dump was failing with PostgreSQL 15-16 Read More »

While restoring my PostgreSQL database to a new FreeBSD server, I discovered the wrong database server in a configuration file

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. I ran a pg_dump on pg02 today. Then a pg_restore on pg03. That took about 6 hours I

While restoring my PostgreSQL database to a new FreeBSD server, I discovered the wrong database server in a configuration file Read More »

pg_dump: error: connection to server failed: fe_sendauth: no password supplied

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 the wrong database server in a configuration file. The backstory: dbclone dumps the bacula database hosted on pg02.

pg_dump: error: connection to server failed: fe_sendauth: no password supplied Read More »

Scroll to Top