weaviate/weaviate · error
init concepts
Error message
init concepts
What it means
Wraps a failure of initConcepts during Init, which loads the persisted concepts/extensions into the module — this surfaces the LoadAll (load all concepts) failure path. Any error reading or concatenating the stored concepts fails module startup with this message.
Source
Thrown at modules/text2vec-contextionary/module.go:120
url := appState.ServerConfig.Config.Contextionary.URL
remote, err := client.NewClient(url, m.logger)
if err != nil {
return errors.Wrap(err, "init remote client")
}
m.remote = remote
if err := m.remote.WaitForStartupAndValidateVersion(ctx,
MinimumRequiredRemoteVersion, 1*time.Second); err != nil {
return errors.Wrap(err, "validate remote inference api")
}
if err := m.initExtensions(); err != nil {
return errors.Wrap(err, "init extensions")
}
if err := m.initConcepts(); err != nil {
return errors.Wrap(err, "init concepts")
}
if err := m.initVectorizer(); err != nil {
return errors.Wrap(err, "init vectorizer")
}
if err := m.initGraphqlAdditionalPropertiesProvider(); err != nil {
return errors.Wrap(err, "init graphql additional properties provider")
}
if err := m.initClassifiers(); err != nil {
return errors.Wrap(err, "init classifiers")
}
return nil
}
func (m *ContextionaryModule) InitExtension(modules []modulecapabilities.Module) error {View on GitHub (pinned to 75aa4b6d11)
Solutions
- Inspect the wrapped cause (likely 'load all concepts' → Scan/read error)
- Verify the extensions store files in the data directory are intact and readable
- Restore the extensions store from backup or clear it and re-add extensions
- Check disk health and available space
Defensive patterns
Strategy: fallback
Validate before calling
// Check extensions store files exist and are readable before startup ls -l "$PERSISTENCE_DATA_PATH" && test -r "$PERSISTENCE_DATA_PATH" || echo "store unreadable"
Try / catch
if err := m.initConcepts(); err != nil {
logger.Warnf("init concepts failed: %v", err)
// optionally continue with no extensions or restore from backup
} Prevention
- Shut down Weaviate cleanly to avoid truncated stores
- Back up extensions before upgrades
- Monitor disk-full events which can corrupt records
When it happens
Trigger: Init when the extensions storage Scan/LoadAll fails (corrupted store, unreadable bucket, I/O error while reading all concept records).
Common situations: Corrupted or truncated extensions files after an unclean shutdown or disk-full condition; data directory permission issues; manually modified extension store contents.
Related errors
AI-assisted analysis of weaviate/weaviate@75aa4b6d11 (2026-09-04).
Data as JSON: /api/errors/3f2fcf7689cba5e9.
Report an issue: GitHub.