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 seems to tie in, time-wise. More info than you want This displays vdev guids: Line 11 shows the […]
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 12.3 to egrep 2.6.0 under FreeBSD 13.1. After the upgrade, I also encountered some egrep: empty (sub)expression messages
logcheck – egrep: trailing backslash (\) Read More »
I forgot to enable compression on this FreshPorts node. I have no idea why/how. After doing this, I went to a directory with a lot of space and copied stuff around. [aws-1 dan /jails/ingress01/var/db/freshports/message-queues/archive] % sudo mv 2021_03.tar.gz 2021_03.tar.gz.tmp 21:01:28 [aws-1 dan /jails/ingress01/var/db/freshports/message-queues/archive] % sudo mv 2021_03.tar.gz.tmp 2021_03.tar.gz 21:01:38 That will free up *some* space. But really, most of this zpool really needs to have zfs send | zfs recv done on each
I forgot to enable compression on ZFS 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: I hit a problem with this approach when updating a jail using mkjail: see https://github.com/mkjail/mkjail/issues/30 In this post:
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 fetch portion. [r720-01 dan ~] % sudo freebsd-update fetch 14:42:08 Looking up update.FreeBSD.org mirrors… 2 mirrors found. Fetching
freebsd-update fetch install -> Cowardly refusing to proceed any further. Read More »
It was May 2021 when I tweeted about monitoring FreeBSD jails which had jail IP addresses only in the 127.0.0.0/8 range. Yesterday, nearly 6 months later, I did the first test of this. This came up because I’m getting a new FreshPorts node ready. I’ve created a file in the jail to be run from the host. That script runs in the jail but it initiated by a process on the host. In
Monitoring FreeBSD jails from the host Read More »
Sometimes I mess up. Then I have to clean up and redo. These help me do that. This deletes FullAutoNoNextPool-12954 to FullAutoNoNextPool-12958. This creates FullAutoNoNextPool-12954 to FullAutoNoNextPool-12958.
Bacula: delete a range of volumes, create the same range Read More »
This started off as a Twitter thread earlier this morning. databases/mysql57-client has an optional dependency on security/cyrus-sasl2 which defaults to on. Let’s try turning that off and see if it also removes openldap-client from the dependency list. Why? I install net-mgmt/nagios-plugins in just above every jail and host. Even hosts which don’t use MySQL. I use poudriere to build all my own packages. I added this entry: # Trying to avoid pulling in
Turning off SASLCLIENT for databases/mysql57-client Read More »
Last last night, after renaming some buildlists, which were actually setnames, for poudriere, I realized that files in /usr/local/etc/poudriere.d also needed to be renamed. In this post: poudriere 3.3.7 nginx 1.20.1_2,2 Both running on FreeBSD 13.0-RELEASE-p4 These are my renamed files: [dan@pkg01:/usr/local/etc/poudriere.d]: $ ls *primary* primary-make.conf primary-poudriere.conf primaryi386-make.conf primaryi386-poudriere.conf The output of svn status illustrates the changes I made: [dan@pkg01:/usr/local/etc/poudriere.d]: $ svn st D master-list-i386-make.conf > moved to primaryi386-make.conf D master-list-i386-poudriere.conf > moved
poudriere: when renaming sets, also rename *-make.conf files etc Read More »
I like readability. I like it in variable names. I prefer something descriptive and easy to ready. In in this post: FreeBSD 13.0-RELEASE-p4 poudriere 3.3.7 I recently started getting messages like this from my daily poudiere build: I could just rename the sets, everything would be rebuilt, but then clients would be stuck pointing at the old no-longer built trees. To fix this easily, I will use symlinks. This is what clients use