how_to:obtaining_error_logs
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revisionLast revisionBoth sides next revision | ||
| how_to:obtaining_error_logs [2009/05/18 16:45] – created mike | how_to:obtaining_error_logs [2009/05/19 16:25] – mike | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| =====How Logging Works===== | =====How Logging Works===== | ||
| - | Under its default settings VPOP3 logs a minimal amount of information about what it is doing to various files in the main VPOP3 directory. When investigating a support issue it is often the case that we will need you to switch on logging to extra files or increase the level of detail being written to the main log. This can generate a lot of data; up to several MB per second. In order to prevent disks getting filled up with logged data VPOP3 limits the maximum size of these log files. By default this size is set to 1MB but can be increased in '' | + | Under its default settings VPOP3 logs a minimal amount of information about what it is doing to various files in the main VPOP3 directory. When investigating a support issue it is often the case that we will need you to switch on logging to extra files or increase the level of detail being written to the main log. This can generate a lot of data; up to several MB per second. In order to prevent disks getting filled up with logged data VPOP3 limits the maximum size of these log files. By default this size is set to 1MB but can be increased in '' |
| + | |||
| + | =====Where the Log Files Are===== | ||
| + | The log files will be found in the directory specified under '' | ||
| =====The Right Files===== | =====The Right Files===== | ||
| Line 24: | Line 27: | ||
| Most of the time it's easy enough to catch the right data in the log files but on a busy server there can be so much data being written to the logs that you need to be pretty quick to grab the data from the logs before they are overwritten. Here's the general approach that works well in all cases: | Most of the time it's easy enough to catch the right data in the log files but on a busy server there can be so much data being written to the logs that you need to be pretty quick to grab the data from the logs before they are overwritten. Here's the general approach that works well in all cases: | ||
| - | - Switch on any of the session logs (e.g. '' | + | - Switch on any of the session logs (e.g. '' |
| - Set the maximum size of these files to an appropriate value (10MB is good for a busy VPOP3 installation) on the '' | - Set the maximum size of these files to an appropriate value (10MB is good for a busy VPOP3 installation) on the '' | ||
| - Set '' | - Set '' | ||
| - | - Set the maximum size of the main VPOP3 log file to an appropriate value (10MB is good for a busy VPOP3 installation) using '' | + | - Set the maximum size of the main VPOP3 log file to an appropriate value (10MB is good for a busy VPOP3 installation) using '' |
| - Perform the actions necessary to trigger the problem you're trying to solve. | - Perform the actions necessary to trigger the problem you're trying to solve. | ||
| - Immediately the problem occurs copy the relevant log files to a temporary directory to avoid the data being overwritten by subsequent data. | - Immediately the problem occurs copy the relevant log files to a temporary directory to avoid the data being overwritten by subsequent data. | ||
how_to/obtaining_error_logs.txt · Last modified: 2018/11/14 10:45 by 127.0.0.1
Page Tools
