# Unable to restart my weaviate container **URL:** \ **Category:** Support\ **Created:** [May 14, 2024, 3:15am UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305 "2024-05-14T03:15:53Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![maddios](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/maddios/32/1491_2.png) [@maddios](https://forum.weaviate.io/u/maddios)\ **Post date:** [May 14, 2024, 3:15am UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/1 "2024-05-14T03:15:53Z")
### Description I’m running weaviate 1.25.0 as a container in AWS ECS. I’m persisting storage via EFS. I’m able to start up weaviate, create my schema and load in a bunch of data. And run some test queries to make sure it’s all working well. Then I run the following test: I redeploy the container by scaling it down to 0 then back up to 1. This forces ECS docker to basically kill my old container and start a new one. At this point weaviate fails to start up correctly. /v1/schema throws an error: {“error”:[{“message”:“could not read schema with strong consistency: failed to execute query: leader not found”}]} In the log I’m seeing the following: {“action”:“bootstrap”,“error”:“could not join a cluster from [172.17.0.22:8300]”,“level”:“warning”,“msg”:“failed to join cluster, will notify next if voter”,“servers”:[“172.17.0.22:8300”],“time”:“2024-05-14T03:07:18Z”,“voter”:true} {“action”:“bootstrap”,“level”:“info”,“msg”:“notified peers this node is ready to join as voter”,“servers”:[“172.17.0.22:8300”],“time”:“2024-05-14T03:07:18Z”} Following env vars are set at the moment. ``` "name": "AUTHENTICATION_APIKEY_ENABLED", "value": "true" "name": "CLUSTER_HOSTNAME ", "value": "weaviate-dev" "name": "AUTHENTICATION_APIKEY_ALLOWED_KEYS", "value": "ae...fd" "name": "AUTHENTICATION_APIKEY_USERS", "value": "a...r" "name": "PERSISTENCE_DATA_PATH", "value": "/var/lib/weaviate" "name": "ENABLE_CUDA", "value": "0" ``` I clearly have something setup wrong so any advice at all is welcome as I’m trying to setup the dev env with just a single host and it’s telling me it wants to join a non-existant cluster. ### Server Setup Information - Weaviate Server Version: 1.25.0 - Deployment Method: docker (aws ecs) - Multi Node? Number of Running Nodes: single node - Client Language and Version: just using graphql for testing ### Any additional Information Here’s the output from the weaviate container: 2024-05-14T03:09:00Z INF action=startup default\_vectorizer\_module=none 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 2024-05-14T03:09:00Z INF action=startup auto\_schema\_enabled=true msg=auto schema enabled setting is set to “true” 2024-05-14T03:09:00Z INF msg=No resource limits set, weaviate will use all available memory and CPU. To limit resources, set LIMIT\_RESOURCES=true 2024-05-14T03:09:00Z INF msg=open cluster service servers={“2983fa3610b4”:8300} 2024-05-14T03:09:00Z INF address=172.17.0.22:8301 msg=starting cloud rpc server … 2024-05-14T03:09:00Z INF msg=starting raft sub-system … 2024-05-14T03:09:00Z INF address=172.17.0.22:8300 msg=tcp transport tcpMaxPool=3 tcpTimeout=10000000000 2024-05-14T03:09:00Z INF metadata\_only\_voters=false msg=construct a new raft node name=2983fa3610b4 2024-05-14T03:09:00Z INF action=raft index=1 msg=raft initial configuration servers=[[{Suffrage:Voter ID:04aa32840caa Address:172.17.0.22:8300}]] 2024-05-14T03:09:00Z INF last\_log\_applied\_index=3 last\_snapshot\_index=0 msg=raft node raft\_applied\_index=0 raft\_last\_index=3 2024-05-14T03:09:00Z INF action=raft follower={} leader-address= leader-id= msg=raft entering follower state 2024-05-14T03:09:02Z warning action=bootstrap error=could not join a cluster from [172.17.0.22:8300] msg=failed to join cluster, will notify next if voter servers=[“172.17.0.22:8300”] voter=true 2024-05-14T03:09:02Z INF action=bootstrap candidates=[{“Suffrage”:0,“ID”:“2983fa3610b4”,“Address”:“172.17.0.22:8300”}] msg=starting cluster bootstrapping 2024-05-14T03:09:02Z ERR action=bootstrap error=bootstrap only works on new clusters msg=could not bootstrapping cluster 2024-05-14T03:09:02Z INF action=bootstrap msg=notified peers this node is ready to join as voter servers=[“172.17.0.22:8300”] 2024-05-14T03:09:02Z warning msg=raft heartbeat timeout reached, not part of a stable configuration or a non-voter, not triggering a leader election 2024-05-14T03:09:02Z INF action=grpc\_startup msg=grpc server listening at [::]:50051 2024-05-14T03:09:03Z INF action=restapi\_management msg=Serving weaviate at http://[::]:8080 2024-05-14T03:09:03Z warning action=bootstrap error=could not join a cluster from [172.17.0.22:8300] msg=failed to join cluster, will notify next if voter servers=[“172.17.0.22:8300”] voter=true 2024-05-14T03:09:03Z INF action=bootstrap msg=notified peers this node is ready to join as voter servers=[“172.17.0.22:8300”] 2024-05-14T03:09:04Z INF action=telemetry\_push msg=telemetry started payload=&{MachineID:0eba0978-f3b0-4d55-92d0-32a900f97751 Type:INIT Version:1.25.0 Modules: NumObjects:0 OS:linux Arch:amd64} 2024-05-14T03:09:04Z warning action=bootstrap error=could not join a cluster from [172.17.0.22:8300] msg=failed to join cluster, will notify next if voter servers=[“172.17.0.22:8300”] voter=true 2024-05-14T03:09:04Z INF action=bootstrap msg=notified peers this node is ready to join as voter servers=[“172.17.0.22:8300”] 2024-05-14T03:09:05Z warning action=bootstrap error=could not join a cluster from [172.17.0.22:8300] msg=failed to join cluster, will notify next if voter servers=[“172.17.0.22:8300”] voter=true 2024-05-14T03:09:05Z INF action=bootstrap msg=notified peers this node is ready to join as voter servers=[“172.17.0.22:8300”] 2024-05-14T03:09:07Z warning action=bootstrap error=could not join a cluster from [172.17.0.22:8300] msg=failed to join cluster, will notify next if voter servers=[“172.17.0.22:8300”] voter=true 2024-05-14T03:09:07Z INF action=bootstrap msg=notified peers this node is ready to join as voter servers=[“172.17.0.22:8300”] 2024-05-14T03:09:08Z warning action=bootstrap error=could not join a cluster from [172.17.0.22:8300] msg=failed to join cluster, will notify next if voter servers=[“172.17.0.22:8300”] voter=true 2024-05-14T03:09:08Z INF action=bootstrap msg=notified peers this node is ready to join as voter servers=[“172.17.0.22:8300”] 2024-05-14T03:09:09Z warning action=bootstrap error=could not join a cluster from [172.17.0.22:8300] msg=failed to join cluster, will notify next if voter servers=[“172.17.0.22:8300”] voter=true 2024-05-14T03:09:09Z INF action=bootstrap msg=notified peers this node is ready to join as voter servers=[“172.17.0.22:8300”] ---
**Author:** ![maddios](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/maddios/32/1491_2.png) [@maddios](https://forum.weaviate.io/u/maddios)\ **Post date:** [May 14, 2024, 3:36am UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/2 "2024-05-14T03:36:41Z")
Looks like this is an issue with 1.25.0 I just tried rolling my configuration down to 1.24.12 and after loading some data then restarting, it’s still working fine. However some other error comes up now: {“error”:[{“message”:“list objects: search index searchvideo: remote shard object search q6648XVHIeWP: resolve node name "240a004f6aec" to host”}]} found this discussion here: [Error resolving node name to host](https://forum.weaviate.io/t/error-resolving-node-name-to-host/572) Does this mean my hostname env parameter isn’t applying right? ---
**Author:** ![maddios](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/maddios/32/1491_2.png) [@maddios](https://forum.weaviate.io/u/maddios)\ **Post date:** [May 14, 2024, 5:13am UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/3 "2024-05-14T05:13:49Z")
omg, I had an extra space in my CLUSTER\_HOSTNAME env variable. 😭 Seems like that was my 1.24.12 issue. ---
**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\ **Post date:** [May 14, 2024, 1:18pm UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/4 "2024-05-14T13:18:21Z")
hi @maddios !! Welcome to our community 🤗 Thanks for sharing!! ---
**Author:** ![evenfrost](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/evenfrost/32/327_2.png) [@evenfrost](https://forum.weaviate.io/u/evenfrost)\ **Post date:** [May 14, 2024, 3:00pm UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/5 "2024-05-14T15:00:54Z")
I’ve migrated from 1.22.x to 1.25.0 and started getting the same error when connecting to the Weaviate instance via weaviate-ts-client: `Error: usage error (403): {"error":[{"message":"could not read schema with strong consistency: failed to execute query: leader not found"}]}` Falling back to 1.24.12 helped, but there is still an error with 1.25.0. ---
**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\ **Post date:** [May 14, 2024, 3:02pm UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/6 "2024-05-14T15:02:36Z")
hi @evenfrost ! If you are running a multi node cluster on k8s, you need to follow this migration guide in order to upgrade to 1.25: > **[1.25 (For Kubernetes users) | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/more-resources/migration/weaviate-1-25)** > > Assumptions & requirements Let me know if this helps! Thanks! ---
**Author:** ![evenfrost](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/evenfrost/32/327_2.png) [@evenfrost](https://forum.weaviate.io/u/evenfrost)\ **Post date:** [May 14, 2024, 3:14pm UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/7 "2024-05-14T15:14:15Z")
Hi @DudaNogueira , no, I’m using Docker image locally. ---
**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\ **Post date:** [May 14, 2024, 8:42pm UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/8 "2024-05-14T20:42:27Z")
That on a multi node deployment, right? There are some changed environment variable changes needed in order to leverage the new RAFT consensus algorithm. Notice the new `RAFT_`environment variables here: > **[Environment variables | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/config-refs/env-vars#multi-node-instances)** > > To configure Weaviate in a Docker or a Kubernetes deployment, set these environment variables @evenfrost, do you mind opening a new thread post so we can have better visibility on that? I will try to reproduce this scenario later this week. Thanks! ---
**Author:** ![evenfrost](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/evenfrost/32/327_2.png) [@evenfrost](https://forum.weaviate.io/u/evenfrost)\ **Post date:** [May 20, 2024, 11:34am UTC](https://forum.weaviate.io/t/unable-to-restart-my-weaviate-container/2305/9 "2024-05-20T11:34:33Z")
Hi @DudaNogueira , sorry for the late reply. I created a separate topic here: [Error when upgrading to Weaviate 1.25.1](https://forum.weaviate.io/t/error-when-upgrading-to-weaviate-1-25-1/2386).