Creating log files: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
| | ||
{{#invoke:Message box|ambox |type=content|text=Always be very careful when manipulating files. | {{#invoke:Message box|ambox |type=content|text=Always be very careful when manipulating files in Linux. One false manoeuvre can break the software.}} | ||
| | ||
Revision as of 12:35, 19 January 2018
Introduction
In case of an incident, it could be helpfull to send logs with the opening of the ticket or anytime the support engineer assignd to your case asks you to.
Solution
 | Always be very careful when manipulating files in Linux. One false manoeuvre can break the software. |
Usinging the SSH client of you choise, login to the command line interface of TVC. Once logged in successfully, execute the following command to create an archive (tarball) that contains all the logs required by support.
You do not have to stop services, unless instruted so by support.
$ sudo su - # cd /opt/tv # sh -x collect_logs.sh
This may take a whilt to complete.
Once you get the command prompt back list all files in the /opt/tv directory:
[root@crt-vir-a-tvc11 tv]# ls appliance collect_logs.sh dataengine flow personality queryengine serverhealth tv-reboot.sh tv-shutdown.sh tv-stop-services.sh application configengine dds manager portal repository tv-logs_2018-01-19_13-22-44.tar.gz tv-restart-services.sh tv-start-services.sh userdiscovery
Notice the file carrying the name tv-logs_YYYY_MM_DD_HH-MM-SS.tar.gz ? This is the archive you have to send to TAC.
Transfer this file to the destination using WinSCP or any SCP tool of your choice.
Make sure to delete these files once they are no longer needed:
# rm tv-logs_YYYY_MM_DD_HH-MM-SS.tar.gz