App crashing

having the same issue. also my app is crashing. I can’t tell if it’s something I’m doing if fly is having issues?

The 500 on the activity page is a UI bug. We don’t believe we’re having any issues with running apps though!

Will you run fly status --all on your app to and see if any VMs are saying “failed” or show restarts? If you can identify one that says it’s failing, you can run:

  • fly vm status <id> to get VM events, including exit codes
  • fly logs -i <id> to see logs for that specific VM

So I see it crashing with

Blockquote
[ 5.999062] Out of memory: Killed process 525 (node) total-vm:510232kB, anon-rss:186336kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:2784kB oom_score_adj:0

Likely the free tier isn’t enough memory for me? Is the best way to try with more memory to redeploy as a brand new app and choose a higher tier?

Hi @ctrlshiftba

Have a look here: https://fly.io/docs/reference/scaling/#adjusting-a-vm-s-memory

(edited to show link destination instead of big generic docs badge)

@ctrlshiftba @kurt points out to me that “yes, good idea to add memory” would have been a good preface to that. :upside_down_face:

This is really impressive! And it fixed my issue. Nice. Does that automatically move me from the free tier?

I’m having trouble figuring out what tier I’m in now looking here. Fly App Pricing I don’t see anything for “shared-cpu-1x 512mb” or am I still “shared-cpu” but with 512mb? It would be nice to see this easily in my dashboard.

I’m informed that “shared-cpu-1x 512MB” does exist, though its line in the VM pricing table is missing. :thinking:

1 Like

it’s shared-cpu-1x with a custom ram scaled to 512MB

fly scale memory 512
2 Likes

@matt2’s answer gets to a subtlety I missed: there is pricing specifically to add just RAM, which means the missing 512MB line in the VM table is what applies only if you use more than the free allowance of VM-hours.

Per @kurt, a 256MB bump in RAM is ~$1.25 per VM for 30 days (billed by the second).