«Oppgraderinger» i dag er bare «bloatware» med ingen ytelsesforbedringer, og er fullstappet med bakgrunnstjenester som overvåker deg og tapper maskinen for krefter.
BIND 9.10.4-P1 is out and available as
dns/bind910 as of r415882 in the FreeBSD ports tree.
Two of our name servers crashed in two different places within the Red-Black tree code of BIND 9.10.4:
general: rbt.c:2765: INSIST(sibling != ((void *)0)) failed, back trace #0 0x1880b in ?? general: exiting (due to assertion failure)
general: rbt.c:2726: INSIST(sibling != ((void *)0)) failed, back trace general: #0 0x0 in ?? general: exiting (due to assertion failure)
A new version of BIND is in the works. Stay patient, or switch back to 9.10.3-P4.
FreeBSD users can revert their ports tree back to r414265, duplicate
/usr/ports/dns/bind9103P4, rush the ports tree towards the present, and change the origin for BIND from
portupgrade -fpvo dns/bind9103P4 dns/bind910. Don’t forget to restart BIND, and change the origin once more when the successor of 9.10.4 is available.
One of my MySQL 5.7.12 instances refused to start after upgrading to FreeBSD’s MySQL port version 5.7.12_1, claiming:
2016-05-18T11:03:26.688719Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file '/var/db/mysql/ibdata1' is of a different size 4864 pages (rounded down to MB) than specified in the .cnf file: initial 8192 pages, max 0 (relevant if non-zero) pages!
“Googling” the error message led me to http://sharadchhetri.com/2014/11/29/upgrading-mysql-5-1-5-6-service-failed-start/. I added the following line to the
[mysqld] section in
innodb_data_file_path = ibdata1:10M:autoextend
At least MySQL is happy.
From the error message I deduced that the current
ibdata1 file has a length equal to 4864 pages × 16 KiB/page = 77824 KiB = 76 MiB, while MySQL 5.7.12 expects this to be at least 8192 pages × 16 KiB/page = 131072 KiB = 128 MiB. The current length was confirmed by running
ls -l /var/db/mysql/ibdata1:
-rw-r----- 1 mysql mysql 79691776 18 mai 13:03 /var/db/mysql/ibdata1
In the long run it’s better to retire the old
/var/db/mysql/my.cnf in favour of the “new”
I too was bitten by the
portupgrade uninstall error, due to broken pipes, on my laptop running FreeBSD/amd64 stable/10. Others have identified the
file 5.26 utility as the culprit, introduced in
stable/10 as r298920.
Watch PR 209211 for any progress.
base/head was corrected at r299234, and
stable/10 will follow soon. Continue reading portupgrade uninstall error, broken pipe
All FreeBSD systems under my care got upgraded last Friday to fix some NTP bugs. That upgrade introduced a new bug in the kernel. The bug first appeared at r298004 in
base/head, and later at r298134 in
base/stable/10. The i386-based systems were more notably affected than the amd64-based systems, as the former typically has less memory than the latter. Continue reading Memory leaks in recent stable/10 kernel
I received a cute email today. It has the usual traits of bad spelling, incorrect information, and other amusements. I wonder if the ID badge is genuine, but I doubt the name matches the pictured individual.
Received: from h1.flipio.ro (unknown [220.127.116.11]) by [WITHHELD] (Postfix) with ESMTP id B85CF94065; Tue, 3 May 2016 04:16:57 +0200 (CEST) Received: from [169.254.123.37] (134.red-81-32-237.dynamicip.rima-tde.net [18.104.22.168]) (Authenticated sender: email@example.com) by h1.flipio.ro (Postfix) with ESMTPA id EF2499BE65; Mon, 2 May 2016 08:17:33 +0300 (EEST) Subject: Finansdepartementet: Congratulations To: Recipients <firstname.lastname@example.org> From: Latin American Chamber <email@example.com> Date: Mon, 2 May 2016 07:17:30 +0200 Reply-To: <firstname.lastname@example.org>