Huge Log Files

Applications Manager | July 25, 2006 | 1 min read

[ <b>Currently:</b> Reading ]<br />Many times we get customers who find it difficult to send us the Support Information File (log files) as they are very huge. Also when running in production for a long time, the log files tend to grow very big.

Here is a small suggestion on how to handle this situation.

When nothing goes wrong a whole week, you can safely move the logs directory to say logs_0 folder after shutting down Applications Manager. A fresh set of log files get created and you can as well delete the logs_0 folder in the next clean up. You can also decrease the log level to ‘Print Fatal Errors‘ only option via the web client so that the amount of logging gets reduced. This has the added benefit of improving performance.

During evaluation, it is normally best to get the full log file. This is because it helps to identify if any previous action you have done, resulted in an erroneous behavior. Alternatively if there is an issue you can consistently reproduce, you can also rename (or delete) the logs and restart AM and execute the exact steps, reproduce the error and then create the support information file and mail our support team.

Please note we do have an alternate FTP location where you can upload a huge file if there is a need.

This site uses Akismet to reduce spam. Learn how your comment data is processed.