can’t re-use a leaf or module_register: module g_label already exists

For some time, I’ve seen these messages and been slightly bothered by them. Today, I found the solution. can’t re-use a leaf (geom_label)! can’t re-use a leaf (geom_part_gpt)! module_register: module g_label already exists! Module g_label failed to register: 17 module_register: module g_part_gpt already exists! Module g_part_gpt failed to register: 17 Those messages appeared on the […]

can’t re-use a leaf or module_register: module g_label already exists Read More »

zpool upgrade to get lz4_compress

FreeBSD now has zl4 compression for ZFS. But you must upgrade your pools to get it. If you try before upgrading, you’ll get: # zfs create -o recordsize=8k -o primarycache=metadata -o compress=lz4 system/usr/home/dan/pgsqlsql cannot create ‘system/usr/home/dan/pgsql’: pool must be upgraded to set this property or value So, let’s upgrade: # zpool upgrade -a This system

zpool upgrade to get lz4_compress Read More »

sym0: SCSI parity error detected: SCR1=1 DBC=11000036 SBCL=ae

This happened today: Nov 15 21:28:36 knew kernel: sym0: SCSI parity error detected: SCR1=1 DBC=11000036 SBCL=ae Nov 15 21:28:49 knew last message repeated 1611 times Nov 15 21:28:49 knew sudo: dan : TTY=pts/0 ; PWD=/usr/home/dan ; USER=root ; COMMAND=/sbin/camcontrol rescan all Nov 15 21:28:49 knew kernel: sym0: SCSI parity error detected: SCR1=1 DBC=11000036 SBCL=ae Nov

sym0: SCSI parity error detected: SCR1=1 DBC=11000036 SBCL=ae Read More »

temporary failure. Command output: maildrop: signal 0x19

Earlier this week, I started seeing this error on a FreeBSD 9.2 mail server running Postfix 2.10.1: CDDB71C56D53 37470 Mon Nov 11 16:22:45 MAILER-DAEMON (temporary failure. Command output: maildrop: signal 0x19) mailarchives@tallboy.unixathome.org I use maildrop, a procmail alternative. I first started using procmail in December 2000. It’s been a good 13 years, but it’s time.

temporary failure. Command output: maildrop: signal 0x19 Read More »

nagios plugin check_pgsql can’t handle all valid database names

I found a problem with the check_pgsql Nagios plugin last week. It can’t handle names such as freshports.org. It’s a valid database name, as witnessed here: $ psql -l | grep freshports freshports.old | dan | SQL_ASCII | C | C | freshports.org | dan | SQL_ASCII | C | C | But it doesn’t

nagios plugin check_pgsql can’t handle all valid database names Read More »

svn: E170000: Unrecognized URL scheme

If you see this message when trying to svn up: then you are missing a subversion compile option. Try this command: cd /usr/ports/devel/subversion && make config Then make sure this option is checked: [X] SERF WebDAV/Delta-V (HTTP/HTTPS) repo access module Then recompile subversion with one of these two commands: portupgrade -f subversion Or portmaster subversion

svn: E170000: Unrecognized URL scheme Read More »

Nvi saved the file sudoers.tmp

Have you ever seen a message like this? From: Nvi recovery program Subject: Nvi saved the file sudoers.tmp Date: November 3, 2013 6:48:00 PM EST To: root@slocum.example.org Reply-To: root@slocum.example.org On Thu Jul 25 18:55:42 2013, the user root was editing a file named /usr/local/etc/sudoers.tmp on the machine slocum.unixathome.org, when it was saved for recovery. You

Nvi saved the file sudoers.tmp Read More »

mounting the FreshPorts chroot within a jail

In my work on FreshPorts, I’ve learned more than the average non-committer about the FreeBSD ports tree and its oddities. Just about everything learns about a port it gets from ‘make -V’. Even this method can be fraught with difficulty. In an attempt to get the fairest information possible, FreshPorts uses a chroot solution, first

mounting the FreshPorts chroot within a jail Read More »

Scroll to Top