General Mechanical

General Mechanical

Lauching Workbench Mechanical from the command line (server)

    • Barbara Cunha
      Subscriber
      I would like to open Ansys Workbench Mechanical GUI from the command line using CygwinX and for that I used the command suggested here> https://www.padtinc.com/2012/02/29/starting-ansys-products-from-the-command-line/
       
      Workbench GUI was launched with success but when I try to open the model it crashes and gives me this error:
       
      Error
       
      and in the command line, I get this:
       
      "

      CLR: Managed code called FailFast, saying "An exception was not handled in an AsyncLocal notification callback."

       

      Unhandled Exception:

      System.Threading.ThreadAbortException: Thread was being aborted.

        at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_threads_state_poll()

        at System.Collections.Generic.List`1+Enumerator[T].MoveNext () <0x7f5a05996cb0 + 0x00028> in <99e7772254e64ba29201f69df54e9889>:0

        at System.Threading.ExecutionContext.OnAsyncLocalContextChanged (System.Threading.ExecutionContext previous, System.Threading.ExecutionContext current) [0x00100] in <99e7772254e64ba29201f69df54e9889>:0

       

      =================================================================

              Native Crash Reporting

      =================================================================

      Got a SIGABRT while executing native code. This usually indicates

      a fatal error in the mono runtime or one of the native libraries

      used by your application.

      =================================================================

       

      =================================================================

              Native stacktrace:

      =================================================================

              0x4a5624 - /ansys_inc/v222/Tools/mono/Linux64/bin/mono : (null)

              0x4a598c - /ansys_inc/v222/Tools/mono/Linux64/bin/mono : (null)

              0x454498 - /ansys_inc/v222/Tools/mono/Linux64/bin/mono : (null)

              0x4a4c8f - /ansys_inc/v222/Tools/mono/Linux64/bin/mono : (null)

              0x7f5a0b94e630 - /lib64/libpthread.so.0 : (null)

              0x7f5a0b38f387 - /lib64/libc.so.6 : gsignal

              0x7f5a0b390a78 - /lib64/libc.so.6 : abort

              0x419f29 - /ansys_inc/v222/Tools/mono/Linux64/bin/mono : (null)

              0x5bf128 - /ansys_inc/v222/Tools/mono/Linux64/bin/mono : (null)

              0x40b3feec - Unknown

       

      =================================================================

              Telemetry Dumper:

      =================================================================

      Pkilling 0x7f58dff9b700 from 0x7f5922c7f700

      Pkilling 0x7f58c58b4700 from 0x7f5922c7f700

      Pkilling 0x7f58c50b3700 from 0x7f5922c7f700

      Pkilling 0x7f5949381700 from 0x7f5922c7f700

      Pkilling 0x7f592300b700 from 0x7f5922c7f700

      Pkilling 0x7f599154d700 from 0x7f5922c7f700

      Pkilling 0x7f5990afe700 from 0x7f5922c7f700

      Pkilling 0x7f599174e700 from 0x7f5922c7f700

      Pkilling 0x7f5a054a9700 from 0x7f5922c7f700

      Pkilling 0x7f5990cff700 from 0x7f5922c7f700

      Pkilling 0x7f5949783700 from 0x7f5922c7f700

      Pkilling 0x7f59910ca700 from 0x7f5922c7f700

      Pkilling 0x7f59531b1700 from 0x7f5922c7f700

      Pkilling 0x7f5949984700 from 0x7f5922c7f700

      Pkilling 0x7f59912cb700 from 0x7f5922c7f700

      Pkilling 0x7f5993d55700 from 0x7f5922c7f700

      Pkilling 0x7f5920af9700 from 0x7f5922c7f700

      Pkilling 0x7f5992552700 from 0x7f5922c7f700

      Pkilling 0x7f5921ddd700 from 0x7f5922c7f700

      Pkilling 0x7f58e7fff700 from 0x7f5922c7f700

      Pkilling 0x7f5949f87700 from 0x7f5922c7f700

      Pkilling 0x7f5920efb700 from 0x7f5922c7f700

      Pkilling 0x7f599c2ee700 from 0x7f5922c7f700

      Pkilling 0x7f58df43a700 from 0x7f5922c7f700

      Pkilling 0x7f5922807700 from 0x7f5922c7f700

      Pkilling 0x7f599c4ef700 from 0x7f5922c7f700

      Pkilling 0x7f58df133700 from 0x7f5922c7f700

      Pkilling 0x7f5a0f8ad7c0 from 0x7f5922c7f700

      Stack overflow in unmanaged: IP: 0x49f67d, fault addr: 0x7f58c50bdf48

      ../../../ansys_inc/v222/Framework/bin/Linux64/runwb2 : ligne 22 : 13469 Erreur de segmentation  (core dumped)$MONO_PREFIX/bin/mono "$@"

      "
       
      Any solution, tip, or comment on how to solve this?
    • peteroznewman
      Subscriber

      CygwinX is software to run Linux under a Windows operating system.

      Why would you install the Linux version of Ansys to run under CygwinX
      when you could install the Windows version of Ansys without CygwinX?

    • Barbara Cunha
      Subscriber

      Because Ansys is running on the Linux server and my Windows machine is not powerful enough for my analysis.

    • peteroznewman
      Subscriber

      Ah, I thought you installed the Linux version of Ansys on your Windows machine, which made no sense. Now I understand you are trying to run Workbench on the Linux computer, but have a remote Xterm display on your Windows computer using Cygwin, is that right? 

      Here is a link to the pdf file for remote display support.  You will see that Cygwin is not supported.

      I have successfully run Workbench on a Linux server while displaying the Xterm on my Windows computer using Open Text Exceed TurboX.  You could try the VCN Connect or Turbo VCN since they are supported.

      Why do you need to run Workbench on the Linux computer?  Why not just run the solver on the Linux computer?  At my work, we have installed Remote Solve Manager on the Linux server to automate the submission of jobs to the server from any Windows computer with Ansys installed that is on the same network with the Linux computer.  The Windows computers do not need to be powerful.  If your Linux server doesn't have Remote Solve Manager installed yet, you should request it, but while you are waiting, you could manually write out the input file, copy that file to the Linux computer, use a command line to start the solver, then copy the results file back to your Windows computer. That is such a pain, you will be so glad when Remote Solve Manager is installed.

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