Omada Controller 2.7.0 for Linux (community version)
Re:Re:Re:Omada EAP Controller v2.7.0 for Linux, anyone? Sure!
2018-08-08 21:15:41 - last edited 2018-08-08 21:17:48

DeanKamitsis wrote

Works perfectly, no issues. Upgraded from 2.6.1 with no issues. Followed the initial 2.7.0 instructions to the letter :)

 

Hi Dean,

 

thanks for feedback. Yes, Debian is always very stable, others sometimes call this »a little bit behind« (in introducing new bugs ). 

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
1
1
#12
Options
Re:Re:Re:Re: Omada Controller 2.7.0 for Linux (community version)
2018-08-08 21:21:00

R1D2 wrote

miked315 wrote

EDIT:

Looks like this version of mongodb might not like the --nohttpinterface parameter. 

 

Yes, that's it. See also https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues/223

 

Please edit /opt/tplink/EAPController/properties/mongodb.properties and remove the --nohttpinterface option from eap.mongod.args.

 

If you're lucky, EAPC obeys this property (it does not always honor all properties, so no guarantee that it works).

So, EAPC does obey that property.  After editing the mongodb.properties file, I do see it attempting to startup mongodb and I now get entries in the mongodb.log.

 

Looks like mongodb is now failing to this error:

 

2018-08-08T17:17:57.209-0400 E STORAGE  [initandlisten] Unable to read the stora

ge engine metadata file: FileNotOpen: Failed to read metadata from /opt/tplink/E

APController-2.7.0/data/db/storage.bson

2018-08-08T17:17:57.209-0400 F -        [initandlisten] Fatal Assertion 28661 at

 src/mongo/db/storage/storage_engine_metadata.cpp 89

2018-08-08T17:17:57.209-0400 F -        [initandlisten] 

 

***aborting after fassert() failure

 

2018-08-08T17:17:57.215-0400 F -        [initandlisten] Got signal: 6 (Aborted).

 

0
0
#13
Options
Re: Omada Controller 2.7.0 for Linux (community version)
2018-08-08 21:35:27 - last edited 2018-08-08 21:38:32

miked315 wrote

Looks like mongodb is now failing to this error:

 

2018-08-08T17:17:57.209-0400 E STORAGE  [initandlisten] Unable to read the stora

ge engine metadata file: FileNotOpen: Failed to read metadata from /opt/tplink/E

APController-2.7.0/data/db/storage.bson

 

Try to remove old files from the data/db directory (only those!). Stop the Controller and mongod before doing so, then execute:

 

cd /opt/tplink/EAPController/data

