UNMS not failing to create device backup about docker-unms HOT 13 CLOSED

@Nico640 Just to keep things updated; I'm in contact with one of the unms developers UI-Radek with regards to the above issue - logs and configs have been submitted to him and he's looking into it. He has mentioned there is no 'limit' that UI have imposed on backups per-se. Will feedback :-)

from docker-unms.

I've managed to get clean out some of the dpkg requirements in my config folder. Its now 3.1Mb and UNMS seems to be backing it up. They nonetheless have mentioned this will be resolved in a future edgemax firmware update.

from docker-unms.

This came up on the logs:

{"name":"UNMS","hostname":"eede6c7cf5db","pid":4152,"component":"ws","cid":516,"mac":"18:e8:29:2b:56:fb","level":40,"error":"RPC request error: 39baead3-275c-4e35-9a24-bc4091d4caea backupConfig (110022) backupConfig: unable to read backup file","msg":"Backup for device 7baa4911-f65b-4112-88f6-d0f93aaaa7d2 failed","time":"2019-10-18T12:56:27.166Z","v":0}

from docker-unms.

Hi,

I'm not sure what backup file UNMS is trying to read when creating a backup.
You can take a look inside the /config/unms/config-backups folder and check if all folders have the same permissions.
Also, check the /config/unms/config-backups/7baa4911-f65b-4112-88f6-d0f93aaaa7d2/ folder.
If everything looks normal, you can try to rename the 7baa4911-f65b-4112-88f6-d0f93aaaa7d2 folder and try to create a backup again.

from docker-unms.

@Nico640 I've just checked and there does not exist a 7baa* folder inside ~/config-backups/; running permission scripts now on unRAID and will retry the backup attempt.

Update:

root@Tower:/mnt/cache/appdata/unms/unms# stat config-backups/
  File: config-backups/
  Size: 72        	Blocks: 0          IO Block: 4096   directory
Device: 1fh/31d	Inode: 2364559     Links: 1
Access: (0777/drwxrwxrwx)  Uid: (   99/  nobody)   Gid: (  100/   users)
Access: 1970-01-01 01:00:00.000000000 +0100
Modify: 2019-10-18 13:52:51.912641117 +0100
Change: 2019-10-18 13:52:51.912641117 +0100
 Birth: 2019-01-21 16:11:21.521141123 +0000
root@Tower:/mnt/cache/appdata/unms/unms# cd config-backups/
root@Tower:/mnt/cache/appdata/unms/unms/config-backups# stat 44a97f97-5e6f-4cd7-8a37-fdbc7fa19d6a/
  File: 44a97f97-5e6f-4cd7-8a37-fdbc7fa19d6a/
  Size: 576       	Blocks: 0          IO Block: 4096   directory
Device: 1fh/31d	Inode: 19311486    Links: 1
Access: (0777/drwxrwxrwx)  Uid: (   99/  nobody)   Gid: (  100/   users)
Access: 2019-05-10 08:29:17.081034308 +0100
Modify: 2019-10-18 13:49:48.842837326 +0100
Change: 2019-10-18 13:49:48.842837326 +0100
 Birth: 2019-05-10 08:29:17.081034308 +0100

from docker-unms.

Hi, can you check whether you're able to manually back up the config by logging onto the device?

from docker-unms.

from docker-unms.

Hmm, my EdgePoint R6 (same architecture) is running on 2.0.6 and it's backups are only 2kb in size, however, it's only running in switch mode at the moment. This could be an problem with the websocket connection between UNMS and the device, which would explain why it works on the webGUI. I assume you already tried restarting both UNMS and the ERX-SFP?

from docker-unms.

from docker-unms.

I just confirmed that the issue is indeed the file size. I downloaded a 10mb dummy file onto the EdgePoint and the UNMS backup now fails, while I can still download it when directly accessing the device. I'll check if this also occurs with a normal UNMS install using the official install script.
The point at which it fails seems to be at around 5mb.

from docker-unms.

Hi, I found out that this also happens on a regular UNMS install. I'm not sure if the ~5MB limit is by design or whether it's a bug.
I think the only way for you to fix this is to either delete unnecessary stuff on the device so that the backups are under 5MB, or open a thread on the Ubiquiti UNMS forum and ask whether this is normal, however, I'm not sure if they help you when you're running on a unofficial image like this.

from docker-unms.

from docker-unms.

Latest update from Ubiquiti; there is a limit of 5MB. This has now been accepted and filed on their internal bug tracker; the issue will be resolved in a firmware update to the edgemax suite as opposed to a change to UNMS I believe.

from docker-unms.