When collecting logs, the entire collection process will be recorded in the messages. When the collection starts, it will print [os_backup_info.sh] Begin
to collect log in the messages, and the collection will print [os_backup_info.sh] Collect logs end, in these two sentences. The log between them is the
printing during the entire collection process. When the log is collected, when a script is started, Begin to execute xxxx is printed in the messages,
where xxxx indicates the name of the script to start execution.
Log collection failures include partial collection failures and full collection failures (meaning no logs were collected). The reasons for the complete
collection failures that are currently known are:
1, the remaining memory is less than 160M, the messages will be printed in the messages: [OS_CreatePolicy] Insufficient memory, not allow to execute
this script.
If there is enough memory, it will print OS_CreatePolicy] There is sufficient memory, so allow to collect log.
2, interrupted by the interrupt signal, the messages will be printed in the messages: [os_backup_info.sh] Have received sinal xxx, so exit the script.
The xxx is the interrupted signal name, but the kill signal can not be captured, currently only capture Three interrupt signals to INT, TERM, and QUIT.
3, because the log collection does not allow concurrency, so when the system is performing a one-click log collection, and then collecting is not allowed,
the messages will be printed in the messages: [os_backup_info.sh] Someone is collecting logs, please try Again later.
