Failed to acquire lock on file - How do I debug this issue?

[amitoj]

Running Strimzi in my local Kubernetes cluster using host-attached storage.

2023-06-12 09:47:08,447 ERROR [KafkaServer id=0] Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer) [main]
org.apache.kafka.common.KafkaException: Failed to acquire lock on file .lock in /var/lib/kafka/data-0/kafka-log0. A Kafka instance in another process or thread is using this directory.
at kafka.log.LogManager.$anonfun$lockLogDirs$1(LogManager.scala:243)
at scala.collection.StrictOptimizedIterableOps.flatMap(StrictOptimizedIterableOps.scala:118)
at scala.collection.StrictOptimizedIterableOps.flatMap$(StrictOptimizedIterableOps.scala:105)
at scala.collection.mutable.ArraySeq.flatMap(ArraySeq.scala:37)
at kafka.log.LogManager.lockLogDirs(LogManager.scala:238)
at kafka.log.LogManager.(LogManager.scala:114)
at kafka.log.LogManager$.apply(LogManager.scala:1383)
at kafka.server.KafkaServer.startup(KafkaServer.scala:261)
at kafka.Kafka$.main(Kafka.scala:109)
at kafka.Kafka.main(Kafka.scala)

Before I restart the Strimzi cluster I would like to understand how to approach debugging these issues.

[scholzj]

What does host-attached storage exactly mean? Kafka needs block storage with read-write-once. But it is hard to say what exactly does your storage do and how it works. I guess the key would be to doublecheck that there is no other broker using the same volume adn that the volume is not some kind of NFS storage.