How to redirect Aspera logging in Linux [syslog,rsyslog,syslog-ng]




You may wish to redirect your Aspera logging to a file confined to Aspera log information. Currently, all Aspera logging in Linux is done to /var/log/messages. You can redirect this to a different file (like /var/log/aspera.log) by making some changes in your logging configuration file.

In the case of RedHat/Centos 6.X syslog is rsyslog. Suse (SLES) systems use syslog-ng.



syslog and rsyslog

1.  Add a parameter to the /etc/rsyslog.conf file.

Note: This step applies only to implementations using rsyslog.


Add the parameter below. It must appear prior to $ModLoad imuxsock:

$PreserveFQDN on


2. Open /etc/syslog.conf or /etc/rsyslog.conf in a file editor depending on what your system uses.

Find the following line:

*.info;mail.none;authpriv.none;cron.none                /var/log/messages

Change it to the following:

*.info;mail.none;authpriv.none;cron.none;local2.none                /var/log/messages


Finally, add the following line to the file:              -/var/log/aspera.log


Note the hyphen before the log file name, which allows for asynchronous logging. Also, the log file name should be separated from the log facility ( by tabs, not spaces.


3. After making these three changes, you need to restart syslogd or rsyslogd:

# service syslog restart
# service rsyslog restart


Additional steps

1. You should also make sure that you are rotating /var/log/aspera.log. See the KB article on log rotation.

2. After finishing these steps for a system using rsyslog, you should disable rate-limiting of log messages which causes problems with Aspera products. See this KB article for more details.


Note: Steps 1 and 2 could be simplified using the step below if rsyslog (RH/CENTOS 7.X are OK ) supports it


1.  create a file: /etc/rsyslog.d/99-aspera.conf with the following content


local2.* -/var/log/aspera.log

& stop



2 . After you need to restart  rsyslogd:

# systemctl restart rsylog




1. Open /etc/syslog-ng/syslog-ng.conf in a text editor.

Locate the following lines:

filter f_local { facility(local0, local1, local2, local3, local4, local5, local6, local7); };

destination localmessages { file("/var/log/localmessages"); };
log { source(src); filter(f_local); destination(localmessages); };

Replace them with the following:

filter f_local { facility(local0, local1, local3, local4, local5, local6, local7); };
filter f_aspera { facility(local2); };

destination localmessages { file("/var/log/localmessages"); };
log { source(src); filter(f_local); destination(localmessages); };

destination asperalog { file("/var/log/aspera.log"); };
log { source(src); filter(f_aspera); destination(asperalog); };


2. Execute the following commands:

# rcsyslog restart

# logger -p aspera test

# cat /var/log/aspera.log


These last steps are to assure that logging has been correctly re-directed.

Something similar to the line below should be seen

Jun 13 10:30:33 linux-kua5 root: aspera test




Powered by Zendesk