Loop restarting of MongoDB after update Omada to 5.13.23

Loop restarting of MongoDB after update Omada to 5.13.23

Loop restarting of MongoDB after update Omada to 5.13.23
Loop restarting of MongoDB after update Omada to 5.13.23
2024-02-16 10:42:44 - last edited 2024-02-19 00:58:10
Hardware Version:
Firmware Version: 5.13.23

After update Omada to 5.13.23 a see in server.log below infinity loop:
 

02-16-2024 11:27:45.741 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.
02-16-2024 11:27:45.741 INFO [mongo-check-thread] [] c.t.s.o.s.OmadaBootstrap(): mongod was shutdown, restarting it
02-16-2024 11:27:45.741 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(): Going to stop mongod which pid is 2092896
02-16-2024 11:27:48.270 ERROR [mongo-check-thread] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
02-16-2024 11:27:48.270 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(): mongodb process id is 2092918
02-16-2024 11:27:48.270 INFO [mongo-check-thread] [] c.t.s.o.s.s.b(): Mongo DB server started
02-16-2024 11:28:00.299 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.

 

What you suggest to check/reinstall?

Before update MongoDB working without issues.

 

PS. Yes, i red readme from new release and i saw supported OSes, but as i wrote, before update all things working properly ;)

 

System details:
​$​​​ mongod --version
db version v4.4.20
Build Info: {
    "version": "4.4.20",
    "gitVersion": "5b82316e5017ff76646fd12878079620f9ad4be7",
    "openSSLVersion": "OpenSSL 1.1.1k  FIPS 25 Mar 2021",
    "modules": [],
    "allocator": "tcmalloc",
    "environment": {
        "distmod": "rhel80",
        "distarch": "x86_64",
        "target_arch": "x86_64"
    }
}

 

$ cat /etc/os-release
NAME="Rocky Linux"
VERSION="8.9 (Green Obsidian)"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.9"
SUPPORT_END="2029-05-31"
+20y experience in Linux/UNIX, +12y VMware, +10y as network admin, +8y as AIX admin (professional) I really know what is going on at background, please don't try to cheat me TP-Link :)
  0      
  0      
#1
Options
1 Accepted Solution
Re:Loop restarting of MongoDB after update Omada to 5.13.23-Solution
2024-02-18 06:49:26 - last edited 2024-02-19 00:58:10

  @Hank21 

Hi, after some playing around DB in Omada directory I decided to downgrade MongoDB to 3.6, install fresh Omada and restore settings (all in less than 5 min!).

So i fix my issue like above.

 

I have all logs during my play with DB if you want to send then to support, just let me know.

 

Many thx!

+20y experience in Linux/UNIX, +12y VMware, +10y as network admin, +8y as AIX admin (professional) I really know what is going on at background, please don't try to cheat me TP-Link :)
Recommended Solution
  0  
  0  
#3
Options
2 Reply
Re:Loop restarting of MongoDB after update Omada to 5.13.23
2024-02-18 06:13:27 - last edited 2024-02-18 06:13:45

Hi @DREEMus

 

Could you upgrade to the new pre-released version v5.13.30.4 for testing?

Omada_SDN_Controller_v5.13.30.4_Linux_x64.deb(Pre-release version)   

Omada_SDN_Controller_v5.13.30.4_Linux_x64.tar.gz(Pre-release version) 

 

Have you tried installing v5.13.23 on the other Linux PC?

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#2
Options
Re:Loop restarting of MongoDB after update Omada to 5.13.23-Solution
2024-02-18 06:49:26 - last edited 2024-02-19 00:58:10

  @Hank21 

Hi, after some playing around DB in Omada directory I decided to downgrade MongoDB to 3.6, install fresh Omada and restore settings (all in less than 5 min!).

So i fix my issue like above.

 

I have all logs during my play with DB if you want to send then to support, just let me know.

 

Many thx!

+20y experience in Linux/UNIX, +12y VMware, +10y as network admin, +8y as AIX admin (professional) I really know what is going on at background, please don't try to cheat me TP-Link :)
Recommended Solution
  0  
  0  
#3
Options