Editing Server logs
From FileZilla Wiki
Jump to navigationJump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
[[Category:Documentation]] | [[Category:Documentation]] | ||
Note: Work in progress! | |||
= Logging in FileZilla Server = | = Logging in FileZilla Server = | ||
FileZilla Server, like the client, includes two means of logging, screen and file log. | FileZilla Server, like the client, includes two means of logging, screen and file log. | ||
| Line 9: | Line 10: | ||
If you want logs when no user is logged on, don't want to leave the admin interface running or want to track large logs, you need to use file logging (see below). | If you want logs when no user is logged on, don't want to leave the admin interface running or want to track large logs, you need to use file logging (see below). | ||
=== What is logged | === What is logged === | ||
* Connection ID (in brackets): every new connection will get a unique ID, this aids in tracking one special connection only<br> | * Connection ID (in brackets): every new connection will get a unique ID, this aids in tracking one special connection only<br> | ||
* Time stamp | * Time stamp | ||
| Line 16: | Line 17: | ||
* The separator ><br> | * The separator ><br> | ||
* Log text: Commands received, replies sent, status messages and more | * Log text: Commands received, replies sent, status messages and more | ||
Note that additional internal status messages don't follow this scheme. | Note that additional internal status messages don't follow this scheme. | ||
| Line 42: | Line 34: | ||
The second logging possibility is logging to file. Filelog is disabled after a fresh installation and must be enabled first. | The second logging possibility is logging to file. Filelog is disabled after a fresh installation and must be enabled first. | ||
=== What is logged | === What is logged === | ||
* Connection ID (in brackets): every new connection will get a unique ID, this aids in tracking one special connection only<br> | * Connection ID (in brackets): every new connection will get a unique ID, this aids in tracking one special connection only<br> | ||
* Time stamp | * Time stamp | ||
| Line 51: | Line 43: | ||
Note that additional internal status messages don't follow this scheme. | Note that additional internal status messages don't follow this scheme. | ||
=== Setting up file log === | === Setting up file log === | ||
Open the server settings | Open the server settings and navigate to the 'Logging' tab. Tick the 'Enable logging to file' box and you're done. The logfiles are stored into a 'Logs' subdirectory of FileZilla Servers installation path. This location cannot be changed.t | ||
=== Limiting the log size === | === Limiting the log size === | ||
| Line 79: | Line 51: | ||
=== Daily logfile rotation === | === Daily logfile rotation === | ||
You can either log everything into one big file, or let the server create a new logfile every day. Just enable 'Use a different logfile each day', and FileZilla Server will create logs in the format '''fzs- | You can either log everything into one big file, or let the server create a new logfile every day. Just enable 'Use a different logfile each day', and FileZilla Server will create logs in the format '''fzs-yyyy-mm-dd.log'''.<br> | ||
The timestamp in the logfile name follows ISO8601 (four digit year, then month, then day), so the logs will sort correctly. Additionally you can set the number of days for which logfiles are kept. Enable 'Delete old logfiles after' and put the desired value (in days) into the field. | The timestamp in the logfile name follows ISO8601 (four digit year, then month, then day), so the logs will sort correctly. Additionally you can set the number of days for which logfiles are kept. Enable 'Delete old logfiles after' and put the desired value (in days) into the field. | ||
