question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Create a script for diagnostic and collect needed info for support in case of troubleshooting

See original GitHub issue

This is a part of https://github.com/codenvy/codenvy/issues/412 epic

We need create a tool which will simplify collecting any needed info for support customers in case of some problems. That tool should be super easy to execute preferably bash script and on first iteration it should collect needed files or commands output and put it into zip. Items to collect: files (note * means all files in the folder) /var/log/puppet/ /var/log/nginx/ /var/log/mongodb/* /var/log/docker-distribution.log /var/log/fail2ban.log /var/log/haproxy.log /var/log/messages /var/log/swarm.log /var/log/yum.log /etc/puppet/auth.conf /etc/puppet/autosign.conf /etc/puppet/fileserver.conf /etc/puppet/puppet.conf /home/codenvy/codenvy-data/che-machines-logs/* /home/codenvy/codenvy-data/logs/* /home/codenvy/codenvy-data/conf/machine.properties /home/codenvy/codenvy-data/conf/general.properties /etc/resolv.conf /etc/hostname /etc/hosts**

commands output to collect (please keep them in a separate files with predictable names): facter fqdn hostname hostname -f puppet agent -t

Everything inside of that zip should be well structured to make it easy to understand and analyze. example: zip/ …/logs/ …/configs/ …/commands_output/

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
ghostcommented, Jul 23, 2016

@riuvshin @skryzhny please try this one on a real Codenvy instance. I have tried it on a freshly installed On-Prem on Digital Ocean. Execute as root: curl https://gist.githubusercontent.com/eivantsov/7744cbf9ce6547f2be5e93aa05b5bce2/raw/54a636d9d92753b2066842bb5c8eecdfcafb956a/report.sh | bash

0reactions
ghostcommented, Jul 26, 2016
Read more comments on GitHub >

github_iconTop Results From Across the Web

MustGather: Collecting data to diagnose issues with User ...
This document describes the general information and diagnostic data needed to start troubleshooting issues related to User Management ...
Read more >
Working with diagnostic support scripts in AWS DMS
Work with AWS DMS support scripts to return diagnostics for AWS DMS ... We want to make sure that AWS Support gets as...
Read more >
Introduction to TroubleShootingScript toolset (TSSv2)
Introduces the TroubleShootingScript Version 2 (TSSv2) toolset and provides answers to frequently asked questions about the toolset.
Read more >
Information required when opening a support case for BIG-IP ...
A qkview diagnostic file contains the configuration files that F5 Support most frequently needs when troubleshooting an issue.
Read more >
Generate a diagnostic file - Splunk Documentation
The diag collection process gathers information such as server ... If your Support case is about forwarding, Support will probably need a ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found