Apache Kafka生产者无法连接Broker问题排查及解决方案咨询

Let's walk through why your Kafka producer can't connect to the broker and how to resolve this step by step.

Common Causes & Solutions #

1. Missing advertised.listeners Configuration #

This is the most frequent culprit for this exact error. Here's why:

• The listeners property tells Kafka which internal address to bind to, but advertised.listeners is what Kafka sends to clients (producers/consumers) as the address to connect to.
• If you don't set advertised.listeners, Kafka might auto-resolve to your machine's hostname instead of 127.0.0.1. When your producer tries to connect to 127.0.0.1:9092, the broker returns a mismatched address, causing the connection to drop abruptly.

Fix:
Edit your server.properties file and add this line:

advertised.listeners=PLAINTEXT://127.0.0.1:9092

Save the file and restart your Kafka broker.

2. Verify Kafka is Listening on Port 9092 #

Even if Kafka says it started successfully, it might not have bound to port 9092 (e.g., the port is occupied by another application).

Check the port status:

• Windows: Open Command Prompt and run:

  netstat -ano | findstr :9092
  

  Look for a line with LISTENING status. If none exists, Kafka isn't listening on the port.
• Linux/macOS: Run in terminal:

  lsof -i :9092  # Alternative: netstat -tulpn | grep 9092
  

  Confirm the Kafka process is listed as the listener for the port.

If the port is occupied:

• Kill the process using the port (use the PID from the netstat/lsof output)
• Or change Kafka's port by updating both listeners and advertised.listeners in server.properties to a free port (e.g., 9093), then restart Kafka.

3. Firewall/Antivirus Blocking the Connection #

Your local firewall or antivirus software might be blocking incoming/outgoing traffic on port 9092, preventing the producer from reaching the broker.

Fix:

• Temporarily disable your firewall/antivirus and test the producer again. If it works, add a rule to allow Kafka's process or port 9092 through the firewall.
• For Windows Firewall: Go to "Advanced Settings" → "Inbound Rules" → New Rule → Port → Enter 9092 → Allow the connection. Repeat the same for Outbound Rules.

4. Check Kafka Startup Logs for Hidden Errors #

Sometimes Kafka appears to start normally but has underlying issues (like failing to connect to ZooKeeper or permission problems with log directories).

Check the logs:

• Navigate to your Kafka installation's logs folder, open server.log, and search for ERROR entries. Common issues to look for:
  • Connection to zookeeper failed: Ensure ZooKeeper is running and the zookeeper.connect property in server.properties is correct.
  • Permission denied: Make sure the log.dirs path (set to ./tmp/kafka-logs in your config) has write permissions for the user running Kafka.

内容的提问来源于stack exchange，提问作者Andrei Suruceanu