Implicit analysis (standard process) not terminating correctly under ubuntu 18.04

[ghost]

Hello Kevin, I installed Abaqus 2018 (and also 6.14) on my ubuntu 18.04 machine using the exact same procedure as you posted here. However I ran in the problem that the standard process (for implicit analyses) is not properly terminated after analysis has been completed.

In simple words, whenever I run an implicit analysis, this just works fine until I see in the .sta file that the analysis has been completed. After that, however, the process is not terminated, and RAM is not freed (and in the .log file the analysis completed message never appears) like if it remains in a deadlock state (more details here). This problem can be bypassed by manually kill the process, but is not very comfortable for example when running parametric studies...

Have you experienced the same? If not, did you install abaqus on a fresh installed or on an upgraded ubuntu?

Thanks for your input!

[Kevin-Mattheus-Moerman]

Hi @pevoz thanks for this comment. Yes I can confirm that I have the exact same issue. I have not found a solution yet.
I have Ubuntu 18.04 as well. I recently reinstalled 18.04 on this machine since some things went wrong after an NVIDIA driver upgrade. Not sure how to fix this yet. I mainly use FEBio for the moment but will use Abaqus more intensively in the future. Please let me know if you have any updates on fixing this. I'll do the same.
Thanks.

[ghost]

Thanks for your quick answer. Currently, I'm not using Abaqus a lot as well. I'll surely update you as soon as I find a fix.

By the way, I fixed the link in my previous post, where you can find my post on askubuntu regarding this issue.

Actually, I've found another post similar to yours and asked if they had the same problem. The author of the article replied he has no problems (here the direct link to his reply on Disqus). This sounds however quite strange to me, as meanwhile I found other users having the exact same issue.

When you have time, I suggest you have a look to my askubuntu post. Maybe you have better ideas to find out a fix.

I also tried to contact Abaqus support (even if ubuntu is not supported) and that was their conclusion:

I talked to my colleague. The probably and main cause is that our codes are certified for OS systems based on linux version 3.x (like the supported RedHat/CentOS or SuSE Linux Enterprise) and not with 4.x (which for example Ubuntu 16.04 is using).

Abaqus needs to use some specific kernel routines to stop and clean up the jobs at completion. This functions with kernel versions 3.x for (un)supported OS systems but not with 4.x. In the latter Abaqus should use some other kernel routines to stop jobs correctly.
Compared to A/Explicit A/Standard apparently uses a bit different set of kernel routines at the end, and that A/Explicit is working is just 'lucky'.

As far as we know at the moment, the only workaround is to use an OS based on linux kernel 3.x.

My current guess is that the problem is not related to the kernel (since with ubuntu 16.04.5 and kernel 4.15 standard gets terminated correctly), but rather with some external libraries. But maybe I'm missing something.

[cjekel]

I use OpenSUSE and have the same issue (Funny I'm actually involved in that Disqus post as well). It appears that Abaqus no longer works properly on modern linux.

I have created a Python wrapper to the abq2018 solver, but it's not perfect. At least not yet...

If you don't have a solution and are still planning on using abaqus, do you mind reviewing my wrapper? https://github.com/cjekel/Abaqus-Installation-Instructions-for-Ubuntu

Edit: this is the wrapper I am talking about https://github.com/cjekel/Abaqus-Installation-Instructions-for-Ubuntu/blob/master/abq

[Kevin-Mattheus-Moerman]

Thanks yeah I'll check it out in the coming months.

[JoKalliauer]

The terminating issue has been fixed in Abaqus2020 HotFix 5

(there exist also a HotFix 16 for Abaqus 2018 and a HotFix 11 for Abaqus 2019 that should also fix the bug)

I wrote a bug-report to the support

I got the reply:

To Submitter	09/15/2020 02:55:17PM

Hallo Johannes,

the issue you reported seems to be related to the following documented bug:

Article ID : BR10000291796 
Abstract :  Abaqus/Standard analyses enter an infinite loop if the job attempts to exit with an error on SLES 15 and Redhat 8 Linux systems.
Link :  https://kb.dsxclient.3ds.com/mashup-ui/page/document?q=docid:BR10000291796
"When running on SLES 15 and Redhat 8 Linux systems, Abaqus/Standard analyses enter an infinite loop if the job attempts to exit with an error on SLES 15 and Redhat 8 Linux systems. The infinite loop occurs during shutdown of the standard process execution. The post analysis cleanup processes are not executed.
abaqus -job test terminate does not terminate this job. The Linux kill command must be used to terminate the job.
More specifically, this issue occurs on any Linux system that contains glibc version 2.25 or later. "

This bug is fixed in the latest Abaqus 2020 HF5 (2020 FP.CFA.2038) release, which will be available for download until the end of this week. Until you can install this version, you may use the Abaqus 2018-HF16 or Abaqus 2019-HF10 (or later) releases, which also contain this bug fix. 

Please let us know, if the issue is not gone even in the mentioned Abaqus releases.

Best Regards

You can find the local support-addresses at https://www.3ds.com/products-services/simulia/services-support/locations/ or write to support.dsxeco(at)3ds.com

How to fix:

I downloaded Part_SIMULIA_EstPrd - SIMULIA Abaqus 2020 FP.CFA.2038 - Linux64 from https://software.3ds.com/ and installed Part_SIMULIA_EstPrd.Linux64/1/Software/SIMULIA_EstPrd.HF5.Linux64/1/StartTUI.sh as well as Part_SIMULIA_EstPrd.Linux64/1/Software/CAASIMULIA_EstPrd.HF5.Linux64/1/StartTUI.sh and now it works on Ubuntu 20.04 without singularity-container. (PS don't forget to change to DSY_OS_Release="CentOS" in all Linux.sh-files, as described in http://coquake.eu/wp-content/uploads/2019/02/Abaqus18_on_Ubuntu18.04LTS.pdf )

copied from willfurnass/abaqus-2017-centos-7-singularity#5 (comment)