Users Guide

● Alerting—Warning logs are displayed on the ThinOS UI as notifications.
Using log files to troubleshoot your thin client
About this task
You can use the troubleshooting options on the ThinOS desktop to troubleshoot your device.
Steps
1. From the desktop menu, click Troubleshooting.
The Troubleshooting dialog box is displayed.
2. Click the General tab, and do the following:
● Click the Extract CMOS option to extract the CMOS settings and certain BIOS settings to the USB drive or file server
based on your target device selection.
● Click the Restore CMOS option to write the CMOS settings and BIOS settings from the USB drive to the target thin
client.
● Click the Performance Monitor option to display the CPU usage history with the Memory, and Networking information.
The graphs display on top of all windows.
● Click the Force Coredump option to forcibly generate the debug information for technical investigation when your
system is not responding. Both the coredump file and the trap information image are saved to the local drive.
After you restart the thin client, both the coredump file and trap issue screenshot file are uploaded to the /wnos/
troubleshoot/ directory of the file server or a USB drive.
● Click the Export System Setting option to export the system settings file to the USB drive that is connected to the
thin client. A password is mandatory for the exported file. The file is stored in the /wnos/trouble_shoot/ folder of
the USB drive.
● Click the Export Screenshot option to export the system screenshots to the USB drive that is connected to the thin
client. The file is stored in the root folder of the USB drive.
● Click the Export logs option to export the system log files to the USB drive that is connected to the thin client. The file
is stored in the root folder of the USB drive—system_log_201910107_125610.tgz.
● Click the Import System Setting option to import the system settings file from the USB drive that is connected to the
thin client. The file is stored in the /wnos/trouble_shoot/ folder of the USB drive.
3. Click the Capture tab, and do the following:
● Capture Network Packets—Use this option to capture network-related logs.
a. Connect a USB drive to the thin client.
b. To start logging the unexpected error messages, enable the Capture Network Packets option, and click OK.
c. To stop logging the unexpected error messages, disable the Capture Network Packets option, and click OK.
d. Open the Troubleshooting window, and click Export Logs on the General tab. The log file is stored in the root
folder of the USB drive—system_log_201910107_125610.tgz.
e. Extract the tgz file. The log files are available at ./var/log/netmng/.
● Capture Wireless Packets—Use this option to capture wireless network-related logs.
a. Connect a USB drive to the thin client.
b. To start logging the unexpected error messages, enable the Capture Wireless Packets option, and click OK.
c. To stop logging the unexpected error messages, disable the Capture Wireless Packets option, and click OK.
d. Open the Troubleshooting window, and click Export Logs on the General tab. The log file is stored in the root
folder of the USB drive—system_log_201910107_125610.tgz.
e. Extract the tgz file. The log files are available at ./var/log/netmng/.
● Capture USB Packets—Use this option to capture USB packets.
a. Connect a USB drive to the thin client.
b. To start logging the unexpected error messages, enable the Capture USB Packets option, and click OK.
c. To stop logging the unexpected error messages, disable the Capture USB Packets option, and click OK.
d. Open the Troubleshooting window, and click Export Logs on the General tab. The log file is stored in the root
folder of the USB drive—system_log_201910107_125610.tgz.
e. Extract the tgz file. The log files are available at ./compat/linux/var/usbdump/.
● Capture User Coredump—Use this option to capture coredump files.
a. Connect a USB drive to the thin client.
b. To start logging the unexpected error messages, enable the Capture User Coredump option, and click OK.
c. To stop logging the unexpected error messages, disable the Capture User Coredump option, and click OK.
14
Product and subsystem security