JoaoJandre commented on issue #10578:
URL: https://github.com/apache/cloudstack/issues/10578#issuecomment-2743166830
> > {1000}
>
> I still can't find the specific problem. Is there any way to troubleshoot
this problem? If the log is too large, why is there such a large log?
As @weizhouapache and I explained, these large logs should not be printed
into this file, this was a bug introduced in version 4.20.0.0. Version 4.21.0.0
should fix this. My last message has a workaround to limit the size of any log
line to 1000 characters. I'm sure that if you're willing to go into the log4j2
documentation there may be other workarounds.
Regarding the issue at hand. You reported that after a restart the UI
recovers, this indicates to me that the logs are not the real culprit, since if
the logs were filling your Management Server's storage, a simple restart would
not fix the issue, you would need to manually recover some space by deleting
stuff.
Therefore, the first step I would take is pinpoint when the services became
unavailable and try to find errors during that period of time in the logs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
