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.

Sign up for GitHub

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

Jump to bottom

initContainer of ws-daemon logs infos as errors #5249

Closed
meysholdt opened this issue Aug 17, 2021 · 2 comments · Fixed by #5283
Closed

initContainer of ws-daemon logs infos as errors #5249

meysholdt opened this issue Aug 17, 2021 · 2 comments · Fixed by #5283

Comments

@meysholdt
Copy link
Member

In the bash script that creates the raid0, the set -x causes all statements to be printed to stderr when executed, which then get severity "error" in our log system.

Expectation: info-messages should not be errors. Maybe -v instead of -x does the trick. Or something with BASH_XTRACEFD.

see also https://serverfault.com/questions/296991/send-bash-x-output-to-logfile-without-interupting-standard-output/579078#579078
@meysholdt
Copy link
Member Author

I'm filing this issue because the errors led to confusion here

@JanKoehnlein
Copy link
Contributor

We're currently swamped. Pleas bring this up again later

@aledbf aledbf mentioned this issue Aug 19, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[chart] Redirect bash debug to stdout gitpod-io/gitpod
2 participants
@meysholdt @JanKoehnlein