nekkidtruth

Today I updated Unraid from 7.0.0 to 7.0.1. Everything seemed fine except I noticed I couldn't bring up the login screen for Omada. I did a bit of digging in the logs and here's what I found: INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) exists; skipping creation INFO: User (omada) exists; skipping creation INFO: Time zone set to 'America/New_York' INFO: Value of 'manage.http.port' already set to 18088 in omada.properties INFO: Value of 'manage.https.port' already set to 18043 in omada.properties INFO: Value of 'portal.http.port' already set to 18088 in omada.properties INFO: Value of 'portal.https.port' already set 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: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Value of 'mongo.external' already set to false in omada.properties INFO: Value of 'eap.mongod.uri' already set to mongodb://127.0.0.1:27217/omada in omada.properties INFO: Version check passed; image version (5.15.20.18) >= the last version ran (5.15.20.18); writing image version to last ran file... INFO: userland/kernel check passed INFO: output of 'java -version': openjdk version "17.0.14" 2025-01-21 OpenJDK Runtime Environment (build 17.0.14+7-Ubuntu-120.04) OpenJDK 64-Bit Server VM (build 17.0.14+7-Ubuntu-120.04, mixed mode, sharing) ############################################################################## ############################################################################## WARN: autobackup directory not found! Please configure automatic backups! For instructions, see https://github.com/mbentley/docker-omada-controller#controller-backups ############################################################################## ############################################################################## INFO: Starting Omada Controller as user omada 04-05-2025 11:31:07.937 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller 04-05-2025 11:31:07.942 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished 04-05-2025 11:31:07.963 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished 04-05-2025 11:31:07.973 INFO [main] [] c.t.s.o.c.o.a(): Native Image: null 04-05-2025 11:31:07.976 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare 04-05-2025 11:31:07.980 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux 04-05-2025 11:31:07.991 INFO [main] [] c.t.s.o.c.o.c.c(): success to load configuration omada.properties 04-05-2025 11:31:07.991 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller 04-05-2025 11:31:07.991 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux 04-05-2025 11:31:07.998 INFO [main] [] c.t.s.o.s.g.f(): Start startup message daemon. 04-05-2025 11:31:08.045 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod. 04-05-2025 11:31:08.047 INFO [main] [] c.t.s.o.m.c.c.d(): FailoverClusterEnable is false 04-05-2025 11:31:22.557 ERROR [main] [] c.t.s.o.s.s.b(): Command execution failed with exit code 14 . 04-05-2025 11:31:22.558 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Fail to start mongo DB server with exit code 14 04-05-2025 11:31:22.558 WARN [main] [] c.t.s.o.s.s.b(): Fail to start mongo DB server 04-05-2025 11:31:22.558 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:201) ~[local-starter-5.15.20.18.jar:5.15.20.18] at com.tplink.smb.omada.starter.server.a.e(SourceFile:74) ~[local-starter-5.15.20.18.jar:5.15.20.18] at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:436) ~[local-starter-5.15.20.18.jar:5.15.20.18] at com.tplink.smb.omada.starter.OmadaBootstrap.v(SourceFile:625) ~[local-starter-5.15.20.18.jar:5.15.20.18] at com.tplink.smb.omada.starter.OmadaBootstrap.a(SourceFile:207) ~[local-starter-5.15.20.18.jar:5.15.20.18] at com.tplink.smb.omada.starter.OmadaBootstrap.f(SourceFile:474) ~[local-starter-5.15.20.18.jar:5.15.20.18] at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:115) ~[local-starter-5.15.20.18.jar:5.15.20.18] at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:62) ~[local-starter-5.15.20.18.jar:5.15.20.18] So I went in to look at the Mongo log and it seems to be looping through this: 2025-04-05T11:34:26.709-0400 I CONTROL [main] ***** SERVER RESTARTED ***** 2025-04-05T11:34:26.711-0400 I CONTROL [initandlisten] MongoDB starting : pid=614 port=27017 dbpath=../data/db 64-bit host=nekkidverse 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] db version v3.6.8 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] git version: 8e540c0b6db93ce994cc548f000900bdc740f80a 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] allocator: tcmalloc 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] modules: none 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] build environment: 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] distarch: x86_64 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] target_arch: x86_64 2025-04-05T11:34:26.712-0400 I CONTROL [initandlisten] options: { repair: true, storage: { dbPath: "../data/db" }, systemLog: { destination: "file", logAppend: true, path: "../logs/mongod.log" } } 2025-04-05T11:34:26.714-0400 I - [initandlisten] Detected data files in ../data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2025-04-05T11:34:26.714-0400 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint. 2025-04-05T11:34:26.714-0400 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=31577M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),cache_cursors=false,compatibility=(release="3.0",require_max="3.0"),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress), 2025-04-05T11:34:42.414-0400 E STORAGE [initandlisten] WiredTiger error (22) [1743867282:414503][614:0x14c509ae0ac0], txn-recover: Error parsing 'access_pattern_hint=none,allocation_size=4KB,app_metadata=(formatVersion=1),assert=(commit_timestamp=none,read_timestamp=none),block_allocation=best,block_compressor=snappy,cache_resident=false,checkpoint=(WiredTigerCheckpoint.1=(addr="",order=1,time=1714834913,size=0,write_gen=0)),checkpoint_lsn=(1,0),checksum=on,collator=,columns=,dictionary=0,encryption=(keyid=,name=),format=btree,huffman_key=,huffman_value=,id=2038,ignore_in_memory_cache_size=false,internal_item_max=0,internal_key_max=0,internal_key_truncate=true,internal_page_max=4KB,key_format=q,key_gap=10,leaf_item_max=0,leaf_key_max=0,leaf_page_max=32KB,leaf_value_max=64MB,log=(enabled=true),memory_page_max=10m,os_cache_dirty_max=0,os]cache_max=0,prefix_compression=false,prefix_compression_min=4,stlit_deepen_min_child=0,split_deepen_per_child=0,split_pct=90,value_format=u,version=(major=1,minor=1)' at offset 851: New value starts without a separator: Invalid argument 2025-04-05T11:34:42.414-0400 E STORAGE [initandlisten] WiredTiger error (22) [1743867282:414735][614:0x14c509ae0ac0], txn-recover: Recovery failed: Invalid argument 2025-04-05T11:34:42.419-0400 F - [initandlisten] Fatal Assertion 28717 at src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 394 2025-04-05T11:34:42.419-0400 F - [initandlisten] ***aborting after fassert() failure I did some searching and found all sorts of different possible workarounds, but none seem to be working for me. Anyone have any ideas? I'm sure I'm missing something.

It looks like Creativerse updated something. I'm getting a mismatched version now. Is this something you need to rectify on your end with an update to the container? Or is it something I can deal with? Appreciate the help! Nevermind! I restarted the container and it seems fine now. 🤷‍♂️

Really surprised this is still not implemented. Add me to the list of people who want to see this ASAP!