RTDService Logs
Log Description
Default paths of RTD log files:
- Path for storing RTDService operation logs and RTDPortal logs: /var/log/Bigdata/rtd/rtdservice
- Path for storing RTDService installation logs: /var/log/Bigdata/rtd/rtdservice/script
Log archive rule: The automatic compression and archive function is enabled for RTD logs. By default, RTD logs are automatically compressed every day into a package named in the format of Original log file name-yyyy-mm-dd_hh-mm-ss.ID..log.zip. By default, the latest 10 compressed files are retained every day. You can set the appender.all.strategy.max parameter on FusionInsight Manager to specify the number of compressed files you want to retain.
Log Type |
Log File |
Description |
---|---|---|
RTDService operation log |
RTDService.log |
Run logs of RTDService |
RTDService_error.log |
Error log of RTDService |
|
RTDService_audit.log |
Audit log of RTDService |
|
RTDService installation log |
cleanup.log |
RTDService uninstallation log |
checkHaStatus.log |
HA check log |
|
checkinstall.log |
Installation and scale-out check log |
|
checknode.log |
Health check log of RTDServer instances |
|
postinstall.log |
Installation and scale-out log |
|
prestart.log |
RTDService prestart log |
|
start.log |
RTDService boot log |
|
stop.log |
RTDService stop log |
|
RTDPortal log |
RTDportal.log |
Run log of RTDPortal |
RTDportal_error.log |
Error log of RTDPortal |
Log Levels
Table 2 describes the log levels supported by RTDService.
The priorities of run log levels are FATAL, ERROR, WARN, INFO, and DEBUG in descending order. Logs whose levels are higher than or equal to a specified level are displayed. The number of displayed log records decreases as the specified log level increases.
Level |
Description |
---|---|
FATAL |
Logs of this level record fatal error information about the current event processing that may result in a system crash. |
ERROR |
Logs of this level record error information about the current event processing, which indicates that system running is abnormal. |
WARN |
Logs of this level record abnormal information about the current event processing. These abnormalities will not result in system faults. |
INFO |
Logs of this level record normal running status information about the system and events |
DEBUG |
Logs of this level record the system information and system debugging information |
To change log levels, perform the following operations:
- Log in to Manager.
- Choose Cluster > Services > RTDService. Click Configurations then All Configurations.
- On the menu bar on the left, select the log menu of the target role.
- Select a desired log level.
- Click Save. In the displayed dialog box, click OK to make the configuration take effect.
Log Formats
The format of RTDService run logs is as follows:
Component |
Format |
Example |
---|---|---|
RTDService |
<yyyy-MM-dd HH:mm:ss,SSS>|<LogLevel>|<Name of the thread that generates the log>|<Location where the log event occurs>|< message> in log; |
2015-10-27 08:51:18,477 DEBUG [http-bio-160.136.0.200-21820-exec-630] common.RestResponseBuilder:61 - {"resultCode":0,"resultMessage":null,"result":{"status":"RUNNING","version":"v1.0"}} |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot