Controller offline (port 27217 is already in use)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Controller offline (port 27217 is already in use)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Controller offline (port 27217 is already in use)
Posts: 46
Helpful: 11
Solutions: 0
Stories: 0
Registered: 2021-02-26
2021-03-08 08:15:34
Posts: 46
Helpful: 11
Solutions: 0
Stories: 0
Registered: 2021-02-26
Controller offline (port 27217 is already in use)
2021-03-08 08:15:34
Tags:
I'm running the controller on Ubuntu 18.04 server. From time to time, the controller goes offline. It probably crashes or tries to restart itself but it does not stop also Mongo and when it tries to start again and Mongo is already running, it stops. Then "tpeap start" fails with:
2021-03-08 00:07:57 [log4j-thread] [INFO]-[SourceFile:29] - success to load configuration omada.properties 2021-03-08 00:07:58 [main] [INFO]-[SourceFile:89] - going to start local mongod. 2021-03-08 00:07:59 [main] [ERROR]-[SourceFile:109] - Failed to init_port 27217 is already in use. com.tplink.omada.start.a.a: port 27217 is already in use. at com.tplink.omada.start.b.b.a(SourceFile:45) ~[omada-start.jar:?] at com.tplink.omada.start.b.d.d(SourceFile:106) ~[omada-start.jar:?] at com.tplink.omada.start.b.b.e(SourceFile:72) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.d(SourceFile:223) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.q(SourceFile:287) ~[omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.a(SourceFile:100) [omada-start.jar:?] at com.tplink.omada.start.OmadaBootstrap.e(SourceFile:245) [omada-start.jar:?] at com.tplink.omada.start.OmadaLinuxMain.b(SourceFile:80) [omada-start.jar:?] at com.tplink.omada.start.OmadaLinuxMain.start(SourceFile:43) [omada-start.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_282] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_282] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_282] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_282] at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) [commons-daemon-1.0.15.jar:1.0.15]
When I kill Mongo and try "tpeap start" again, it succeeds. This is quite annoying . Is there something that I can do about it or it needs to be fixed in the controller?
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
Announcement Manage
11 Reply
Posts: 46
Helpful: 11
Solutions: 0
Stories: 0
Registered: 2021-02-26
Re:Controller offline (port 27217 is already in use)
2021-04-16 06:54:24
Even when freshly started, the Omada Controller is the most memory-intensive process on my server.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#12
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 46
Helpful: 11
Solutions: 0
Stories: 0
Registered: 2021-02-26
2021-03-08 08:15:34
Posts: 46
Helpful: 11
Solutions: 0
Stories: 0
Registered: 2021-02-26
Information
Helpful: 0
Views: 12783
Replies: 11
Voters 0
No one has voted for it yet.
Tags
Related Articles
Report Inappropriate Content
Transfer Module
New message