Yesterday I thought that I learned the Zen since reexport without description in documentation forced to work. Today the Zen laughed at me and gave the next surprises. Now is more detailed.
Working with cp_log_export yesterday, I defined that at the started process of cp_log_export the reexport function just did not work, the logs were not transferred to external kiwi syslog server, though displayed in the Smartlog console. Found a solution. It turned out that if to stop process by the cp_log_export stop command, and then to execute cp_log_export reexport, then the logs go for the entire period. But it was yesterday! Today decided to fix the experience, but in attempt to unload the log at the working process of cp_log_export that not worked yesterday, today perfectly earned. The truth new ghost effects were added, the logs in the unloaded log from the SMS server went by dates alternately. So not in on increase, but separately by day 20, 19, 17. 19. 17, 19 and so on. The same situation with logs reexports if the log_export process was at first stoped and then reexport executed.
Somebody met this problem?
Developers can give the detailed answer in what state it is necessary to start the reexport function and how to adjust logs export for N days