(Cyclic quasi-static)-ABAQUS/Explicit aborts job randomly?

[g.alshamsi]

Hello all,

I'm running a set of quasi-static pushover/cyclic test on a shear wall assembly using explicit. My issue is that sometimes the analysis would abort suddenly and report the following error:

ERROR in job messaging system: Error in connection to analysis
Error in job Base_Beam: Abaqus/Explicit Analysis exited with an error - Please see the status file for possible error messages if the file exists.
Job Base_Beam aborted due to errors.

I rechecked the .sta and .msg file and the following message was reported in the status file:

***ERROR: Process terminated by external request (SIGTERM or SIGINT received).

If I'm not mistaken, this message appears when the user manually terminates the job (through the GUI or command window); however I didn't do that as I left the simulation overnight hoping it would be complete by the time I wake up and to my surprise I found this error message in the morning.
I re-ran the same analysis and it worked fine, however I recently ran into the same error and I'm wondering if anyone has any explanation to what is causing ABAQUS to abort midway? I'm running the job on 6 cores using double precision on ABAQUS 2021 for anyone who's wondering.
Any help is appreciated,I can't afford having jobs abort randomly as I have a ton of jobs to run and each job takes around 14 hours to complete.

Thanks!​

 

[FEA way]

This happens sometimes, especially on laptops. The reason is usually loss of power (even if battery is still charged) or problem with connection to license server. Such issues are one of the main reasons to use restart feature in Abaqus.

 

[g.alshamsi]

Great, I am indeed working on a laptop and I had a feeling I was overloading it. Would decreasing the number of cores solve the problem perhaps?

Regarding the restart analysis, I started going through the manual but I'm not completely familiar with the process. Would restarting the analysis continue the job from the last increment of the aborted simulation?

Thanks for the help,,,

 

[FEA way]

You can try reducing the number of CPUs but it’s very likely that the problem will happen from time to time anyway.

There are several options for restart analysis and you can write the restart information every increment but keep in mind that it will increase the size of files significantly.

 

[g.alshamsi]

Got it, appreciate the quick reply.

For anyone who's interested in the issue, I found this blog post by Simuleon that discusses restart analysis:

https://info.simuleon.com/blog/how-to-restart-an-abaqus-analysis

Cheers,