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.