![unifi controller version unifi controller version](https://i.ytimg.com/vi/O32zHvRr4fg/maxresdefault.jpg)
Unifi controller version upgrade#
I did not bother updating to the latest version/s of mongodb nor upgrade to the shiniest, newest version/s of the Unifi Controller.) mongo localhost:
![unifi controller version unifi controller version](https://kontech.net/wp-content/uploads/No-devices-Found-–-Everything-is-Great-1024x474.jpg)
Re-installing Unifi on the old MongoDB version 3.4 was necessary as Unifi was the one that started up MongoDB using the specific Unifi-only data files.Īt this point, I was really pissed off, and I just chose to add in the “compatibility flag” as below (just in case I forget to next time) and simply restored the entire configuration from a back up. Just run apt-mark unhold against the 5 packages as per the NOTE below, then run apt upgrade again. Of course, the 5 packages have been “locked”, so will need to be unlocked to update…
Unifi controller version update#
Turns out, after a false start attempting to change the source server, I ended up finding this, and all I needed to do was to update the signature: echo "deb xenial/mongodb-org/3.4 multiverse" | sudo tee /etc/apt//mongodb-org-3.4.listĪpt-key adv -keyserver hkp://:80 -recv BC711F9BA15703C6Ĩ Update: After suffering through countless apt update errors due to mongodb source signature errors (but ignoring them), I finally sat down to try and fix this. mv /etc/nf /etc/Īpt purge mongo-tools mongodb-server mongodb-server-core unifiĪt this time, both Unifi and the MongoDB from the Ubuntu repository is gone, leaving only the files. To cut the long story short, I drove into the wall due to the above issue and had to, quite literally, downgrade MongoDB to 3.4, activate that stupid setting then upgrade again. To save you the trouble: simply (re-)installing MongoDB will not work as the upgrade pooched your MongoDB (read why, and also find the fix here ). Thereafter came the apt clean-up… apt -fix-broken installĪt this stage, you might actually see the Unifi was uninstalled. Fortunately, I managed to find the MongoDB data and some other files, so I just tar‘d them up – just in case… tar -zcvf ~/unifi_ /var/lib/unifi /usr/lib/ubiquity
![unifi controller version unifi controller version](https://i.ytimg.com/vi/Tm82IQCg4CU/maxresdefault.jpg)
Well, first off, I needed to make sure I backed up whatever files are left over. NOTE The “fix” offerred below is not really one – it does not restore your data, although you could conceivably do so if you got creative in restoring some data files before re-installing MongoDB version 3.4 as per below… The “official” fix is relatively useless, but that is another shouting match argument with another idiot person for a different time… Rooting around the Internet turned this thread up… And accordingly, there is a work-around, with some “clean-up” work. Apparently, the entire /usr/lib/unifi directory disappeared (alongside with MongoDB)! Ubiquiti’s Motto: If It Ain’t Broke, Don’t Won’t Fix ItĪfter my upgrade of my Ubuntu LTS 16.04 to 18.04, I discovered some things had broken, including the Unifi Controller used for my UAP-HD.