Business Community > All Threads > BUG in TPEAP Stop - mongod.lock
< All Threads
 
0
Votes

BUG in TPEAP Stop - mongod.lock

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

BUG in TPEAP Stop - mongod.lock

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
BUG in TPEAP Stop - mongod.lock
BUG in TPEAP Stop - mongod.lock
2021-08-25 13:44:04
Model: Omada Software Controller (Linux)  
Hardware Version:
Firmware Version: 4.4.4

Hi,

 

tpeap stop leaves a mongod.lock file in the db directory.

 

This prevents tpeap start from working until one deletes the mongod.lock file.

 

Running on ubuntu 20.04 with db version v3.6.8.

 

Thanks

 

 

 

 

#1
Options
4 Reply
Re:BUG in TPEAP Stop - mongod.lock
2021-08-26 09:12:47
Does deleting the file one time resolve this issue completely? Seems the controller just shut down abnormally. I ever run a controller on Linux system, but I didn't have this issue.
#2
Options
Re:BUG in TPEAP Stop - mongod.lock
2021-08-26 09:30:53 - last edited 2021-08-26 09:31:08

No. The file needs to be deleted each time the controller is stopped.

#3
Options
Re:BUG in TPEAP Stop - mongod.lock
2021-08-26 09:49:44

@HomeAdmin 

 

No better idea. But Ubuntu 20.04 is not recommended officially. I think you can try to install it with Docker. See this thread.

#4
Options
Re:BUG in TPEAP Stop - mongod.lock
2021-08-26 09:52:21
The Ubuntu build works fine except for the lock file. My backup script deletes the lock file each time it runs. My suggestion is to run a mongo repair in the startup script which should resolve the issue.
#5
Options

Information

Helpful: 0

Views: 744

Replies: 4

Voters 0

No one has voted for it yet.

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.