As written, the script will only keep entries from the past 7 days.
Establish an SSH connection with the Cloud Key. Note: The Legacy Cloud Key (UC CK) utilizes the following: If the dataset has already grown too large to proceed with the db.repairDatabase() command there are instructions below to work around that. To be able to run a database repair, the Cloud Key will have to have enough free disk space equal to the size of the current data set plus 2 gigabytes. This repair may be needed for those who are suspecting invalid entries, corruption, or collection scaling issues. Getting back that valuable disk space on a 32-bit MongoDB instance will require a repair of the database. This process does not return useable disk space to the UniFi Host when the storage engine is MMAPv1. When running a compact command on the MongoDB, the database is rewritten and defragmented without error correction. While running the MMAPv1 storage engine this can cause issues when trying to shrink the aggregate collection sizes. The UniFi Network application service will not start due to database errors.ģ2-bit MongoDB collections are limited to a total size of 2GB. An error 400 is generated when trying to open UniFi Network. Settings-only backups cannot complete, or are created but are unable to be restored due to corruption. Backups including statistics data cannot be generated. Statistics are only recorded for a few days and then are cut off or are only intermittently available. We generally recommend using a UniFi OS Host for the best experience. 
Please note this only applies to users self-hosting the UniFi Network Server on their own Windows/macOS/Linux machine, or those hosting UniFi Network on a legacy Cloud Key.
Use this article to repair the database of malfunctioning UniFi Network applications.
0 kommentar(er)
