9e8f1bbeed
Dashboard / frontend (push) Failing after 0s
Dashboard / api (push) Failing after 0s
Lint PowerShell / powershell-lint (ubuntu-latest) (push) Failing after 1s
Python Lint / Lint Python with Ruff (push) Failing after 1s
ShellCheck / Lint shell scripts (push) Failing after 1s
Matrix Smoke / linux-smoke (push) Failing after 1s
Matrix Smoke / distro: cachyos (push) Failing after 15s
Matrix Smoke / distro: linux-mint-21.3 (push) Failing after 15s
Matrix Smoke / distro: debian-12 (push) Failing after 5m21s
Matrix Smoke / distro: fedora-41 (push) Failing after 4m56s
Matrix Smoke / distro: ubuntu-24.04 (push) Failing after 2m13s
Matrix Smoke / distro: rocky-9 (push) Failing after 10m39s
Matrix Smoke / distro: manjaro (push) Failing after 12m11s
Matrix Smoke / distro: opensuse-tw (push) Failing after 11m53s
Matrix Smoke / distro: archlinux (push) Failing after 20m3s
Matrix Smoke / distro: ubuntu-22.04 (push) Failing after 13m49s
Validate .env Schema / tier-1-env-validation (push) Successful in 52s
Validate .env Schema / tier-2-env-validation (push) Successful in 44s
Validate .env Schema / tier-3-env-validation (push) Successful in 52s
Validate .env Schema / tier-4-env-validation (push) Successful in 51s
Validate Extensions Catalog / Check catalog is up-to-date (push) Failing after 9m47s
Secret Scan / Scan for secrets (push) Failing after 21m4s
Validate Docker Compose / Validate Docker Compose files (push) Has been cancelled
Python Type Check / Type check with mypy (push) Has been cancelled
Validate .env Schema / tier-0-env-validation (push) Has been cancelled
Test Linux / integration-smoke (push) Has been cancelled
Lint PowerShell / powershell-lint (windows-latest) (push) Has been cancelled
Matrix Smoke / macos-smoke (push) Has been cancelled
57 lines
1.4 KiB
Markdown
57 lines
1.4 KiB
Markdown
# ODS — Post-Install Checklist
|
|
|
|
Run these checks after installation to confirm everything is working.
|
|
|
|
---
|
|
|
|
## 1. Overall health
|
|
|
|
```bash
|
|
ods status
|
|
```
|
|
|
|
Shows container status, service health checks, and GPU metrics in one view. All enabled services should report **healthy**. If any show as not responding, check the logs (step 6 below).
|
|
|
|
## 2. LLM response test
|
|
|
|
```bash
|
|
ods chat "Hello, are you working?"
|
|
```
|
|
|
|
You should receive a text response within a few seconds. If you see an error, check `ods logs llm`.
|
|
|
|
## 3. Web interface
|
|
|
|
Open your browser and navigate to the address shown at the end of installation (default: `http://localhost:3000`). The Open WebUI chat interface should load and let you send a message.
|
|
|
|
## 4. GPU verification
|
|
|
|
**NVIDIA** — GPU utilisation, VRAM, and temperature appear automatically in `ods status`.
|
|
|
|
**AMD:**
|
|
```bash
|
|
rocm-smi
|
|
```
|
|
|
|
**Apple Silicon** — GPU is used automatically; no separate check needed.
|
|
|
|
## 5. Check enabled services
|
|
|
|
```bash
|
|
ods list
|
|
```
|
|
|
|
Core services (llama-server, open-webui, dashboard) should be shown as running. Optional services selected during install should also appear.
|
|
|
|
## 6. Diagnose a failing service
|
|
|
|
```bash
|
|
ods logs <service> # e.g. ods logs llm
|
|
```
|
|
|
|
Replace `<service>` with the name from `ods list`. Common aliases: `llm` for llama-server, `stt` for Whisper, `tts` for Kokoro.
|
|
|
|
---
|
|
|
|
If a service fails its health check after reviewing logs, see [TROUBLESHOOTING.md](TROUBLESHOOTING.md).
|