# Crash due to out of memory **URL:** \ **Category:** Floating Topics\ **Tags:** server\ **Created:** [May 23, 2025, 7:48pm UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871 "2025-05-23T19:48:31Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [May 23, 2025, 7:48pm UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871/1 "2025-05-23T19:48:31Z")
Running a server with 21.0.2.202 through [FMPHost.com](http://FMPHost.com). They spin up virtual machines on AWS, and it's been great for a while. This week it's crashed 3 times, and I've had to call them to restart it. The first two times the guy just said it was just an AWS fault, but the third time I got a different tech and he looked closely and said it was a memory issue, so he suggested turning up the cache. The Virtual Machine has 16GB RAM, and cache was set to 512, so he bumped it to 1024. I looked at the Stats.log and it's usually pinned at 100%, with some dips to 95 or 97 (and obviously less right after restart). Is that "bad" that I turned up the cache when it was already at 100%? I looked at event log and don't see anything happening around the time it crashed worth noting. ---
**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\ **Post date:** [May 23, 2025, 9:06pm UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871/2 "2025-05-23T21:06:16Z")
If you are hitting the cache most of the time - that's good! The cache is in RAM and it means that you don't need to search the disk looking for your data. When your cache % is low you should increase your RAM, not the other way around. ---
**Author:** ![janhagemeister](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@janhagemeister](https://the.fmsoup.org/u/janhagemeister)\ **Post date:** [May 24, 2025, 4:34am UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871/3 "2025-05-24T04:34:11Z")
A full cache doesn’t cause server crashes, but an out-of-memory situation definitely can. That said, 16 GB is usually more than enough. I suspect there’s a different issue at play here! Jan ---
**Author:** ![MonkeybreadSoftware](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/monkeybreadsoftware/32/361_2.png) [@MonkeybreadSoftware](https://the.fmsoup.org/u/MonkeybreadSoftware)\ **Post date:** [May 24, 2025, 9:10am UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871/4 "2025-05-24T09:10:19Z")
Do you have some crash reports? Or monitoring? Like did the machine run out of memory? Which would also mean that swap file was full. But what does crash mean? e.g. if you run a script that allocates lots of memory on the server and the system kills the process eventually, it would just be restarted and continue. ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [May 24, 2025, 11:42am UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871/5 "2025-05-24T11:42:11Z")
Ok this is helpful. Cache didn't make sense to me, but this is the company who I pay to host so I just sort of assumed they knew of an issue I wasn't aware of. I have the Filemaker Logs but they don't show anything helpful. I've requested the server logs from AWS so I can see what the actual error is. I'm honestly unclear if it's a "crash" or a "hang" anyway. Just that it became unresponsive. Here's the logs I have, please let me know if I should turn anything else on. ![CleanShot 2025-05-24 at 07.16.49](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/5/5c7214f881f5afa0c5bd6924ceffbb928d1b8e8a.png) ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [May 24, 2025, 9:58pm UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871/6 "2025-05-24T21:58:09Z")
[a711783\_AWS.log.zip](https://the.fmsoup.org/uploads/short-url/lOdHJJ99Bx8ZvrnOzFykgnRf3Ng.zip) (16.7 KB) I got the AWS log from my host (attached), but I don't know what it means... Can someone help me know what to look for for a clue about what's causing the crash. Apparently, they looked at this and saw it was a memory error. They also said they could send me the system level log from Linux (I thought I was on Windows, but I guess the moved me at some point). Thanks in advance. ---
**Author:** ![janhagemeister](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@janhagemeister](https://the.fmsoup.org/u/janhagemeister)\ **Post date:** [May 25, 2025, 7:34am UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871/7 "2025-05-25T07:34:51Z")
As far as I can tell, the VM did not crash but was properly rebooted. This doesn’t appear to be a FileMaker issue. ---
**Author:** ![daleallyn](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/daleallyn/32/819_2.png) [@daleallyn](https://the.fmsoup.org/u/daleallyn)\ **Post date:** [May 25, 2025, 8:49am UTC](https://the.fmsoup.org/t/crash-due-to-out-of-memory/4871/8 "2025-05-25T08:49:04Z")
Just an aside comment for anyone interested: Some time ago @WimDecorte (and others) suggested activating Top Call Statistics on all deployments for various kinds of troubleshooting. We've done this to all of our servers and detect no performance issues (although our deployments are on premises servers, aside from certain test environments).