Coreform 202x Segmentation faults (Ubuntu 18.04)

jsilva.mit · October 22, 2021, 5:07pm

The solution that you provided in the link does not work. I don’t have the files

/var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb
/var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb

The only ones I have on /var/cache/apt/archives/ are the following:

duplicity_0.7.17-0ubuntu1_amd64.deb  
python-fasteners_0.12.0-3_all.deb  
python-lockfile_1%3a0.12.2-2_all.deb
librsync1_0.9.7-10build1_amd64.deb
python-gi_3.26.1-2_amd64.deb
python-monotonic_1.1-2_all.deb

Let me know if you have any other ideas.

Thanks!

scot · October 22, 2021, 5:17pm

Try this:

sudo apt-get purge libglvnd0
sudo apt-get autoremove
sudo apt-get clean
sudo apt-get install libglvnd0

The blessing and curse with Linux is that you have complete control over everything on the system. This also means almost every install is custom in some way, and there’s hundreds of ways to break things. Is there an IT administrator you can talk to for help?

jsilva.mit · October 22, 2021, 5:22pm

@scot,

Thanks. Before I try the above commands, do you foresee that it might break other packages that I already have installed? Is there any other workaround to get Coreform Cubit 2021.5 to work on my Ubuntu 18.05 LTS ?

I don’t have an IT administrator that can help me.

Thanks,
Josimar

scot · October 22, 2021, 5:32pm

It may break other packages, I don’t know what you have installed on your system.

If you don’t want to jeopardize your system, you can install Docker and I can give you a Dockerfile that will let you run Cubit inside a Docker container and connect to the GUI in your browser.

jsilva.mit · October 22, 2021, 5:38pm

@scot,

Could you send me the Dockerfile so that I can run Cubit inside the Docker? This might work better for now.

Thanks,
Josimar

scot · October 22, 2021, 6:16pm

centos7-cubit-gui.zip (1.1 KB)
Download the Cubit 2021.5 RPM installer, name it Cubit.rpm, and place it next to the Dockerfile. Name your license file license.lic, and also place it next to the Dockerfile. Also make sure you have the included supervisord.conf next to the Dockerfile.

Build the image like this with your terminal in the Dockerfile directory:

sudo docker build --build-arg VERSION=2021.5 -t cubit_gui .

Run the container like this:

sudo docker container run -d -p 6080:6080 -p 5900:5900 -v /dev/shm:/dev/shm -v <path to a folder on your machine>:/home/coreform/data  --name cubit_gui centos_gui_1

Then open up a browser tab and connect to http://localhost:6080/#/ in your browser. That’ll show a GUI where you can then run Cubit. Save any data in /home/coreform/data and it’ll be accessible in the path you specified as a volume mount.

jsilva.mit · October 22, 2021, 6:28pm

@scot ,

Thanks for the detailed explanation. I have a question regarding the license:

I am accessing a floating license that is hosted in a different computer. In the previous instruction for the docker, how do I put my license in a license.lic file?

Thanks,
Josimar

scot · October 22, 2021, 6:29pm

Write a file like this one:

HOST <IP address or hostname> ANY 5053
ISV csimsoft

Name it license.lic.

jsilva.mit · October 22, 2021, 6:43pm

@scot

Thanks again for the detailed help. I am new to docker as well. Right now I am having the following error for the second command that you sent above:

The command that I typed is the following:

sudo docker container run -d -p 6080:6080 -p 5900:5900 -v /dev/shm:/dev/shm -v ~/Coreform/Docker/Data --name cubit_gui centos_gui_1

The error message is the following:

Unable to find image ‘centos_gui_1:latest’ locally
docker: Error response from daemon: pull access denied for centos_gui_1, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied.
See ‘docker run --help’.

Let me know if you have any insights.

Thanks,
Josimar

scot · October 22, 2021, 6:47pm

Sorry, switch cubit_gui and centos_gui_1. The --name argument is the name of the container, the last argument is the name of the image you built with docker build and should match the -t argument there.

jsilva.mit · October 22, 2021, 6:54pm

Thanks,

The correct command is then

sudo docker container run -d -p 6080:6080 -p 5900:5900 -v /dev/shm:/dev/shm -v :/home/coreform/data --name centos_gui_1 cubit_gui

jsilva.mit · October 22, 2021, 6:57pm

@scot

Now the issue is that coreform cubit cannot connect to my license server.

How can I give you the rlm_diagnostic without disclosing my remote server information to the general public?

Thanks,
Josimar

Here is the image of the error message:

scot · October 22, 2021, 7:04pm

To fix that, instead of passing in the -p options when you run the docker container, run it with --network=host. Your container will then use the host network instead of port forwarding, and should be able to reach your license server.

jsilva.mit · October 22, 2021, 7:15pm

@scot

Ok, so the new updated command should be:

sudo docker container run -d --network=host -v /dev/shm:/dev/shm -v :/home/coreform/data --name centos_gui_1 cubit_gui

jsilva.mit · October 22, 2021, 7:19pm

@scot,

When I tried the command above with --network=host, then now the http://localhost:6080/#/ does not work anymore. I get a failed connection error, see below.

Would you know how to fix this?

Thanks,
Josimar

scot · October 22, 2021, 7:20pm

What does sudo docker logs centos_gui_1 say?

jsilva.mit · October 22, 2021, 7:23pm

@scot,

Here is the output:

output.zip (3.8 KB)

scot · October 22, 2021, 7:28pm

The error is here:

127.0.0.1 - - [22/Oct/2021 19:17:10] connecting to: localhost:5900
handler exception: [Errno 111] Connection refused

Open ports 5900 and 6800 in your firewall.

jsilva.mit · October 22, 2021, 7:39pm

@scot,

Unfortunately still does not work:

Here is the output from sudo docker logs centos_gui_1:

output.zip (2.5 KB)

I open up the ports that you mentioned:

sudo ufw status verbose

Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), deny (routed)
New profiles: skip

To                         Action      From
--                         ------      ----
22/tcp                     ALLOW IN    Anywhere                  
22                         ALLOW IN    Anywhere                  
5900                       ALLOW IN    Anywhere                  
6800                       ALLOW IN    Anywhere                  
6080                       ALLOW IN    Anywhere                  
22/tcp (v6)                ALLOW IN    Anywhere (v6)             
22 (v6)                    ALLOW IN    Anywhere (v6)             
5900 (v6)                  ALLOW IN    Anywhere (v6)             
6800 (v6)                  ALLOW IN    Anywhere (v6)             
6080 (v6)                  ALLOW IN    Anywhere (v6)

scot · October 22, 2021, 7:49pm

If that’s not working, then you’ll have to run the docker container with the -p options again and talk to your network administrator about connecting your docker container to your local network or VPN that your license server is on.