Learning Forum

[KirillKabalyk]

Hello,

currently I faced the following issue: running SLES 12 SP3 the GUI of Ansys Mechanical 20R1 would not start. Instead, it throws the following message:

[tsiriaks]

Hi Kirill,nAre you using this Linux machine directly or remotely ? If remote, describe how.nThe error doesn't show much info. Could you set the following environment variablesnANSYS_FRAMEWORK_DEVELOPMENT=1nWBTRACING=truenANSYS_FRAMEWORK_DIAGS=Utilities.TraceToConsolenThen, launch Workbench withn/runwb2 2>~/stderr.log 1>~/stdout.lognand check the error from ~/stderr.log and ~/stdout.lognnAlso, please provide the output of the followingsnlspci -vnn | grep VGA -A 12nglxinfo | grep OpenGLnnThanks,nWinn

[KirillKabalyk]

Hello, Win.nnThanks a lot for a quick reply.This is a remote Linux server. It has 16 compute-nodes and one common server which shares the disk space with each node. I access it from a Windows PC through a local network at my institute. Firstly, I create an SSH-tunnel using Putty and then use it to establish a VNC connection. I use RealVNC viewer as a remote desktop client.Below are the outputs you requested:nAdditionaly, here is the status of the environment variables:nThese are the same at server5 where the logs are taken from. However, at server5 the system has been already upgraded to SLES 12 SP4. But the CommandBar and DockingPane errors are still there regardless of the system version.nnThanks again,nnKirilln

[tsiriaks]

Hi Kirill,nThank you for the info. Unfortunately, ANSYS employees are not allowed to download files/attachment. Could you post screenshots of the content inline with text or copy the content out and post it here ? If those *.log content is too long, you can focus only on the 'error' part.nThank you,nWinn

[KirillKabalyk]

Ok, nSo, below are the outputs:n1. glxinfo:n----------------------------------------------------------------nserver5:/home/kirill # glxinfo | grep OpenGLnOpenGL vendor string: VMware, Inc.nOpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits)nOpenGL version string: 3.0 Mesa 18.0.2nOpenGL shading language version string: 1.30nOpenGL extensions:n------------------------------------------------------------------n2. lspci:n----------------------------------------------------------------------------------------nserver5:/home/kirill # lspci -vnn | grep VGA -A 12n01:00.1 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA G200EH [102b:0533] (prog-if 00 [VGA controller])ntSubsystem: Hewlett-Packard Company Device [103c:330e]ntFlags: bus master, fast devsel, latency 0, IRQ 17ntMemory at f9000000 (32-bit, prefetchable) [size=16M]ntMemory at fb9e0000 (32-bit, non-prefetchable) [size=16K]ntMemory at fb000000 (32-bit, non-prefetchable) [size=8M]nt[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]ntCapabilities: [a8] Power Management version 3ntCapabilities: [b0] MSI: Enable- Count=1/1 Maskable- 64bit+ntCapabilities: [c0] Express Legacy Endpoint, MSI 00ntKernel driver in use: mgag200ntKernel modules: mgag200n-------------------------------------------------------------------------------------------n3. stderr.log:n-------------------------------------------------------------------------------------------------n******************************************************************************n*** A fatal error has occurred within AnsysWBU.exe and it must be closed...***n******************************************************************************n--------------------------------------------------------------------------------------------------n4. stdout.log:nnn

[tsiriaks]

Thank you Kirill.nCan you try setting the following environment variablesnLIBGL_ALWAYS_INDIRECT=1nLIBGL_ALWAYS_SOFTWARE=1nLD_LIBRARY_PATH=/home/ansys_inc/v201/Framework/bin/Linux64/Mesanthen start Workbench with this commandn/home/ansys_inc/v201/Framework/bin/Linux64/runwb2 -oglmesannDoes this help ? nIf not,nDo you have install.err file under /home/ansys_inc ? If so, please post its content.nPlease try another debug method by setting these environment variablesnANSYS_FRAMEWORK_DEVELOPMENT=1nMWDEBUG=truenMWOUTPUT=stdoutnthen launch Workbenchn/home/ansys_inc/v201/Framework/bin/Linux64/runwb2 2>~/stderr.log 1>~/stdout.lognand post the content of these logs again.nThanks,nWinn

[KirillKabalyk]

Hello, Win,nnThanks again for the reply. The method with -oglmesa did not help, unfortunatelly. nI have the install.err file, but its contents concern only couple of comments about the installation of version 19.0, so its basically empty.nEmpty is also stderr.log after I set the variables you requested.nBelow are the screenshots from stdout.log after the Failed loading DockingPane error (Design Modeller):nnnBelow is also some content of the stdout.log after the Failed loading Commandbar error (Mechanical):nnMany thanks for assistance,nnKirill

[KirillKabalyk]

My another thought is:nthe /home/ansys_inc directory I currently use is actually located on server node's disk and is shared with each computing node. Previously (until 2019 R3, I suppose) this approach allowed us to run all WB applications on computing nodes without problems. Could it be that after changes introduced in 2019 R... this way of sharing the /home/ansys_inc directory might now cause this issue? n

[tsiriaks]

Hmm, the error is the same as earlier. nWhat if you create a test user account, does it encounter the same issue ?nFor the other thought, as long as each compute node has all required prerequisites installed and ran product configurations, this shouldn't be an issue. You can check Linux installation guide from online ANSYS Help. For prerequisites, check Chapter 2. For product configurations, check section 4.5.3.nDid you go ahead and try updating the LSB ?n

[KirillKabalyk]

Thanks a lot for your response. The actual configuration is quite complex and hence I have taken the cylinder to study the effect of various parameters on the incident radiation. So far I've tried the following:nKeeping other parameters constant I've changed:nTheta Division/pixels(up to 75)nPhi Division/pixels(up to 75)nBeam width(1e-06The shell output is:nkirill@server5:~> lsb_release -anLSB Version:tcore-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarchnDistributor ID:tSUSEnDescription:tSUSE Linux Enterprise Server 12 SP4nRelease:t12.4nCodename:tn/annThe Yast pkglist.txt is:nStan (state) | Pakiet (package) | Podsumowanie (summary) | Zainstalowano (dostepne) (installed-available) | Rozmiar (size)nn[Pozostaw] [Keep] | lsb | Linux Standard Base Core | 4.0-20.1.1 | 110 Bn[Pozostaw] [Keep] | lsb-release | Linux Standard Base Release Tools | 2.0-28.1 (2.0-18.1.1) | 16,2 KiBnnI may try to uninstall lsb-release (2.0) to leave the 4.0 version only, however since I'm not a system administrator, I will not do this unless I know whether it is safe.nnThanks again,nKirillnnn n

[tsiriaks]

Thank you for the input Kirill. That sounds good.nFor the LSB, I agree, it's best to have your system admin do this. Probably they can just update the version without having to uninstall the 2.0 but this is up to them.n