-
Notifications
You must be signed in to change notification settings - Fork 459
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
Often unable to see container logs due to "error from daemon in stream: Error grabbing logs: log message is too large" #7177
Comments
looks like similar scenarios are seen here #7074 . Could be an issue in Docker. |
As mentioned in #7074 I did a In Azure Portal > IoT Hub > devices > troubleshoot module it appears as indicated by screenshot It may very well be an issue in Docker, but we are seeing this problem mostly with edgeAgent and edgeHub (perhaps because they generate more logs than our custom modules?). Starting end of last week (roughly December 15th) I feel we see this problem much more frequent on our devices. Also on devices that ran fine for many days prior. |
Regarding the "log message is too large" issue, we have noticed it is possible to largely overcome this problem by using tail. |
@ggjjj Why was this issue closed? It has not been fixed yet. I simply suggested a workaround that can be handy for other users who encounter this problem. |
@bhjertaas The "Error grabbing logs" output is coming from docker. We engaged someone with expertise on the other issue (#7074), and that person has started looking into the original docker issue. We'll be following that issue to see how it progresses. |
Closing this issue, please refer to this comment. Please reopen the bug if you are still seeing the issue. |
Expected Behavior
When running
sudo iotedge logs edgeAgent
or the identicalsudo docker logs edgeAgent
I expect the log file being printed.Current Behavior
Instead the output is
error from daemon in stream: Error grabbing logs: log message is too large (108229732 > 1000000)
or the slightly shorter versionError grabbing logs: log message is too large (1937007727 > 1000000)
.The first number in brackets are not always the same, but it is still larger than 1000000.
How can this be possible. Local logging driver is supposed to rotate the log files.
When we look at the /var/lib/docker/containers//local-logs/container.log is is only 896K. Far smaller than the configured limit.
Is this related to moby/moby#46699 ?
We have also seen
Error grabbing logs: error unmarshalling log entry (size=126): proto: LogEntry: illegal tag 0 (wire type 0)
but that is less commonly seen than the too large error.Steps to Reproduce
Provide a detailed set of steps to reproduce the bug.
Context (Environment)
Output of
iotedge check
Click here
Device Information
Runtime Versions
iotedge version
]: 1.4.20docker version
]: 20.10.25Note: when using Windows containers on Windows, run
docker -H npipe:////./pipe/iotedge_moby_engine version
insteadLogs
aziot-edged logs
edge-agent logs (retrieved by sudo cat /var/lib/docker/containers//local-logs/container.log
edge-hub logs
Additional Information
Please provide any additional information that may be helpful in understanding the issue.
The text was updated successfully, but these errors were encountered: