Closed NathanTheGr8 closed 5 years ago
Seeing the same issue. Created new dirs for a fresh install to make sure my DB wasnt corrupted. Issues persists on fresh pull.
I just noticed this in the read me.
Starting with Unifi Video 3.10.x, in-place upgrades are not fully supported. It's best to generate and save a backup file, and remove your data folder. Then restore the backup from the web setup page.
I will change unifi video to not auto update with watchtower. I will just have to bite the bullet and restore from a backup :(. I don't think I have a recent config backup, but that is my own fault.
Reading the Unifi release notes they say
To ensure a smooth upgrade path, NVR appliances must upgrade to 3.9.12 before upgrading to 3.10.0+
Looking at the Docker tags, I don't believe a 3.9.12 tag Docker contaner was ever released. We may need this along with some notes here how to upgrade.....
I am seeing the same thing. I think our issues are related #128
Possible, I ended up recreating my setup instead of fixing the issue. I will plan to do manual updates to this container in the future.
There's a tag for 3.9.12 now (and it works for me).
Funny enough though, the error I'm seeing is
2019-03-04T16:24:26.936-0500 I STORAGE [initandlisten] exception in initAndListen: 28662 Cannot start server. Detected data files in /usr/lib/unifi-video/data/db created by the 'wiredTiger' storage engine, but the specified storage engine was 'mmapv1'., terminating```
Not looking too good based on UBNT's release notes: https://community.ubnt.com/t5/UniFi-Video-Blog/UniFi-Video-3-10-1-Soft-Release/ba-p/2658279
upgrading an NVR from 3.9.12 to 3.10.0+ must be done via the web UI update. Subsequent updates can then be performed via apt, manual, etc. unless otherwise noted in the release notes.
@fryfrog were you able to upgrade from 3.9. to 3.10 or did you create a new instance?
I've been using the same unifi-video instance that I started with years ago, born outside a Docker container. I do all the unifi-video Docker changes in my own repo and make sure mine works before I even merge it to the beta channel.
So yes, mine has been working the whole time you guys have all been having issues and I still have no idea why. :/
Edit: In that time, all of my troubles have stemmed from the featureVersion
in mongodb. Instead of pinning the mongodb version to 3.2 or 3.4 or 3.6, I've been updating that in my db and running the latest monodb version. Which is what I switched the container to start doing too.
Does anyone know anything about wiredtiger versus mmapv1?
A fix for this ... edit /usr/lib/unifi-video/conf/mongodv3.0+.conf replace engine: mmapv1 with engine: wiredTiger
then restart the container.
Would be good to get this changed in the image.
Wouldn't anyone actually using wiredTiger be boned then?
I had a bad experiance updating. In the end I have removed the container, unmanaged the cameras and rebuilt a fresh directory and container. No matter what I tried I was getting errors all over the shop, some relating to chrome I suspect as Edge was stable for the config. I didnt have infinite ammount of time to debug.
Anyway CPU on my Synology is v low and its consuming about 2gb of RAM. Happy with that.
fwiw, I created a brand new container, grabbed the latest .zip backup from the backups folder in my Unifi Video volume and loaded that into the new container. Everything is working again. 🤷♂️
@acantril: Do you know what the heck the mongodv3.0+.conf
files are used for?
I don't remember doing anything to make it happen, but my unifi-video db is wiredTiger. :/
So 3.10.2 uses a mongod-wt.conf
which is really wiredTiger. Older versions don't. I'm closing this, but for future searchers... the overall solution is probably to upgrade the db from mmapv1
to wiredTiger
and then put it in the right place, the db-wt
folder.
I have two docker containers that broke when upgrading recently. I am not sure when it happened, maybe last week, but I noticed it yesterday. Looking at the docker logs I see this
So some error about java running out of resources? The system has and had plenty of free ram. I wasn't running the docker container with any sort of constraits. I recreated the container and got this error.
The "Waiting for mongodb to come online." appears to be from this project's bash script.
Below is the command I created the container with