Pathological IVORN causes failure to release eventdb lock #34
Labels
Comments
Every time a new event with the broken IVORN is received, we attempt to acquire the lock on the |
jdswinbank
pushed a commit
that referenced
this issue
Aug 26, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If we create an event with the IVORN
ivo://
, then the event db check will attempt to create a database at${eventdb_root}
, which is a directory. This will fail, and the event will be rejected, which is fine.However, there is now an entry called
""
in the list of databases. When we try to prune the databases, that will get locked, but the prune fails and the database is never unlocked. Our event validation then seizes up.The text was updated successfully, but these errors were encountered: