CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   ANSYS (https://www.cfd-online.com/Forums/ansys/)
-   -   Installation of Ansys 19 on Ubuntu 18.4 (https://www.cfd-online.com/Forums/ansys/203041-installation-ansys-19-ubuntu-18-4-a.html)

victor pira June 15, 2018 10:00

Installation of Ansys 19 on Ubuntu 18.4
 
I am trying to intsall ANSYS 19 on Ubuntu 18.4. I have followed the brilliant installation guide here but sadly some issues persisted. Namely:


- The installation wizard freezes at ca. 93%, the last action being "Created service script: arcnode". When it is shut down manually, it does not provide any error log and ANSYS is still executable but one does not know whether the installation was truly succesful.


- The Design Modeler is unable to be opened by the Workbench.



Tested solutions:

- I have installed all the packages recommended in the link above.
- I have tried to execute the .../runwb2 -oglmesa
- I have tried LD_LIBRARY_PATH=/ansys_inc/v190/Framework/bin/Linux64/Mesa

rweber August 9, 2018 07:45

Same problem
 
I have the same issue, could you find any solution?

lycastrog August 10, 2018 13:14

I have the same issue, could you find any solution? Please anyone...

buck2202 August 13, 2018 02:50

I just spent a limited amount of time trying to debug this after a clean install of Mint 19 (based on ubuntu 18.04)--the INSTALL script does accepts a -debug flag, but the point where the installer hangs is still fairly opaque.

FWIW, things fell apart for me in script
Code:

ansys_inc/v162/commonfiles/configs/linx64/config/AnsConfigWB.sh
at the first execution of line 265
Code:

$WB_INSTALL_DIR/.workbench -cmd $exeFile -RegServer
The first successful execution would report
Code:

RegSvr32: DllRegisterServer in /usr/ansys_inc/v162/aisol/dll/linx64/libans.common.clrhostmonou.so succeeded.
but mine would just sit there forever. I'm guessing the problem stems from Ansys's integration mess with Mono.

At that point, I reinstalled ubuntu 16.04 in a virtualbox instance, installed ansys there, tar'd up the whole directory, moved it to my 18.04 installation, and extracted it. I'm able to launch fluent without issue, which luckily is all I care about right now. Workbench in v162 depends on libpng12 which is not in ubuntu 18.04's repos, but maybe you'll have better luck with 19. I'm stuck with 16 because the behavior of my UDF code mysteriously changes at v17+

ztnuaa August 18, 2018 01:23

Dear Fellows:
I just upgraded my Ubuntu 16.04 to 18.04 yesterday. And I have ansys 19.1 installed in 16.04. Fluent and ICEM works fine in 16.04.
But in 18.04, ICEM can't start. the error message is:

Quote:

ICEM_ACN is "/home/zt/software/ansys_inc/v191/icemcfd/linux64_amd".
ANSYSLIC_DIR is set to /home/zt/software/ansys_inc/shared_files/licensing
LD_LIBRARY_PATH is "/home/zt/software/ansys_inc/v191/icemcfd/linux64_amd/lib:/usr/local/tecplot/360ex_2017r2/bin:/usr/local/tecplot/360ex_2017r2/bin/sys:/usr/local/lib::/home/zt/software/ansys_inc/v191/icemcfd/linux64_amd/bin:/home/zt/software/ansys_inc/v191/icemcfd/linux64_amd/dif/iges:/home/zt/software/ansys_inc/v191/icemcfd/linux64_amd/../../Framework/bin/Linux64".
args =
[1] 16983 segmentation fault (core dumped) /home/zt/software/ansys_inc/v191/icemcfd/linux64_amd/bin/icemcfd
When i reinstalled ansys 19.1, I got stuck at 89%. Then I forced to shutdown the installer. ICEM still gives the same segmentation fault error.

And i think this error is not something like the "segmentation violation error" which need xfonts-75dpi and xfonts-100dpi to be installed.

I tried :
1.export LD_LIBRARY_PATH=/ansys_inc/v190/Framework/bin/Linux64/Mesa (because i messed up some mesa libraries when i upgrade my system)
2.upgrade mesa to the lateset using ppa
3.checked arguments available in the icemcfd script, all of them didn't work

Did you guys have the problem with icemcfd?

Thank you for helping!

Regards

ztnuaa August 31, 2018 00:51

Hi,
I solved the problem with ICEMCFD a few days ago.
I check the start script file of icemcfd at "ansys_inc/v191/icemcfd/linux64_amd/bin"
There are two solutions:
Solution 1. If you don't want to change the icemcfd start script, just run the following comman:
Code:

icemcfd -log tmp.log
-log is a icemcfd argument, tmp.log is the log file generated at your pwd.
Solution2. If you use other argument when you start icemcfd, the following solution may be not very good. (I don't use arguments when start icemcfd, so it works well for me)
First- cd to your icemcfd bin dir:
Code:

cd /usr/ansys_inc/v191/icemcfd/linux64_amd/bin
Then: edit the icemcfd by any text editor you want, here we use gvim:
Code:

gvim icemcfd
change line 607:
Code:

      eval "$ICEM_ACN/bin/med" "$args"
to:
Code:

"$ICEM_ACN/bin/med" $args
This may cause a error message when icemcfd started:"Unknown filetype", just ignore it.
or without $args
Code:

"$ICEM_ACN/bin/med"
I think it's caused by a bug of "eval" shell command at ubuntu 18.04.
Hope this solution can help

ANV October 24, 2018 04:52

Quote:

Originally Posted by buck2202 (Post 702400)
I just spent a limited amount of time trying to debug this after a clean install of Mint 19 (based on ubuntu 18.04)--the INSTALL script does accepts a -debug flag, but the point where the installer hangs is still fairly opaque.

FWIW, things fell apart for me in script
Code:

ansys_inc/v162/commonfiles/configs/linx64/config/AnsConfigWB.sh
at the first execution of line 265
Code:

$WB_INSTALL_DIR/.workbench -cmd $exeFile -RegServer
The first successful execution would report
Code:

RegSvr32: DllRegisterServer in /usr/ansys_inc/v162/aisol/dll/linx64/libans.common.clrhostmonou.so succeeded.
but mine would just sit there forever. I'm guessing the problem stems from Ansys's integration mess with Mono.

At that point, I reinstalled ubuntu 16.04 in a virtualbox instance, installed ansys there, tar'd up the whole directory, moved it to my 18.04 installation, and extracted it. I'm able to launch fluent without issue, which luckily is all I care about right now. Workbench in v162 depends on libpng12 which is not in ubuntu 18.04's repos, but maybe you'll have better luck with 19. I'm stuck with 16 because the behavior of my UDF code mysteriously changes at v17+

Were you able to figure out the integration with mono issue?

Thanks,
Amey

Mojtaba.a April 25, 2019 05:51

Quote:

Originally Posted by ztnuaa (Post 704782)
Hi,
I solved the problem with ICEMCFD a few days ago.
I check the start script file of icemcfd at "ansys_inc/v191/icemcfd/linux64_amd/bin"
There are two solutions:
Solution 1. If you don't want to change the icemcfd start script, just run the following comman:
Code:

icemcfd -log tmp.log
-log is a icemcfd argument, tmp.log is the log file generated at your pwd.
Solution2. If you use other argument when you start icemcfd, the following solution may be not very good. (I don't use arguments when start icemcfd, so it works well for me)
First- cd to your icemcfd bin dir:
Code:

cd /usr/ansys_inc/v191/icemcfd/linux64_amd/bin
Then: edit the icemcfd by any text editor you want, here we use gvim:
Code:

gvim icemcfd
change line 607:
Code:

      eval "$ICEM_ACN/bin/med" "$args"
to:
Code:

"$ICEM_ACN/bin/med" $args
This may cause a error message when icemcfd started:"Unknown filetype", just ignore it.
or without $args
Code:

"$ICEM_ACN/bin/med"
I think it's caused by a bug of "eval" shell command at ubuntu 18.04.
Hope this solution can help

What's it got to do with the problem in the first message? The freezing while installing Ansys?
Any solutions to this?

ztnuaa April 25, 2019 06:08

Hi Mojtaba,
Sorry, I don't know. Since I only use ICEM and Fluent. This problem doen't bother me.
FYI, I also installed Ansys in a workstation running CentOS6.9. The installation freezing problem didn't show up.
ztnuaa

ginggs October 3, 2019 10:30

Quote:

Originally Posted by ztnuaa (Post 704782)
I think it's caused by a bug of "eval" shell command at ubuntu 18.04.

There was a bug (LP: #1739505) in csh in Ubuntu 18.04, but it has been fixed now.


All times are GMT -4. The time now is 15:32.