Omada Controller failed to start after update 5.9 to 5.14

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

Omada Controller failed to start after update 5.9 to 5.14

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada Controller failed to start after update 5.9 to 5.14
Omada Controller failed to start after update 5.9 to 5.14
2024-06-13 06:33:42 - last edited 2024-06-14 11:11:29
Hardware Version:
Firmware Version: 5.14.20.9

Hi there,

 

yesterday i decided to update out Software Controller on Windows Server 2016 from version 5.9 to 5.14. I did a backup, stopped the service, installed the package and started the service afterwards, but nothing happend. In task manager i can see the processes java.exe and mongod.exe are started. In the log file logs\server.log i got several errors mentioned below. I updated java to 1.8 and read and did already the faq when controller is not starting. 

 

This is the second time i have issues getting a controller running after a update...

 

*sry, i tried t upload log file but i get an error..."

 

Only WARN and ERROR from server-Log


06-13-2024 08:02:33.921 WARN [main] [] o.s.d.c.CustomConversions(): 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-13-2024 08:02:53.804 ERROR [main] [] c.t.s.o.d.c.ApiServiceInMemoryCache(): Try to register repeated path   /  {omadacId}  /  api  /  v2  /  sites  /  {siteId}  /  batchEvents, httttpMethod GET, apiType [webApi] for method d and b
06-13-2024 08:02:53.805 ERROR [main] [] c.t.s.o.d.c.ApiServiceInMemoryCache(): Try to register repeated path   /  {omadacId}  /  api  /  v2  /  sites  /  {siteId}  /  batchAlerts, httttpMethod GET, apiType [webApi] for method b and a
06-13-2024 08:02:56.668 WARN [main] [] o.s.d.c.CustomConversions(): 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-13-2024 08:03:09.394 WARN [main] [] o.s.d.c.CustomConversions(): 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-13-2024 08:03:13.006 WARN [main] [] o.s.d.c.CustomConversions(): 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-13-2024 08:03:15.279 WARN [main] [] c.t.c.r.c.d.MemoryDictionary(): Duplicate type code [-1,207], overwriting Digest-Attributes with WISPr-Redirection-URL
06-13-2024 08:03:15.279 WARN [main] [] c.t.c.r.c.d.MemoryDictionary(): Duplicate type code [-1,207], overwriting WISPr-Redirection-URL with WISPr-Location-ID
06-13-2024 08:03:16.535 ERROR [main] [] c.t.s.o.s.d.a(): Controller install failed. Failed to start.
06-13-2024 08:03:16.536 ERROR [main] [] c.t.s.o.s.t.FailExitTask(): Failed to start omada controller, going to exit
06-13-2024 08:03:16.536 ERROR [main] [] c.t.s.o.s.OmadaBootstrap(): com.tp li nk .smb.omada.starter.b.a: Omada StartUp  /  Init task execute failed.
com.tp li nk .smb.omada.starter.b.a: Omada StartUp  /  Init task execute failed.
    at com.tp li nk .smb.omada.starter.task.FailExitTask.execute(SourceFile:26) ~[local-starter-5.14.20.9.jar:5.14.20.9]
    at com.tp li nk .smb.omada.starter.task.c.a(SourceFile:20) ~[local-starter-5.14.20.9.jar:5.14.20.9]
    at com.tp li nk .smb.omada.starter.OmadaBootstrap.f(SourceFile:363) ~[local-starter-5.14.20.9.jar:5.14.20.9]
    at com.tp li nk .smb.omada.starter.OmadaMain.a(SourceFile:64) ~[local-starter-5.14.20.9.jar:5.14.20.9]
    at com.tp li nk .smb.omada.starter.OmadaMain.main(SourceFile:33) ~[local-starter-5.14.20.9.jar:5.14.20.9]
06-13-2024 08:03:16.541 ERROR [facade-msg-thread] [] c.t.s.f.s.FacadeMessageHandler(): Data abnormal due to install failed. Failed to start.
06-13-2024 08:03:37.750 WARN [hp-nio-8088-exec-2] [] o.s.d.c.CustomConversions(): 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-13-2024 08:03:37.761 WARN [hp-nio-8088-exec-2] [] o.s.d.c.CustomConversions(): 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

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Omada Controller failed to start after update 5.9 to 5.14-Solution
2024-06-14 11:11:19 - last edited 2024-06-14 11:11:29

Fixed it for myself:

1. Uninstalled the 5.15 controller. Retained user data.

2. Moved Userdata to a backup folder.

3. Installed latest 5.14 controller and restored the backup-file which i have created from the old controller 5.9

4. All EAPs are connected instead of "managed by others".

Recommended Solution
  0  
  0  
#4
Options
3 Reply
Re:Omada Controller failed to start after update 5.9 to 5.14
2024-06-13 07:29:39

  @AdminCat 

 

try and disable the service and restart the PC, then start omada in the usual way manually from the icon and see if it works.

 

  0  
  0  
#2
Options
Re:Omada Controller failed to start after update 5.9 to 5.14
2024-06-13 07:46:27

  @MR.S I restarted the server yesterday. Same issue today.

  0  
  0  
#3
Options
Re:Omada Controller failed to start after update 5.9 to 5.14-Solution
2024-06-14 11:11:19 - last edited 2024-06-14 11:11:29

Fixed it for myself:

1. Uninstalled the 5.15 controller. Retained user data.

2. Moved Userdata to a backup folder.

3. Installed latest 5.14 controller and restored the backup-file which i have created from the old controller 5.9

4. All EAPs are connected instead of "managed by others".

Recommended Solution
  0  
  0  
#4
Options