Creating log files: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
<pre>$ sudo su - | <pre>$ sudo su - | ||
# cd /opt/tv | # cd /opt/tv | ||
# | # ./collect_logs.sh | ||
</pre> | </pre> | ||
Still within the same directory, list all regular files: | |||
<pre>[root@crt-vir-a-tvc11 tv]# ls | <pre>[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 | appliance collect_logs.sh dataengine flow personality queryengine serverhealth tv-reboot.sh tv-shutdown.sh tv-stop-services.sh | ||
Revision as of 07:07, 19 April 2020
Introduction
In case of an incident, it is advisable to send logs together with the creation of the ticket or anytime the support engineer asks you to. This solution applies to all TruView devices.
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 a file containing all the logs required.
Keep all services running and run the following script as sudoer:
$ sudo su - # cd /opt/tv # ./collect_logs.sh
Still within the same directory, list all regular files:
[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 tv-logs*. This is the file you have to send to support.
These files could be large; make sure to delete the file afterwards:
# rm tv-logs*