Configuring the Database Logger

Update the settings in the Aspera configuration to establish connections with the MySQL database.

To configure Database Logger in a Terminal, open aspera.conf with a text editor (/opt/aspera/etc/aspera.conf). Locate or create the section <database>...</database>:

<CONF version="2">
   ...
   <database>
      <server>            <!-- Host IP -->
        127.0.0.1
      </server>
      <port>              <!-- Port -->
        4406
      </port>
      <user>              <!-- User -->
        logger
      </user>
      <password>          <!-- Password -->
        logger-password
      </password>
      <database_name>     <!-- Database Name -->
        aspera_console
      </database_name>
      <threads>           <!-- Threads -->
        10
      </threads>
      <exit_on_database_error>     <!-- Stop Transfers on Database Error -->
        false
      </exit_on_database_error>
      <session_progress>           <!-- Show Session Progress -->
        true
      </session_progress>
      <session_progress_interval>  <!-- Session Progress Interval -->
        1
      </session_progress_interval>
      <file_events>                <!-- Show File Events -->
        true
      </file_events>
      <file_progress>              <!-- Show File Progress -->
        true
      </file_progress>
      <files_progress_interval>    <!-- File Progress Interval -->
        1
      </files_progress_interval>
      <files_per_session>          <!-- File Per Session -->
        0
      </files_per_session>
      <ignore_empty_files>         <!-- Ignore Empty Files -->
        false
      </ignore_empty_files>
      <ignore_no_transfer_files>   <!-- Ignore No-transfer Files -->
        false
      </ignore_no_transfer_files>
      <rate_events>                <!-- Show Rate Events -->
        true
      </rate_events>
      <file_errors>                <!-- Log File Errors -->
        false
      </file_errors>
   </database>
   ...
</CONF>

Note:

You can find a Database Logger configuration example in this file:

/opt/aspera/etc/samples/aspera-everything.conf

If you have modified these settings in command line, execute these commands to restart Aspera Central and HTTP Fallback Server:

$ /etc/init.d/asperacentral restart
$ /etc/init.d/asperahttpd restart

Here is a list of all the Database Logger configuration options:

#	Field	Description	Values	Default
1	Host IP	The MySQL server's IP address.	valid IPv4 address	127.0.0.1
2	Port	The MySQL server's port number.	integer between 1 and 65535	4406
3	User	User login for the database server.	text string	blank
4	Password	The database user account's password.	text string	blank
5	Database Name	Name of the database used to store Aspera transfer data.	text string	blank
6	Threads	The number of parallel connections used for database logging. A higher value may be useful when a large number of files are being transferred within a given timeframe.	integer between 1 and 40	10
7	Stop Transfers on Database Error	Quits all ongoing transfers and no new transfers are permitted when a database error prevents data from being written to the database. Set this to true if all transfers must be logged by your organization.	true false	false
8	Show Session Progress	Setting this value to true will log transfer status such as number of files transferred, and bytes transferred, at a given interval.	true false	true
9	Session Progress Interval	The frequency at which an Aspera node logs transfer session information, in seconds. up to 65535 seconds.	integer between 1 and 65535	1
10	Show File Events	Setting this value to true enables the logging of complete file paths and file names. Performance may be improved when transferring datasets containing thousands of files. Also see File Per Session for setting a threshold for the number of files to log per session.	true false	true
11	Show File Progress	Setting this value to true will log file status such as bytes transferred, at a given interval.	true false	true
12	File Progress Interval	The frequency at which an Aspera node logs file transfer information, in seconds.	integer between 1 and 65535	1
13	Files Per Session	The value set will be the cut-off point for file names logged in a given session. For instance, if the value is set to 50, the first 50 file names will be recorded for any session. The session will still record the number of files transferred along with the number of files completed, failed or skipped. The default setting of 0 logs all file names for a given session.	positive integer or zero (all file names)	0
14	Ignore Empty Files	Setting this to true will block the logging of zero-byte files.	true false	false
15	Ignore No-transfer Files	Setting this to true will block the logging of files that have not been transferred because they exist at the destination at the time the transfer started.	true false	false
16	Show Rate Events	Setting this to true will log changes made to the Target Rate, Minimum Rate, and Transfer Policy by any user or Aspera node administrator during a transfer.	true false	true
17	Node Registration	Setting this to true will cause the database logger to register the node automatically on startup.	true false	true
18	File Error	This option logs files with errors. It overrides the Files Per Session setting, for example, if Files Per Session is set to 10, but there are 20 files with errors, all 20 files will be logged.	true false	false

If you have modified these settings in command line, restart the Aspera Central and the HTTP Fallback Server:

$ /etc/init.d/asperacentral restart
$ /etc/init.d/asperahttpd restart