This can be determined by asking some questions. The first step to identifying what caused the crash is to determine where the issue is stemming from: such as the files you are using, the environment SOLIDWORKS is installed on, or the installation of SOLIDWORKS itself. Note: This process will not work well with random occurrences as it requires some repeatability.

In this guide, I will discuss some steps for how to troubleshoot SOLIDWORKS crashes, especially if this is a steady occurrence. The suspicious statistic is a huge spike in Read Bandwith on the ebs volume just before the crash which seems to maintain until restart.Everyone who has used SOLIDWORKS has at one time or another experienced a crash whether that be a one time instance or a steady occurrence. The instance is a t2.micro but before i increase this i'd like to understand the cause of the issue as during its peak use times it seems to handle things fine and its not quite making sense why its failing early morning.Īt the point where the issue occurs there is a minor spike in CPU usage from ~2% to ~8%. I have confirmed this with both the nginx logs on the instance and the app logs. This is odd as the app is used through the day and not through the night. Its often at 4:01am UTC (which doesnt seem like a coincidence) but there have been other failure times ranging from 1:26am to 5:21am. Most mornings the ec2 instance falls over and therefore the app is no longer running where i receive a text from sns. However, only the main, asset-serving, instance falls over. I have 2 versions of the exact same instance running with one receiving slightly more traffic than the other (as one serves the assets for both apps). The application is accessed through ELB which forwards requests to the instance. Nginx and mongodb is also running on the instance. I have a java application running on an ec2 instance.

Quick cpu application crashing