[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian 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.

[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian 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.
139 Reply
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2020-12-12 20:38:27

 

manfer wrote

 

Caused by: java.lang.OutOfMemoryError: unable to create new native thread

 

@manfer 

 

Looks like the problem was systemd task max limit on the system, maybe imposed by default by VPS virtualization software. I checked the value with

 

systemctl show --property DefaultTasksMax

DefaultTasksMax=60

 

So I incresed to 512 by editing /etc/systemd/system.conf, adding a line

 

DefaultTasksMax=512

 

followed by a reboot. And Omada Controller is now running.

 

So, is it ok installing jsvc from repositories like I did?

  0  
  0  
#123
Options
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2020-12-16 16:02:10 - last edited 2020-12-16 19:48:14

I managed to use the new controller on a Raspbian Buster version without using docker. I use the Mongodb binaries with version 3.0.14 from

https://andyfelong.com/2017/08/mongodb-3-0-14-for-raspbian-stretch/

Just unpacked them into a directory (/opt/mongodb3 or whatever you like) and changed the link in the bin folder of the Omada SDN Controller installation to point to it and it works fine so far (you can also make a link from /usr/bin/mongod to the mongodb3 file if you don't have a "regular" mongodb installed).

 

The manual of Omada SDN controller states the allowed MongoDB versions:

Omada SDN Controller Software 4.1.5Windows/Linux_User Guide (page 11)

==

Ensure that MongoDB has been installed in your system. The controller works when the system runs MongoDB 3.0.15–3.6.18

==

I didn't find a manual for 4.2.4 but probably it is unchanged? 3.0.14 is apart from minor security patches the same as 3.0.15 and I found it to work flawlessly.

 

In Raspbian Buster, the current OpenJDK VM is a bit outdated (was from March 2019). Therefore, it is advisable to use another one which gets security updates automatically. I switched to AdoptOpenJDK. They have installation steps here:

https://adoptopenjdk.net/installation.html?variant=openjdk8&jvmVariant=hotspot#installers

However, upon startup, it does not work out of the box. You always get the message

==

Cannot find any VM in Java Home

==

The reason for this error message is basically some kind of bug in JSVC which searches for the jvm.cfg in a location which depends on the CPU architecture "arm" but with the AdoptOpenJDK the files are in aarch32 instead (if someone is interested: The source file for the error message in JSVC is src/native/unix/native/java.c, the "data"-variable used there is filled in home.c and the paths for the jvm.cfg are in location.c (Variable location_jvm_cfg)). I added these lines to my Omada-CONFIG file in order to create a link and through that it works and will survive also updates/reinstalls of the Java VM (as long as it stays the AdoptOpenJDK one, others may have other problems):

==

JAVA_HOME=/usr/lib/jvm/adoptopenjdk-8-hotspot-jre-armhf
if [[ ! -d $JAVA_HOME/lib/arm && -d $JAVA_HOME/lib/aarch32 ]]; then
    ln -s $JAVA_HOME/lib/aarch32 $JAVA_HOME/lib/arm
fi

==

 

Two other things were change by me but not sure if everyone wants that:

1. I disabled the mongodb journal because it causes lots of additional disk writes which is not so good for the life of the Raspberry SD card. It is possible to disable it in the omada.properties (linux.mongod.nojournal=true). However, it does have drawbacks when your system crashes or has a power-loss. But in my small installation, I don't really care about and regular backups are more important in my eyes.

2. Also in order to reduce disk activity, I changed the log location to /var/log (which is in my installation in RAM by Log2Ram utility) by setting SRV_LOG, MDB_LOG and BKUP_LOG. I found out that it is necessary to also edit the log4j2.properties because the logging location is hardcoded there. Probably it's better to use a symbolic link here...

  0  
  0  
#124
Options
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2020-12-21 16:41:10

@R1D2 Dono if you remember me.. but..
Omada controller started failing..(wouldn't boot up etc...) and i belive it was the cause that almost blew up my pi with errors.. lol
But.. i have now done a fresh install on Ubuntu server 64bit on the pi4 .. and im happy to say that installation was flawless.. no problems at all and is happily running omada and samba!

  0  
  0  
#125
Options
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2020-12-27 21:54:37
Admin
  0  
  0  
#126
Options
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2020-12-27 21:55:05

 

R1D2 wrote

This:

 

2020-11-28 00:11:26,009 main ERROR RollingFileManager (/opt/tplink/OmadaController-4.2.4/lib/../logs/server.log) java.io.FileNotFoundException: /opt/tplink/OmadaController-4.2.4/lib/../logs/server.log (Permission denied)

 

is caused by one of the bugs in the official TP-Link controller version which has been fixed already in my community controller version since v4.1.5.

 

Whatever you run as the SW controller, it's not the community version.

@R1D2 

  0  
  0  
#127
Options
Re:Omada SDN Controller 4.1.5 for Devuan, Debian and other Linux systems
2020-12-27 21:58:23
hsoon1
  0  
  0  
#128
Options
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2020-12-30 16:53:25

@Ronald1965 Is there any way to get the docker image updated to 4.2.4?

  1  
  1  
#129
Options
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2021-01-01 12:39:06

@saajid  Done :-)

 

I made a new latest version and one new tage 4.2.4-1.

 

docker pull ronaldo1965/omada-sdn-controller:4.2.4-1

 

I always recommend the version tag. Because then you know on which version you are.  latest can brick your environment but good for testing.

I didn't do much tests but it starts up as fresh build.

  1  
  1  
#130
Options
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2021-01-01 19:49:56 - last edited 2021-01-01 19:58:56

@Ronald1965 

 

It looks like I'm running in to the mongodb 32bit 2gb limit when trying to upgrade to 4.2.4-1 image.  Is there some work around like purging the current database?

 

Thanks-

Jason

File:
server.logDownload
Jason Omada Software Controller ER605 v1.0, TL-SG2008P v1.0, EAP225(US) v3.0 (2x)
  0  
  0  
#131
Options
Re:[Update 11/2020] Omada SDN Controller 4.2.4 for Devuan, Debian and other Linux systems
2021-01-02 09:44:00

@jasonsf 

 

I upgraded by backup and restore.  I just create a new instance. Make a backup of the old instance and restore it on the new one.

But I didn't run against that kind of problems.

  0  
  0  
#132
Options