Skip to content
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

Open
bartoliniii opened this issue Feb 4, 2022 · 8 comments
Open

Logs are cut off in dashboard UI #144

bartoliniii opened this issue Feb 4, 2022 · 8 comments

Comments

@bartoliniii
Copy link

bartoliniii commented Feb 4, 2022

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.
image

@patrickleet
Copy link
Contributor

more details would help

I haven't seen this

Is there an error?

@keskad
Copy link
Contributor

keskad commented Feb 16, 2022

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? 🙂

@bartoliniii
Copy link
Author

@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:
image

@bartoliniii
Copy link
Author

I'm not sure if it is connected with this issue, but sometimes I get the below between log lines:

failed to create fsnotify watcher: too many open files

@patrickleet
Copy link
Contributor

patrickleet commented Feb 17, 2022

failed to create fsnotify watcher: too many open files

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

@bartoliniii
Copy link
Author

@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.
It looks like a general error with sending data from a server. Isn't this kind of problem that occurs for each user?

@patrickleet
Copy link
Contributor

I didn't make the ui but maybe something to do with stdout vs stderr?

@momelod
Copy link

momelod commented Feb 23, 2022

I am also experiencing the same.

example pipeline step:

- name: db-wait
          image: docker.io/amazon/aws-cli:2.0.52
          script: |
            #!/bin/sh
            source .jx/variables.sh
            echo ">>> Found PR #$PULL_NUMBER"

sometimes it will show the echo output, sometimes it wont.
if i have multiple lines that use echo, some will show, others will not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants