weaviate/weaviate · critical

init near imu

Error message

init near imu

What it means

multi2vec-bind module startup: initNearIMU() failed (registering/validating the nearIMU near-search argument) and is wrapped with 'init near imu'. One of the per-modality init steps in Init(); the wrapped error carries the concrete cause.

Source

Thrown at modules/multi2vec-bind/module.go:107

	m.logger = params.GetLogger()
	if err := m.initVectorizer(ctx, params.GetConfig().ModuleHttpClientTimeout, params.GetLogger()); err != nil {
		return errors.Wrap(err, "init vectorizer")
	}

	if err := m.initNearImage(); err != nil {
		return errors.Wrap(err, "init near image")
	}

	if err := m.initNearAudio(); err != nil {
		return errors.Wrap(err, "init near audio")
	}

	if err := m.initNearVideo(); err != nil {
		return errors.Wrap(err, "init near video")
	}

	if err := m.initNearIMU(); err != nil {
		return errors.Wrap(err, "init near imu")
	}

	if err := m.initNearThermal(); err != nil {
		return errors.Wrap(err, "init near thermal")
	}

	if err := m.initNearDepth(); err != nil {
		return errors.Wrap(err, "init near depth")
	}

	return nil
}

func (m *BindModule) InitExtension(modules []modulecapabilities.Module) error {
	for _, module := range modules {
		if module.Name() == m.Name() {
			continue
		}

View on GitHub (pinned to 75aa4b6d11)

Solutions

1. Inspect the wrapped inner error in the startup log.
2. Resolve any earlier init failures in the chain first.
3. Verify module and core versions match; rebuild from a clean checkout.
4. Report with the full wrapped error chain if it persists.

// No pre-call validation exists for startup-time GraphQL init; guard at deploy time:
wget -qO- http://localhost:8080/v1/meta | grep multi2vec-bind

Startup-time error; cannot be caught at runtime. Inspect the wrapped inner error on the log line above and fix earlier init failures first.

When it happens

Trigger: Weaviate startup with multi2vec-bind enabled when construction of the nearIMU GraphQL argument returns an error — practically only via the shared GraphQL argument builder, usually cascading from an earlier init failure.

Common situations: Broken or version-mismatched module build; cascade after 'init vectorizer' failure; seen during bad upgrades or custom builds with stale dependencies.

Related errors

• init near image
• init near audio
• init near video
• init near thermal
• init near depth

AI-assisted analysis of weaviate/weaviate@75aa4b6d11 (2026-09-04). Data as JSON: /api/errors/36a8593ef9edc57c. Report an issue: GitHub.