-
Notifications
You must be signed in to change notification settings - Fork 3
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 not available anymore? #23
Comments
That sounds like a problem of the HOBBIT platform itself. Can you please provide the ID of your experiment for which you would like to have the logs? |
experiment ID: 1523524992970
Thanks!
…On Thu, Apr 12, 2018 at 1:16 PM, Michael Röder ***@***.***> wrote:
That sounds like a problem of the platform itself. Can you please provide
the ID of your experiment for which you would like to have the logs?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABkrIgAxp01IKdlV3ItKp-3Qb_XFazAuks5tnymOgaJpZM4TRc1r>
.
|
I can confirm that the server answers with HTTP 500 for both benchmark and system because of an internal problem retrieving the logs. @earthquakesan from the logs of the GUI it looks like the result is empty (or something similar). In Kibana, there are no logs of the system and only two log messages from containers of the benchmark.
However, the platform controller logged that the experiment was executed without problems
|
@acip an earlier run of your system created more than 400,000 log messages. It would be nice if you could reduce the number of log messages the system produces 😉 |
@MichaelRoeder It throws because the result set is empty. I will make a check for this. Another issue is that the containers do not write logs to ELK. |
@MichaelRoeder Indeed, that slipped in production :) We'll double check to prevent that from happening. |
@MichaelRoeder Is the problem solved? We try to download the System log today and also get 500 HTTP error. Could you please take a look into this? Thanks. |
We are facing a mixture of two problems. The first issue is already solved by @earthquakesan and he is currently working on the second issue. |
The problems regarding logging should be solved now in the new platform version. Please note that logs > 500.000 lines won't be retrieved anymore. |
Hi!
Downloading logs returns a 500 HTTP error today. Can you look into it?
Thanks!
Ciprian Amariei
The text was updated successfully, but these errors were encountered: