Business Community > WiFi > Can't successfully install and start tpeap Omada controller software on Linux host
< WiFi

Can't successfully install and start tpeap Omada controller software on Linux host

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

Can't successfully install and start tpeap Omada controller software on Linux host

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Can't successfully install and start tpeap Omada controller software on Linux host
Can't successfully install and start tpeap Omada controller software on Linux host
2019-11-01 09:12:36 - last edited 2021-02-10 15:26:33

I am trying to setup the latest Omada controller using the .deb file provided at the Official TP Link download list (omada_v3.2.1_linux_x64_20190620104911.deb).

 

I'm Not trying to perform an upgrade, I've never had an instance installed before.

 

I'm using LXC Containers under Proxmox. I've tried Debian Buster, then triedUbuntu 18.04, both seem to give me the same issue. I am unsure whether I am installing it wrong or whether the issue is that I'm running in an LXC instead of a KVM Virtual Machne.

 

 

My install process was as follows;

 

use apt to install the prerequisites curl, net-tools and jsvc

wget the .deb file from tp-link

dpkg -i <deb file>

 

This runs a whole lot of stuff culminating in "Starting Omada controller....." which just runs for ages, at least 5 minutes, before failing.

 

 

 

I note from forum browsing that there's also a community release of the software, which as part of the installation process mentions installing Oracle java instead of OpenJDK as well as mongodb. The TP Link instructions didn't mention this, and I'm not sure if I need to install those separately or whether the tp link official .deb package contains everything that is required.

 

Can anyone point me in the right direction, or shall i start uploading some log files...

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Can't successfully install and start tpeap Omada controller software on Linux host-Solution
2019-11-01 09:59:35 - last edited 2021-02-10 15:26:33

Oh.

 

https://community.tp-link.com/en/business/forum/topic/161211?replyId=327475

 

I didn't occur to me that it would need so much disk space. Perhaps the system requires should state the need for 4+ GB of disk space. Maybe they already do and I just missed that.

Recommended Solution
  0  
  0  
#3
Options
4 Reply
Re:Can't successfully install and start tpeap Omada controller software on Linux host
2019-11-01 09:29:47

I'll just these log files here anyway in case they're useful;

 

/opt/tplink/EAPController/logs/startup.log

java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)
commons daemon version "1.0.15-dev"
commons daemon process (id: 205, parent: 202)
Going to init controller!
Going to start controller!
Exception in thread "Thread-0" java.lang.IllegalArgumentException: URI is not hierarchical
        at java.io.File.<init>(File.java:418)
        at com.tp_link.eap.util.g.a.a(SourceFile:47)
        at com.tp_link.eap.configuration.b.a(SourceFile:58)
        at com.tp_link.eap.util.o.c(SourceFile:443)
        at com.tp_link.eap.util.o.b(SourceFile:434)
        at com.tp_link.eap.start.f.run(SourceFile:35)
startup...
Nov 01, 2019 9:19:19 AM org.hibernate.validator.internal.util.Version <clinit>
INFO: HV000001: Hibernate Validator 4.3.1.Final
Failed to start omada controller, going to exit
ShutdownHook: service stopped.
Service exit with a return value of 1
 

 

 

/opt/tplink/EAPController/logs/server.log

2019-11-01 09:15:42 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : jetty.properties
2019-11-01 09:15:42 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : device.properties
2019-11-01 09:15:42 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : mongodb.properties
2019-11-01 09:15:42 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : netty.properties
2019-11-01 09:15:42 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : user.params.properties
2019-11-01 09:15:42 [main] [WARN]-[SourceFile:108] - can't get resolve value for key: appender.rolling.fileName
2019-11-01 09:15:42 [main] [WARN]-[SourceFile:108] - can't get resolve value for key: appender.rolling.strategy.action.basepath
2019-11-01 09:15:42 [main] [WARN]-[SourceFile:108] - can't get resolve value for key: appender.rolling.filePattern
2019-11-01 09:15:42 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : log4j2.properties
2019-11-01 09:15:42 [main] [INFO]-[SubstituteLogger.java:169] - success to load configuration : eap.properties
2019-11-01 09:15:43 [main] [INFO]-[SourceFile:94] - going to start mongod.
2019-11-01 09:17:23 [main] [WARN]-[SourceFile:124] - Fail to start mongo DB server
2019-11-01 09:17:23 [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:125) ~[eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.c.a.e(SourceFile:75) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.g(SourceFile:324) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.y(SourceFile:410) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.a(SourceFile:95) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.h(SourceFile:350) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.EapLinuxMain.b(SourceFile:79) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.EapLinuxMain.start(SourceFile:36) [eap-start-3.2.1.jar:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_162]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_162]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
        at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) [commons-daemon-1.0.15.jar:1.0.15]
2019-11-01 09:17:25 [main] [INFO]-[SourceFile:168] - mongod is not running
2019-11-01 09:19:05 [main] [WARN]-[SourceFile:124] - Fail to start mongo DB server
2019-11-01 09:19:05 [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:125) ~[eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.c.a.e(SourceFile:75) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.g(SourceFile:324) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.v(SourceFile:317) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.y(SourceFile:413) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.a(SourceFile:95) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.a.h(SourceFile:350) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.EapLinuxMain.b(SourceFile:79) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.EapLinuxMain.start(SourceFile:36) [eap-start-3.2.1.jar:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_162]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_162]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
        at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) [commons-daemon-1.0.15.jar:1.0.15]
2019-11-01 09:19:07 [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.1.33:0) anyway as requested.
2019-11-01 09:19:10 [main] [INFO]-[ContextHandler.java:2040] - Initializing Spring root WebApplicationContext
2019-11-01 09:19:11 [pool-5-thread-1] [INFO]-[SourceFile:91] - Omada Controller isn't prepared to handle event
2019-11-01 09:19:16 [pool-5-thread-2] [INFO]-[SourceFile:91] - Omada Controller isn't prepared to handle event
2019-11-01 09:19:16 [Thread-3] [INFO]-[SourceFile:168] - mongod is not running
2019-11-01 09:19:16 [Thread-3] [INFO]-[SourceFile:491] - mongod was shutdown , restarting it
2019-11-01 09:19:21 [pool-5-thread-3] [INFO]-[SourceFile:91] - Omada Controller isn't prepared to handle event
2019-11-01 09:19:26 [pool-5-thread-1] [INFO]-[SourceFile:91] - Omada Controller isn't prepared to handle event
2019-11-01 09:19:31 [pool-5-thread-2] [INFO]-[SourceFile:91] - Omada Controller isn't prepared to handle event
2019-11-01 09:19:36 [pool-5-thread-3] [INFO]-[SourceFile:91] - Omada Controller isn't prepared to handle event
2019-11-01 09:19:41 [pool-5-thread-1] [INFO]-[SourceFile:91] - Omada Controller isn't prepared to handle event
2019-11-01 09:19:46 [pool-5-thread-2] [INFO]-[SourceFile:91] - Omada Controller isn't prepared to handle event
2019-11-01 09:19:49 [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)}}]
        at org.springframework.data.mongodb.core.MongoExceptionTranslator.translateExceptionIfPossible(MongoExceptionTranslator.java:77) ~[spring-data-mongodb-1.10.17.RELEASE.jar:?]
        at org.springframework.data.mongodb.core.index.MongoPersistentEntityIndexCreator.createIndex(MongoPersistentEntityIndexCreator.java:162) ~[spring-data-mongodb-1.10.17.RELEASE.jar:?]
        at org.springframework.data.mongodb.core.index.MongoPersistentEntityIndexCreator.checkForAndCreateIndexes(MongoPersistentEntityIndexCreator.java:133) ~[spring-data-mongodb-1.10.17.RELEASE.jar:?]
        at org.springframework.data.mongodb.core.index.MongoPersistentEntityIndexCreator.checkForIndexes(MongoPersistentEntityIndexCreator.java:125) ~[spring-data-mongodb-1.10.17.RELEASE.jar:?]
        at org.springframework.data.mongodb.core.index.MongoPersistentEntityIndexCreator.onApplicationEvent(MongoPersistentEntityIndexCreator.java:109) ~[spring-data-mongodb-1.10.17.RELEASE.jar:?]
