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

Gather and print System Information before running to give more information while debugging #57

Open
tkilias opened this issue Apr 1, 2021 · 1 comment
Labels
feature Product feature

Comments

@tkilias
Copy link
Collaborator

tkilias commented Apr 1, 2021

Background

  • we often need to debug setups on user systems
  • we typical need information about the system, e.g
    • OS
    • OS Version
    • Docker Daemon Version
    • Docker Client Version
    • Host can access Docker Hub
    • Docker container can access internet (Ubuntu)
    • bash version
    • gnu utils Version
    • installed exaslct Version
    • Project name
    • Repository Status + Sub module status
      • modified?
      • commit id history until first commit in main branch history
      • paths to exaslct.log files for the last X builds
      • Docker images with exasol script languages prefix
    • available disk space on /
    • are checksums ok

Acceptance Criteria

  • would be a new command of exaslct (something like "diagnosis")
  • add message like "Please send to Exasol"
  • develop a bash script which collect the listed information and prints it to terminal and file
  • the script needs to work on minimal dependencies
  • the script needs to be as error resilient as possible and collect as much information as possible

Add new integration tests in installer scripts, for testing version number.
For that, extract most part of https://github.com/exasol/script-languages-container-tool/blob/main/installer/tests/test_exaslct_install_template_with_current_ref.sh into separate script and include via source (to keep trap/env variable/etc.)

@redcatbear
Copy link
Contributor

Please elaborate which system information, where to gather to and triggered by what.

@tkilias tkilias transferred this issue from exasol/script-languages-release Jul 16, 2021
@tkilias tkilias added feature Product feature source:exasol timeline:long-term Unlikely to be implemented in the near future labels Jul 16, 2021
@tomuben tomuben removed the timeline:long-term Unlikely to be implemented in the near future label Jul 20, 2021
@tkilias tkilias added the timeline:long-term Unlikely to be implemented in the near future label Nov 12, 2021
@redcatbear redcatbear removed the timeline:long-term Unlikely to be implemented in the near future label Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Product feature
Projects
None yet
Development

No branches or pull requests

3 participants