Hi Erik,
C
an you clarify a few things for me?
It sounds like your GeoGig repository is created via GeoServer, correct?
Then you are accessing the repository via QGIS. I'm assuming you are using the GeoGig plugin in QGIS to connect. If so, are you exposing the repository via command line "geogig serve", or are you accessing the repository as exposed via GeoServer (using a URL similar to
http://localhost/geoserver/geogig/repos/myRepo)?
The problem with issue #309 is that there are 2 processes trying to access a single RocksDB database at the same time. Currently, the RocksDB integration in GeoGig is such that GeoGig will maintain an exclusive lock on the RocksDB database as long as the repository remains open in a given process. This means that GeoServer can serve out the repository, or "geogig serve" from the command line can serve out the repository, but not both at the same time. I suspect this may be the issue, if you have a QGIS session open and connected to the repository (via geogig serve), and then you try to restart GeoServer, which will try to open the repository as well.
If this is not the case, that is you only have a single process accessing the repository, then it may be related to issue #302, or it may be a new issue we have not come across.
If you would, could you please reply back and let us know if your issue is being caused by more than one process trying to access the database. If that is not the issue, we can collect more details and open a new ticket in GitHub.
Many thanks,