Closed timbru closed 9 months ago
This issue affects Krill versions v0.14.0-v0.14.2.
This issue manifests itself as Krill running but not responding to HTTP requests or doing anything, as internally it is blocked while waiting to acquire a lock that it cannot acquire because the related lock file is unexpectedly present.
It could also occur later while Krill was running if the lock file that was left behind (when Krill was terminated without being able to clean up) did not need to be acquired until then.
The
kvx
library deletes lock files onDrop
, but this may not work if the server crashes.