This is a reference of the log locations for Enterprise Server, Connect Server, Point to Point, and Aspera Client. The log location differs by operating system and whether the install was done for All Users on the machine or a Single User.
When sending logs to Aspera it is best to zip or tar up the entire log directory. For more information on how to send your logs to Aspera, see this article (How to send your log files to Aspera).
GUI on all platforms
If you use the graphical user interface for your product, you can access your logs easily from here.
Go to Tools > Open Logs folder on your product's main toolbar to open the folder that contains all the log files.
Replace user with the logged in username, and product_name with the name of your product, such as Enterprise Server.
Any Windows (All Users)
C:\Program Files [(x86)]\Aspera\product_name\var\log
Windows Vista, 7, 2008 Server (Single User)
Windows XP, 2003 Server (Single User, or non-admin install)
C:\Documents and Settings\user\Application Data\Aspera\product_name\var\log
For root user:
For all other users, where user is the name of the account:
Most Aspera processes use the rsyslog facility
local2. It goes by default to:
If segregated it may be found in:
If you are using an On Demand transfer server, the log files are at the following locations:
/opt/aspera/var/log contains directories for
trapd, both of which contain logs that should be sent to Support engineers. For more information on
trapd, see this Knowledge Base article: How To Debug Trap.
The Aspera processes use the rsyslog facility
To redirect aspera logs to a file, configure syslog accordingly:
echo 'local2.debug /var/log/aspera.log' >> /etc/syslog.conf touch /var/log/aspera.log refresh -s syslogd
Syslogd also supports log rotation and compression.
msg_src_list destination [rotate [size sizek|m] [files files] [time timeh|d|w|m|y] [compress] [archive archive]]
For example, to enable log rotation by 50MB on 10 files, add the record below to
local2.debug /var/log/aspera.log rotate size 50m files 10
Then, refresh the configuration:
# refresh -s syslogd
To remove Aspera logs from other rules, add
level2.none to the related record.