I have successfully installed Abaqus 2017 on Ubuntu 16.04, but fail completely on any newer Ubuntu version. Here is the routine that leads to the problem.
All prerequisites that are listed here (install ksh and what not) are met.
Then, the usual shell script edit has to be made to mimic a supported OS (see also here). From the folder where
StartTUI.sh sit I run
and insert at line 4
Running then StartGUI.sh produces the error
ERROR: Cannot wait for process "/home/gluege/Software/ABQ/2 /SIMULIA_AbaqusServices/Linux64/1/inst/linux_a64/code/bin /DSYInsAppliTUI" "-CDpath" "/home/gluege/Software/ABQ/2 /SIMULIA_AbaqusServices/Linux64/1/"
An inspection shows that
cannot find the shared libraries that are to be found in
./inst/linux_a64/code/bin/ (as seen from the folder where
StartTUI.sh is located).
Upon adding the path to the default library search folders by
and informing the OS by
the error message when running
Cannot change log file to /InstallData-2018_06_21-180430+0100 /log/2018_06_21-180430+0100/Replay.xml Error stack: Unable to create the directory '/InstallData-2018_06_21-180430+0100', reason: Error num: 13 Permission denied Error code: Type: FATAL, Error: 2, Owner: 103
I find it strange that the installer wants to put logs in the root folder, but anyway: I suppose that this issue could be resolved by executing all scripts with root privileges. So I run
sudo env LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/gluege/Software/ ABQ/2/SIMULIA_AbaqusServices_CAA_API/Linux64/1/inst/linux_a64 /code/bin/ ./inst/linux_a64/code/bin/DSYInsAppliTUI -CDpath /home/gluege/Software/ABQ/2/SIMULIA_AbaqusServices/Linux64/1/
to start the terminal-based installer, exporting the library path before the command. The installer starts, but instead of showing the text strings, the variable names are shown, like so:
DSYInsControler.Title.Template(3DEXPERIENCE R2017x, Abaqus Simulation Services, , DSYInsControler.Welcome.Title()) ___________________________________________________________________ DSYInsControler.TextTUI.DefaultSelection(Next)
It is impossible to go through the installation like this, who knows what other variables are not accessed correctly. Applying the same technique
sudo env ... to the real installation entry point
StartTUI.sh just produces the above error
Cannot wait for process.
So, what can I do to get the installer running? Does anyone know what exactly breaks the installer when going from 16.04 to 18.04??