[DOCS-9950] Add limitNOFILE to OP troubleshooting #29077
Conversation
Preview links (active after the
|
| @@ -65,6 +65,10 @@ If you try to install a new version of the Worker in an instance that is running | |||
|
|
|||
| If you do not see Worker logs in [Log Explorer][12], make sure they are not getting excluded in your log pipelines. Worker logs must be indexed in Log Management for optimal functionality. The logs provide deployment information, such as Worker status, version, and any errors, that is shown in the Observability Pipelines UI. The logs are also helpful for troubleshooting Worker or pipelines issues. All Worker logs have the tag `source:op_worker`. | |||
|
|
|||
| ## Too many files error | |||
|
|
|||
| If you see the error `Too many files` and the Worker processes continually to restart, it could be due to a low file descriptor limit on the host. To resolve this issue for Linux environments, set `LimitNOFILE` in the systemd service configuration to `65,536` to increase the file descriptor limit. | |||
There was a problem hiding this comment.
Is the phrase "the Worker processes continually to restart" right? I'm having trouble understanding it. Does it mean that the Worker processes repeatedly restart?
There was a problem hiding this comment.
Yes, I updated to say "the Worker processes repeatedly restart". Thanks!
| @@ -65,6 +65,10 @@ If you try to install a new version of the Worker in an instance that is running | |||
|
|
|||
| If you do not see Worker logs in [Log Explorer][12], make sure they are not getting excluded in your log pipelines. Worker logs must be indexed in Log Management for optimal functionality. The logs provide deployment information, such as Worker status, version, and any errors, that is shown in the Observability Pipelines UI. The logs are also helpful for troubleshooting Worker or pipelines issues. All Worker logs have the tag `source:op_worker`. | |||
|
|
|||
| ## Too many files error | |||
|
|
|||
| If you see the error `Too many files` and the Worker processes repeatedly restarts, it could be due to a low file descriptor limit on the host. To resolve this issue for Linux environments, set `LimitNOFILE` in the systemd service configuration to `65,536` to increase the file descriptor limit. | |||
There was a problem hiding this comment.
There's still a plural error. It should either be "processes restart" or "process restarts".
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
devflow unqueued this merge request: It did not become mergeable within the expected time |
dd-devflow
bot
added
mergequeue-status: waiting
mergequeue-status: removed
and removed
mergequeue-status: waiting
labels
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
dd-devflow
bot
added
mergequeue-status: waiting
mergequeue-status: queued
and removed
mergequeue-status: removed
mergequeue-status: waiting
labels
dd-devflow
bot
added
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
What does this PR do? What is the motivation?
Add entry to OP troubleshooting.
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes