Advanced Maintenance

You can perform basic maintenance and resolve issues using the Command Line Interface (CLI). This section provides a list of useful commands with brief descriptions to help you with maintenance tasks and basic troubleshooting.

Use these commands with caution and only with the complete understanding of what a specific command does, or consult with technical support. Progress Software does not take any responsibility for data loss or other damage due to the use of the listed commands.

Command	Description
sudo systemctl <start|stop|restart> ads-stream	Start, stop, or restart action for the ADS stream processing engine. It runs all the methods with the exception of the BPATTERN method. The restart could help if you see information in the UI that the processing database is not running. In a Distributed Architecture (DA) deployment this process is only runs on the slave units.
systemctl status ads-stream	Check the status of the ADS stream processing engine.
sudo systemctl <start|stop|restart> ads-bpattern-engine	Start, stop, or restart the BPATTERN detection engine. In a DA architecture this process only runs on the slave units.
systemctl status ads-bpattern-engine	Check the status of the BPATTERN detection engine.
sudo systemctl <start|stop|restart> ads-psql	Start, stop, or restart of the backend system creating events in the database. These are then presented in the UI. In a DA deployment this only runs on the Top Priority Master (TPM) unit.
systemctl status ads-psql	Check the status of the daemon responsible for event input to the database.
tail /data/components/ads-stream/log/ads-license.log	Check the processing log to see how many Flows Per Second (FPS) have been processed and check what the platform or license limit is.
tail /data/components/ads-psql/log/ads-output.log	In this log file you can find the number of events per minute. It is the number right after the # character at the end of each line.