Introduction

If Kafka was installed through Ambari and Bash says bin/kafka-topics.sh: No such file or directory, the usual problem is that you are running the command from the wrong directory or using the wrong installation path. Ambari-managed Kafka installs are often placed under distribution-specific directories and symlinks rather than in a hand-unpacked local folder.

Why bin/kafka-topics.sh Often Fails

The command:

bin/kafka-topics.sh --list

only works if your current directory is the Kafka home directory. On Ambari-managed clusters, that assumption is often false. Kafka binaries are commonly installed under a path such as:

/usr/hdp/current/kafka-broker/bin/

or another versioned package path managed by the platform. So bin/kafka-topics.sh fails simply because there is no bin folder relative to your current shell directory.

Find the Actual Script Location

Start by locating the script rather than guessing the path.

find /usr -name kafka-topics.sh 2>/dev/null

If you want to check likely Ambari-managed locations first:

ls -l /usr/hdp/current/kafka-broker/bin

Once you know the real path, call the script explicitly:

/usr/hdp/current/kafka-broker/bin/kafka-topics.sh --bootstrap-server localhost:9092 --list

That removes any ambiguity about the working directory.

Understand the Ambari Layout

Ambari-managed Hadoop distributions often use versioned install directories with a stable symlink such as /usr/hdp/current/.... The symlink points to the currently active package version, which is why documentation or old scripts may mention paths that do not look like a typical manual Kafka installation.

That means two things:

• do not assume Kafka lives in the shell's current directory
• prefer the stable symlink path over hardcoding a fully versioned package path

The stable path is usually better for scripts and operations tasks.

Make Sure You Are on the Right Host

The script must be run on a node where the Kafka client tools or broker package is actually installed. On Ambari clusters, not every host necessarily has the same service components.

Before debugging deeper, confirm:

• Kafka is installed on the host you are logged into
• the broker or client package is present
• you are using the correct Unix user or sudo context

If the package is not installed on that machine, no amount of relative-path troubleshooting will fix the command.

Check Permissions and Line Endings

If the file exists but still fails, inspect permissions and script integrity.

ls -l /usr/hdp/current/kafka-broker/bin/kafka-topics.sh
head -n 1 /usr/hdp/current/kafka-broker/bin/kafka-topics.sh

Make sure the script is executable and has a valid shebang. In rare cases, copied or edited scripts can fail because of incorrect line endings or a missing interpreter path.

Use Modern Kafka CLI Options

Older examples often show ZooKeeper-based commands, while newer Kafka tooling prefers --bootstrap-server.

1/usr/hdp/current/kafka-broker/bin/kafka-topics.sh \
2  --bootstrap-server broker1.example.com:9092 \
3  --describe \
4  --topic orders

Even when troubleshooting a path issue, it is worth checking that the command syntax itself matches the Kafka version you are running.

If the Path Still Looks Wrong

At that point, inspect the host through Ambari:

1. Verify the Kafka component is installed on the node.
2. Check the service version and package layout.
3. Inspect environment scripts or service configs for the advertised Kafka home.
4. Compare with another working Kafka node if available.

This usually reveals whether the problem is the shell path, the host choice, or an incomplete package installation.

Common Pitfalls

The biggest mistake is assuming bin/kafka-topics.sh is a universal relative path. It only works when your current directory is the Kafka home directory.

Another issue is logging into a node that does not actually have the Kafka broker or client tools installed. Ambari clusters often distribute components across different hosts.

Developers also copy old Kafka commands without checking whether the installation path or CLI flags match the cluster's packaging and Kafka version.

Finally, avoid hardcoding fully versioned package paths when a stable Ambari-managed symlink already exists. The symlink is usually the safer operational path.

Summary

• 'bin/kafka-topics.sh fails on Ambari installs mainly because the current directory is not Kafka home.'
• Locate the real script and invoke it with an absolute path.
• Ambari-managed Kafka often lives under /usr/hdp/current/kafka-broker/bin/ or a similar stable symlink.
• Verify that Kafka is installed on the host where you run the command.
• Use the correct Kafka CLI syntax once the path issue is resolved.