mrsisk
April 26, 2023, 12:00pm
1
iam trying to deploy a phoenix application but i keep getting error when its running release_command
--> Pushing image done
image: registry.fly.io/name:deployment-01GYYPD43AVTFRP7B4P2NG1QN8
image size: 124 MB
Provisioning ips for application name
Dedicated ipv6: #########
Shared ipv4: ########
Add a dedicated ipv4 with: fly ips allocate-v4
Running app-name release_command: /app/bin/migrate
Error: release command failed - aborting deployment. error running release_command machine: error creating a release_command machine: failed to launch VM: EOF
Hey, can you retry with LOG_LEVEL=debug fly deploy and paste the output here?
mrsisk
April 26, 2023, 1:09pm
3
its quite long not sure if this last part will shade some light
Running wandering-breeze-2198 release_command: /app/bin/migrate
DEBUG --> POST https://api.machines.dev/v1/apps/wandering-breeze-2198/machines
DEBUG Config has metrics token
{
"appId": "wandering-breeze-2198",
"organizationId": "P7lZB0nw2ylg8sm1P5Rqp9JzZqIZ88ZeK",
"region": "jnb",
"config": {
"env": {
"FLY_PROCESS_GROUP": "fly_app_release_command",
"PHX_HOST": "wandering-breeze-2198.fly.dev",
"PORT": "8080",
"PRIMARY_REGION": "jnb",
"RELEASE_COMMAND": "1"
},
"init": {
"cmd": [
"/app/bin/migrate"
]
},
"metadata": {
"fly_platform_version": "v2",
"fly_process_group": "fly_app_release_command",
"fly_release_id": "4Y6bmgkVVz56RfkxOkyzPK9G6",
"fly_release_version": "1"
},
"image": "registry.fly.io/wandering-breeze-2198:deployment-01GYYTEW0604WYE4C6CSG2WA32",
"auto_destroy": true,
"restart": {
"policy": "no"
},
"guest": {
"cpu_kind": "shared",
"cpus": 2,
"memory_mb": 512
},
"dns": {
"skip_registration": true
},
"stop_config": {
"signal": "SIGTERM"
}
},
"SkipHealthChecks": false
}
DEBUG {0xc000dcd920}
DEBUG <-- 200 https://api.machines.dev/v1/apps/wandering-breeze-2198/machines (685.73ms)
DEBUG
DEBUG --> POST https://api.fly.io/graphql
DEBUG Config has metrics token
{
"query": "\nmutation MachinesUpdateRelease ($input: UpdateReleaseInput!) {\n\tupdateRelease(input: $input) {\n\t\trelease {\n\t\t\tid\n\t\t}\n\t}\n}\n",
"variables": {
"input": {
"clientMutationId": "",
"releaseId": "4Y6bmgkVVz56RfkxOkyzPK9G6",
"status": "failed"
}
},
"operationName": "MachinesUpdateRelease"
}
DEBUG {0xc000e3f2f0}
DEBUG <-- 200 https://api.fly.io/graphql (359.83ms)
{
"data": {
"updateRelease": {
"release": {
"id": "4Y6bmgkVVz56RfkxOkyzPK9G6"
}
}
}
}
Error: release command failed - aborting deployment. error running release_command machine: error creating a release_command machine: failed to launch VM: EOF
Hey, can you try again? We might have fixed a bug that was causing this.
mrsisk
April 26, 2023, 3:39pm
5
iam able to pass that stage now iam having this problem?
Pulling container image registry.fly.io/binary-monitor:deployment-01GYZ3CQ31PSH7RP4JB9C8TCM3
Unpacking image
Successfully prepared image registry.fly.io/binary-monitor:deployment-01GYZ3CQ31PSH7RP4JB9C8TCM3
Configuring firecracker
Starting init (commit: 1578345)...
Preparing to run: `/app/bin/migrate` as nobody
2023/04/26 15:37:58 listening on [fdaa:2:fb1:a7b:d5a7:7b86:ec63:2]:22 (DNS: [fdaa::3]:53)
** (EXIT from #PID<0.94.0>) shutdown
Starting clean up.
[ 2.202482] reboot: Restarting system
machine restart policy set to 'no', not restarting
DEBUG --> POST https://api.fly.io/graphql
{
"query": "\nmutation MachinesUpdateRelease ($input: UpdateReleaseInput!) {\n\tupdateRelease(input: $input) {\n\t\trelease {\n\t\t\tid\n\t\t}\n\t}\n}\n",
"variables": {
"input": {
"clientMutationId": "",
"releaseId": "QgDeJ3o11V2D7fmx9JLbDgj2q",
"status": "failed"
}
},
"operationName": "MachinesUpdateRelease"
}
DEBUG {0xc0010a3c50}
DEBUG <-- 200 https://api.fly.io/graphql (440.31ms)
{
"data": {
"updateRelease": {
"release": {
"id": "QgDeJ3o11V2D7fmx9JLbDgj2q"
}
}
}
}
Error: release command failed - aborting deployment. error release_command machine 6e8275dc790d87 exited with non-zero status of 1
It looks like you have migrations set to run but no database connected to this app. If you want to remove the migrations step delete the release_command field from your fly.coml.
If you intended to have a postgres you’ll need to create one and attach it to this app.
Do you remember if you said yes or no to the Postgres setup step in fly launch?
mrsisk
April 26, 2023, 4:00pm
7
i actually did. seems like the problem might have been phoenix version. i just changed the phoenix version and created brand new project. and all seems to be working fine now. Thank you
1 Like