ruvnet/ruflo · error
Neither RuVector nor Ollama available. Provider may not work
Error message
Neither RuVector nor Ollama available. Provider may not work.
What it means
Warning in RuVectorProvider.doInitialize(): both the RuVector HTTP server health check and the Ollama fallback probe (/api/tags) failed, so the provider has no working backend and inference calls are expected to fail.
Source
Thrown at v3/@claude-flow/providers/src/ruvector-provider.ts:212
// Check if RuVector HTTP server is running
const health = await this.doHealthCheck();
if (health.healthy) {
this.logger.info('RuVector server connected');
return;
}
// Fallback: Check if Ollama is running for local model execution
try {
const ollamaHealth = await fetch(`${this.ollamaUrl}/api/tags`, {
signal: AbortSignal.timeout(3000),
});
if (ollamaHealth.ok) {
this.useOllamaFallback = true;
this.logger.info('Using Ollama as fallback for local model execution');
}
} catch {
this.logger.warn('Neither RuVector nor Ollama available. Provider may not work.');
}
}
protected async doComplete(request: LLMRequest): Promise<LLMResponse> {
// Use Ollama fallback if RuVector server isn't available
if (this.useOllamaFallback) {
return this.completeWithOllama(request);
}
const ruvectorRequest = this.buildRuvectorQuery(request);
const controller = new AbortController();
const timeout = setTimeout(() => controller.abort(), this.config.timeout || 120000);
try {
// Use ruvLLM's /query endpoint (not OpenAI-compatible)
const response = await fetch(`${this.baseUrl}/query`, {
method: 'POST',View on GitHub (pinned to fa13ee4ad6)
Solutions
- Install RuVector or start a local Ollama server so the provider has a working backend.
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at v3/@claude-flow/providers/src/ruvector-provider.ts:212 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18).
Data as JSON: /api/errors/541339b77bdfde1b.
Report an issue: GitHub.