✶Update 09/2020✶ Omada Controller 3.2.10 for Debian, Raspbian and other Linux systems

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
18910...

✶Update 09/2020✶ Omada Controller 3.2.10 for Debian, Raspbian and other Linux systems

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
168 Reply
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-13 11:20:14

Hi @Snc, the step-by-step instructions are in post #1 already, but overall setup varies slightly on different Java environments used in different Raspbian versions. Maybe you have a friend with a bit more Linux experience who can help you to follow the instructions in post #1?

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#102
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-18 23:40:36

@R1D2 

 

Thanks for the steps, looking forward to get this running.

 

I'm not too familiar w/ linux, but have most of the steps done, only thing I need help w/ right now is jsvc

 

As for jsvc, don't use the Debian binary package, it requires OpenJDK last time I checked this. Instead, get the source code for jsvc (command apt-get source jsvc), compile it and install jsvc manually. 

 

Can you please provide the steps to compile and install jsvc manually? And where to install exacltly? Is there a compiled version already available somewhere to download? 

 

$ sudo dpkg -i omada-controller_3.2.6-1_all.deb

Selecting previously unselected package omada-controller.

(Reading database ... 118004 files and directories currently installed.)

Preparing to unpack omada-controller_3.2.6-1_all.deb ...

Unpacking omada-controller (3.2.6-1) ...

Setting up omada-controller (3.2.6-1) ...

* /etc/init.d/omadad: could not find the Java launcher 'jsvc'.

Processing triggers for systemd (242-7ubuntu3.7) ...

Processing triggers for man-db (2.8.7-3) ...

karimkb@ubuntu:~$ jsvc

 

Command 'jsvc' not found, but can be installed with:

 

sudo apt install jsvc


Let me know.


Take Care

 

  0  
  0  
#103
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-19 01:36:49

@karimkb, just follow the instruction (apt install jsvc) from your Ubunut system to install jsvc. Probably it installs OpenJDK or Oracle JDK/JRE to satisfy the dependencies. Please test with the JDK/JRE it installs, even if it is OpenJDK.

 

If it doesn't work with the Java JRE, load the jsvc source code:

Uncomment the appropriate lines in /etc/apt/sources.list starting with a deb-src label.

Then use apt-get source jsvc to install the source. Compile it and install it (make install).

 

Probably you need to install the Oracle JRE from the Oracle website, but probably it's available in the Ubuntu repositories, too. To find out google for »Installing Oracel JRE in Ubuntu« or similar, there is almost certainly a step-by-step instruction for doing so.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#104
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-19 02:25:58

@R1D2 

 

Thanks, I used that command, it installed openJDK along with it...I had already installed oracle jre 8, so I changed the default to be oracle...was able to install the deb file w/o any errors but the controller is not starting, mongod is not starting, I tested and mongodb is running and working as expected.  Is there a log with specific reason as to why it failed to start mongo DB server?  Are there any special permissions I would need to set?

 

2020-03-18 22:13:51 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : log4j2.properties

2020-03-18 22:13:51 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : jetty.properties

2020-03-18 22:13:51 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : user.params.properties

2020-03-18 22:13:51 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : mongodb.properties

2020-03-18 22:13:51 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : netty.properties

2020-03-18 22:13:51 [main] [INFO]-[SourceFile:94] - going to start mongod.

2020-03-18 22:15:31 [main] [WARN]-[SourceFile:123] - Fail to start mongo DB server

2020-03-18 22:15:31 [main] [WARN]-[SourceFile:78] - com.tp_link.eap.start.a.a: Fail to start mongo DB server

com.tp_link.eap.start.a.a: Fail to start mongo DB server

        at com.tp_link.eap.start.c.c.a(SourceFile:124) ~[eap-start-3.2.6.jar:?]

        at com.tp_link.eap.start.c.a.e(SourceFile:75) [eap-start-3.2.6.jar:?]

        at com.tp_link.eap.start.a.g(SourceFile:324) [eap-start-3.2.6.jar:?]

        at com.tp_link.eap.start.a.y(SourceFile:410) [eap-start-3.2.6.jar:?]

        at com.tp_link.eap.start.a.a(SourceFile:95) [eap-start-3.2.6.jar:?]

        at com.tp_link.eap.start.a.h(SourceFile:350) [eap-start-3.2.6.jar:?]

        at com.tp_link.eap.start.EapLinuxMain.b(SourceFile:79) [eap-start-3.2.6.jar:?]

        at com.tp_link.eap.start.EapLinuxMain.start(SourceFile:36) [eap-start-3.2.6.jar:?]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_241]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_241]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_241]

        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_241]

        at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:241) [commons-daemon-1.1.0.jar:1.1.0]

2020-03-18 22:15:33 [main] [INFO]-[SourceFile:167] - mongod is not running

 

Here is what it shows for java/mongod

 

karimkb@ubuntu:/opt/tplink/OmadaController-3.2.6/logs$ java -version

