LS Dyna

LS Dyna

can’t run ls-dyna in background on Linux

    • wei.yang
      Subscriber

      Dear Sir/Madam,

      I am running ls-dyna in Linux. When I ran it on screen (foreground) it worked fine,
      but when I tried to run it in the background (command: lsdyna i=job.k > out) it got
      terminated and returned error message(s) as attached below.
       
      Could you please give me some advice on what is the cause of the issue?
       
      Your timely help is highly appreciated!
       
      Wil Yang

      wei.yang@aero.org
       
      +++++++++ copy/paste of message from “lsdyna i=job.k > out” +++++++
       
      *** buffer overflow detected ***: /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2 terminated
      ======= Backtrace: =========
      /lib64/libc.so.6(__fortify_fail+0x37)[0x7fa80e8f47a7]
      /lib64/libc.so.6(+0x116922)[0x7fa80e8f2922]
      /lib64/libc.so.6(+0x115e2b)[0x7fa80e8f1e2b]
      /lib64/libc.so.6(_IO_default_xsputn+0xe1)[0x7fa80e859031]
      /lib64/libc.so.6(_IO_vfprintf+0x28c5)[0x7fa80e826ec5]
      /lib64/libc.so.6(__vsprintf_chk+0x88)[0x7fa80e8f1eb8]
      /lib64/libc.so.6(__sprintf_chk+0x7d)[0x7fa80e8f1e0d]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0xba27493]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0xba29259]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0xb9bfe1d]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0xb9f6369]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0x62631f]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0x63c8d0]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0x471906]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0x462e1e]
      /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fa80e7fe555]
      /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2[0x462d29]
      ======= Memory map: ========
      00400000-0ca4c000 r-xp 00000000 00:39 13681602215                        /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2
      0cc4c000-0d463000 rw-p 0c64c000 00:39 13681602215                        /tcs/ago/group/ls-dyna/r11/ls-dyna_smp_d_R11_1_0_x64_redhat65_ifort160_sse2
      0d463000-1e414000 rw-p 00000000 00:00 0
      1ef38000-1f058000 rw-p 00000000 00:00 0                                  [heap]
      7fa80dd96000-7fa80df96000 rw-p 00000000 00:00 0
      7fa80df96000-7fa80df98000 r-xp 00000000 fd:06 308578                     /usr/lib64/libXau.so.6.0.0
      7fa80df98000-7fa80e198000 ---p 00002000 fd:06 308578                     /usr/lib64/libXau.so.6.0.0
      7fa80e198000-7fa80e199000 r--p 00002000 fd:06 308578                     /usr/lib64/libXau.so.6.0.0
      7fa80e199000-7fa80e19a000 rw-p 00003000 fd:06 308578                     /usr/lib64/libXau.so.6.0.0
      7fa80e19a000-7fa80e1c1000 r-xp 00000000 fd:06 308586                     /usr/lib64/libxcb.so.1.1.0
      7fa80e1c1000-7fa80e3c0000 ---p 00027000 fd:06 308586                     /usr/lib64/libxcb.so.1.1.0
      7fa80e3c0000-7fa80e3c1000 r--p 00026000 fd:06 308586                     /usr/lib64/libxcb.so.1.1.0
      7fa80e3c1000-7fa80e3c2000 rw-p 00027000 fd:06 308586                     /usr/lib64/libxcb.so.1.1.0
      7fa80e3c2000-7fa80e3c4000 r-xp 00000000 fd:06 2629                       /usr/lib64/libdl-2.17.so
      7fa80e3c4000-7fa80e5c4000 ---p 00002000 fd:06 2629                       /usr/lib64/libdl-2.17.so
      7fa80e5c4000-7fa80e5c5000 r--p 00002000 fd:06 2629                       /usr/lib64/libdl-2.17.so
      7fa80e5c5000-7fa80e5c6000 rw-p 00003000 fd:06 2629                       /usr/lib64/libdl-2.17.so
      7fa80e5c6000-7fa80e5db000 r-xp 00000000 fd:06 841395                     /usr/lib64/libgcc_s-4.8.5-20150702.so.1
      7fa80e5db000-7fa80e7da000 ---p 00015000 fd:06 841395                     /usr/lib64/libgcc_s-4.8.5-20150702.so.1
      7fa80e7da000-7fa80e7db000 r--p 00014000 fd:06 841395                     /usr/lib64/libgcc_s-4.8.5-20150702.so.1
      7fa80e7db000-7fa80e7dc000 rw-p 00015000 fd:06 841395                     /usr/lib64/libgcc_s-4.8.5-20150702.so.1
      7fa80e7dc000-7fa80e9a0000 r-xp 00000000 fd:06 2623                       /usr/lib64/libc-2.17.so
      7fa80e9a0000-7fa80eb9f000 ---p 001c4000 fd:06 2623                       /usr/lib64/libc-2.17.so
      7fa80eb9f000-7fa80eba3000 r--p 001c3000 fd:06 2623                       /usr/lib64/libc-2.17.so
      7fa80eba3000-7fa80eba5000 rw-p 001c7000 fd:06 2623                       /usr/lib64/libc-2.17.so
      7fa80eba5000-7fa80ebaa000 rw-p 00000000 00:00 0
      7fa80ebaa000-7fa80ecab000 r-xp 00000000 fd:06 2631                       /usr/lib64/libm-2.17.so
      7fa80ecab000-7fa80eeaa000 ---p 00101000 fd:06 2631                       /usr/lib64/libm-2.17.so
      7fa80eeaa000-7fa80eeab000 r--p 00100000 fd:06 2631                       /usr/lib64/libm-2.17.so
      7fa80eeab000-7fa80eeac000 rw-p 00101000 fd:06 2631                       /usr/lib64/libm-2.17.so
      7fa80eeac000-7fa80eec3000 r-xp 00000000 fd:06 520361                     /usr/lib64/libpthread-2.17.so
      7fa80eec3000-7fa80f0c2000 ---p 00017000 fd:06 520361                     /usr/lib64/libpthread-2.17.so
      7fa80f0c2000-7fa80f0c3000 r--p 00016000 fd:06 520361                     /usr/lib64/libpthread-2.17.so
      7fa80f0c3000-7fa80f0c4000 rw-p 00017000 fd:06 520361                     /usr/lib64/libpthread-2.17.so
      7fa80f0c4000-7fa80f0c8000 rw-p 00000000 00:00 0
      7fa80f0c8000-7fa80f1b1000 r-xp 00000000 fd:06 751242                     /usr/lib64/libstdc++.so.6.0.19
      7fa80f1b1000-7fa80f3b1000 ---p 000e9000 fd:06 751242                     /usr/lib64/libstdc++.so.6.0.19
      7fa80f3b1000-7fa80f3b9000 r--p 000e9000 fd:06 751242                     /usr/lib64/libstdc++.so.6.0.19
      7fa80f3b9000-7fa80f3bb000 rw-p 000f1000 fd:06 751242                     /usr/lib64/libstdc++.so.6.0.19
      7fa80f3bb000-7fa80f3d0000 rw-p 00000000 00:00 0
      7fa80f3d0000-7fa80f3d7000 r-xp 00000000 fd:06 520365                     /usr/lib64/librt-2.17.so
      7fa80f3d7000-7fa80f5d6000 ---p 00007000 fd:06 520365                     /usr/lib64/librt-2.17.so
      7fa80f5d6000-7fa80f5d7000 r--p 00006000 fd:06 520365                     /usr/lib64/librt-2.17.so
      7fa80f5d7000-7fa80f5d8000 rw-p 00007000 fd:06 520365                     /usr/lib64/librt-2.17.so
      7fa80f5d8000-7fa80f710000 r-xp 00000000 fd:06 1018356                    /usr/lib64/libX11.so.6.3.0
      7fa80f710000-7fa80f910000 ---p 00138000 fd:06 1018356                    /usr/lib64/libX11.so.6.3.0
      7fa80f910000-7fa80f911000 r--p 00138000 fd:06 1018356                    /usr/lib64/libX11.so.6.3.0
      7fa80f911000-7fa80f916000 rw-p 00139000 fd:06 1018356                    /usr/lib64/libX11.so.6.3.0
      7fa80f916000-7fa80f938000 r-xp 00000000 fd:06 2616                       /usr/lib64/ld-2.17.so
      7fa80fad4000-7fa80fb01000 rw-p 00000000 00:00 0
      7fa80fb14000-7fa80fb37000 rw-p 00000000 00:00 0
      7fa80fb37000-7fa80fb38000 r--p 00021000 fd:06 2616                       /usr/lib64/ld-2.17.soforrtl: error (76): Abort trap signal
      Image              PC                Routine            Line        Source
      ls-dyna_smp_d_R11  000000000BB6D785  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000BB6B3A7  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000BA22254  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000BA22066  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000B9A1E09  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000B9A8EE8  Unknown               Unknown  Unknown
      libpthread.so.0    00007FA80EEBB630  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E812387  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E813A78  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E854F67  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E8F47A7  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E8F2922  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E8F1E2B  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E859031  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E826EC5  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E8F1EB8  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E8F1E0D  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000BA27493  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000BA29259  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000B9BFE1D  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000B9F6369  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000062631F  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  000000000063C8D0  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  0000000000471906  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  0000000000462E1E  Unknown               Unknown  Unknown
      libc.so.6          00007FA80E7FE555  Unknown               Unknown  Unknown
      ls-dyna_smp_d_R11  0000000000462D29  Unknown               Unknown  Unknown
      Abort

    • Reno Genest
      Ansys Employee

      Hello Wei,

      How do you run LS-DYNA in the foreground? What process do you use?

      To run LS-DYNA, an execution command line needs to be issued at some point. Which command do you use when running in the "foreground"?

       

      Reno.

       

    • wei.yang
      Subscriber
      The command (to run on screen/foreground") is lsdyna i=job.klsdyna i=job.k
    • Reno Genest
      Ansys Employee

      Are you sure this is the command you are using? There should not be two i= arguments on the command line.

      Here is the command line I use to run SMP on Linux:

      /data2/rgenest/lsdyna/ls-dyna_smp_d_R13_0_0_x64_centos610_ifort190/ls-dyna_smp_d_R13_0_0_x64_centos610_ifort190 i=/data2/rgenest/runs/Test/input.k ncpu=-4 memory=20m

      Try to specify the complete path of the LS-DYNA solver as in the command line above. 

      Which LS-DYNA solver are you using when the run is successful? Have a look at the LS-DYNA banner in the messag file:

       

      Reno.

    • wei.yang
      Subscriber

      "lsdyna" is the default ls-dyna executable filename created from "make", as I am using user subroutines, and I run ls-dyna in the same (working) directory as "lsdyna" is created. Again, the command that works is "lsdyna i=job.k"

    • Reno Genest
      Ansys Employee

      Hello Wei,

      If lsdyna i=job.k works, why don't you continue using this command?

      Which version of LS-DYNA are you using? Does the model work with the regular version of LS-DYNA (without user subroutines). If so, then the problem is likely the user subroutine. 

       

      Reno.

    • wei.yang
      Subscriber

      I use telnet (PuTTY) to log on to HPC when I run ls-dyna, and the connection is NOT always guaranteed to maintain while a job is still ongoing. To avoid ls-dyna jobs being suspended or terminated due to network disconnections, I need to run the jobs in the background, such as using " > out" after "lsdyna i=filename.k ". Hope it is understandable.

    • Reno Genest
      Ansys Employee

      Hello Wei,

      The HPC cluster should have a solid connection to the license server to avoid interruptions. You should be able to remotely connect to the HPC cluster, launch a run in the "foreground", and then disconnect from the cluster. The run should continue no problem. We do this all the time; we remotely connect to a Linux machine at the office via VPN, start a run on the Linux machine, and then disconnect. The run continues.

      I am not sure I fully understand your issue. Could you give more explanations?

      Also, I am not sure why using > out creates a problem. It may have to do with the user subroutine which are not officially supported by Ansys. Have you tried running with an LS-DYNA version downloaded from the Ansys website? 

      lsdyna.ansys.com

      username: user

      password: computer

      If you still have issues with a regular version of LS-DYNA, then the problem may be model specific. Ansys employees cannot download your model on the Ansys forum. You will have to create a service request on the Ansys customer portal:

      support.ansys.com

       

      Reno.

       

       

       

       

Viewing 7 reply threads
  • You must be logged in to reply to this topic.