Error: memberlist not created

Support
1

Moved from a question on the Weaviate docs repo

From @BKShalini

Hi @DudaNogueira would you be able to take a look?

Description

Hello - Can someone please help here - we are still facing this issue with weaviate pods
{“action”:“config_load”,“config_file_path”:“/weaviate-config/conf.yaml”,“level”:“info”,“msg”:“Usage of the weaviate.conf.json file is deprecated and will be removed in the future. Please use environment variables.”,“time”:“2024-04-01T07:53:57Z”}
{“deprecation”:{“apiType”:“Configuration”,“id”:“config-files”,“locations”:[“–config-file=”“”],“mitigation”:“Configure Weaviate using environment variables.”,“msg”:“use of deprecated command line argument --config-file”,“sinceTime”:“2020-09-08T09:46:00.000Z”,“sinceVersion”:“0.22.16”,“status”:“deprecated”},“level”:“warning”,“msg”:“use of deprecated command line argument --config-file”,“time”:“2024-04-01T07:53:57Z”}
{“action”:“startup”,“default_vectorizer_module”:“none”,“level”:“info”,“msg”:“the default vectorizer modules is set to “none”, as a result all new schema classes without an explicit vectorizer setting, will use this vectorizer”,“time”:“2024-04-01T07:53:57Z”}
{“action”:“startup”,“auto_schema_enabled”:true,“level”:“info”,“msg”:“auto schema enabled setting is set to “true””,“time”:“2024-04-01T07:53:57Z”}
{“action”:“memberlist_init”,“bind_port”:7000,“error”:“Failed to get final advertise address: No private IP address found, and explicit IP not provided”,“hostname”:“”,“level”:“error”,“msg”:“memberlist not created”,“time”:“2024-04-01T07:53:57Z”}
{“action”:“startup”,“error”:“create member list: Failed to get final advertise address: No private IP address found, and explicit IP not provided”,“level”:“error”,“msg”:“could not init cluster state”,“time”:“2024-04-01T07:53:57Z”}

Please let me know if these versions would cause any issue.

Server Setup Information

We are using the versions of Openshift and Kubernetes as below
Client Version: 4.10.35
Server Version: 4.10.57
Kubernetes Version: v1.23.17+16bcd69

2

hi @BKShalini !

This can happen on this situation when the ips that are handed to you nodes are not in a valid range.

Can you check that on your cluster? I am assuming here you are using k8s.

Thanks!

3

Yes finally we got this issue resolved by doing these things

  1. The cluster nodes had to have IP ranges in the allowed ranges as per the Weaviate documentation.
  2. Once the IP ranges was updated, nodes were labelled with app=weaviate
  3. The nodeaffinity was added and then the weaviate application is working as expected.
    Thank you for your reply
4

Awesome!

Thanks for sharing the solution, @BKShalini !!

2 Likes