at org.springframework.data.mongodb.core.index.MongoPersistentEntityIndexCreator.onApplicationEvent(MongoPersistentEntityIndexCreator.java:51) ~[spring-data-mongodb-1.10.17.RELEASE.jar:?]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:122) ~[spring-context-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.springframework.context.support.AbstractApplicationContext.registerListeners(AbstractApplicationContext.java:825) ~[spring-context-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:540) ~[spring-context-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:443) ~[spring-web-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:325) [spring-web-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107) [spring-web-4.3.21.RELEASE.jar:4.3.21.RELEASE]
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782) [jetty-server-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424) [jetty-servlet-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774) [jetty-server-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249) [jetty-servlet-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242) [jetty-webapp-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717) [jetty-server-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494) [jetty-webapp-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) [jetty-util-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) [jetty-server-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172) [jetty-server-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) [jetty-util-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) [jetty-server-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.server.Server.doStart(Server.java:282) [jetty-server-8.1.15.v20140411.jar:8.1.15.v20140411]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) [jetty-util-8.1.15.v20140411.jar:8.1.15.v20140411]
        at com.tp_link.eap.start.c.b.a(SourceFile:40) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.c.a.e(SourceFile:75) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.task.EapJettyStartUpTask.a(SourceFile:19) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.m.e.a(SourceFile:13) [eap-infrastructure-3.2.1.jar:?]
        at com.tp_link.eap.start.a.i(SourceFile:446) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.EapLinuxMain.b(SourceFile:86) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.EapLinuxMain.start(SourceFile:36) [eap-start-3.2.1.jar:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_162]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_162]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
        at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) [commons-daemon-1.0.15.jar:1.0.15]
Caused by: 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)}}]
        at com.mongodb.connection.BaseCluster.createTimeoutException(BaseCluster.java:377) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.connection.BaseCluster.selectServer(BaseCluster.java:104) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.binding.ClusterBinding$ClusterBindingConnectionSource.<init>(ClusterBinding.java:75) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.binding.ClusterBinding$ClusterBindingConnectionSource.<init>(ClusterBinding.java:71) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.binding.ClusterBinding.getWriteConnectionSource(ClusterBinding.java:68) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.operation.OperationHelper.withConnection(OperationHelper.java:415) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.operation.CreateIndexesOperation.execute(CreateIndexesOperation.java:144) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.operation.CreateIndexesOperation.execute(CreateIndexesOperation.java:71) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.Mongo.execute(Mongo.java:845) ~[mongo-java-driver-3.4.3.jar:?]
        at com.mongodb.Mongo$2.execute(Mongo.java:828) ~[mongo-java-driver-3.4.3.jar:?]

 at com.mongodb.DBCollection.createIndex(DBCollection.java:1618) ~[mongo-java-driver-3.4.3.jar:?]
        at org.springframework.data.mongodb.core.index.MongoPersistentEntityIndexCreator.createIndex(MongoPersistentEntityIndexCreator.java:142) ~[spring-data-mongodb-1.10.17.RELEASE.jar:?]
        ... 39 more
2019-11-01 09:19:49 [main] [ERROR]-[SourceFile:72] - java.lang.NullPointerException
java.lang.NullPointerException: null
        at com.tp_link.eap.start.task.EapMetaDataInitTask.a(SourceFile:28) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.m.e.a(SourceFile:13) [eap-infrastructure-3.2.1.jar:?]
        at com.tp_link.eap.start.a.i(SourceFile:446) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.EapLinuxMain.b(SourceFile:86) [eap-start-3.2.1.jar:?]
        at com.tp_link.eap.start.EapLinuxMain.start(SourceFile:36) [eap-start-3.2.1.jar:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_162]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_162]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
        at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) [commons-daemon-1.0.15.jar:1.0.15]
2019-11-01 09:19:49 [main] [ERROR]-[SourceFile:17] - Failed to start omada controller, going to exit

 

  0  
  0  
#2
Options
Re:Can't successfully install and start tpeap Omada controller software on Linux host-Solution
2019-11-01 09:59:35 - last edited 2021-02-10 15:26:33

Oh.

 

https://community.tp-link.com/en/business/forum/topic/161211?replyId=327475

 

I didn't occur to me that it would need so much disk space. Perhaps the system requires should state the need for 4+ GB of disk space. Maybe they already do and I just missed that.

Recommended Solution
  0  
  0  
#3
Options
Re:Can't successfully install and start tpeap Omada controller software on Linux host
2021-02-09 21:52:51

@PhilV You just saved me from another 24h of ripping my heair out.  Thank you for that little note, increasing my VM from 4GB to 10GB solved this instantly.

  1  
  1  
#4
Options
Re:Can't successfully install and start tpeap Omada controller software on Linux host
2021-02-10 15:33:38

@pensive_tom You don't even need that much it seems, my controller has just 4.5 GB assigned and its only actually using 1GB of that now, maybe the initial install just needs more room to unpack. You can always keep an eye on what it's using and reduce it down. RAM usage is pretty low too, I've assigned 512MB but it rarely uses more than 256

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 5818

Replies: 4

Related Articles
TPEAP won't start.
1272 0
 Can't install Omada Controller software
2840 0
Can't start controller after port change
2193 0
How to determine which Omada version to install
984 0
 How to successfully open Omada Discovery Utility?
4719 0
 Omada Start failed
352 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.