cnMaestro 2.1.0 (On-Premises)

egor · January 17, 2019, 12:34am

I have same problem when i tried to restore database from 1.6.3-r39

123.PNG (146 KB)

Telemar · January 17, 2019, 11:39am

Another little bug:

In "default" tree don't show anymore the Towers throughput (empty)

(see attached file)

screen.JPG (13.1 KB)

Cambium_Ajay · January 17, 2019, 1:20pm

Hi,

We have analyzed the import issue on one of the setup and it looks like an issue with data created from a version probably older than 1.6.1. Anyway we are aggressively working on the fix and planning to make a 2.1.0 patch available on priority basis.

Thanks,

Ajay

dshea · January 17, 2019, 4:05pm

That makes sense - I had been running 1.6.0 for a long time, and only converted to 1.6.1 and upgraded to 1.6.3 right before the switch to 2.1.0.

I guess the relevant question is "does version 1.6.3 take a while to convert the database, perhaps in the background, or is it supposed to convert all the data at the time of the import?"

Usseglio_Gaudi_Franc · January 17, 2019, 4:06pm

Hi,

I can't restore from back 1.6.3-r39.

I have tried via command line and i got this error:

2019-01-17 15:59:59,283 - cns.migration - INFO - Publishing json data {'value': 25, 'account': 'cnmaestro', 'action': 'restore', 'status': 'PROGRESS'}
2019-01-17 16:00:01,457 - cns.migration - ERROR - Error in extract tar file /srv/storage/tmp/migration/uploads/cnmaestro-import.tar.gz to destination dir /srv/storage/tmp/migration/dumps
2019-01-17 16:00:01,457 - cns.migration - INFO - Cleaning restore files and directories!
2019-01-17 16:00:01,458 - cns.migration - ERROR - Failed restore!
2019-01-17 16:00:01,458 - cns.migration - ERROR - Command 'tar -xvf "/srv/storage/tmp/migration/uploads/cnmaestro-import.tar.gz" -C "/srv/storage/tmp/migration"' returned non-zero exit status 2
2019-01-17 16:00:01,458 - cns.migration - INFO - Publishing json data {'code': 'RESTORE_FAILED', 'cause': 'Failed to import data!', 'account': 'cnmaestro', 'action': 'restore', 'status': 'ERROR'}
2019-01-17 16:00:01,459 - cns.redis - INFO - Flushing redis db 4 ...
2019-01-17 16:00:01,461 - cns.migration - ERROR - Command 'tar -xvf "/srv/storage/tmp/migration/uploads/cnmaestro-import.tar.gz" -C "/srv/storage/tmp/migration"' returned non-zero exit status 2
closing postgres connection! host 127.0.0.1, port 5432, database cnmaestro_server, user postgres

I have checked the file /srv/storage/tmp/migration/uploads/cnmaestro-import.tar.gz and it is a tar gz file so the comamnd line should be tar xzvf /srv/storage/tmp/migration/uploads/cnmaestro-import.tar.gz, but I got error anyway because it's seems a double gzipped file.

If i use: gzip -cd /srv/storage/tmp/migration/uploads/cnmaestro-import.tar.gz | gunzip -cd -| tar tvf -

i get a list of files

I hope this can help

Francesco

Usseglio_Gaudi_Franc · January 17, 2019, 4:15pm

Hi,

I have tried again gunzipping the backup,. adding again .gz extension to the file and now I have restored and the server rebooted, now the gui says: "Data Migration to 2.1.0 In Progress. Do not initiate System Backup and Data Report jobs or restart the system"

I can see my network and my customers' devices

Anish · January 17, 2019, 4:20pm

This is expected behaviour.

Do not initiate System Backup and Data Report jobs or restart the system

jaggermifter · January 17, 2019, 8:47pm

I ran the update from the CLI and I got the following error.

