Tomcat
The Tomcat access log records requests to the server. By default the access log is configured in $TOMCAT/conf/server.xml. The access log may be configured to log the PhixFlow username of the user making the request. It may be specified as %{username}s in the log file configuration message pattern. For more information on configuring the access log see https://tomcat.apache.org/tomcat-8.5-doc/config/valve.html#Access_Log_Valve/Attributes
Configuring Server Log Files
PhixFlow generates detailed logs of activity on PhixFlow and Tomcat and writes them toDuring the PhixFlow webapp installation, the administrator configures the level of server logging in:
- logback.xml; see Configure logback.xml
- phixflow-logging.xml; see Configure phixflow-login.xml
When investigating problems, you can change the logging level for PhixFlow. If you are working with the PhixFlow support team, they can provide advice on what to change.
logback.xml
logback.xml controls detailed event/error logging on the server. Changes to logback.xml take effect within a minute or so, without having to restart the Tomcat server.
Change the configuration of this file
- at installation, to rename the log file if you have multiple PhixFlow instances; see Renaming the Log File.
- to log more detailed information when troubleshooting.
Edit and save the logback.xml file, which is in:
| Code Block |
|---|
[tomcat installation base]/webapps/[instance name]/logs/WEB-INF/classes/logback.xml |
For example:
| Code Block |
|---|
/usr/local/tomcat/webapps/phixflow/WEB-INF/classes/logback.xml |
Some options can generate huge amounts of extra logging, and these will create very large log files.
PhixFlow will automatically pick up the change, so you can continue investigating, for example repeating the activity that has the problem. After repeating the problem, check your phixflow.log file to see the additional logging details.
| Tip |
|---|
Remember to reset |
If you want to integrate PhixFlow server logs into other logging frameworks, such as Google Cloud's stackdriver, please contact support@phixflow.com.
phixflow-logging.xml
phixflow-logging.xml file contains a list of directories that contain log files, and is used when you download log files from the GUI. You only need to change this file as requested by PhixFlow Support.
| Anchor | ||||
|---|---|---|---|---|
|
In addition to viewing the log files in the logs directory you can download a zip file of all or selected log files.
In the bottom right, click
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Select Other Options → Download Log Files. PhixFlow opens a window prompting you to enter file names.
Enter file names, optionally using an asterisk * as a wildcard.
Click
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
When the download is finished, a blue notification box reports that the file is ready. Click the notification to download the zip file.
The server log files generated by PhixFlow and Tomcat, are:
- phixflow.log and phixflow.log.<date>
phixflow.log is the default name. The name and recorded data can be configured in logback.xml. - security.log
- manager.<date>.log
- localhost_access_log.<date>.txt
- localhost.<date>.log
- host-manager.<date>.log
- catalina.out and catalina.<date>.log
The main log files are phixflow.log and phixflow.log.<date>. This is the default name. The name and recorded data can be configured in logback.xml.
Security.log contains a record of all login attempts and logouts. Successful login attempts and logouts are logged with the username, session and IP address of the user. Logouts also record if the logout was the result of a user action or session timeout. Failed attempts to login are also logged with the username, IP address and reason for the failure.
If you have multiple instances of PhixFlow hosted under the same Tomcat instance, each PhixFlow instance will have a different log file name. Check logback.xml file to find out the main log file names.
Configuring Server Log Files
During the PhixFlow webapp installation, the administrator configures the level of server logging in:
- logback.xml; see Configure logback.xml
- PhixFlow-logging.xml; see Configure phixflow-login.xml
When investigating problems, you can change the logging level for PhixFlow. If you are working with the PhixFlow support team, they can provide advice on what to change.
Edit and save the logback.xml file, which is in:
| Code Block |
|---|
[tomcat installation base]/webapps/[instance name]/WEB-INF/classes/logback.xml |
For example:
| Code Block |
|---|
/usr/local/tomcat/webapps/phixflow/WEB-INF/classes/logback.xml |
Some options can generate huge amounts of extra logging, and these will create very large log files.
PhixFlow will automatically pick up the change, so you can continue investigating, for example repeating the activity that has the problem. After repeating the problem, check your phixflow.log file to see the additional logging details.
.