启动Apache Kafka失败：Zookeeper启动报Classpath为空错误

Hey there, let's work through this Zookeeper startup issue you're hitting—that "Classpath is empty" error is a common gotcha, usually tied to which Kafka (or Zookeeper) package you're using.

First, Double-Check Your Downloaded Package #

The error you're seeing almost always happens when you're using the source code distribution instead of the pre-built binary package. Even if you thought you grabbed a binary one, it's easy to mix them up on the download page:

• Binary packages have a Scala version in their filename, like kafka_2.13-3.6.0.tgz—these are pre-compiled, ready to use out of the box.
• Source packages look like kafka-3.6.0.tgz (no Scala suffix) and require you to build the project first, which is why you're getting that "Please build the project first" message.

Solutions to Get Zookeeper Up and Running #

Option 1: Switch to the Pre-Built Binary Package

This is the quickest fix:

1. Delete your current source package directory.
2. Grab the correct binary package (look for the one labeled "binary" on the Kafka downloads page).
3. Unzip it, navigate to the root directory, and run the Zookeeper startup command again:

   ./bin/zookeeper-server-start.sh config/zookeeper.properties
   

   It should work without needing any compilation steps.

Option 2: Build the Source Package (If You Need to Use It)

If you have a reason to stick with the source package, follow the error message's instruction to compile first:

./gradlew jar -PscalaVersion=2.11.12

Just make sure the Scala version you specify matches the one compatible with your Kafka version. For newer Kafka releases, 2.13 is usually the recommended Scala version instead of 2.11.

Fixing the Same Issue with Standalone Zookeeper #

If you're using a separate Zookeeper installation (not the one bundled with Kafka), the same logic applies:

• Ensure you downloaded the pre-compiled binary release of Zookeeper, not the source code.
• If you did use the source package, you'll need to compile it first using the project's build tool (usually Maven or Ant, depending on the Zookeeper version).

Quick Pre-Flight Checks #

Before trying to start again, verify these two things:

• Make sure you unzipped the package completely—missing lib directory jars will cause classpath issues.
• Ensure the startup script has execution permissions:

  chmod +x ./bin/zookeeper-server-start.sh
  

内容的提问来源于stack exchange，提问作者Andreas bleYel