Skip to content
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

2023-11-12 11:06:38.376765500 AGENT EXITED WITH CODE 256, SIGNAL 6, KILLING CONTAINER #21252

Open
jamesseo-alation opened this issue Dec 1, 2023 · 0 comments

Comments

@jamesseo-alation
Copy link

Our DD agent is dead w/ the below log, but it is unclear for us to do triage.
Usually 256 EXIT CODE in Linux is general error and thus we cannot get any clue on why DD agent is dead.

2023-11-10 03:46:09.894924500 starting security-agent
2023-11-10 03:46:09.895081500 starting agent
2023-11-10 03:46:09.895668500 starting trace-agent
2023-11-10 03:46:09.896011500 starting system-probe
2023-11-10 03:46:09.895191500 starting process-agent
2023-11-10 03:46:16.014388500 security-agent exited with code 0, disabling
2023-11-10 03:46:16.015933500 system-probe exited with code 0, disabling
2023-11-12 11:06:38.376765500 AGENT EXITED WITH CODE 256, SIGNAL 6, KILLING CONTAINER
2023-11-12 11:06:38.401523500 trace-agent exited with code 0, disabling
2023-11-12 11:06:38.416417500 process-agent exited with code 0, disabling

We are running the DD agent on K8s and thus we can see "KILLING CONTAINER".
Can any expert in DD agent help us to do triage?
Thx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant