Same thing over and over: T19:58:06.170 app sea keeper | T19:58:06.170Z INFO cmd/keeper.go:1557 our db requested role is standby Nothing that explains what is going on (or I think it doesn’t) Pg critical 2f2ebf1a sea HTTP 5m45s ago HTTP GET Role passing 2f2ebf1a sea HTTP 5m28s ago replica Vm passing 2f2ebf1a sea HTTP 1m7s ago HTTP GET Pg critical b01e8595 sea HTTP 44m40s ago HTTP GET Role passing b01e8595 sea HTTP 44m29s ago leader Vm passing b01e8595 sea HTTP 1m21s ago HTTP GET NAME STATUS ALLOCATION REGION TYPE LAST UPDATED OUTPUT ***v2 failed - Failed due to unhealthy allocations and deploying as v3įly checks list renders: ➜ postgres-ha git:(main) ✗ fly checks list V2 failed - Failed due to unhealthy allocations still having issues: I’ll check if I can connect using WireGuard 2 desired, 2 placed, 0 healthy, 2 unhealthy Ok, I added a second volume and scaled it to 2. ***v0 failed - Failed due to unhealthy allocations and deploying as v1 it repeats here several times the same thing. Health Checks = 3 total, 2 passing, 1 critical V0 failed - Failed due to unhealthy allocations You can detach the terminal anytime without stopping the deploymentġ desired, 1 placed, 0 healthy, 1 unhealthy => CACHED COPY -from=flyutil /fly/bin/* /usr/local/bin/ 0.0s => CACHED RUN CGO_ENABLED=0 GOOS=linux go build -v -o /fly/bin/start. => CACHED RUN CGO_ENABLED=0 GOOS=linux go build -v -o /fly/bin/flyadmin. => CACHED WORKDIR /go/src//fly-examples/postgres-ha 0.0s => CACHED RUN mkdir -p /run/haproxy/ 0.0s => CACHED RUN useradd -ms /bin/bash stolon 0.0s => CACHED COPY -from=postgres_exporter /postgres_exporter /usr/local/bin/ 0.0s => CACHED COPY -from=stolon /go/src/app/bin/* /usr/local/bin/ 0.0s => CACHED RUN apt-get update & apt-get install -no-install-recommends -y ca-certificates curl bash dnsutils vim-tiny procps jq haproxy postgresql-13-postgis-3 postgresql-13-postgis-3-scripts & apt a 0.0s => load metadata for docker.io/library/golang:1.16 4.0s => load metadata for docker.io/wrouesnel/postgres_exporter:latest 4.0s => load metadata for docker.io/library/postgres:13.4 4.0s => load metadata for docker.io/flyio/stolon:b6b9aaf 4.0s Sending build context to Docker daemon 172.5kB Secrets are staged for the first deploymentĭeploying ➜ postgres-ha git:(main) ✗ flyctl deploy Here the app is created but pending deployment ➜ postgres-ha git:(main) ✗ flyctl volumes create pg_data -region sea -size 10Īdding the secrets as per the README ➜ postgres-ha git:(main) ✗ flyctl secrets set SU_PASSWORD= REPL_PASSWORD= ? Select region: sea (Seattle, Washington (US))Ĭreated app postgres-ha-example in organization metronome ? Select organization: Metronome (metronome) ? App Name (leave blank to use an auto-generated name): postgres-ha-example ? Would you like to copy its configuration to the new app? YesĬreating app in /Users/ericktamayo/Code/metronome/postgres-ha Here is the whole failing deploy Launching ➜ postgres-ha git:(main) flyctl launchĪn existing fly.toml file was found for app postgres-ha-example ***v1 failed - Failed due to unhealthy allocations and deploying as v2 The deploy is giving me the following error: T04:54:29.000 keeper | T04:54:29.334Z INFO cmd/keeper.go:1676 postgres parameters not changed I cloned the repo and did a flyctl launchįlyctl volumes create pg_data -region sea -size 10įlyctl secrets set SU_PASSWORD= REPL_PASSWORD=
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |