We’re changing where we run our SonarQube 8.9 server – it runs as a container in Kubernetes and we’re changing it to run on a different host. We’ve synced the database (which is starting fine in postgres) and also synced the entire sonarqube folder, but during startup on the new node and new storage host, we get this error:
java.lang.IllegalStateException: failed to obtain node locks, tried [[/opt/sq/data/es7]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?
Likely root cause: java.io.IOException: No locks available
It’s a different host and different storage, so there definitely isn’t anything holding a lock on the folder. We’ve confirmed the user/container has full write access to the folder. We’ve tried various attempts to remove the node.lock file in the es7/nodes/0 folder, and even tried removing the entire es7 folder. We’ve also tried various config mods to attempt to pass the node.max_local_storage_nodes value as “2” as mentioned here:
https://stackoverflow.com/questions/53157387/getting-error-failed-to-obtain-node-locks-tried-when-starting-second-node-1
Nothing seems to change the error above to allow startup of the sonarqube service. This seems to be a common issue mentioned in the sonarqube forums but we can’t find any clear resolution for this. Could you help route this query?