Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
Re: Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
2019-01-28 21:29:05 - last edited 2019-03-06 01:55:43

Numb3rs wrote

My solution was to add omadactl to rc.local. Now it auto starts on boot. Is this solution ok or not advised?

 

That's o.k. if it works for you. Normally, the dpkg installer should create a link from /etc/init.d/omadad (a stripped-down version of omadactl) to a script in the proper rc-directory such as /etc/rc2.d/S01omadad, but you could also start it via omadactl in rc.local. Only difference between omadactl and omadad is logging - more verbose error messages on stderr in omadactl - and stripped-down functionality only for functions required at boot time in omadad. You could also start the controller by calling /etc/init.d/omadad from rc.local to have error message sent to /var/log/syslog via the rsyslogd daemon.

 

As for the replacement of -server by -client when starting Java, this depends on the optimization level of the JRE for your platform. See https://stackoverflow.com/a/198651 for the difference of -client vs. -server option.

 

Have fun!

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

Bobby-Gecko wrote


In any case, things for me worked differently when I tried to run a setup on Debian 9.6... So I wrote out install instructions AND built a script to automate the install (only for fresh installs of Debian please - probably wouldn't work well for an upgrade) for anyone who may be interested...

 

That's cool, thanks for your contribution. I will refer to when I have to install the controller on Debian 9. Any tips and helper scripts to get it running on other distros / versions is definitely much appreciated by the community.

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
1
1
#106
Options
Re:Re: Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
2019-02-15 11:29:36 - last edited 2019-03-06 01:55:43

I used your installer, can i update to 3.0.5 using the tp-link linux installer, or would i have to wait for an update from you?

(Still no 3.1.0 by the way, what would be the benefit of that release?)

R1D2 wrote

Numb3rs wrote

My solution was to add omadactl to rc.local. Now it auto starts on boot. Is this solution ok or not advised?

 

That's o.k. if it works for you. Normally, the dpkg installer should create a link from /etc/init.d/omadad (a stripped-down version of omadactl) to a script in the proper rc-directory such as /etc/rc2.d/S01omadad, but you could also start it via omadactl in rc.local. Only difference between omadactl and omadad is logging - more verbose error messages on stderr in omadactl - and stripped-down functionality only for functions required at boot time in omadad. You could also start the controller by calling /etc/init.d/omadad from rc.local to have error message sent to /var/log/syslog via the rsyslogd daemon.

 

As for the replacement of -server by -client when starting Java, this depends on the optimization level of the JRE for your platform. See https://stackoverflow.com/a/198651 for the difference of -client vs. -server option.

 

Have fun!

0
0
#110
Options
Re:Re:Re: Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
2019-02-16 00:20:55 - last edited 2019-03-06 01:55:43

Hello,

 

I installed Omada Controller 3.0.2 but I'm not able to start the EAP server.

 

Here is the content of server.log file:

2019-02-16 01:13:41 [main] [INFO]-[SourceFile:34] - success to load configuration : eap.properties
2019-02-16 01:13:41 [main] [INFO]-[SourceFile:34] - success to load configuration : netty.properties
2019-02-16 01:13:42 [main] [INFO]-[SourceFile:34] - success to load configuration : mongodb.properties
2019-02-16 01:13:42 [main] [INFO]-[SourceFile:34] - success to load configuration : jetty.properties
2019-02-16 01:13:44 [nioEventLoopGroup-4-1] [WARN]-[Slf4JLogger.java:131] - A non-root user can't receive a broadcast packet if the socket is not bound to a wildcard address; binding to a non-wildcard address (/192.168.0.159:0) anyway as requested.
2019-02-16 01:13:47 [Thread-4] [INFO]-[SourceFile:34] - success to load configuration : device.properties
2019-02-16 01:13:51 [pool-6-thread-1] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event
2019-02-16 01:13:51 [pool-6-thread-2] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event
2019-02-16 01:13:56 [pool-6-thread-3] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event
2019-02-16 01:13:57 [pool-6-thread-1] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event

...

2019-02-16 01:19:48 [pool-6-thread-1] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event
2019-02-16 01:19:52 [pool-6-thread-2] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event
2019-02-16 01:19:53 [pool-6-thread-3] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event
2019-02-16 01:19:57 [pool-6-thread-1] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event
2019-02-16 01:19:58 [pool-6-thread-2] [INFO]-[SourceFile:92] - Omada Controller isn't prepared to handle event

 

The "Omada Controller isn't prepared to handle event" sentence never stop to be written.

 

Can you help me?

 

Thanks,

Emilien

0
0
#111
Options
Re: Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
2019-02-16 11:32:43 - last edited 2019-03-06 01:55:43

Dynamo wrote

I used your installer, can i update to 3.0.5 using the tp-link linux installer, or would i have to wait for an update from you?

(Still no 3.1.0 by the way, what would be the benefit of that release?)

 

 

Version 3.0.x re-introduced a bug with logos on portal pages, see this post. As for my use case, I worked hard to fix those issue (among others) appearing first in v2.5.3 and that's the reason why I still use v2.7.0 in the field rather than installing v3.0.x.

 

For reasons I don't know, TP-Link picked only some of my suggestions/fixes from my tpeap in their v3.0.2 control.sh script and changed it slightly so that the official release v3.0.x is incompatible with my tpeap script. What's more, they use the Java utility jsvc, while I use the standard Linux wrapper start-stop-daemon for privilege separation up to v2.7.0, but my tpeap also supports the jsvc method with v3.0.2. Other differences are: they deliver a bundled (old) JRE, I use a newer JRE from Oracle repository, they use an outdated monogdb binary, I use the standard mongodb package available in the system's OS repository, thus making the community version platform-independent.

 

As for using the official TP-Link distribution with my tpeap script, you could install TP-Link's TAR version (if any), but you would have to install the files in the final place manually (that's easy) rather than with the included installer script. However, the official .deb package isn't compatible with my package and would overwrite it. Of course, you can replace the community version of v3.0.2 with the official 3.0.5 if you wish, this is no problem. The community version existed only b/c there was no up-to-date official Linux version for a long time and the old one available had very critical security bugs.

 

If you want to install just the files from TP-Link's TAR version of 3.0.5, don't use their installer, it will break the directory layout of the community version. Rather unpack the files somewhere else from the TAR archive, create a directory /opt/tplink/OmadaController-3.0.5, copy only the new files/directories over to this directory which are present in community version v3.0.2 too, and change the ownership of the copied files which need to be writeable to the eapc user (you can find out in v3.0.2 which files should have which ownership and permissions). That's all. This way, you have both versions installed, which allows you to switch versions forth (and back!) with tpeap (see its switch option). To copy your database, just duplicate all files from the data subdirectory in v3.0.2 over to v3.0.5 and restart the v3.0.5 controller.

 

 

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
0
0
#112
Options
Re: Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
2019-02-16 11:39:26 - last edited 2019-03-06 01:55:43

@Emilien, which OS are you using? Note that on micro systems such as the Pi you will have to wait long enough (5 to 10 minutes) until the server is ready to handle events. This is normal. If it still doesn't start, check whether jsvc is installed (run command: which jsvc to see whether it's there) and whether mongod is available (run: mongod -version).

༺ 0100 1110 0011 0010 10ཏ1 0010 0110 1010 1101༻
2
2
#113
Options
Re:Re: Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
2019-02-16 16:31:39 - last edited 2019-03-06 01:55:43

Dear R1D2,

 

Thanks for your feedback and your help.

 

I use a raspberry PI 3B+ on stretch.

which jsvc: /usr/bin/jsvc

mongod -version: db version v2.4.14


I have been waiting over 1 hour and I still have the same message :-(

 

Best regards,

Emilien

0
0
#114
Options
Re:Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
2019-02-17 18:32:34 - last edited 2019-03-06 01:55:43

No idea to help me ?

0
0
#115
Options
Re: Omada Controller 3.0.2 for Linux (including new tpeap v1.4)
2019-02-18 12:42:34 - last edited 2019-03-06 01:55:43

Emilien wrote

No idea to help me ?

 

Be patient, I'm not reading the forum each day.

 

Make sure that no other controller is running in the same subnet.

 

Next, kill all processes which might have been running from a previous start:

 

$ sudo bash

# killall mongod

# killall java

 

Next, start the controller interactively to error messages on stderr:

 

# omadactl -W 240 start

Starting Omada Controller ..................................................................................................................
Omada Controller started successfully after 116 seconds.
Direct your browser to http://raspi:8088 for accessing Omada Controller.

 

Depending on the load of your Pi it can even last longer to start the controller, try -W 300.

 

If it still not starts, re-install the system and the controller freshly and try again. Make sure you use omada-controller_3.0.2-2_all.deb from my FTP archive. Maybe you have a spare SDHC card for the test so you don't lose other setups. 

 

Sometimes Raspbian can get into a really, really weird state. For example, after installing the official controller 3.0.5 package and purging it again today, dpkg reported doing so would make 110 GB available on my 32 GB SDHC card. laugh

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