-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unifi Controller does not Produce Backups #512
Comments
Fwiw, this bug is also occurring in 6.5.55 (which is latest as of writing this). |
@mountaindude can you provide a copy of your docker-compose or docker run command line? This works on my setup so I want to look at narrowing down the common difference between my setup and you guys. |
Of course! Running Docker 20.10.12, build e91ed57 on Ubuntu 18.04.6 LTS docker-compose is pretty much standard except I hardcoded the container names, plus a few extra labels (should not affect things).
I also notice some log errors relating to the scheduled backups.
|
@jacobalberty Do you want to track these issues in separate posts? I checked and it looks like the auto backup errors in the log are related to the fact that
Digging a bit deeper, permissions on that backup directory looks funky.
From within the running container, these are the non-standard/Linux-out-of-the-box users available:
On the host we instead have an old account no longer used on that id
...and the directory on the host where docker-compose lives looks like this.
|
In your configuration yeah it should be So the problem you're running into is the same one I've been struggling to come up with a solution to in #362 / #373 I do not have a good solution as of yet. On my setup I manually chown those directories to be owned by the unifi uid/gid (default 999/999) I've investigated using a setuid binary to change permissions style solution but I haven't found one that felt right to me yet. |
Ok makes sense. I'll move things around on this server, freeing up 999:999 on the host etc. |
Yup, that did the trick. I can now do manual backup downloads as expected.
But I guess the backup file was created anyway, because it downloaded just fine. I've set an auto-backup to execute in ca 25 minutes, will report back what happened. I'd be happy to do a short writeup on the steps/commands needed to solve this. Where would that best go? In a markdown file in the examples folder? Maybe a reference from the readme to the more exhaustive description in the examples folder? |
That sounds good to me |
The scheduled auto-backup that just ran resulted in an error in the log files:
But the backup was created anyway, so I suspect this happens just the first time when that file doesn't exist. Will include the above in the howto/writeup too. |
This is quite likely fixed in |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Operating system
Ubuntu Linux 20.04.3 LTS
UniFi Tag
6.2.23
Docker run
docker-compose up -d
Bug description
The Unifi Controller is not creating backups, autobackups, nor will it download/create a backup when requested within the controller itself.
Backup files are not being generated in the volumes of the OS.
Placing old backups (created before moving to Docker Unifi) in the volumes directory are not visible as well.
Compose File
docker-unifi-backup-issue_docker-compose.txt
Steps to reproduce
[ Setting up Autobackup ]
Log into Unifi Controller as Super User
Settings > Backup > [Configure settings for autobackup]
*No backups are created as time progresses (based on settings)
[ Downloading Backup File ]
Log into Unifi Controller as Super User
Settings > Backup
Select "Download Backup" button
*Button just spins (for hours) with no resolution
*Refreshing the page allows me to press the button again
Relevant log output
None. No errors or issues appear in the logs related to creating backups.
The text was updated successfully, but these errors were encountered: