-
Notifications
You must be signed in to change notification settings - Fork 35
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 are cut off in dashboard UI #144
Comments
more details would help I haven't seen this Is there an error? |
Could you post any screenshots to show how it looks like? Any logs from browser's inspector while viewing this view? Server responses from inspector? 🙂 |
@keskad @patrickleet I've just attached a screenshot to the issue description. In network traffic, I see that dashboard is presenting everything that gets from the server: |
I'm not sure if it is connected with this issue, but sometimes I get the below between log lines:
|
is an error with how your kubernetes nodes are configured. see kubernetes/kubernetes#64315 (comment) FWIW, I've only seen this happen with worker groups, not managed node groups - I think defaults for managed node groups are better |
@patrickleet I've changed the node configuration, now I don't see an error with "open files" anymore. Unfortunately original issue, with cut off logs, still occurs. |
I didn't make the ui but maybe something to do with stdout vs stderr? |
I am also experiencing the same. example pipeline step:
sometimes it will show the echo output, sometimes it wont. |
Logs presented in web UI are always cut off and there is no way to find the reason for the failure from this view.
In
jx get build logs
logs are present correctly.Sample URL address for this view - https://dashboard-jx.jenkinsx.company/org/repot/master/XXX
Pipelines visualizer version: 1.7.5
Described situation is illustrated below. On the left you can see all logs from a pod, on the right you can see that in dashbord there are a few last lines missing. I have this issue for every failing build.
The text was updated successfully, but these errors were encountered: