<![CDATA[Latest quarterly FreeBSD package upgrade broke my Nextcloud 😮‍💨]]>Latest quarterly FreeBSD package upgrade broke my Nextcloud 😮‍💨

Post mortem: The new version of php85-pdo_pgsql is now compiled against PostgreSQL 18, not 17. So pkg upgrade removed postgresql17-server, leaving Nextcloud dysfunctional without a database.

Solution:
- Reinstalled postgresql17-server
- Dumped the db with pg_dump
- Installed postgresql18-server & php85-pdo_pgsql
- Copied over pg_hba.conf & postgresql.conf
- Created empty db/user in PG18
- Imported the db dump
- Ran occ maintenance:data-fingerprint

Restarted php-fpm & nginx

All fine again. But that was unpleasant 🙂

]]>https://board.circlewithadot.net/topic/924880d5-f6cb-4867-bb41-f89b444ba22e/latest-quarterly-freebsd-package-upgrade-broke-my-nextcloudRSS for NodeFri, 17 Apr 2026 10:18:40 GMTTue, 14 Apr 2026 10:36:45 GMT60<![CDATA[Reply to Latest quarterly FreeBSD package upgrade broke my Nextcloud 😮‍💨 on Tue, 14 Apr 2026 16:43:17 GMT]]>@freezr @Larvitz I wouldn’t say it broke it. When new DB server is required as dependency then pkg manager shows that previous server will be removed. This is signal for admin to dump/transfer data to new server. It seems that this time user overlooked what pkg manager said it will do.
Not sure how it is on other systems but on FreeBSD the package manger is not automagically transfer databases between servers when there is a major DB server update.

]]>https://board.circlewithadot.net/post/https://floss.social/users/t0maz/statuses/116404060021122864https://board.circlewithadot.net/post/https://floss.social/users/t0maz/statuses/116404060021122864Tue, 14 Apr 2026 16:43:17 GMT<![CDATA[Reply to Latest quarterly FreeBSD package upgrade broke my Nextcloud 😮‍💨 on Tue, 14 Apr 2026 13:50:51 GMT]]>@Larvitz

I don't really get it what you stated.
A OS that is supposedly to be tailored more toward server side rather than desktop site shouldn't break stuff... 🤷‍♂️

]]>https://board.circlewithadot.net/post/https://friendica.myportal.social/objects/e65e1095-9869-de46-3b20-40f746898209https://board.circlewithadot.net/post/https://friendica.myportal.social/objects/e65e1095-9869-de46-3b20-40f746898209Tue, 14 Apr 2026 13:50:51 GMT<![CDATA[Reply to Latest quarterly FreeBSD package upgrade broke my Nextcloud 😮‍💨 on Tue, 14 Apr 2026 10:49:42 GMT]]>@db_geek Yeah that wasn't ideal. But I could solve it in approx. 20 minutes via dump+restore. The php-pdo package now is linked to postgres18..

But that could have been avoided by using the FreeBSD Ports system (/usr/ports) where you have control about the dependencies of software. Not using ports was a trade-off, that I was aware which consequences it implies and I accepted that.

]]>https://board.circlewithadot.net/post/https://mastodon.bsd.cafe/users/Larvitz/statuses/116402669649412672https://board.circlewithadot.net/post/https://mastodon.bsd.cafe/users/Larvitz/statuses/116402669649412672Tue, 14 Apr 2026 10:49:42 GMT<![CDATA[Reply to Latest quarterly FreeBSD package upgrade broke my Nextcloud 😮‍💨 on Tue, 14 Apr 2026 10:45:23 GMT]]>@Larvitz 🤔
Sounds a little bit like Arch Linux.

Package of new PostgreSQL major version is stable?
So just replace package of installed PostgreSQL major version with new major version.
Database migration to new major version?
That's on you, user.
After that I learned something about IgnorePkg settings.
🙂

That's why I liked the slot mechanism of Gentoo, where such problems could be avoided.

]]>https://board.circlewithadot.net/post/https://norden.social/users/db_geek/statuses/116402652674383148https://board.circlewithadot.net/post/https://norden.social/users/db_geek/statuses/116402652674383148Tue, 14 Apr 2026 10:45:23 GMT