WRN Failed to read system backends after successful install
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2k
- Forks
- 291
- Avg merge
- 30m
- Merged PRs (30d)
- 3
Description
Constant error in log " 9:39PM WRN Failed to read system backends, proceeding with user-managed backends error="open /usr/share/localai/backends: no such file or directory""
Getting this constantly and nothing works other than the main page. Tried various cpu, gpu compose all install correctly but then nothing works. And this error reads out constantly in the backend.
Tried reinstalling the backends. Still same error.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source file or test; start by reproducing the repeated backend log with the referenced CPU or GPU compose setup. Trace how installation selects /usr/share/localai/backends and compare that with the path used when the application reads system backends. Done means the installed backends load and the repeated missing-directory warning no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100