Manually Downloading and Deleting Log Files

Whenever possible, we recommend you use the FTP Log Push feature for downloading and deleting log files. See Using FTP Push to Automatically Download and Delete Log Files.

If you need to manage your log files manually, we recommend that you establish a regular schedule and ensure that all those responsible for downloading and deleting log files know the following things:

You will want to develop specific procedures for your situation. The following sections contain general ideas for accomplishing these tasks.


When to Download and Delete Log Files

The primary consideration is that log files must be downloaded and deleted before the logging disk space fills up.


Getting Log Filenames

Before you can download or delete a log file, you must know its exact name.

Appliance log filenames can be listed in the browser-based management tool in Monitoring > Cache Logs. They can also be listed from the command line, or through a Telnet session using the get command.

The appliance automatically generates log filenames as follows:

This naming convention accommodates up to 702 log files per day. If the rollover options are set so that all the possible filenames are used in one day, the log file with the ZZ letter identifier should not be closed manually until the start of the next day (unless the logging disk becomes full).

To list log files using FTP, you must know the path to the files. Use the following table to determine the paths to various log files.

File Location

All log files

LOG:ETC/PROXY/DATA/LOGS/

Transparent and forward proxy log files in common format

LOG:ETC/PROXY/DATA/LOGS/FORWARD/COMMON/

Transparent and forward proxy log files in extended format

LOG:ETC/PROXY/DATA/LOGS/FORWARD/EXTENDED/

Filter log files in appliance filtering common format

LOG:ETC/PROXY/DATA/LOGS/FILTER/COMMON/

Web server accelerator log files in common format

LOG:ETC/PROXY/DATA/LOGS/REVERSE/COMMON/name

The variable name is the name of the Web server accelerator.

Web server accelerator log files in extended format

LOG:ETC/PROXY/DATA/LOGS/REVERSE/EXTENDED/name

The variable name is the name of the Web server accelerator.

Dynamic Bypass log files in extended format

LOG:ETC/PROXY/DATA/LOGS/DBYPASS/EXTENDED/

Clustered service log files in common format

LOG:ETC/PROXY/DATA/LOGS/CLUSTER/COMMON/name

The variable name is the name of the clustered service.

IMPORTANT:  Clustered services often have multiple IP addresses assigned to them. Clustered services are distributed among cluster members by IP address. This means that the log files of a clustered service will probably be stored on multiple appliances if the service has more than one IP address assigned to it.

Clustered service log files in extended format

LOG:ETC/PROXY/DATA/LOGS/CLUSTER/EXTENDED/name

The variable name is the name of the clustered service.

IMPORTANT:  Clustered services often have multiple IP addresses assigned to them. Clustered services are distributed among cluster members by IP address. This means that the log files of a clustered service will probably be stored on multiple appliances if the service has more than one IP address assigned to it.


Using the Browser-Based Tool to Get Filenames

You can most easily view log filenames in the browser-based management tool. To do so, click Monitoring > click Cache Logs > select a log format > select a service.


Using FTP to Get Filenames

The Mini FTP Server in version 1.3 and later supports the CWD command for changing to the target log directories. All appliance versions let you use the LS command in connection with full paths to list log files.

For example, the following command lists transparent and forward proxy log files in common format:

ls log:etc/proxy/data/logs/forward/common/ 

For a complete list of log file directory paths, see Getting Log Filenames.


Using the Command Line or Telnet to Get Filenames

You can also see a list of log filenames from the command line. However, you cannot download files from the command line.

The following table presents some command line/Telnet examples.

If You Want To Then Enter

See a list of available forward/transparent log files in common format

get comlog forward

See a list of available Web server accelerator log files in common format

get comlog reverse:name

(The variable name is the name of the Web server accelerator.)

See a list of available filtering log files in appliance filtering common format

get comlog filter

See a list of available forward/transparent log files in extended format

get extlog forward

See a list of available Web server accelerator log files in extended format

get extlog reverse:name

(The variable name is the name of the Web server accelerator.)


Downloading Log Files


Using the Browser-Based Management Tool to Download Log Files

You can download the files in the browser-based management tool as you view them. After you click Download, when the browser asks what you want to do with the file, save it to your designated log file storage location.


Using FTP to Download Log Files

You can use FTP from the storage location to retrieve the files using the GET command. You must first obtain each filename using one of the options explained in Getting Log Filenames.

After you have the log filename, you can transfer it to your workstation. For example, to download a forward proxy common format log file, you would use the following command after starting an FTP session with the appliance:

get log:/etc/proxy/data/logs/forward/common/filename.log

The filename variable is the name of the log file you have previously obtained.

You can also use the MGET command, but be aware that this command also downloads active log files that are not complete.

The appliance doesn't currently support the FTP server PUT command.


Deleting Downloaded Log Files

After the log files have been downloaded and saved to another location, delete the files using one of the following options: