Skip to content

Operations

The SmartAGT services are created during installation and start with the server. This page gathers their operating commands.

To replace packages with a new version, follow Update.

Prerequisites

Operating procedure

Service Role Display name on Windows
SmartAGT-Platform-Service API SmartAGT Platform Service
smartagt-rag-ingestor-worker Document extraction and chunking SmartAGT RAG-Ingestor Worker
smartagt-rag-embed-worker Vector computation SmartAGT RAG-Embed Worker
smartagt-scheduler-worker Scheduled tasks SmartAGT Scheduler Worker
SmartAGT-AI-Gateway-Service AI Gateway SmartAGT AI Gateway Service
smartagt-frontend-service Frontend SmartAGT Frontend Service
Action Command
Start sudo systemctl start <service>
Stop sudo systemctl stop <service>
Restart sudo systemctl restart <service>
Check status systemctl status <service>
Read the logs journalctl -u <service>
Disable automatic start sudo systemctl disable <service>
Restore automatic start sudo systemctl enable <service>

Several services can follow one another in a single command.

Action Command
Start Start-Service <service>
Stop Stop-Service <service>
Restart Restart-Service <service>
Check status Get-Service <service>
Read the logs folders C:\app\logs\backend and C:\app\logs\bff
Disable automatic start Set-Service <service> -StartupType Manual
Restore automatic start Set-Service <service> -StartupType Automatic

Several services can follow one another in a single command, separated by commas.

Restart a service after changing the YAML or its environment. The workers wait for the API to prepare the database before starting.

Every Backend node carries the services of the roles that deployment.nodes assigns to it, every Frontend node the Frontend service. Run the commands on the relevant node.

A change to the YAML or the environment is copied to every relevant node. For this configuration change, restart them one at a time: the other nodes keep serving in the meantime. The workers wait for the API to prepare the database before starting.

A version change follows the coordinated shutdown in Update.

Special cases

Reset the Backend

init --reset erases the smartagt and smartagt_vector databases and starts from a new installation: activation must be done again.

  1. Back up the databases, then stop the Backend services. The built-in storage refuses the reset while one of its processes is running.
  2. Run the command from the Initialize step again, with --reset.
  3. Start the Backend services, run the Frontend Initialize step again with --adopt-backend-key, then restart its service.

The previous built-in storage stays under <data_dir>/mediastore/seaweedfs.reset-<timestamp>. To go back, restore the databases and rename this folder to seaweedfs. Otherwise, delete it to free the disk. With S3: Configure S3.

Reset the Backend

init --reset erases the smartagt and smartagt_vector databases, empties the bucket of its SmartAGT objects and starts from a new installation: activation, deployment secret and Frontend node enrollment must be done again, as during installation.

Back up the databases and the bucket, then stop the Backend services on all nodes. On the first Platform node only, run the commands from the Initialize step again, init with --reset. Purge details: Configure S3.