Server log files

At installation, PhixFlow logging id configured using the files logback.xml and PhixFlow-logging.xml; see Configure logback.xml and phixflow-logging.xml for details.

PhixFlow generates a number of detailed logs on the server. These will be written to:

[tomcat installation base]/logs

For example:

/usr/local/tomcat/logs

In most cases, you only need to use these files when investigating problems - for most day-to-day issues the logging information generated in the Console.

The name of the principal log file for the PhixFlow application is set in the log4j.properties file (see below), but commonly this is called phixflow.log.  Generally, the only reason that the default name (phixflow.log) is not used, is when multiple instances of PhixFlow are being hosted under the same tomcat instance - in this case, check in the log4j.properties file for the PhixFlow instance you are interested in, and find out the file name of the principal server log being generated for this instance of PhixFlow.

Server logging configuration - log4j.properties

The level of server logging generated by PhixFlow is controlled in the log4j.properties file.

The name of the principal server log file generated by this instance of PhixFlow is also set in this file, although this will commonly be left as the default value, phixflow.log. This will be set when the instance is installed - see Install PhixFlow Webapp for details.

You will find the log4j.properties file at:

[tomcat installation base]/webapps/[instance name]/WEB-INF/classes/log4j.properties

For example:

/usr/local/tomcat/webapps/phixflow/WEB-INF/classes/log4j.properties

Changing the server logging configuration

When investigating problems, you may wish to alter the logging level for certain features of PhixFlow. You will either be guided to do this by the PhixFlow support team, or you may find options in the troubleshooting sections of this help. If you want to add an option, simply open the log4.properties file, add the line, and save it. PhixFlow will automatically pick up the change, and you can carry out the operations you are investigating, e.g. running a certain task plan. Once these operations are complete, look in your principal server log file (as above, usually phixflow.log) to see the results with enhanced logging details.

Reverting to standard logging

Don't forget to remove any enhanced logging options once your investigation is finished!

Some options can generate huge amounts of extra logging, and these will create very large log files.