Manage an existing service

First identify how the backend was started. A terminal-launched process is not managed by systemd; restarting a service will not update that terminal process.

WSL systemd deployment

Run in WSL Bash:

systemctl status devsecops-ai ollama
systemctl cat devsecops-ai
journalctl -u devsecops-ai -n 50 --no-pager

Inspect the working directory, Python environment, import path, writable storage paths, and environment loading. Redact any credentials before sharing service output.

When a restart is intended:

sudo systemctl restart devsecops-ai

Then complete verification, including inference.

Terminal-launched lab

Stop the process with Ctrl+C in its terminal. Restart it using the command in installation from the same repository root. Recheck configured environment variables first.

Windows helper

The repository contains scripts/wsl-manage.ps1. Read its parameter help and target distribution before using it from Windows PowerShell. Service-control scripts affect an existing installation; they do not validate its configuration.

Next: Inspect logs or plan an update.