2019-01-17 20:46:40,512 - cns.migration - INFO - Offline connected devices!
2019-01-17 20:46:40,532 - cns.migration - INFO - Offline connected devices done in 0 (sec)
2019-01-17 20:46:40,532 - cns.migration - INFO - Cleaning restore files and directories!
2019-01-17 20:46:40,538 - cns.migration - INFO - Deleted Mongo dump files exists in path /srv/storage/tmp/migration/dumps
2019-01-17 20:46:40,539 - cns.redis - INFO - Flushing redis db 4 ...
2019-01-17 20:46:40,540 - cns.migration - INFO - Cleaning restore files and directories!
2019-01-17 20:46:40,540 - cns.migration - ERROR - Failed restore!
2019-01-17 20:46:40,540 - cns.migration - ERROR - Command '['cnmaestro-mongo-migration --ver 2.1.0 --step 2 --sver 1.6.3']' returned non-zero exit status 1
2019-01-17 20:46:40,541 - cns.migration - INFO - Publishing json data {'code': 'RESTORE_FAILED', 'action': 'restore', 'cause': 'Failed to import data!', 'status': 'ERROR', 'account': 'cnmaestro'}
2019-01-17 20:46:40,551 - cns.migration - INFO - Executing command 'service cnmaestro-router start'
2019-01-17 20:46:44,200 - cns.migration - INFO - Executing command 'service nginx restart'
2019-01-17 20:46:44,353 - cns.redis - INFO - Flushing redis db 4 ...
2019-01-17 20:46:44,354 - cns.migration - ERROR - Command '['cnmaestro-mongo-migration --ver 2.1.0 --step 2 --sver 1.6.3']' returned non-zero exit status 1

Any Idea's?

Cambium_Rupam · January 17, 2019, 11:40pm

What was the last cnmaestro server version you running from where you exported the data ? And the OVA was 1.6.0 or 1.6.1 ?

Rupam

Sean_Heskett · January 17, 2019, 11:50pm

OVA Version:

1.6.1-r10

Package Version:

1.6.3-r15

jaggermifter · January 18, 2019, 2:08am

OVA Version:
1.6.1-r10
Package Version:
1.6.3-r19

Tuvix_IT · January 18, 2019, 3:08am

AP Medusa: after the update the Frame Utilization download is no longer registered ....

Ryan_Ray · January 18, 2019, 4:06am

Same issue, ticket is submitted.

KR1 · January 18, 2019, 6:22am

Hi Tuvix_IT

We were able to reproduce the issue locally and filed a JIRA ticket for tracking the same. The issue will be fixed and patch will be shared soon.

Thanks,

KR.

postmanerk · January 18, 2019, 7:18pm

I am not able to pull in my backup on 2.1.0 from 1.6.3r39. I assume it is similar to the others where it came from previous.

Timothy_Alexander · January 18, 2019, 9:25pm

Looks like the autoprovisioning is not working correctly re: moving devices into a network in V2.1.0 for R series routers. I've got auto-provisioning setup to move R series routers into a network called auto-onboarded-rseries. These devices are showing up the Devices Awaiting Approval and when they are approved are showing up in the Default group not the auto-onboarded-rseries group.

Screenshots attached where you can see the IPs match and type matches, these rules worked in previous dozen releases of cnMaestro.

Cambium_Rupam · January 18, 2019, 10:49pm

Hi

Auto provisioning rule will be applied to devices which are not yet onboarded into the system.

Once it’s onboarded you need to manually move them under the right network.

So please confirm was the device already onboarded and after that you edited the provisioning settings ?

Rupam

Timothy_Alexander · January 19, 2019, 7:55am

The device was not onboarded before. It was a new device which did not auto approve and was waiting in pending device approval. Again, this woeked flawlessly on all previous versions of cnmaestro and has only failed since 2.1.0. Previous to this r series once they contacted our cnmaestro server would be placed automatically into auto-onboarded-rseries network and be approved by the auto provisioning rule.

Tim

Cambium_Rupam · January 19, 2019, 2:55pm

Thanks for reporting this issue.

We are looking into it and will fix in the next patch coming soon.

Rupam

Cambium_Ajay · January 19, 2019, 4:48pm

That might be most likely the case but to make sure this is not a different issue, could you please share the cnMaestro Techsupport file after attempting the data migration. I have sent you private message for same.

Thanks,

Ajay