Business Community > Controllers > Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"
< Controllers

Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"

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

Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"
Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"
2024-01-21 08:31:11 - last edited 2024-01-21 08:32:48
Tags: #Controller #Omada
Model: Omada Software Controller (Windows)  
Hardware Version:
Firmware Version: 5.3.1

Hi all,

 

I have my 5.3.1 omada controller installed d on my Windows PC for more than 2 years-- but for for the past 3 months it keeps getting stuck at "mongodb server started." See screenshot below:

 

 

Take note it never fails, it just gets stuck here no matter how long I wait.

 

I've tried uninstalling and reinstalling fresh, but the problem is still there. I've also tried troubleshooting by opening the start.bat file in the bin folder for the omada controller-- no luck as well, it errors out and instead displays this:

 

"failed to launch Omada controller. Fail to start mongo DB server Please launch Omada controller again after troubleshooting the problem"

 

Some notes:

I have a unifi app running on the same windows PC but this hasnt been an issue for the past 2 years. Error may have coincided with an update to Unifi and an update to Java (Java 8 update 311). I've made sure there are no conflicts in terms of ports between the two.

 

Attaching the logs below.

 

Would really appreciate the help with this. Thanks!

 

File:
Logs.zipDownload
  0      
 
  0      
 
#1
Options
5 Reply
Re:Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"
2024-01-21 10:27:14 - last edited 2024-01-21 10:31:35

  @JKAlpheron 

 

you have at least one port conflict.

HTTPS Port for Portal 8843 is used for unifi and omada.

 

01-21-2024 15:17:06.572 ERROR [main] [] c.t.s.o.s.a(120): Port 8843 is already in use.
01-21-2024 15:17:06.576 ERROR [main] [] c.t.s.o.s.a(145): Port 8843 is already in use. Release the port and try again.
01-21-2024 15:17:06.576 ERROR [main] [] c.t.s.o.s.OmadaBootstrap(281): Environment is not ok for controller running
01-21-2024 15:17:06.576 ERROR [facade-msg-thread] [] c.t.s.f.s.FacadeMessageHandler(44): Port 8843 is already in use. Release the port and try again.

 

 

try and stop unifi controller and then start omda.

  0  
  0  
#2
Options
Re:Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"
2024-03-03 05:19:44

Hi  @MR.S 

 

For good measure, I've uninstalled Unifi and also reinstalled Omada. however Im still getting the same results even with Unifi uninstalled. When trying to run the bat file in omada controller > bin, I get this error instead:

 

 

 

Indicates to me it is more than just a port conflict.

 

Attaching logs below.

 

File:
logs mongod and server.zipDownload
  0  
  0  
#3
Options
Re:Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"
2024-03-03 05:41:44

  @JKAlpheron 

 

look like there is some problems with your installation, 

 

try uninstall unifi and omada, uninstall java and reboot your computer.

 

then install 64 bit java8 if your computer is 64bit.

then install omada controller

 

start up your omada software and then restore your omada backup

 

Unifi controller use a mutch newer java , i think java 17 now and this make problem for omada that use java8 so dont run unifi and omada on same computer anymore, I run unifi and omada on same computer before but have to splitt them to different computers.

 

 

 

 

 

 

  0  
  0  
#4
Options
Re:Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"
2024-03-04 14:44:03

  @JKAlpheron 

 

My money is on @MR.S being right about the java upgrade.  If it gets to be a problem, you could consider running the Omada controller and its legacy java inside a vm or container.  I haven't tried it yet, but, I imagine you could get the Linux controller version running under WSL in Windows.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#5
Options
Re:Omada Controller v5.3.1 Not booting, stuck at "mongodb server started"
2024-04-17 07:22:18 - last edited 2024-04-19 20:42:55

In case anyone is having this issue with the current version (v5.13), make sure 32bit Java isn't installed on your server! Once removed, the Omada controller started without issue for me  wink

 

Also ensure you have OpenJDK installed too, as per this article - https://www.tp-link.com/us/support/faq/3086/

  0  
  0  
#6
Options

Information

Helpful: 0

Views: 2815

Replies: 5

Tags

Controller
Omada
Related Articles
Omada Software Controller customise Launch URL
243 0
Upgrading Omada Controller, app unable to detect existing Omada instance on server
168 0
Omada Software Controller (Windows 11) - missing Wifi and Wired clients on the clients list - 5.9.31
2134 0
Change base URL of software controller
116 0
Moving Omada Software from Docker to standalone PC
864 0
 Omada SDN Controller
416 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.