a year ago
according to deploy logs, all seems fine
Environment variables:
DATABASE_URL: (gonna hide it)
System check identified no issues (0 silenced).
Successfully connected to MySQL!
Running migrations…
Operations to perform:
Running migrations:
No migrations to apply.
Starting Django server…
[2025-02-18 20:26:03] INFO [django.utils.autoreload:668] Watching for file changes with StatReloader
Performing system checks…
System check identified no issues (0 silenced).
February 18, 2025 - 20:26:04
Django version 4.2, using settings 'backend.settings_dev'
Starting development server at http://0.0.0.0:8000/
Quit the server with CONTROL-C.
but I'm failing healthchecks
====================
Starting Healthcheck
====================
Path: /api/health/
Retry window: 1m40s
Attempt #1 failed with service unavailable. Continuing to retry for 1m29s
Attempt #2 failed with service unavailable. Continuing to retry for 1m18s
Attempt #3 failed with service unavailable. Continuing to retry for 1m6s
Attempt #4 failed with service unavailable. Continuing to retry for 52s
Attempt #5 failed with service unavailable. Continuing to retry for 34s
Attempt #6 failed with service unavailable. Continuing to retry for 8s
1/1 replicas never became healthy!
Healthcheck failed!
can you help me understand why?
ⓘ Deployment information is only viewable by project members and Railway employees.
7 Replies
a year ago
Hello,
Have you checked the deploy logs while the health check is failing? looks like your app cannot connect to the database.
a year ago
yea, that is the end of the deploy logs above (before healthchecks). I can check while its in progress. I must be missing something.
a year ago
ok yea, I see. looks like railway internal networking needs time to stabilize before attempting. I have a script I can adjust for this. sorry for the noise
a year ago
well I'm stumped. I'm connected to the DB, django is running, but healthchecks are saying the service is unavailable. what service?
a year ago
I made some changes to my scripts. I'm good now. again, sorry
a year ago
Awsome, glad you got it working! and for future reference, here is a page of the platform terminology -
Status changed to Solved brody • about 1 year ago