[database] ;=================================================================
; This stanza provides access details for the (optional) SQL database, as
; well as control of how data is retained.
; Whether or not to enable use of a database for read/write
; Valid values include Yes/True/1 / No/False/0
; If left blank will default to false
enabled=true
; Which database driver should be used. At this time only "mysql" is accepted.
; If left blank will default to "mysql"
; Valid values include mysql
driver=mysql
; Name of the host which contains the database. This can be localhost, the
; ip of a host, or the fully qualified domain name of a host.
; If left blank will default to "localhost"
hostname=localhost
; Name of the database which will contain the the SecAst tables.
; If left blank will default to "secast"
; default: secast
databasename=secastdb1
; Username for database access
; default: secastun
username="secast"
; Password for database access
; default: secastpw
password="xxxxxxxx"
; Database can hold records from multiple SecAst hosts (in the event of a
; cluster). Upon purging old records, should SecAst delete all records of
; the specified type, or only those which originated from this hostname.
; Valid values: Yes/True/1 / No/False/0
; Default value: false
purgeonlyown=false

It looks like your MySQL server database is closing the connection - causing SecAst to constantly reopen the connection. Normally a support rep would connect to your system by SSH to look for a MySQL related issue, or to capture more detail about the cause of the database closure. As you are running the free edition we can't assist much further, but I've opened a ticket to see if we can reproduce this in our lab prior to our next release. Could you post your Linux distro, version, and architecture? (So I can add to the ticket)