llama-farm /llamafarm:status - Service Health Check
Check the health and status of all LlamaFarm components.
Usage
/llamafarm:status # Full status report
/llamafarm:status --json # JSON output for scripting
/llamafarm:status --component rag # Check specific component
What This Command Does
- Checks each component - Server, RAG worker, databases, runtimes
- Reports health - Healthy, degraded, or failed
- Shows configuration - Active project, models, databases
- Identifies issues - Common problems and fixes
Implementation
When the user runs /llamafarm:status, follow these steps:
Step 1: Check CLI and Services
# Check if services are running
lf services status
Step 2: Check Health Endpoint
curl -s http://localhost:14345/health | jq .
Expected healthy response:
{
"status": "healthy",
"components": {
"server": "healthy",
"celery": "healthy",
"database": "healthy"
},
"version": "0.x.x"
}
Step 3: Check Project Configuration
# Current project info
lf projects list
# Model availability
lf models list
Step 4: Check RAG Health
lf rag health
Step 5: Present Comprehensive Status
LlamaFarm Status Report
=======================
Overall: HEALTHY
Services:
Server: Running (http://localhost:14345)
RAG Worker: Running (Celery)
MCP Server: Available (http://localhost:14345/mcp)
Current Project: my-project (namespace: default)
Models Available:
- default (universal/unsloth/Qwen3-4B-GGUF:Q4_K_M) [DEFAULT]
- fast (universal/unsloth/Qwen3-1.7B-GGUF:Q4_K_M)
Databases:
- main_db (ChromaStore): 1,234 documents indexed
Recent Activity:
- Last chat: 5 minutes ago
- Last ingestion: 2 hours ago
Health Checks:
[OK] Server responding
[OK] Celery worker connected
[OK] Vector database accessible
[OK] Model endpoint reachable
Component Details
Server Health
| Status | Meaning |
|---|---|
healthy |
Server responding, all endpoints available |
degraded |
Server running but some features unavailable |
failed |
Server not responding |
RAG Worker Health
| Status | Meaning |
|---|---|
healthy |
Celery worker connected and processing |
degraded |
Worker running but queue backed up |
failed |
Worker not connected |
Database Health
| Status | Meaning |
|---|---|
healthy |
Vector store accessible, queries working |
degraded |
Store accessible but slow |
failed |
Cannot connect to vector store |
Troubleshooting Output
When issues are detected:
LlamaFarm Status Report
=======================
Overall: DEGRADED
Issues Detected:
1. RAG Worker Not Connected
- Celery worker is not running
- Fix: lf services start --worker
2. Model Endpoint Unreachable
- Universal Runtime not responding at 127.0.0.1:11540
- Fix: Start Universal Runtime on port 11540
Recommendations:
- Run /llamafarm:logs to see error details
- Check debugging/service-issues skill for more help
JSON Output
For scripting and automation:
lf services status --json
{
"overall": "healthy",
"services": {
"server": {"status": "healthy", "url": "http://localhost:14345"},
"worker": {"status": "healthy", "queue_length": 0},
"mcp": {"status": "healthy", "url": "http://localhost:14345/mcp"}
},
"project": {
"name": "my-project",
"namespace": "default"
},
"models": [
{"name": "default", "provider": "universal", "model": "unsloth/Qwen3-4B-GGUF:Q4_K_M"}
],
"databases": [
{"name": "main_db", "type": "ChromaStore", "document_count": 1234}
]
}
Related Commands
/llamafarm:start- Start services/llamafarm:stop- Stop services/llamafarm:logs- View service logs