-
Notifications
You must be signed in to change notification settings - Fork 49
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a troubleshooting section to the LangSmith self-hosted documentation to help users resolve ClickHouse startup issues when running in environments with AquaSec security software.
- Adds a new troubleshooting section for ClickHouse and AquaSec compatibility issues
- Provides configuration solutions for both Kubernetes and Docker environments
- Documents the use of
AQUA_SKIP_LD_PRELOAD
environment variable to bypass AquaSec interference
Preview ID generated: preview-infraa-1758641348-47d5dbf |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.
src/langsmith/troubleshooting.mdx
Outdated
docker compose up | ||
``` | ||
|
||
### *ClickHouse Fails to Startup when running a Cluster with AquaSec* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The heading uses inconsistent formatting with asterisks around the title. Remove the asterisks to match the standard heading format used elsewhere in the documentation.
### *ClickHouse Fails to Startup when running a Cluster with AquaSec* | |
### ClickHouse Fails to Startup when running a Cluster with AquaSec |
Copilot uses AI. Check for mistakes.
src/langsmith/troubleshooting.mdx
Outdated
``` | ||
|
||
#### Docker | ||
1. Edit your `docker-compose.yaml` and set the `AQUA_SKIP_LD_PRELOAD` environment variable. This might look something like this: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing space after the numbered list marker. Should be '1. Edit' with proper spacing for consistency with the Kubernetes section above.
Copilot uses AI. Check for mistakes.
Preview ID generated: preview-infraa-1758642275-05c410c |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made a few suggestions, but looks good!
Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
### *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: |
There was a problem hiding this comment.
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.
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.
Preview ID generated: preview-infraa-1758642841-8609d75 |
Overview
Update langsmith self hosted documentation with a troubleshooting guide when running in environments with AquaSec.
Type of change
Type: [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other]
Related issues/PRs
Checklist
docs dev
src/docs.json
if neededAdditional notes