Skip to end of metadata
Go to start of metadata

 

page under construction

Icon

This article makes use of deprecated configuration items and has to be re-worked

Specifying log files

  • YADE can write a separate log file for each transfer it carries out.
  • It can do this when the file transfer is started from the console and when it is started from the crontab. There are two stages to doing this:
    • specifying the global log file name and
    • specifying the log file name for each transfer.

Specifying the global log file name

  • The log file to be used for a particular transfer is defined in the log4j.properties file.
    • A "rollingFileAppender" is used to configure the "global" log, which is not transfer-specific.
  • The log4j.properties file can be located in the same folder as the settings file. The parameter defining the location of log4j does not have to be explicitly set in the profil.

A typical log4j.properties file would look like:

Note that

  • the default value for stdout is set by the operating system and
  • the default location for the YADE log file is:
    • /var/opt/sosftp/log/sosdex.log
  • YADE will overwrite the default file name with values set in the log_filename parameter.

Note also that

  • the working directory for chron is not ./jade/bin, where the log4j.properties file is to be found.
  • this means that when starting chron:
    • use cd to navigate to the home directory
    • start jade.sh
    • start runner-script.sh, which switches the working directory to the bin directory
    • the name of the log4j.properties file can then be set with a parameter.

A typical YADE settings file with profiles would look like:

Specifying the log file name for each transfer

The log4.jproperties file is universal. The name specified with the log_filename parameter is extended using the extension ".html" and used for log4j. The trick here is that the definitions in the property file are dynamically modified. This results in two files:

  • the file with the name specified in the log_filename parameter and
  • the HTML file with a summary of the transfer. The HTML file will be overwritten with every transfer, the log file specified by the log_filename parameter is a rolling log file.

The complete log4j.properties file would look like this:

The transfer-specific log file is configured in the HTML appender shown in the listing above. The file name in the file is just a placeholder. YADE modifies this to "log_filename".html

Note that at the time of writing in the current (1.5.4014) YADE version a standard and relatively simple log4j layout is used. A modified layout, that includes line breaks, is being tested.