rm -f db/* db/journal/* db/_tmp/*

 

On start EAPC re-creates those files if they are missing by issuing an initial DB setup.

 

Also please check the UID of the mongod process. It should be the eapc user if started using tpeap.

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
0
0
#14
Options
Re:Re:Re:Re:Re: Omada Controller 2.7.0 for Linux (community version)
2018-08-08 21:42:48

So I wiped my 2.7.0 directory and started over....this time I edited the mongodb.properties before ever attempting to start it up.  Everything seems to be working now, except it seems that it won't import my data though, I had to adopt my APs again to get them to show up.  Restoring my backup from 2.6.1 did not restore my APs.

2
2
#15
Options
Re:Re: Omada Controller 2.7.0 for Linux (community version)
2018-08-08 21:48:43

R1D2 wrote

miked315 wrote

Looks like mongodb is now failing to this error:

 

2018-08-08T17:17:57.209-0400 E STORAGE  [initandlisten] Unable to read the stora

ge engine metadata file: FileNotOpen: Failed to read metadata from /opt/tplink/E

APController-2.7.0/data/db/storage.bson

 

Try to remove old files from the data/db directory (only those!). Stop the Controller and mongod before doing so, then execute:

 

cd /opt/tplink/EAPController/data

rm -f db/* db/journal/* db/_tmp/*

 

On start EAPC re-creates those files if they are missing by issuing an initial DB setup.

 

Also please check the UID of the mongod process. It should be the eapc user if started using tpeap.

Yes, now that tpeap is starting mongod it is running as the eapc user.  What should I do with my data directory at this point?  Seems I have almost 3GB of useless historical data sitting there in the tpeap.0, tpeap.1 and tpeap.ns files.  Guess I should stop the controller, delete the files mentioned above and then restart it...is that my best bet?

0
0
#16
Options
Re: Omada Controller 2.7.0 for Linux (community version)
2018-08-08 21:55:15 - last edited 2018-08-08 22:09:27

miked315 wrote

So I wiped my 2.7.0 directory and started over....this time I edited the mongodb.properties before ever attempting to start it up.  Everything seems to be working now, except it seems that it won't import my data though, I had to adopt my APs again to get them to show up.  Restoring my backup from 2.6.1 did not restore my APs.

 

Thanks a lot, Mike! That's very helpful.

 

I will add a note in my recipe about removing the --nohttpinterface option for mongodb >= 3.6. Did you check wether mongod listens on a port for HTTP requests? If so, it would be interesting on which port and on which IP (localhost? Primary IP? INADDR_ANY?), so one could firewall this port if running EAPC on a public Internet server.

 

You are right, unfortunately TP-Link's backup procedure doesn't save or restore adopted APs and it also doesn't restore maps. That's why I did recommend to use the native mongod in EAP Controller v2.6.1 for Linux already - changes are that data can be either copied over or that apt-get takes care of programmatically restoring the DB's content on upgrades.

 

Edit: regarding your historic data I would recommend to save/restore them using EAP Controller. If you did follow the installation instructions, it is easy to switch back to EAP Controller v2.5.3 with embedded mongodb (just change the symlink /opt/tplink/EAPController to do so).

 

Maybe there is a better way to restore old data with the mongodb client directly (starting old mongodb, creating a dump, starting new mongodb, loading the dump), but I didn't investigate in this (yet). This would probably copy even APs and maps.

 

IIRC there was a stand-alone shell script in the JRE directory in version 2.4.7 or 2.4.8 to do backups - if I have some time, I will probably analyze what it does. But question is what has been changed since then in the DB layout - remember: Omada Controller is closed source, so only TP-Link could tell.

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
2
2
#17
Options
Re:Re: Omada Controller 2.7.0 for Linux (community version)
2018-08-08 22:13:24

Looks like mongod only listens on 127.0.0.1

 

root@jalapeno:~# netstat -anp |grep mongod

tcp        0      0 127.0.0.1:27017         0.0.0.0:*               LISTEN      8560/mongod         

tcp        0      0 127.0.0.1:27017         127.0.0.1:38108         ESTABLISHED 8560/mongod         

tcp        0      0 127.0.0.1:27017         127.0.0.1:38110         ESTABLISHED 8560/mongod         

tcp        0      0 127.0.0.1:27017         127.0.0.1:38104         ESTABLISHED 8560/mongod         

tcp        0      0 127.0.0.1:27017         127.0.0.1:38102         ESTABLISHED 8560/mongod         

unix  2      [ ACC ]     STREAM     LISTENING     577142   8560/mongod          /tmp/mongodb-27017.sock

 

Thanks for all the help, I'm not super concerned about my historical data.  I was more concerned about having to re-adopt the APs and reconfigure most of my settings but it's not that big of a deal, I've only got 2 APs.

0
0
#18
Options
Re:Re:Re: Omada Controller 2.7.0 for Linux (community version)
2018-08-08 22:28:22 - last edited 2018-08-08 22:29:09

miked315 wrote

Looks like mongod only listens on 127.0.0.1

 

Thanks for all the help, I'm not super concerned about my historical data.

 

Ok, not critical if it listens on localhost only. You're welcome, glad it finally did work out for you.

 

 

I was more concerned about having to re-adopt the APs and reconfigure most of my settings but it's not that big of a deal, I've only got 2 APs.

 

Lucky you  I have to re-adopt two dozens APs running at customer's sites with no physical access under an old AWS account. That's somewhat tricky.

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
0
0
#19
Options
Re:Omada Controller 2.7.0 for Linux (community version)
2018-09-22 08:55:09

ok sorry in addvance for my poor grammer i am very dyslixic and my coding ability is cut and paste when it come to linux i am a windows guy i need to learn linux more anyways i am trying my best to fallow the instruction while adapting the step to the latest release and using the .deb packages that installed most of the step i am getting like access denyed inttell i stated to us sudo command  made it to Step 6: Set up the mongo database then ran into issues getting permission denyed

 

 

 

0
0
#20
Options
Re: Omada Controller 2.7.0 for Linux (community version)
2018-09-22 11:12:31

srgsng25 wrote

i am getting like access denyed inttell i stated to us sudo command  made it to Step 6: Set up the mongo database then ran into issues getting permission denyed

 

Hi srgsng25,

 

which platform are you using? RasPi? In Raspbian, mongodb is installed already, no need to execute the commands in step 6.

 

If you use a platform on which mongdb is not installed:

 

To avoid having to type sudo for each and every command, either switch permanently to the root user (command su, password required) or just run sudo bash once to start a new shell with admin privileges. Then execute the two apt-get commands shown in step 6. Then exit the shell with ^D or command exit.

 

A .deb packages for almost all Linux versions is on the way for 2.7.0 and 3.0.2, but it still needs some polishing and testing.

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
0
0
#21
Options