---
title: DS diagnostic tools
description: The bin/ds-debug.sh script lets you obtain diagnostic information for any DS pod running in your cluster. It also lets you perform several cleanup and recovery operations on DS pods.
component: forgeops
version: 2026.1
page_id: forgeops:troubleshoot:debug-tools
canonical_url: https://docs.pingidentity.com/forgeops/2026.1/troubleshoot/debug-tools.html
keywords: ["Troubleshooting", "Kubernetes", "Directory Server"]
section_ids:
  ds-debug: Debug script
  debug-tools-container: Debug tools container
---

# DS diagnostic tools

## Debug script

The bin/ds-debug.sh script lets you obtain diagnostic information for any DS pod running in your cluster. It also lets you perform several cleanup and recovery operations on DS pods.

Run bin/ds-debug.sh -h to refer to the command's syntax.

The following bin/ds-debug.sh subcommands provide diagnostic information:

| Subcommand   | Diagnostics                                                   |
| ------------ | ------------------------------------------------------------- |
| status       | Server details, connection handlers, backends, and disk space |
| rstatus      | Replication status                                            |
| idsearch     | All the DNs in the `ou=identities` branch                     |
| monitor      | All the directory entries in the `cn=monitor` branch          |
| list-backups | A list of the backups associated with a DS instance           |

The bin/ds-debug.sh purge command purges all the backups associated with a DS instance.

## Debug tools container

The `ds-util` debug tools container provides a suite of diagnostic tools that you can execute inside of a running Kubernetes cluster.

The container has two types of tools:

* DS tools—A DS instance is installed in the /opt/opendj directory of the `ds-util` container. DS tools, such as the ldapsearch and ldapmodify commands, are available in the /opt/opendj/bin directory.

* Miscellaneous diagnostic tools—A set of diagnostic tools, including `dig`, `netcat`, `nslookup`, `curl`, and `vi`, have been installed in the container. The file, /path/to/forgeops/docker/ds/dsutil/Dockerfile, has the list of operating system packages that have been installed in the debug tools container.

To start the debug tools container:

```
$ kubectl run -it ds-util --image=gcr.io/forgeops-public/ds-util -- bash
```

After you start the tools container, a command prompt appears:

```
root@ds-util:/opt/opendj#
```

You can access all the tools available in the container from this prompt. For example:

```
root@ds-util:/opt/opendj# nslookup am
Server:		10.96.0.10
Address:	10.96.0.10#53

Name:	am.my-namespace.svc.cluster.local
Address: 10.100.20.240
```