Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
3.0.0
-
None
-
None
-
None
Description
During startup Kafka creates some files in logs folder, but then outputs two java.nio.file.AccessDeniedException exceptions for logs folder (configured in server.properties via log.dirs), and four ERROR log lines with messages:
ERRROR Failed to write meta.properties due to (kafka.server.BrokerMetadataCheckpoint)
java.nio.file.AccessDeniedException c:\Users\user\kafka3-data
...
ERROR [KafkaServer id=0] Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
java.nio.file.AccessDeniedException c:\Users\user\kafka3-data
...
ERROR Error while writing to checkpoint file c:\Users\user\kafka3-data\recovery-point-offset checkpoint (kafka.server.LogDirFailureChannel)
...
ERROR Error while writing to checkpoint file c:\Users\user\kafka3-data\log-start-offset-checkpoint (kafka.server.LogDirFailureChannel)
Before Kafka startup log directory (c:\Users\user\kafka3-data) was empty.
But after the attempted startup the directory contains files, specifically meta.properties of size 94 bytes, recovery-point-offset-checkpoint and log-start-offset-checkpoint - both of size 6 bytes, and 4 more 0 sized files (replication-offset-checkpoint, cleaner-offset-checkpoint, .lock, .kafka_cleanshutdown).
Which indicates that Kafka actually has permissions to create these files and write to them.
P.S. See also https://stackoverflow.com/questions/69289641/accessdeniedexception-while-running-apache-kafka-3-on-windows
Attachments
Issue Links
- duplicates
-
KAFKA-13391 Failure on Windows due to AccessDeniedAcception when attempting to fsync the parent directory
- Resolved