deployment failure - replica never became healthy
curiouskal
PROOP

23 days ago

here's what i see:
[Region: us-east4]

==============

Using Nixpacks

==============

context: zjtl-vUTx

╔══════════════════════════════ Nixpacks v1.38.0 ══════════════════════════════╗

║ setup │ nodejs_22, pnpm-9_x ║

║──────────────────────────────────────────────────────────────────────────────║

║ install │ npm install -g corepack@0.24.1 && corepack enable ║

║ │ pnpm i --frozen-lockfile ║

║──────────────────────────────────────────────────────────────────────────────║

║ build │ pnpm install --frozen-lockfile && pnpm --filter=backend clean ║

║ │ && pnpm exec turbo run build --filter=./apps/backend ║

║──────────────────────────────────────────────────────────────────────────────║

║ start │ pnpm --filter=backend start:prod ║

╚══════════════════════════════════════════════════════════════════════════════╝

internal

load build definition from Dockerfile

0ms

internal

load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1745885067

147ms

internal

load .dockerignore

0ms

internal

load build context

0ms

stage-0

COPY . /app cached

0ms

stage-0

RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile cached

0ms

stage-0

RUN pnpm install --frozen-lockfile && pnpm --filter=backend clean && pnpm exec turbo run build --filter=./apps/backend cached

0ms

stage-0

COPY . /app/. cached

0ms

stage-0

RUN pnpm i --frozen-lockfile cached

0ms

stage-0

RUN npm install -g corepack@0.24.1 && corepack enable cached

0ms

stage-0

COPY . /app/. cached

0ms

stage-0

RUN nix-env -if .nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix && nix-collect-garbage -d cached

0ms

stage-0

COPY .nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix .nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix cached

0ms

stage-0

WORKDIR /app/ cached

0ms

auth

sharing credentials for production-us-east4-eqdc4a.railway-registry.com

1ms

=== Successfully Built! ===

Run:

docker run -it production-us-east4-eqdc4a.railway-registry.com/c3cb07e9-5c35-4ab0-9c28-5dcd1b19f8af:958797a5-6ea2-48c7-be18-6354b1e21b66

Build time: 61.29 seconds

==================== Starting Healthcheck ====================

Path: /health

Retry window: 5m0s

Attempt #1 failed with service unavailable. Continuing to retry for 4m49s

Attempt #2 failed with service unavailable. Continuing to retry for 4m38s

Attempt #3 failed with service unavailable. Continuing to retry for 4m26s

Attempt #4 failed with service unavailable. Continuing to retry for 4m12s

Attempt #5 failed with service unavailable. Continuing to retry for 3m54s

Attempt #6 failed with service unavailable. Continuing to retry for 3m28s

Attempt #7 failed with service unavailable. Continuing to retry for 2m48s

Attempt #8 failed with service unavailable. Continuing to retry for 2m18s

Attempt #9 failed with service unavailable. Continuing to retry for 1m47s

Attempt #10 failed with service unavailable. Continuing to retry for 1m17s

Attempt #11 failed with service unavailable. Continuing to retry for 47s

Attempt #12 failed with service unavailable. Continuing to retry for 17s

1/1 replicas never became healthy!

Solved$10 Bounty

2 Replies

Railway
BOT

23 days ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


Status changed to Solved brody 23 days ago


curiouskal
PROOP

23 days ago

problem solved - it was an issue with my code. sorry for the false alarm .


Status changed to Awaiting Railway Response Railway 23 days ago


Status changed to Solved curiouskal 23 days ago


Loading...