waarp-analyze accepts the following options
Verbose output. All information about the collect of data and the generation of the report is written on the standard error.
Prints version and exits
Write report to this location. Use ‘-‘ for standard output (default is standard output)
Limit analyze to this Waarp instance
Show the help message
Depending on which system user runs waarp-analyze, it might not have the rights to collect all information. It might not have the required UNIX permissions.
To work around that limitation, make sure you run waarp-analyze with the same user that runs Waarp instances.
Waarp Analyze can be run when needed to get a full picture of the of an instance configuration along with its system environment.
It is useful to debug the configuration or to have all the elements necessary to fine-tune it.
Generate HTML reports¶
Waarp Analyze generates its report in the ReStructured Text format.
To generate a HTML report, you can run the following command:
./waarp-analyze -o report.txt rst2html report.txt report.html
or use the one-liner :
./waarp-analyze | rst2html > report.html
Run as error task in Waarp R66¶
It can be useful to run Waarp Analyze as a error task in Waarp R66 to ease the debug of failed transfers by capturing the system environment when the error occured.
To do so, add the following XML to your transfer rules in a <rerrortasks> and/or <serrortasks> (whether you want to run it on the receiver and/or the sender of the file):
<tasks> [...] <task> <type>EXEC</type> <path>/path/to/waarp-analyze --output=/path/to/reports/#DATE##HOUR#-#TRANSFERID#.txt</path> <delay>30000</delay> </task> [...] </tasks>