Skip to content

docs: add troubleshooting step for clickhouse and aquasec #628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Sep 23, 2025
Merged

docs: add troubleshooting step for clickhouse and aquasec #628

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
3620c0d
docs: add troubleshooting step for clickhouse and aquasec
langchain-infra Sep 23, 2025
abc2371
Update src/langsmith/troubleshooting.mdx
langchain-infra Sep 23, 2025
dd85604
Update src/langsmith/troubleshooting.mdx
langchain-infra Sep 23, 2025
bc7da5a
Update src/langsmith/troubleshooting.mdx
langchain-infra Sep 23, 2025
d3a4f90
Update src/langsmith/troubleshooting.mdx
langchain-infra Sep 23, 2025
bbf9fef
Update src/langsmith/troubleshooting.mdx
langchain-infra Sep 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions src/langsmith/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,3 +176,30 @@ langchain-clickhouse:
docker compose down --volumes
docker compose up
```

### *ClickHouse fails to start up when running a cluster with AquaSec*

In some environments, AquaSec may prevent ClickHouse from starting up correctly. This may manifest as the ClickHouse pod not emitting any logs and failing to get marked as ready.
Generally this is due to `LD_PRELOAD` being set by AquaSec, which interferes with ClickHouse. To resolve this, you can add the following environment variable to your ClickHouse deployment:
Copy link
Preview

Copilot AI Sep 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The explanation could be clearer about what AquaSec is and why this conflict occurs. Consider adding a brief explanation that AquaSec is a security platform that uses LD_PRELOAD to inject security monitoring, which conflicts with ClickHouse's startup process.

Suggested change
Generally this is due to `LD_PRELOAD` being set by AquaSec, which interferes with ClickHouse. To resolve this, you can add the following environment variable to your ClickHouse deployment:
This issue is generally caused by AquaSec, a security platform that uses the `LD_PRELOAD` environment variable to inject security monitoring libraries into running processes. ClickHouse's startup process is incompatible with this kind of dynamic library injection, which can prevent it from starting correctly. To resolve this, you can add the following environment variable to your ClickHouse deployment:

Copilot uses AI. Check for mistakes.


#### Kubernetes

Edit your `langsmith_config.yaml` (or corresponding config file) and set the `AQUA_SKIP_LD_PRELOAD` environment variable:

```yaml
clickhouse:
statefulSet:
extraEnv:
- name: AQUA_SKIP_LD_PRELOAD
value: "true"
```

#### Docker

Edit your `docker-compose.yaml` and set the `AQUA_SKIP_LD_PRELOAD` environment variable:

```yaml
langchain-clickhouse:
environment:
- AQUA_SKIP_LD_PRELOAD=true
```