Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
Re:Re:Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-25 18:59:51 - last edited 2019-03-06 01:55:43

E-raser wrote

I also get "General Error"

Fresh install didn't solve it :-(

 

That's mysterious. A general error is thrown when something unforeseen, unspecific happens. Can't imagine what could go wrong with a simple TCP connection via HTTPS into the Cloud (AWS) ... Have you already tested binding with another browser or from a network with another Internet connection? Did you check for possible Javascript errors when loading the web UI pages?

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
1
1
#22
Options
Re:Re:Re:Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-26 08:28:42 - last edited 2019-03-06 01:55:43

Tested with other browsers -> same problem

Can't find any javascript errors on loading page

 

server has several connections to AWS without any problem

 

In my logs when I enable disable/enable cloud & try to bind I get:

--> Stop

2018-08-26 10:24:10 [qtp232307208-127] [INFO]-[CloudClient.java:194] - CloudClient is stopped.
2018-08-26 10:24:10 [qtp232307208-127] [INFO]-[SourceFile:147] - Cloud service is stopped.
2018-08-26 10:24:10 [qtp232307208-127] [INFO]-[SourceFile:91] - Stopping PF module.
2018-08-26 10:24:10 [Thread-33] [INFO]-[SourceFile:526] - cleanExpiredCacheThread is interrupted.
2018-08-26 10:24:10 [qtp232307208-127] [INFO]-[SourceFile:547] - Clean expired cache thread is destroyed.
2018-08-26 10:24:10 [qtp232307208-127] [INFO]-[SourceFile:180] - Stopping SCMP Server.
2018-08-26 10:24:10 [Thread-34] [INFO]-[SourceFile:393] - handleRequestThread is interrupted.
2018-08-26 10:24:10 [Thread-34] [INFO]-[SourceFile:433] - SCMP request handle thread is ended.
2018-08-26 10:24:10 [qtp232307208-127] [INFO]-[SourceFile:449] - SCMP request handle thread is destroyed.
2018-08-26 10:24:10 [qtp232307208-127] [INFO]-[SourceFile:131] - clear proxy connection info

--> Start
2018-08-26 10:24:22 [qtp232307208-127] [INFO]-[SourceFile:80] - Starting PF module.
2018-08-26 10:24:22 [qtp232307208-127] [INFO]-[SourceFile:155] - Starting SCMP Server.
2018-08-26 10:24:23 [qtp232307208-114] [INFO]-[SourceFile:189] - Request tries to trigger CloudClient to recover connection.
2018-08-26 10:24:23 [qtp232307208-114] [WARN]-[SourceFile:94] - [Exception]execution(OperationResponse com.tp_link.eap.monitor.cloud.clouduser.service.impl.CloudUserServiceImpl.bindDeviceOwner(ControlType,JSONObject))[exception message:null]

 

Grtz,

E-raser
 

0
0
#23
Options
Re: Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-26 09:14:09 - last edited 2019-03-06 01:55:43

Seems to have to do with the user name/TP-Link ID. What happens if you create a new TP-Link ID with a different mail address and use this to bind?

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
0
0
#24
Options
Re:Re: Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-26 10:12:19 - last edited 2019-03-06 01:55:43

Also tested -> same problem 

 

Grtz,
E-raser

0
0
#25
Options
Re:Re:Re: Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-26 10:33:47 - last edited 2019-03-06 01:55:43

If it's just an ID for tests and if you want, I can try to bind an Omada Controller running on a spare system to it, just to see if it works.

 

If I should test, just send the ID/PW by private mail.

 

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
1
1
#26
Options
Re:Re:Re:Re: Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-26 10:46:57 - last edited 2019-03-06 01:55:43

check PM

 

Grtz,

0
0
#27
Options
Re:Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-28 15:54:10 - last edited 2019-03-06 01:55:43

Seems like tpeap restore doesn't work?

 

root@jalapeno:/opt/tplink/EAPController# tpeap restore /tmp/backup

Restoring database from dump in '/tmp/backup'

2018-08-28T11:52:31.914-0400 preparing collections to restore from

2018-08-28T11:52:31.914-0400 don't know what to do with file "/tmp/backup/tpeap/accessSubentGroup.bson", skipping...

2018-08-28T11:52:31.914-0400 don't know what to do with file "/tmp/backup/tpeap/accessSubentGroup.metadata.json", skipping...

0
0
#28
Options
Re: Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-28 16:16:50 - last edited 2019-03-06 01:55:43

miked315 wrote

Seems like tpeap restore doesn't work?

 

root@jalapeno:/opt/tplink/EAPController# tpeap restore /tmp/backup

Restoring database from dump in '/tmp/backup'

2018-08-28T11:52:31.914-0400 preparing collections to restore from

2018-08-28T11:52:31.914-0400 don't know what to do with file "/tmp/backup/tpeap/accessSubentGroup.bson", skipping...

2018-08-28T11:52:31.914-0400 don't know what to do with file "/tmp/backup/tpeap/accessSubentGroup.metadata.json", skipping...

 

Note that tpeap just executes mongodump to create a dump and mongorestore to restore it. It does not do the real work for itself.

 

From which version of Omada/EAP Controller did you restore to which other version (if any)?

 

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
0
0
#29
Options
Re:Re: Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-28 16:38:54 - last edited 2019-03-06 01:55:43

It was a backup from 2.7.0 using mongod v3.6.3 on Ubuntu. I ended up stopping 3.0.2 and copying over /data from 2.7.0 into 3.0.2 and then starting it back up and everything came up perfectly.

 

EDIT: I should note, for anyone following along that may attempt the same thing, I had to delete the /data directory from 3.0.2 first and then copy over the old 2.7.0 /data directory.  Originally I tried copying the 2.7.0 /data on top of 3.0.2 after it had been started up and was sitting at the wizard screen when accessing the web interface, this did not work at all, the controller would not start up.  Also for reference purposes, the 2.7.0 /data was a fresh install created on 2.7.0 with the Ubuntu package of mongod v3.6.3.

0
0
#30
Options
Re: Omada EAP Controller 3.0.2 for Linux (including new tpeap v1.4)
2018-08-28 17:42:26 - last edited 2019-03-06 01:55:43

miked315 wrote

It was a backup from 2.7.0 using mongod v3.6.3 on Ubuntu. I ended up stopping 3.0.2 and copying over /data from 2.7.0 into 3.0.2 and then starting it back up and everything came up perfectly.

 

I see. Maybe the file just was unused in 3.0.2 due to changed DB layout (I couldn't locate it in a dump made with mongodump, maybe it's gone). Anyway, copying over the data directories is the preferred way to transfer settings from one version to another version for me, too. Omada Controller will then add any new collections and ignore old ones silently, while mongorestore prints a warning in such cases.

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
2
2
#31
Options