LevelDB Lock error

[xiangyangli-cn]

F0421 20:12:58.524404 5173 data_layer.cpp:139] Check failed: status.ok() Failed to open leveldb dish_train_leveldb
IO error: lock dish_train_leveldb/LOCK: Resource temporarily unavailable
what I can do?

[Yangqing]

This means that your leveldb is currently opened by another program. Close the other program would solve the issue.

[jeffdonahue]

I think I've actually gotten into strange situations where I have no processes reading from the LevelDB but the lock is still there, so as a backup measure if you can't find any processes that might be reading from that LevelDB to kill, you can try actually deleting the LOCK file from the leveldb dir.

[HoldenCaulfieldRye]

Another reason this error might occur is if *train.prototxt accidentally has *val_leveldb (or vice versa) as source field under data_param.

[ghost]

Another use case of a deadlock on a levelDB/LOCK file.
When I modified MNIST lenet_train_test.prototxt model to use the same data layer for TRAIN and TEST phases. For this, I removed the include: { phase: TRAIN } directive from the TRAIN layer definition and removed the TEST data layer definition altogether. I expected for the same database to participate both in TRAIN and TEST phases. In TRAIN phase Caffe opens database, in TEST phase it deadlocks.
I resolved it by referring to the separate databse for the TEST phase.

[SeraphConst]

When I was using '.jpg' files set to do some training, I forgot update ' type: "ImageData" ', then this "F0421 20:12:58.524404 5173 data_layer.cpp:139] Check failed: status.ok()" poped.

[Henry75m39]

I encountered the same issue in my development environment. since I restart my service when every change I made in code. Finally, I delete LOCK file under leveldb dir.