The document outlines how to control the location of the Access logs for the TIM httpd server and can these be cleaned up if they are occupying too much space.
We installed the TIM service in one of our production Linux servers. There are currently around 1.6G in Access log files in /var/log/httpd.
PROD[[email protected] httpd]$ ls -alh /var/log/httpd/
total 1.6G
drwx------ 2 root root 4.0K Feb 10 03:15 .
drwxr-xr-x. 20 root root 4.0K Feb 14 14:35 ..
-rw-r--r-- 1 root root 137M Feb 14 14:35 access_log
-rw-r--r-- 1 root root 233M Feb 10 03:15 access_log.1
-rw-r--r-- 1 root root 493M Feb 3 03:17 access_log.2
-rw-r--r-- 1 root root 421M Jan 27 03:44 access_log.3
-rw-r--r-- 1 root root 293M Jan 20 03:34 access_log.4
-rw-r--r-- 1 root root 907 Feb 13 02:50 error_log
-rw-r--r-- 1 root root 1.2K Feb 10 03:15 error_log.1
-rw-r--r-- 1 root root 2.5K Feb 3 03:18 error_log.2
-rw-r--r-- 1 root root 817 Jan 27 03:44 error_log.3
-rw-r--r-- 1 root root 817 Jan 20 03:34 error_log.4
What are the steps to clean up these log files and to configure the log files to redirect to another directory.
APM 10.x TIM on Linux
The location that the TIM httpd server writes it's log files is controlled by the CustomLog parameter in the TIM_HOME/httpd/conf/httpd.conf file.
| Description: | Sets filename and format of log file |
|---|---|
| Syntax: | CustomLog file|pipe format|nickname [env=[!]environment-variable] |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_log_config |
CustomLog directive is used to log requests to the server. A log format is specified, and the logging can optionally be made conditional on request characteristics using environment variables.