Device logs are not saved in the following conditions:
- Forced power OFF (by disconnecting the power plug or holding the power switch pressed)
When forced power OFF occurs, debug logs cannot be saved because the shutdown sequence does not run normally. - When the machine is shut down while engine debug logs are being saved
When the machine is shut down while engine debug logs are being saved, the machine stops saving the logs. When this happens, engine debug logs cannot be output to media. - When too many debug logs are outputted
When the modules are outputting debug logs faster than the machine can save them, the machine fails to save the debug logs.
The following logs are not saved:
- Debug logs that are output between main power is turned ON and startup of log trace function
In order to avoid affecting the startup time, the log trace function starts after the prioritized application is displayed. Debug logs outputted immediately after machine startup may not be saved.
Examples of logs that cannot be saved:
- The logs of wake-up operation when the machine failed to resume from engine OFF mode
- Network communication logs
- NRS-related logs
- HTTP session timeout logs
- Security communication logs (see below)
Security of the Operation Log:
- User ID
- Password
- IP address
- Encryption key
- Transition to SP mode