-
Notifications
You must be signed in to change notification settings - Fork 60
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
Logs aggregator dies/is stopped #1832
Comments
status codes of the exited containers are I wonder if this is caused by the logs collector resource leak. |
## Description: This change strengthens the restart policy for the logs aggregator. Prior to this, the restart only occurred on failure. Now, we make docker attempt to always restart the logs aggregator. This should help address #1832 where the logs aggregator was stopped with a `137` status code but wasn't restarted. This change also addresses a `Propagate must be provided with a cause` panic occurred here: #1832. This was caused by nil err's being propagated in the create logs collector code. This change fixes that issue. ## Is this change user facing? NO ## References: #1832 #1311
Update - this likely wasn't being caused by the log collector memory leak. Going to look deeper into memory limits on the logs aggregator. |
What's your CLI version?
0.85.29
Description & steps to reproduce
I tried a
kurtosis run
today, and got this:I dumped the engine logs, and found:
I checked, and my logs aggregator was indeed stopped, though I'm not sure why:
I also have a logs-collector somehow hanging around, even though I don't have any enclaves running:
This is the output of
docker container inspect kurtosis-logs-aggregator
:And the container logs:
Desired behavior
I never get this error; Kurtosis correctly manages the logs-aggregator
What is the severity of this bug?
Critical; I am blocked and Kurtosis is unusable for me because of this bug.
What area of the product does this pertain to?
CLI: the Command Line Interface
The text was updated successfully, but these errors were encountered: