The logs are meant for analysis by Aspera Technical Support, and are useful to provide whenever you would like assistance in troubleshooting a problem.
Naming and Rollover
On Windows, Aspera logs are rotated based on the log size. When the first log file (named fileName.0.log) reaches 10MB, it will begin logging to a new file with a *.1.log suffix. This process continues until *.9.log exceeds the 10MB limit, and then starts over. The log file of fileName.log (with no number added) is the current working log, and is identical to the latest-numbered log.
For the location of these logs, see https://support.asperasoft.com/entries/20901593-where-are-the-client-or-server-logs-located
Some users prefer to archive these logs for security or analysis purposes. To do this, you can send the logs to a zip file in a desired location.
Attached is a Powershell script that takes two input parameters:
- log directory
- archive directory
The script zips the log directory and places it in the archive directory, with the name aspera_logs_MM_DD_YY_at_HH_MM.zip (to capture the date and time when the logs were archived).
Run the Powershell file from the command line as follows:
Powershell.exe -ExecutionPolicy Bypass -file C:\path\to\script\aspera_archive_logs.ps1 "C:\path\to\logs" "C:\aspera-log-archive"
In the command sequence above, note the following:
- Replace C:\path\to\script with the path to the location of the script on your system.
- Replace C:\path\to\logs with the path to the logs that you want to archive (for example: C:\Program Files (x86)\Aspera\Enterprise Server\var\log). For information on the location of these logs on your system, see https://support.asperasoft.com/entries/20901593-where-are-the-client-or-server-logs-located.
- Replace C:\aspera-log-archive with the directory where you want to store the archive files.
Note: You must run this script as a user who has access to these folders.
Scheduling the Archive Task
You will likely want to set this script up as a scheduled task. Using the Windows Task Scheduler, you can set up this script to run as frequently as you want. However, the interval you choose should be relative to how quickly your logs grow. If your logs from .1.log to .9.log are filling up weekly, you may wish to run this script once a week or more.
When scheduling the task using Windows Task Scheduler, be sure to use the following configuration:
Add arguments (optional): -ExecutionPolicy Bypass -file .\aspera_archive_logs.ps1 [path to logs dir] [path to zip file]
(For example: -ExecutionPolicy Bypass -file .\aspera_archive_logs.ps1 "C:\Program Files (x86)\Aspera\Enterprise Server\var\log" "C:\archive_logs")
Note: Trailing "\" on paths is not permitted.
Start in (optional): The path to the script
(For example: C:\my_scripts)