Error and warning messages

Arrived from a link in a message? Its entry is one click below. Have only the message text? Search this section for a phrase from it, or open the group it belongs to. Every entry shows the message as it prints, what caused it, and how to fix it.

1. 1

   Weaviate logs it

   A log entry with a documented cause carries a docs_url field. Weaviate logs JSON by default; with LOG_FORMAT=text the same field prints as docs_url="…".

   "docs_url": "https://docs.weaviate.io/e/core-mem001"
2. 2

   Your client gets it too

   The error returned for the same failure ends in the link, on REST, gRPC and GraphQL, so it reaches the person who made the request and not only the operator reading the logs.

   cannot init shard: not enough memory mappings (see https://docs.weaviate.io/e/core-mem001)
3. 3

   The id lands on the fix

   Follow the link, or search this section for a phrase from the message. Each entry shows the message as it prints, what caused it, and how to fix it.

   /e/core-mem001 → /errors/cluster-resources#not-enough-memory-mappings

Message groups

Cluster resources

Shards that will not load, and other messages that mean the node has run out of memory, memory mappings, or disk.

Collection configuration

Deprecated ways of describing vectors, vector indexes, and multi-vector embeddings when you create or update a collection.

Model integrations

Renamed and retired embedding, multimodal, and generative model integrations.

Reading a message id

core-mem001OriginCategoryNumbercore is Weaviate Database. A client short name such as py means the message was raised before the request left your application.The topic: mem for memory, dep for a deprecation, auth for authentication.Unique within its origin and category.

Ids are permanent. The message text and the page it points to can both change, but an id that shipped in a release keeps meaning the same thing forever, so it is safe to search for, to alert on, and to quote in a support ticket.

Bare legacy ids

Released Python clients print the id without the origin, so what you see today is Dep024, not py-dep024. Both forms lead to the same entry, and bare ids are never reassigned.

Missing an entry?

This section is being filled in message by message. An id whose entry is not written yet lands you on this page rather than on a dead link. Every id printed by a released version has an entry planned. Until it exists, quote the id in a support request; it names the message exactly.

Rolling out

The docs_url field and the link suffix ship with Weaviate Database v1.40. The Python client prints a bare id such as Dep024 today, and the other clients none yet. The messages themselves are not new: the entries describe what current releases already print.

Questions and feedback

Have a question or feedback? Here's how to reach us.

Community Forum

Ask questions and connect with other developers on our Community forum.

Support

Weaviate Cloud user or customer? Find the right channel on the Support page.