CooperKC Posted January 5, 2022 Share Posted January 5, 2022 Greetings, Having trouble with the Omada Controller container. It fails to pull the image. I get the following (see below). Any idea what could be causing this? ---------------------------------------------------------------------------------------------------------------------------------------- Pulling image: mbentley/omada-controller:latest TOTAL DATA PULLED: 0 B Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='Omada-controller' --net='host' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'MANAGE_HTTPS_PORT'='18043' -e 'MANAGE_HTTP_PORT'='18088' -e 'PORTAL_HTTPS_PORT'='18843' -e 'PORTAL_HTTP_PORT'='18088' -v '/mnt/cache_nvme_apps_docker/appdata/Omada Controller/data/':'/opt/tplink/EAPController/data':'rw,slave' -v '/mnt/cache_nvme_apps_docker/appdata/Omada Controller/work/':'/opt/tplink/EAPController/work':'rw,slave' -v '/mnt/cache_nvme_apps_docker/appdata/Omada Controller/logs/':'/opt/tplink/EAPController/logs':'rw,slave' 'mbentley/omada-controller' Unable to find image 'mbentley/omada-controller:latest' locally Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.10.20:53: read udp 192.168.10.10:52651->192.168.10.20:53: i/o timeout The command failed. Quote Link to comment
hedrinbc Posted January 6, 2022 Author Share Posted January 6, 2022 Hey there, the addresses in the error below seem to tell me that the DNS lookup for registry-1.docker.io failed for you. Are you able to download other dockers right now? 1 hour ago, CooperKC said: Unable to find image 'mbentley/omada-controller:latest' locally Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.10.20:53: read udp 192.168.10.10:52651->192.168.10.20:53: i/o timeout The command failed. Quote Link to comment
mhn_10 Posted January 6, 2022 Share Posted January 6, 2022 I'm facing an issue with webui not loading. The container starts in docker tab, but when I check logs, I see the below error 2022-01-05 18:44:26 [main] [WARN]-[SourceFile:367] - Mongo Client connect error while init Jetty.com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting to connect. 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)}}] 2022-01-05 18:45:07 [mongo-check-thread] [WARN]-[SourceFile:151] - Fail to start mongo DB server 2022-01-05 18:45:07 [mongo-check-thread] [WARN]-[SourceFile:78] - com.tplink.omada.start.a.a: Fail to start mongo DB server com.tplink.omada.start.a.a: Fail to start mongo DB server at com.tplink.omada.start.b.d.a(SourceFile:152) ~[omada-start.jar:?] at com.tplink.omada.start.b.b.e(SourceFile:75) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.d(SourceFile:224) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.n(SourceFile:217) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.x(SourceFile:335) ~[omada-start.jar:?] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312] Any suggestion on what I can do Quote Link to comment
CooperKC Posted January 6, 2022 Share Posted January 6, 2022 11 hours ago, hedrinbc said: Hey there, the addresses in the error below seem to tell me that the DNS lookup for registry-1.docker.io failed for you. Are you able to download other dockers right now? Interesting... As it turns out I can't. Time to look and see what's going on with DNS. Quote Link to comment
CooperKC Posted January 7, 2022 Share Posted January 7, 2022 On 1/5/2022 at 7:29 PM, hedrinbc said: Hey there, the addresses in the error below seem to tell me that the DNS lookup for registry-1.docker.io failed for you. Are you able to download other dockers right now? Thanks for the assist. It turns out when I changed my DNS to utilize PiHole, it messed things up with my UnRAID server. Thanks again! 1 Quote Link to comment
hedrinbc Posted January 7, 2022 Author Share Posted January 7, 2022 On 1/5/2022 at 8:58 PM, mhn_10 said: I'm facing an issue with webui not loading. The container starts in docker tab, but when I check logs, I see the below error 2022-01-05 18:44:26 [main] [WARN]-[SourceFile:367] - Mongo Client connect error while init Jetty.com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting to connect. 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)}}] 2022-01-05 18:45:07 [mongo-check-thread] [WARN]-[SourceFile:151] - Fail to start mongo DB server 2022-01-05 18:45:07 [mongo-check-thread] [WARN]-[SourceFile:78] - com.tplink.omada.start.a.a: Fail to start mongo DB server com.tplink.omada.start.a.a: Fail to start mongo DB server at com.tplink.omada.start.b.d.a(SourceFile:152) ~[omada-start.jar:?] at com.tplink.omada.start.b.b.e(SourceFile:75) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.d(SourceFile:224) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.n(SourceFile:217) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.x(SourceFile:335) ~[omada-start.jar:?] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312] Any suggestion on what I can do @mhn_10 Sorry for late response. Not sure why your database woudl fail to start. Not sure it it might help to re-download the docker? If you switch from "basic view" to "advanced view" in the upper right of docker tab you can "force update" that I think will re-download the container. Next thing I'd do I guess is if you could share your settings? Quote Link to comment
mhn_10 Posted January 8, 2022 Share Posted January 8, 2022 INFO: Time zone set to 'America/Los_Angeles' INFO: Setting 'manage.http.port' to 18088 in omada.properties INFO: Setting 'manage.https.port' to 18043 in omada.properties INFO: Setting 'portal.http.port' to 18088 in omada.properties INFO: Setting 'portal.https.port' to 18843 in omada.properties INFO: Starting Omada Controller as user omada 01-07-2022 17:57:47.590 INFO [log4j-thread] [] c.t.s.o.c.o.a.b(32): success to load configuration omada.properties 01-07-2022 17:57:47.658 INFO [main] [] c.t.s.o.s.OmadaBootstrap(79): going to start local mongod. 01-07-2022 17:59:27.773 ERROR [main] [] c.t.s.f.c.FacadeUtils(68): facadeMsgEnable is not enable, msg: Fail to start mongo DB server 01-07-2022 17:59:27.774 WARN [main] [] c.t.s.o.s.s.b(145): Fail to start mongo DB server 01-07-2022 17:59:27.775 WARN [main] [] c.t.s.o.s.s.a(77): com.tplink.smb.omada.starter.b.a: Fail to start mongo DB server com.tplink.smb.omada.starter.b.a: Fail to start mongo DB server at com.tplink.smb.omada.starter.server.b.a(SourceFile:146) ~[local-starter-5.0.29.jar:5.0.29] at com.tplink.smb.omada.starter.server.a.e(SourceFile:74) [local-starter-5.0.29.jar:5.0.29] at com.tplink.smb.omada.starter.OmadaBootstrap.d(SourceFile:218) [local-starter-5.0.29.jar:5.0.29] at com.tplink.smb.omada.starter.OmadaBootstrap.q(SourceFile:290) [local-starter-5.0.29.jar:5.0.29] at com.tplink.smb.omada.starter.OmadaBootstrap.a(SourceFile:89) [local-starter-5.0.29.jar:5.0.29] at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:245) [local-starter-5.0.29.jar:5.0.29] at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:84) [local-starter-5.0.29.jar:5.0.29] at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:36) [local-starter-5.0.29.jar:5.0.29] I tried re-downloading the docker by force update. But I still get the same error. Could it be some permission issue with my shares? Attaching my docker settings. My appdata is set to public, if that would help Not sure if this issue is related. https://github.com/mbentley/docker-omada-controller/issues/138 It looks similar, but not sure how to resolve it. Quote Link to comment
jarkle Posted January 18, 2022 Share Posted January 18, 2022 What do I need to do to upgrade to version 5? Quote Link to comment
jarkle Posted February 3, 2022 Share Posted February 3, 2022 Just circling back on this if anyone can offer me some guidance? Quote Link to comment
Vhile1 Posted February 18, 2022 Share Posted February 18, 2022 (edited) I have been having issues with the same errors in the log as @jarkle, only fix so far has been to create all new folders and pull down the docker again. If the docker goes offline when it is started again mongodb fails to start. Edited February 18, 2022 by Vhile1 Quote Link to comment
GalacticSpines Posted March 18, 2022 Share Posted March 18, 2022 Anyone having this issue where Omada is keeping all the Unraid drive from spinning down due to file activity? This happens across all my drives. Quote Link to comment
Januszmirek Posted April 27, 2022 Share Posted April 27, 2022 (edited) I also have a problem with setting up this container. The problem in my case appears to be with ports not paths. For the world I am unable to change the port settings. Even though the ports in Edit appear to be set properly and don't interfere with other container ports: After saving the config, the container sets the ports on its own regardless of the settings I made: I cant use above ports for omada (8043, 8088, 8043) as I use it for a different container and don't want to mess things up with that other container. This is the first instance I see such behaviour with the container, where editing the ports does not have any effect on actual changes to container. Usually the workaround I used was to change network type from host to bridge, but in bridge mode omada webui mode is not available;( I also tried to delete the default ports in the container which use Variable config type, and set it as Ports (instead of Variable) - still no joy;( Any ideas on how to force the port change? Btw, when I turn off the other container, omada works great, so its not the paths config issue, but ports in my case. Edited April 27, 2022 by Januszmirek typos Quote Link to comment
Phreaknes Posted June 18, 2022 Share Posted June 18, 2022 I'm going to try this again in the hopes that I can get some help on this problem. I'm at my wits end. I'm new to unraid and I need to get this system back online. I've been fighting this since late last year. I have a 6.9.2 XFS UnRaid install with three 2Tb drives a 6tb parity drive and a 500GB cache drive. I only have Binhex-krusader and Plex-media-server dockers and a Home Assistant VM. I have edited the original docker settings for Host paths to these so they're on the SSD as suggested in several post. /mnt/cache/appdata/omada/data/ /mnt/cache/appdata/omada/work/ /mnt/cache/appdata/omada/logs/ All other settings are stock. What is happening is after a fresh docker install I can get in, setup a new system or restore a backup and everything for the most part runs very well but after 36 hours the docker crashes and you get a message the please wait while Omada is loading but never gets me to a login screen. I have installed this docker 10+ times with the same results. This includes different versions of the Omada controller with the same results. Below is a recent reddit thread that I had with a kind soul but Mongodb isn't their specialty it includes a Mongodb log. Below is a recent log from a fresh docker install after about 36 hours. This all seems to be around the Mongodb failing / crashing. . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.6.6) 06-12-2022 06:35:39.027 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(55): Starting OmadaLinuxMain v5.3.1 using Java 1.8.0_312 on PhreakServe with PID 1 (/opt/tplink/EAPController/lib/local-starter-5.3.1.jar started by omada in /opt/tplink/EAPController/lib) 06-12-2022 06:35:39.030 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(640): No active profile set, falling back to 1 default profile: "default" 06-12-2022 06:35:45.592 WARN [main] [] o.s.d.c.CustomConversions(261): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation. 06-12-2022 06:35:47.864 WARN [main] [] o.s.d.c.CustomConversions(261): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation. 06-12-2022 06:35:51.512 INFO [main] [] c.t.s.l.c.s.d.CacheLogConsumeHandler(61): log mq consume task is start... 06-12-2022 06:35:51.514 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(61): Started OmadaLinuxMain in 12.883 seconds (JVM running for 17.255) 06-12-2022 06:35:52.583 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(124): upgrade workGroup core thread num is 16, max thread num is 16 06-12-2022 06:35:52.619 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(151): upgradeSendReq workGroup core thread num is 16, max thread num is 16 06-12-2022 06:35:52.788 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(97): manager workGroup core thread num is 16, max thread num is 16 06-12-2022 06:35:53.587 INFO [main] [] c.t.s.o.m.d.d.m.d.a.c.ApBatchGroupConfig(36): apBatchGroup thread size is 17, queue size is 1500 06-12-2022 06:35:53.737 INFO [main] [] c.t.s.o.m.c.d.m.s.w.s.c.WirelessGroupConfig(37): ssidWorkerGroup thread size is 17, queue size is 1500 06-12-2022 06:35:54.457 INFO [main] [] c.t.s.e.s.c.c(158): start schedule remove expire device... period = 10 06-12-2022 06:35:54.463 INFO [main] [] c.t.s.e.s.c.c(145): update rateLimiterCache, permitsPerSecond = 5.0 06-12-2022 06:35:54.485 INFO [main] [] c.t.s.o.m.d.d.m.m.c.DeviceMsgConfig(38): setMsgThreadPool thread size is 16, queue size is 10000 06-12-2022 06:35:54.718 INFO [main] [] c.t.s.o.s.d.a(78): Db unchanged. No need to compatible or init data. 06-12-2022 06:35:59.710 INFO [mongo-check-thread] [] c.t.s.o.s.OmadaBootstrap(352): mongod was shutdown, restarting it 06-12-2022 06:35:59.710 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(213): Going to stop mongod which pid is 55 06-12-2022 06:36:03.325 ERROR [main] [] c.t.s.o.s.OmadaBootstrap(319): org.springframework.dao.DataAccessResourceFailureException: Prematurely reached end of stream; nested exception is com.mongodb.MongoSocketReadException: Prematurely reached end of stream org.springframework.dao.DataAccessResourceFailureException: Prematurely reached end of stream; nested exception is com.mongodb.MongoSocketReadException: Prematurely reached end of stream at org.springframework.data.mongodb.core.MongoExceptionTranslator.translateExceptionIfPossible(MongoExceptionTranslator.java:85) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.mongodb.core.MongoTemplate.potentiallyConvertRuntimeException(MongoTemplate.java:2929) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.mongodb.core.MongoTemplate.executeFindMultiInternal(MongoTemplate.java:2865) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.mongodb.core.MongoTemplate.doFind(MongoTemplate.java:2605) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.mongodb.core.ExecutableFindOperationSupport$ExecutableFindSupport.doFind(ExecutableFindOperationSupport.java:220) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.mongodb.core.ExecutableFindOperationSupport$ExecutableFindSupport.oneValue(ExecutableFindOperationSupport.java:132) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.mongodb.repository.query.AbstractMongoQuery.lambda$getExecution$4(AbstractMongoQuery.java:159) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.mongodb.repository.query.AbstractMongoQuery.doExecute(AbstractMongoQuery.java:132) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.mongodb.repository.query.AbstractMongoQuery.execute(AbstractMongoQuery.java:107) ~[spring-data-mongodb-3.3.3.jar:3.3.3] at org.springframework.data.repository.core.support.RepositoryMethodInvoker.doInvoke(RepositoryMethodInvoker.java:137) ~[spring-data-commons-2.6.3.jar:2.6.3] at org.springframework.data.repository.core.support.RepositoryMethodInvoker.invoke(RepositoryMethodInvoker.java:121) ~[spring-data-commons-2.6.3.jar:2.6.3] at org.springframework.data.repository.core.support.QueryExecutorMethodInterceptor.doInvoke(QueryExecutorMethodInterceptor.java:159) ~[spring-data-commons-2.6.3.jar:2.6.3] at org.springframework.data.repository.core.support.QueryExecutorMethodInterceptor.invoke(QueryExecutorMethodInterceptor.java:138) ~[spring-data-commons-2.6.3.jar:2.6.3] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215) ~[spring-aop-5.3.18.jar:5.3.18] at com.sun.proxy.$Proxy180.findByAccountId(Unknown Source) ~[?:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_312] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_312] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_312] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_312] at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:137) ~[spring-tx-5.3.18.jar:5.3.18] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215) ~[spring-aop-5.3.18.jar:5.3.18] at com.sun.proxy.$Proxy180.findByAccountId(Unknown Source) ~[?:?] at com.tplink.smb.omada.identityaccess.port.mongo.adaptor.persistence.tenant.a.a(SourceFile:32) ~[identityaccess-port-mongo-5.3.1.jar:5.3.1] at com.tplink.smb.omada.identityaccess.port.mongo.adaptor.persistence.tenant.a$$FastClassBySpringCGLIB$$d19782ef.invoke(<generated>) ~[identityaccess-port-mongo-5.3.1.jar:5.3.1] at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.3.18.jar:5.3.18] at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:783) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:137) ~[spring-tx-5.3.18.jar:5.3.18] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753) ~[spring-aop-5.3.18.jar:5.3.18] at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:698) ~[spring-aop-5.3.18.jar:5.3.18] at com.tplink.smb.omada.identityaccess.port.mongo.adaptor.persistence.tenant.a$$EnhancerBySpringCGLIB$$3707c08b.a(<generated>) ~[identityaccess-port-mongo-5.3.1.jar:5.3.1] at com.tplink.smb.omada.identityaccess.domain.model.c.h.a(SourceFile:31) ~[identityaccess-core-5.3.1.jar:5.3.1] at com.tplink.smb.omada.identityaccess.domain.model.c.h$$FastClassBySpringCGLIB$$cfd076bb.invoke(<generated>) ~[identityaccess-core-5.3.1.jar:5.3.1] at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.3.18.jar:5.3.18] at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:689) ~[spring-aop-5.3.18.jar:5.3.18] at com.tplink.smb.omada.identityaccess.domain.model.c.h$$EnhancerBySpringCGLIB$$d977a6c2.a(<generated>) ~[identityaccess-core-5.3.1.jar:5.3.1] at com.tplink.smb.omada.identityaccess.b.e.b(SourceFile:54) ~[identityaccess-core-5.3.1.jar:5.3.1] at com.tplink.smb.omada.identityaccess.port.common.d.f.b(SourceFile:40) ~[identityaccess-core-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.task.OmadacInitTask.doDbUnchanged(SourceFile:146) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.d.a.c(SourceFile:140) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.d.a.b(SourceFile:79) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.d.a.a(SourceFile:44) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.task.OmadacInitTask.execute(SourceFile:64) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.task.c.a(SourceFile:20) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.OmadaBootstrap.f(SourceFile:317) [local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:91) [local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:36) [local-starter-5.3.1.jar:5.3.1] Caused by: com.mongodb.MongoSocketReadException: Prematurely reached end of stream at com.mongodb.internal.connection.SocketStream.read(SocketStream.java:112) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.SocketStream.read(SocketStream.java:131) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.InternalStreamConnection.receiveResponseBuffers(InternalStreamConnection.java:718) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.InternalStreamConnection.receiveMessageWithAdditionalTimeout(InternalStreamConnection.java:576) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.InternalStreamConnection.receiveCommandMessageResponse(InternalStreamConnection.java:415) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.InternalStreamConnection.sendAndReceive(InternalStreamConnection.java:342) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.UsageTrackingInternalConnection.sendAndReceive(UsageTrackingInternalConnection.java:116) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.DefaultConnectionPool$PooledConnection.sendAndReceive(DefaultConnectionPool.java:647) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.CommandProtocolImpl.execute(CommandProtocolImpl.java:71) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:244) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:227) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:127) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:117) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.connection.DefaultServer$OperationCountTrackingConnection.command(DefaultServer.java:348) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.CommandOperationHelper.createReadCommandAndExecute(CommandOperationHelper.java:228) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.FindOperation.lambda$execute$1(FindOperation.java:666) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.OperationHelper.lambda$withSourceAndConnection$2(OperationHelper.java:564) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.OperationHelper.withSuppliedResource(OperationHelper.java:589) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.OperationHelper.lambda$withSourceAndConnection$3(OperationHelper.java:563) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.OperationHelper.withSuppliedResource(OperationHelper.java:589) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.OperationHelper.withSourceAndConnection(OperationHelper.java:562) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.FindOperation.lambda$execute$2(FindOperation.java:661) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.async.function.RetryingSyncSupplier.get(RetryingSyncSupplier.java:65) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.FindOperation.execute(FindOperation.java:692) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.internal.operation.FindOperation.execute(FindOperation.java:86) ~[mongodb-driver-core-4.4.2.jar:?] at com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.execute(MongoClientDelegate.java:191) ~[mongodb-driver-sync-4.4.2.jar:?] at com.mongodb.client.internal.MongoIterableImpl.execute(MongoIterableImpl.java:135) ~[mongodb-driver-sync-4.4.2.jar:?] at com.mongodb.client.internal.MongoIterableImpl.iterator(MongoIterableImpl.java:92) ~[mongodb-driver-sync-4.4.2.jar:?] at org.springframework.data.mongodb.core.MongoTemplate.executeFindMultiInternal(MongoTemplate.java:2853) ~[spring-data-mongodb-3.3.3.jar:3.3.3] ... 53 more 06-12-2022 06:36:04.710 WARN [https-jsse-nio-18043-exec-6] [] o.s.d.c.CustomConversions(261): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation. 06-12-2022 06:36:04.722 WARN [https-jsse-nio-18043-exec-6] [] o.s.d.c.CustomConversions(261): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation. 06-12-2022 06:37:41.832 ERROR [mongo-check-thread] [] c.t.s.f.c.FacadeUtils(68): facadeMsgEnable is not enable, msg: Fail to start mongo DB server 06-12-2022 06:37:41.833 WARN [mongo-check-thread] [] c.t.s.o.s.s.b(145): Fail to start mongo DB server 06-12-2022 06:37:41.833 WARN [mongo-check-thread] [] c.t.s.o.s.s.a(77): com.tplink.smb.omada.starter.b.a: Fail to start mongo DB server com.tplink.smb.omada.starter.b.a: Fail to start mongo DB server at com.tplink.smb.omada.starter.server.b.a(SourceFile:146) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.server.a.e(SourceFile:74) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.OmadaBootstrap.d(SourceFile:225) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.OmadaBootstrap.n(SourceFile:218) ~[local-starter-5.3.1.jar:5.3.1] at com.tplink.smb.omada.starter.OmadaBootstrap.x(SourceFile:353) ~[local-starter-5.3.1.jar:5.3.1] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312] 06-12-2022 06:37:53.850 INFO [mongo-check-thread] [] c.t.s.o.s.OmadaBootstrap(352): mongod was shutdown, restarting it 06-12-2022 06:37:55.383 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(161): mongodb process id is 251 06-12-2022 06:37:55.384 ERROR [mongo-check-thread] [] c.t.s.f.c.FacadeUtils(68): facadeMsgEnable is not enable, msg: Mongo DB server started 06-12-2022 06:37:55.384 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(142): Mongo DB server started 06-12-2022 06:37:55.864 INFO [https-jsse-nio-18043-exec-5] [] c.t.s.o.a.d.InterruptBeforeInitFinishedInterceptor(36): Controller is starting up, cannot handle request Quote Link to comment
Dark_Bubbles Posted July 31, 2022 Share Posted July 31, 2022 I saw this mentioned in an earlier comment, but I don't see the fix mentioned. I have the Omada controller running in a docker container, but when I reboot my server and go back into the GUI, it is like it is the first time it has ever been opened. I have to input all the data and then restore from an old backup. It even has me update the docker container each time. It seems like none of the changes to the container itself survive a reboot, almost like it is all held in RAM, rather than on the cache drive (which is a 480G nvme drive, if that matters). Quote Link to comment
_whatever Posted August 3, 2022 Share Posted August 3, 2022 While this docker container works great on Unraid, if you're using it on a drive formatted with Btrfs, you might be killing your drive(s). A couple of months ago I gave my son my TP-Link OC200 for this apartment setup and I decided to replace it with this docker container on my Unraid server. The other day I noticed that my cache drives, where the docker data lives, had unusually high numbers of writes accumulated, and after using iotop I saw the biggest contributor was mongod, followed closely by btrfs-transacti. Then a lightbulb went off in my head. I remembered reading some time ago about the gotchas of Btrfs and workloads with a lot of random writes (databases) causing excessive fragmentation and thrashing discs. This excellent post on the MongoDB community forums explains the issue very well. So I was left with 3 choices in that moment: Upgrade my Unraid license so I could add an XFS formatted drive for the Omada controller data. Remove one of the drives from my mirrored Btrfs array and make it a standalone XFS drive for the Omada controller. Figure out a way to retroactively turn off CoW for the MongoDB data. Since I was pressed for time (and money), option 3 seemed best, so that's the route I went, using these great instructions on the Arch Wiki. Because I had been previously bitten by the loopback write amplification bug with in Unraid 6.8 I had switched from using a docker image to having docker write directly to disk. This made things a little bit easier since I had direct access to the database. So I stopped the docker service went to the terminal, renamed the db folder in /mnt/cache/appdata/omada/data to 'dbold', created a new folder named 'db' and added the +C attribute, then used cp to recursively copy everything from dbold to db using the --reflink=never switch. Started the docker service back up and kept my fingers crossed. So far the number of writes does seem to be down considerably. I'll keep an eye on it over the next few weeks to be sure. My long term plan is to rebuild my server soon anyway b/c these drives are REALLY old SATA SSDs from like 2017. So once I get to that point I'll probably switch to NVMe for cache and dedicate a cheap SATA drive formatted XFS for anything with a database workload, just to play it safe. YMMV. Quote Link to comment
Hadrian_Aurelius Posted August 22, 2022 Share Posted August 22, 2022 I have the same problem(s) that other have reported in this thread. After a month of constantly messing around with then wiping the container before it once again inevitably crashes, I've given up and installed the controller in an Ubuntu VM. Works fine and doesn't have any of these problems. Something just isn't right with this container. I run lots of other containers in Unraid and had/have none of the issues this one has. Quote Link to comment
nxtiak Posted September 23, 2022 Share Posted September 23, 2022 (edited) The internet capacity input box doesn't show up for me. It's been like this for months. I've tried different browsers, different computers. Edited September 23, 2022 by nxtiak Quote Link to comment
nxtiak Posted October 25, 2022 Share Posted October 25, 2022 So the controller updated to 6.5.3 and now my router ER605 v2 is constantly provisioning, adopting, provisioning in a loop. Power cycled it and still doing it. Quote Link to comment
MaxAbsorbency Posted October 28, 2022 Share Posted October 28, 2022 First off, thanks for the container, very useful. On 10/24/2022 at 10:05 PM, nxtiak said: So the controller updated to 6.5.3 and now my router ER605 v2 is constantly provisioning, adopting, provisioning in a loop. Power cycled it and still doing it. TL-R605 v1.0 here no issue but I have heard of others having this issue - maybe its a device/version/firmware combination with the new version of the controller software? Quote Link to comment
ardendolas Posted November 12, 2022 Share Posted November 12, 2022 Many thanks for the container, I used to run the Omada software on one of our windows PCs, but having it all under my server is so much better. That said, it has installed properly, and was running fine for a while, but now suddenly it won't start. Something about failing to start mongo DB server? I do see one warning about ownership not being set, but the process seems to set it itself... I'm at a loss here... Any advice would be appreciated tail: '/opt/tplink/EAPController/logs/server.log' has become inaccessible: No such file or directory tail: '/opt/tplink/EAPController/logs/server.log' has appeared; following new file INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) doesn't exist; creating INFO: User (omada) doesn't exist; creating INFO: Time zone set to 'America/New_York' INFO: Setting 'manage.http.port' to 18088 in omada.properties INFO: Setting 'manage.https.port' to 18043 in omada.properties INFO: Setting 'portal.http.port' to 18088 in omada.properties INFO: Setting 'portal.https.port' to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf' WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada) INFO: Version check passed; image version (5.6.3) >= the last version ran (5.6.3); writing image version to last ran file... INFO: Starting Omada Controller as user omada 11-12-2022 01:11:17.925 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller 11-12-2022 01:11:17.933 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished 11-12-2022 01:11:17.957 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished 11-12-2022 01:11:17.959 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare 11-12-2022 01:11:17.960 INFO [log4j-thread] [] c.t.s.o.c.o.a.b(): success to load configuration omada.properties 11-12-2022 01:11:17.961 INFO [log4j-thread] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller 11-12-2022 01:11:18.025 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod. 11-12-2022 01:12:58.103 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Fail to start mongo DB server 11-12-2022 01:12:58.103 WARN [main] [] c.t.s.o.s.s.b(): Fail to start mongo DB server 11-12-2022 01:12:58.103 WARN [main] [] c.t.s.o.s.s.a(): com.tplink.smb.omada.starter.b.a: Fail to start mongo DB server com.tplink.smb.omada.starter.b.a: Fail to start mongo DB server at com.tplink.smb.omada.starter.server.b.a(SourceFile:151) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.server.a.e(SourceFile:74) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.d(SourceFile:248) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.q(SourceFile:328) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.a(SourceFile:115) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:277) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:92) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:42) ~[local-starter-5.6.3.jar:5.6.3] 11-12-2022 01:14:40.153 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Fail to start mongo DB server 11-12-2022 01:14:40.153 WARN [main] [] c.t.s.o.s.s.b(): Fail to start mongo DB server 11-12-2022 01:14:40.153 WARN [main] [] c.t.s.o.s.s.a(): com.tplink.smb.omada.starter.b.a: Fail to start mongo DB server com.tplink.smb.omada.starter.b.a: Fail to start mongo DB server at com.tplink.smb.omada.starter.server.b.a(SourceFile:151) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.server.a.e(SourceFile:74) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.d(SourceFile:248) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.n(SourceFile:241) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.q(SourceFile:331) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.a(SourceFile:115) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:277) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:92) ~[local-starter-5.6.3.jar:5.6.3] at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:42) ~[local-starter-5.6.3.jar:5.6.3] 11-12-2022 01:14:52.154 INFO [mongo-check-thread] [] c.t.s.o.s.OmadaBootstrap(): mongod was shutdown, restarting it 11-12-2022 01:14:52.199 ERROR [mongo-check-thread] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: An unexpected error occurred in MongoDb. Omada Controller will try to restart it. Quote Link to comment
Skidmark Posted November 13, 2022 Share Posted November 13, 2022 On 7/31/2022 at 6:27 PM, Dark_Bubbles said: I saw this mentioned in an earlier comment, but I don't see the fix mentioned. I have the Omada controller running in a docker container, but when I reboot my server and go back into the GUI, it is like it is the first time it has ever been opened. I have to input all the data and then restore from an old backup. It even has me update the docker container each time. It seems like none of the changes to the container itself survive a reboot, almost like it is all held in RAM, rather than on the cache drive (which is a 480G nvme drive, if that matters). Hi, I didn't see any replies to your question so I thought i'd share what I found. I had the same issue and I believe I figured out what it was. The container's default path for it's data, logs, etc begins with "/mnt/disks". in unraid this directory doesn't exist but when the container runs, it creates it. The directory works fine until a host reboot occurs at which point the directory will cease to exist hence the first run experience upon logging in after a reboot. I fixed it by copying the contents of the default path to unraid's appdata and mapping the container paths to appdata (/mnt/user/appdata/omada-controller) as opposed to the container default (/mnt/disks/extrassd/docker-settings/omada-controller). Anywho, hope that helps. Quote Link to comment
trurl Posted November 13, 2022 Share Posted November 13, 2022 4 minutes ago, Skidmark said: The container's default path for it's data, logs, etc begins with "/mnt/disks". in unraid this directory doesn't exist /mnt/disks is created by Unassigned Devices plugin, whether that is the path needed depends Quote Link to comment
Skidmark Posted November 15, 2022 Share Posted November 15, 2022 On 11/13/2022 at 12:22 PM, trurl said: /mnt/disks is created by Unassigned Devices plugin, whether that is the path needed depends Is /mnt/disks/extrassd/docker-settings/omada-controller the expected location for the container to use? At least on my machine, that directory wouldn't persist after a reboot. Quote Link to comment
MaxAbsorbency Posted November 15, 2022 Share Posted November 15, 2022 2 hours ago, Skidmark said: Is /mnt/disks/extrassd/docker-settings/omada-controller the expected location for the container to use? At least on my machine, that directory wouldn't persist after a reboot. My setup: Path in container <--> Path on host OS /opt/tplink/EAPController/data <--> /mnt/cache/appdata/omada-controller/data/ /opt/tplink/EAPController/work <--> /mnt/cache/appdata/omada-controller/work/ /opt/tplink/EAPController/logs <--> /mnt/cache/appdata/omada-controller/logs/ Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.