{
  "schema_version": 2,
  "id": "integrate/redis-data-integration/troubleshooting",
  "title": "Troubleshooting",
  "url": "https://redis.io/docs/latest/integrate/redis-data-integration/1.19.1/troubleshooting/",
  "summary": "Solve and report simple problems with RDI",
  "content": "\nThe following sections explain how you can get extra information from\nRedis Data Integration (RDI) to help you solve problems that you may encounter. Redis support may\nalso ask you to provide this information to help you resolve issues.\n\n## Debug information during installation {#install-debug}\n\nIf the installer fails with an error, then try installing again with the\nlog level set to `DEBUG`:\n\n```bash\n./install.sh --log-level DEBUG\n```\n\nThis gives you more detail about the installation steps and can often\nhelp you to pinpoint the source of the error.\n\n## RDI logs\n\nBy default, RDI records the following logs in the host VM file system at\n`/opt/rdi/logs` (or whichever path you specified during installation);\n\n| Filename | Phase |\n| :-- | :-- |\n| `rdi_collector-collector-initializer.log` | Initializing the collector. |\n| `rdi_collector-debezium-ssl-init.log` | Establishing the connector SSL connections to the source and RDI database (if you are using SSL). |\n| `rdi_collector-collector-source.log` | Collector [change data capture (CDC)](https://redis.io/docs/latest/integrate/redis-data-integration/1.19.1/architecture) operations. |\n| `rdi_rdi-rdi-operator.log` | Main [RDI control plane](https://redis.io/docs/latest/integrate/redis-data-integration/1.19.1/architecture#how-rdi-is-deployed) component. |\n| `rdi_processor-processor.log` | RDI stream processing. |\n\nLogs are recorded at the minimum `INFO` level in a simple format that\nlog analysis tools can use.\n\n\u003e [!NOTE]\n\u003e Often during the initial sync phase, the collector source log will contain a message\n\u003e saying RDI is out of\n\u003e memory. This is not an error but an informative message to say that RDI\n\u003e is applying *backpressure* to the collector. See\n\u003e [Backpressure mechanism](https://redis.io/docs/latest/integrate/redis-data-integration/1.19.1/architecture#backpressure-mechanism)\n\u003e in the Architecture guide for more information.\n\n## Dump support package\n\nIf you need to send a comprehensive set of forensics data to Redis support,\nrun the\n[`redis-di dump-support-package`](https://redis.io/docs/latest/integrate/redis-data-integration/1.19.1/reference/cli/redis-di-dump-support-package)\ncommand from the CLI.\n\nThis command gathers the following data:\n\n- All the internal RDI components and their status\n- All internal RDI configuration\n- List of secret names used by RDI components (but not the secrets themselves)\n- RDI logs\n- RDI component versions\n- Text of the `config.yaml` file\n- Text of the Job configuration files\n- Rejected records along with the reason for their rejection (should not exist in production)\n",
  "tags": ["docs","integrate","rs","rdi"],
  "last_updated": "2026-09-19T17:55:58-07:00"
}