On Sat, Nov 22, 2025 at 5:52 AM Stuart Henderson <stu@spacehopper.org> wrote:
>
> On 2025/11/21 22:18, David Higgs wrote:
> > On Fri, Nov 21, 2025 at 8:14 AM Stuart Henderson <stu@spacehopper.org> wrote:
> > >
> > > On 2025/11/21 07:54, David Higgs wrote:
> > > > Since the upgrade to 7.8 (amd64, -stable) I am having problems
> > > > connecting to my unifi service from both the iOS app and webui.
> > > > FWIW, I use the github mirror to build it from -current ports and just
> > > > updated to this latest version without any success.
> > > >
> > > > Right now the unifi java process is just sitting there using 100% of a
> > > > CPU core.  I don't see a mongod process, but maybe this is why:
> > > >
> > > > [2025-11-21T07:50:57,464-05:00] <mongo-db> WARN  mongo  - Stop
> > > > listening to Mongo logs after process has exited
> > > > [2025-11-21T07:50:57,466-05:00] <mongo-db> INFO  mongo  - Database
> > > > process stopped, code=137
> > > > [2025-11-21T07:50:57,467-05:00] <mongo-db> WARN  mongo  - Unable to
> > > > delete repair file from path:/usr/local/share/unifi/run/db.needsRepair
> > > >
> > > > Was there some sort of flag day recently?  I've never done any mongodb
> > > > upgrades previously but maybe I should have?  Any advice?
> > >
> > > shouldn't be anything that's affected mongodb. mongodb build was broken
> > > for a while but that's fixed now.
> > >
> > > it can take a while for database schema changes to be applied after
> > > updating to a new version of unifi, but as mongod is not still running
> > > on your machine it can't be doing that. based on the log it looks like
> > > your db is possibly corrupt somehow.
> > >
> > > if you have a .unf backup (/usr/local/share/unifi/data/backup or
> > > /usr/local/share/unifi/data/backup/autobackup) then i'd suggest moving
> > > the old db out the way and rebuilding from that:
> > >
> > > rcctl stop unifi
> > > pkg_delete unifi
> > > mv /usr/local/share/unifi /usr/local/share/unifi.bak
> > > TRUSTED_PKG_PATH=/usr/ports/packages/amd64/all pkg_add unifi
> > > rcctl start unifi
> > >
> > > open the web interface; as it won't find an existing db it should offer
> > > the option of restoring from backup.
> > >
> > > if you don't have a backup then redoing the config is probably the
> > > best option.
> > >
> >
> > Hm, it looks like there's some mongodb upgrade that I didn't catch...
> >
> > @name mongodb-3.6.23p5
> > @url https://cdn.openbsd.org/pub/OpenBSD/7.6/packages/amd64/mongodb-3.6.23p5.tgz
> > @version 12
> > @signer openbsd-76-pkg
> >
> > I run `pkg_add -u` with every upgrade but it looks like dependencies
> > don't get auto-upgraded?  This was the first time in a while that I've
> > run sysclean, which is probably what finally broke mongodb.
>
> It wouldn't have been sysclean. sysclean does not list libraries unless
> they are unused by installed packages.
>
> More likely it would either be due to changes to the kernel/libc ABI (it
> is not expected that an old libc will keep working with a new kernel
> long term, this is often changed incompatibly every 2-3 releases or so)
> or the changes to libc making the FILE object opaque.

Good to know, but I think that is roughly what happened anyway due to
my mangled upgrade - my /usr was too small.

> You would either need to move the 3.6 database to a machine where 3.6
> can
> still run and follow the dump/restore steps in the pkg-readme for unifi,
> or clean and restore from .unf backup.

I removed unifi and the old mongodb, cleaned up, reinstalled unifi
(which installed a new mongodb), and loaded from backup.  Everything
is happy again though I don't quite understand why mongodb was never
updated.

> > Looks like I have a few other packages from other versions too:
> > @name p5-Error-0.17029
> > @signer openbsd-69-pkg
> > @name p5-Mail-Tools-2.21p0
> > @signer openbsd-69-pkg
> > @name p5-Time-TimeDate-2.33
> > @signer openbsd-69-pkg
>
> pkg_add -u only updates packages when there was a change. these ones
> don't include binaries and the relevant ports have been untouched for
> some time, so there's been no need to update them.

Cool. I figured that there'd be an upgrade because some portion of the
manifest had changed, e.g. old signify keys?  I force-upgraded them
anyways, and security(8) didn't comment, interestingly.

Thanks for the tips.

--david