java version "1.8.0_241"

Java(TM) SE Runtime Environment (build 1.8.0_241-b07)

Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode)

karimkb@ubuntu:/opt/tplink/OmadaController-3.2.6/logs$ mongod -version

db version v3.6.8

git version: 8e540c0b6db93ce994cc548f000900bdc740f80a

OpenSSL version: OpenSSL 1.1.1c  28 May 2019

allocator: tcmalloc

modules: none

build environment:

    distarch: x86_64

    target_arch: x86_64

karimkb@ubuntu:/opt/tplink/OmadaController-3.2.6/logs$

 

  0  
  0  
#105
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-19 13:44:34

Additional error in log:

 

2020-03-19 00:15:50 [main] [ERROR]-[ContextLoader.java:350] - Context initialization failed

org.springframework.dao.DataAccessResourceFailureException: Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Client view of cluster state is {type=UNKNOWN, servers=[{address=127.0.0.1:27217, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectException: Connection refused (Connection refused)}}]; nested exception is com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting for a server that matches WritableServerSelector. Client view of cluster state is {type=UNKNOWN, servers=[{address=127.0.0.1:27217, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectException: Connection refused (Connection refused)}}]

 

As a test I tried to manually start mongod -port 27217, and that worked...left it running and then tried to run "sudo omadactl start" and it erroed out saying port 27217 is in use, which makes sense.

 

I just don't know what the cause is for the genric "connection refused" message.

  0  
  0  
#106
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-19 16:04:19

@karimkb, unfortunately Omada Controller wants to start mongod for itself.

 

You can neither use the existing mongod server for Omada controller nor run the two mongod services in parallel (what I consider a major bug in Omada controller's concept).

 

Work-around is to disable the mongod started by the system, albeit this is no solution when needing mongod services for other database-driven applications.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#107
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-19 17:17:06

@R1D2 

Thanks for the reply and appricate your assistance.

 

I did not have mongodb set to auto startup, so there was no instance running, I manally started an instance for testing.

 

I figured I would start all over and maybe get a newer version of mongodb (instead of 3.6 ... move to 4.2), so uninstalled mongodb and traces of the omada controller package ... reinstalled latest mongodb and tried to run the .deb package again...but now it fails with Package mongodb is not installed :/

 

karimkb@ubuntu:~$ sudo dpkg -i omada-controller_3.2.6-1_all.deb

Selecting previously unselected package omada-controller.

(Reading database ... 118775 files and directories currently installed.)

Preparing to unpack omada-controller_3.2.6-1_all.deb ...

Unpacking omada-controller (3.2.6-1) ...

dpkg: dependency problems prevent configuration of omada-controller:

omada-controller depends on mongodb (>= 1.2.4); however:

  Package mongodb is not installed.

 

dpkg: error processing package omada-controller (--install):

dependency problems - leaving unconfigured

Processing triggers for systemd (242-7ubuntu3.7) ...

Processing triggers for man-db (2.8.7-3) ...

Errors were encountered while processing:

omada-controller

 

karimkb@ubuntu:~$ mongod -version

db version v4.2.3

git version: 6874650b362138df74be53d366bbefc321ea32d4

OpenSSL version: OpenSSL 1.1.1c  28 May 2019

allocator: tcmalloc

modules: none

build environment:

    distmod: ubuntu1804

    distarch: x86_64

    target_arch: x86_64

 

karimkb@ubuntu:~$ java -version

java version "1.8.0_241"

Java(TM) SE Runtime Environment (build 1.8.0_241-b07)

Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode)

 

 

  0  
  0  
#108
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-20 00:20:55

@karimkb, did you install the mongodb meta package or did you install mongod-server package alone?

 

If the mongodb meta-package is indeed installed, but still not recognized by the omada-controller package, you can try the official Omada controller version from TP-Link, which contains the mongod binary.

 

The goal of the community version is to be architecture-independent, but if packet management fails, try to use TP-Link's x86-specific version. You could also unpack the official controller version without installing it and copy the mongod binary contained therein to /opt/tplink/OmadaController/bin if you want. See the manpage of dpkg for the command to unpack rather than to install a package.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#109
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-20 00:59:04

@R1D2 

I don't know what the "meta" package is, I installed it using sudo apt install -y mongodb-org...which I'm assuming is the meta package.

 

Thanks for the instructions, but I think w/ my limited linux experince, these steps are a little over my head.

  0  
  0  
#110
Options
Re:✶Update 01/2020✶ Omada Controller 3.2.6 for Debian, Raspbian and any other Linux system
2020-03-20 01:46:10 - last edited 2020-03-20 01:47:03

@R1D2 

 

Ok, figured it out, uninstalled latest version of mongo, installed version 3.6.8 again (with this version the deb package installed as expected, must be somehting w/ version 4)...looking at one of your prevoius posts, I had to get rid of the --nohttpinterface option from the mongodb.properties...after that the controller was able to start.

  1  
  1  
#111
Options