Hello,

My controller runs on a Linux Mint VM

VERSION="18.3 (Sylvia)"

java --version

openjdk version "1.8.0_275"
OpenJDK Runtime Environment (build 1.8.0_275-8u275-b01-0ubuntu1~16.04-b01)
OpenJDK 64-Bit Server VM (build 25.275-b01, mixed mode)

mongod --version
db version v2.6.10
2020-11-23T10:48:29.164+0100 git version: nogitversion
2020-11-23T10:48:29.164+0100 OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016

I have just upgraded my controller to version 4.2.4

Every time I stop tpeap and start it again I run into the following error:

2020-11-23 10:27:36 [main] [INFO]-[SourceFile:180] - success to shutdown mongodb database
2020-11-23 10:27:36 [main] [INFO]-[SourceFile:185] - Omada Controller exited
2020-11-23 10:27:37 [Thread-1] [INFO]-[SourceFile:180] - success to shutdown mongodb database
2020-11-23 10:27:37 [Thread-1] [INFO]-[SourceFile:185] - Omada Controller exited
2020-11-23 10:27:59 [log4j-thread] [INFO]-[SourceFile:29] - success to load configuration omada.properties
2020-11-23 10:27:59 [main] [INFO]-[SourceFile:89] - going to start local mongod.
2020-11-23 10:28:29 [main] [ERROR]-[SourceFile:115] - Failed to delete old mongod.lock, exit starting mongod
2020-11-23 10:28:31 [main] [WARN]-[SourceFile:239] - Failed to stop mongod, pid is null
2020-11-23 10:29:01 [main] [ERROR]-[SourceFile:273] - Failed to delete old mongod.lock, exit repair mongod
2020-11-23 10:29:31 [main] [ERROR]-[SourceFile:115] - Failed to delete old mongod.lock, exit starting mongod
2020-11-23 10:29:33 [mongo-check-thread] [INFO]-[SourceFile:312] - mongod was shutdown, restarting it
2020-11-23 10:29:33 [mongo-check-thread] [WARN]-[SourceFile:239] - Failed to stop mongod, pid is null
2020-11-23 10:30:03 [mongo-check-thread] [ERROR]-[SourceFile:273] - Failed to delete old mongod.lock, exit repair mongod
2020-11-23 10:30:32 [main] [WARN]-[SourceFile:342] - Mongo Client connect error while init Jetty.com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=127.0.0.1:27217, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectException: Connection refused (Connection refused)}}]
2020-11-23 10:30:33 [mongo-check-thread] [ERROR]-[SourceFile:115] - Failed to delete old mongod.lock, exit starting mongod
2020-11-23 10:30:45 [mongo-check-thread] [INFO]-[SourceFile:312] - mongod was shutdown, restarting it
2020-11-23 10:30:45 [mongo-check-thread] [WARN]-[SourceFile:239] - Failed to stop mongod, pid is null
2020-11-23 10:31:07 [main] [ERROR]-[ContextLoader.java:312] - Context initialization failed

When I forcefully remove the lock file as root the service starts once again and all is fine.

/opt/tplink/EAPController/data/db $ ll
total 376852
drwxrwxr-x 3 omada omada      4096 Nov 23 10:41 ./
drwxr-xr-x 4 root  root       4096 Nov 23 10:41 ../
drwxr-x--- 2 omada omada      4096 Nov 23 10:42 journal/
-rw------- 1 omada omada  67108864 Nov 23 10:41 local.0
-rw------- 1 omada omada  16777216 Nov 23 10:41 local.ns
-rwxr-xr-x 1 root  root          6 Nov 23 10:41 mongod.lock*
-rw------- 1 omada omada  67108864 Nov 23 10:42 omada.0
-rw------- 1 omada omada  67108864 Nov 23 10:50 omada_data.0
-rw------- 1 omada omada 134217728 Nov 23 10:50 omada_data.1
-rw------- 1 omada omada  16777216 Nov 23 10:50 omada_data.ns
-rw------- 1 omada omada  16777216 Nov 22 18:46 omada.ns

I have tried changing ownership and permission to mongod.lock without success.