|
|
| Line 1: |
Line 1: |
| [[Category:Documentation]]
| | hello there and thank you for your info e2€“ I have definitely picekd up something new from right here. I did however expertise a few technical points using this site, as I experienced to reload the web site many times previous to I could get it to load properly. I had been wondering if your hosting is OK? Not that I am complaining, but sluggish loading instances times will sometimes affect your placement in google and can damage your high-quality score if advertising and marketing with Adwords. Well I am adding this RSS to my email and could look out for a lot more of your respective exciting content. Ensure that you update this again soon.. |
| Note: Work in progress!
| |
| | |
| = Logging in FileZilla =
| |
| FileZilla includes two ways of logging all communication with the server, which essentially consists of commands sent by the client and server replies.
| |
| The following chapters will shortly explain, what you'll need to do if you're asked to 'Please post a log'.
| |
| | |
| == Screen log ==
| |
| The first logging type is the screen log. It is always enabled, but the pane can be hidden using the View menu. Please note that the screen log is limited to a finite number of lines displayed, long logs may scroll out of the screen and can't be recalled.
| |
| | |
| === What is logged ===
| |
| * Timestamp (optional)<br>
| |
| * Description: Status, Command, Response, Trace etc.<br>
| |
| * Log text: Commands sent, status messages and more
| |
| | |
| === Location ===
| |
| By default the log pane is located directly below the QuickConnect bar, but you can adjust the location using the interface settings:
| |
| | |
| * Above the file lists<br>
| |
| * Next to the transfer queue<br>
| |
| * As tab in the transfer queue pane
| |
| | |
| === Color coding ===
| |
| The screen log is color-coded:
| |
| | |
| * Informational: black<br>
| |
| * Commands: blue<br>
| |
| * Responses: green<br>
| |
| * Errors: red<br>
| |
| * Raw directory listing: Dark cyan<br>
| |
| * Debug messages: Purple<br>
| |
| | |
| Please note that the last two only appear if verbose logs are activated (using the Debug menu, see below)
| |
| | |
| === Changing the verbosity ===
| |
| Please don't change the verbosity of the logs for normal operation of FileZilla. Only change it if you're asked for it, change it back after the problem has been solved. Using the Debug menu in the FileZilla settings, you can adjust the verbosity in five levels (0-4) and enable the display of raw directory listings.
| |
| | |
| == File log ==
| |
| Since version 3.2.0-rc1, FileZilla includes the possibility of logging to a file. Contrary to screen log, file log is not enabled by default.
| |
| | |
| === What is logged ===
| |
| * Timestamp: data and time<br>
| |
| * FileZilla process ID<br>
| |
| * Connection ID, browsing connection is 0<br>
| |
| * Log text: Commands sent, status messages and more
| |
| | |
| === Setting up file log ===
| |
| Just enable 'Log to file' in FileZilla's settings, Logging tab and select a path and filename for the log. You can select the path freely, but you must use a directory where you have write permission.
| |
| | |
| === Limiting the log size ===
| |
| On the same tab, enable 'Limit size of logfile' and enter the desired value in Mebibyte (MiB). One MebiByte equals 1048576 Bytes.<br>
| |
| Please note that FileZilla makes one backup, so the amount you enter here is doubled!
| |
| | |
| If the log file reaches the size limit, FileZilla renames it to <filename>.1, and starts a new file. Any <filename>.1 file that exists prior to renaming will be deleted.
| |
| | |
| = See also =
| |
| | |
| [[Server logs|Logging in FileZilla Server]]
| |
