Stats Collector is responsible for keeping track of transfer status and statistics,
which can thus affect things such as notifications and reporting. When there are issues with the
Stats Collector database for Shares, such as tables not being updated, corrupted entries or other
database-specific errors, reset the database to get the system running again.
- Stop the Stats Collector.
# /opt/aspera/shares/sbin/sv stop stats-collector
- Back up the Shares database:
# /opt/aspera/shares/u/setup/bin/backup backup_dir
- Re-create the Stats Collector database.
# /opt/aspera/shares/u/stats-collector/bin/aspera-stats-collector-init.sh admin db-recreate --quiet
- Restart the Stats Collector database.
# /opt/aspera/shares/sbin/sv start stats-collector
- Regenerate the keys and wait for the public key to be added to the database:
# /opt/aspera/shares/u/stats-collector/bin/aspera-stats-collector-init.sh admin regenerate-keys
- Reset the iteration sequence number to 0 for re-polling all transfers and re-add
all nodes:
# /opt/aspera/shares/u/shares/bin/run mysql -e 'update shares.transfer_reporters set sequence_number = 0'
# /opt/aspera/shares/u/shares/bin/run rake aspera:stats_collector:add_all_nodes