- #UNIFI CONTROLLER CLOUD KEY 32 BIT#
- #UNIFI CONTROLLER CLOUD KEY SOFTWARE#
- #UNIFI CONTROLLER CLOUD KEY PLUS#
If all is well, you should find the unifi controller interface is now back up and running on port 8443. After that, all you need to do now is re-start the unifi service: service unifi start Having run that, re-run the repair: mongod -dbpath /usr/lib/unifi/data/db -smallfiles -logpath /usr/lib/unifi/logs/server.log -repairĪnd that should sort it (check the logs to see). The command to run is this one: mv -vi /usr/lib/unifi/data/db/journal /usr/lib/unifi/data/db/journal-$(date -I) It says: In some cases, where the journal is corrupted, it will be helpful to run the following command before repairing the database, to move it to another location: To fix it I took the same step as described in the instructions for debian ( which are bit lower down on the same support article) Sun Feb 14 05:38:37.472 couldn't uncompress journal sectionĪlong with a similar stack trace as before. Sun Feb 14 05:38:37.368 recover skipping application of section more.
#UNIFI CONTROLLER CLOUD KEY PLUS#
Designed for easy deployment, the UCK G2 Plus can be quickly configured with UniFis Protect and Network mobile apps. Manage your UniFi devices simultaneously with the new multi-application UCK G2 Plus. Sun Feb 14 05:38:37.350 allocator: system The Cloud Key Gen2 Plus (UCK G2 Plus) is a compact, powerful UniFi OS Console with pre-installed UniFi Network and Protect applications and an upgradeable, 1 terabyte (TB) hard disk drive (HDD). Sun Feb 14 05:38:37.350 git version: nogitversion
#UNIFI CONTROLLER CLOUD KEY 32 BIT#
Sun Feb 14 05:38:37.349 ** 32 bit builds are limited to less than 2GB of data (or less with -journal). Sun Feb 14 05:38:37.349 ** NOTE: This is a 32 bit MongoDB binary. Mongod -dbpath /usr/lib/unifi/data/db -smallfiles -logpath /usr/lib/unifi/logs/server.log -repairīut this wasn't working for the same reason as before: Sun Feb 14 05:38:37.349 MongoDB starting : pid=5133 port=27017 dbpath=/usr/lib/unifi/data/db 32-bit host=UniFi-CloudKey I tried the mongodb repair steps ( detailed here on this ubiquiti support doc): service unifi stop Sun Feb 14 05:38:37.472 Assertion: 15874:couldn't uncompress journal section Having SSH'd onto the cloudkey and looking at the logs at /usr/lib/unifi/logs/server.log I found the following: Sun Feb 14 05:38:37.472 couldn't uncompress journal section
I just want something physical controlling my kit at home.This morning, I was having an issue where my cloud key appear to be running (SSH and the webui at :443 was up) but I couldn't connect to the controller interface on port 8443.
So, if I only want to use the Cloud Key for the local UniFi kit, am I going to have any issues? As a side benefit, I would also be able to try UniFi Protect but that’s not the main reason for using the Cloud Key.
#UNIFI CONTROLLER CLOUD KEY SOFTWARE#
The UniFi Cloud Key is an integrated computer and software controller minus the bulk. (thanks Tom for the video on that, it was very helpful) Introducing the UniFi Cloud Key, a miniaturized marvel of technology. Currently, the SG-3100 has a couple of NAT firewall rules to point to the VM, UniFi controller for external devices, I use HA Proxy on the SG-3100 for port 443. I was wondering if I can continue to host the external sites on the VM controller but manage my “home” UniFi equipment from the Cloud Key? I use a Netgate SG-3100 as the firewall but everything else is UniFi. Luckily, I recovered it without having to start from scratch. That said, I occasionally play with my lab and almost locked myself out of everything as I broke the server hosting the UniFi VM and then did not have an easy way to manage the UniFi switches and VLANS on certain ports.
I switched from the Cloud Key to hosting my own controller on a Ubuntu VM as I also host a few other sites in the UniFi controller. Fast forward to today and I now have two servers hosting VM’s using XCP-ng.
So I bought a Gen2 Cloud Key a while ago before I learned a lot more about networks.
0 kommentar(er)
