Collecting The Log Of Key Operations - Canon imageRUNNER ADVANCE C5500 Series Service Manual

Hide thumbs Also See for imageRUNNER ADVANCE C5500 Series:
Table of Contents

Advertisement

■ Initializing the Debug Log Settings (DEFAULT)
Set all debug log-related settings back to the default settings (the state at the time of shipment).
• You must perform this measure when you complete troubleshooting and return the device to the customer. (Operations
required)
• Perform this measure when you reset or make another settings relating to debug log during a log collection investigation.
For log files that were automatically stored in the debug log storage space secured in the machine's controller (/var/xpt/dbglog),
they kept to be stored unless the number of log files exceeds the limit. To delete the stored log (to use HIT-STS), use "LOG-DEL"
described later.
■ Deleting Debug Logs (LOG-DEL)
This is a function to delete log files that have been automatically stored. The settings on log operation such as the log storage
trigger are not cleared.
Normally, there is no need to use this function (the firmware automatically restricts the upper limit for the number of stored logs);
however, it is necessary to delete logs by LOG-DEL when using HIT-STS to see whether the log is collected or not after changing
the log storage trigger setting.
(Because the HIT-STS status always shows OK as long as there is a log that has been stored.)

Collecting the Log of Key Operations

■ Overview
• The key operation log function collects key operation log of the user to identify the cause of an error such as a wrong FAX
transmission, to see whether the error is caused by a failure in the machine or a wrong operation of the user.
• The key operation log is not recorded with the status at the time of shipment.
• A setting is ready in "Setting/ Registration" menu to enable the saving function of key operation log.
• Only when the above setting is enabled, the machine determines that the user permission has been obtained and starts
recording user operation log.
• User operation log is saved/collected to be included in sublog when the sublog is saved.
• Among the user operation log that was saved, the following confidential information is masked.
• Password entered from the software keyboard
• Password, PIN code, etc. entered from the numeric keypad
• Character strings displayed with turned letters on the UI screen
NOTE:
• When the log is output, information such as passwords and PINs is output as masked characters. This can help prevent
sensitive information from being leaked externally.
• Collect this log when it is determined that analysis of the firmware debug log is required.
■ Operation Procedure
● Preparation
• USB memory device
Prepare a USB device that meets the following conditions.
• Formatted with the FAT file system
• Not locked with a password
• Has the firmware of the corresponding model registered
● Prerequisites
It is necessary to obtain user permission to record the log of key operations to analyze problems in advance.
● Operation
1. Enable the [Store Key Operation Log] setting.
After obtaining user permission, select [Settings/Registration] > [Management Settings] > [Device Management] > [Store
Key Operation Log].
471
6. Troubleshooting

Advertisement

Table of Contents
loading

Table of Contents