Q1: What do I do if the files of collected logs are excessively large?
A: The size of log files is limited to 2 GB on a single node. If the size of log files exceeds the limit, no log file is returned and the error message Error:File too large is returned. In this case, you must adjust the query time range or change the value of the file_number_limit parameter in the config.yml file.
Summary:
+------------------+----------------------+--------+------------+--------+------------+
| Node | Status | Size | Password | Time | PackPath |
+==================+======================+========+============+========+============+
| xxx.xxx.xxx.xxx | Error:File too large | 0.000B | | 21 s | |
+------------------+----------------------+--------+------------+--------+------------+
| xxx.xxx.xxx.xxx | Error:File too large | 0.000B | | 70 s | |
+------------------+----------------------+--------+------------+--------+------------+
Q2: What do I do if too many log files are to be collected?
A: The number of log files is limited to 20 on a single node. If the number of log files exceeds the limit, the collection task is not executed and the error message Error:Too many files xx > 20 is returned. In this case, you must adjust the query time range or change the value of the file_size_limit parameter in the config.yml file.
Q3: What do I do if the error message zip: command not found is returned?
A: Collected information is compressed by using a Zip tool on the target host. Therefore, a Zip tool must be installed on the target host whose information is to be collected.