Run Flow as a Linux Service

Flow can be set up as a systemd service on Linux that runs in the background, persists across reboots and user logouts, automatically restarts on crashes, and can use integrated logging via journalctl.

Note: This procedure is compatible with systemd-based Linux distributions. You may need to adapt it for your specific environment.

Follow these steps to configure Flow to run as a service:

  1. Create the systemd unit file.

    sudo vi /etc/systemd/system/<your-service-name>.service

    Replace <your-service-name> with a name of your choice, such as flow-ingest or flow-xl-ingest.

  2. Add the following content into the file, and update the User, WorkingDirectory, and ExecStart fields to match your environment.

    [Unit]
    Description=SingleStore Flow Ingest
    After=network.target
    
    [Service]
    Type=simple
    User=<your-username>                             # e.g., /home/ec2-user           
    WorkingDirectory=<path-to-your-working-directory # e.g., /home/ec2-user/ingest
    # Adjust JVM options if you need memory limits, GC tuning, etc.
    ExecStart=/usr/bin/java -jar <path-to-your-jar>  # e.g. /home/ec2-user/ingest/ingest.jar 
    #SuccessExitStatus=143     # so Ctrl-C / SIGTERM is treated as clean
    Restart=always
    RestartSec=10
    LimitNOFILE=65536          # bump open-file limit if ingest opens many files
    
    [Install]
    WantedBy=multi-user.target
  3. Enable and start the service.

    sudo systemctl daemon-reload
    sudo systemctl enable --now <your-service-name>
  4. Check service status and logs.

    sudo systemctl status <your-service-name>     # health-check
    sudo journalctl -u <your-service-name> -f     # live logs (Ctrl-C to quit)

Last modified: September 17, 2025

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK