Welcome to the forums. Please post in English or French.

You are not logged in.

#1 Re: Salome-Meca installation » Salome Meca 2021 on WSL2 » 2022-07-21 05:12:20

I did an experiment.
Running Windows 11 and WSL2, build 22621r1
Fresh windows store install of Ubuntu 22.04

install golang from a linux binary
sudo tar -C /usr/local -xzf go1.18.4.linux-amd64.tar.gz

install singularity from a debian package:
wget -c https:/ /github.com/sylabs/singularity/releases/download/v3.10.1/singularity-ce_3.10.1-jammy_amd64.deb
sudo apt install ./singularity-ce_3.10.1-jammy_amd64.deb

prep directories - not sure if it is required, but I took a suggestion from this forum.
sudo rm -r /dev/shm
sudo mkdir /dev/shm
sudo chmod 777 /dev/shm
chmod 777 .singularity/

Also, from a suggestion of this forum:
curl -sfL https:/ /install.goreleaser.com/github.com/golangci/golangci-lint.sh | sh -s -- -b $(go env GOPATH)/bin v1.21.0

sudo singularity run --app install ./salome_meca-lgpl-2021.0.0-2-20211014-scibian-9.sif
singularity run --app install ./salome_meca-lgpl-2021.0.0-2-20211014-scibian-9.sif


Now, running the script does find the GPU, but it generates errors and exits.

./salome_meca-lgpl-2021.0.0-2-20211014-scibian-9
not exist: /etc/krb5.conf
/usr/bin/nvidia-smi
**************************************
INFO : Running salome_meca in GPU mode
**************************************
runSalome running on EGR
Searching for a free port for naming service: 2819 - OK
Searching Naming Service  + found in 0.1 seconds
Searching /Kernel/Session in Naming Service  +++++SALOME_Session_Server: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /.singularity.d/libs/libGLX.so.0)
Traceback (most recent call last):
  File "/opt/salome_meca/Salome-V2021-s9/modules/KERNEL_V9_7_0/bin/salome/orbmodule.py", line 181, in waitNSPID
    os.kill(thePID,0)
ProcessLookupError: [Errno 3] No such process

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/salome_meca/appli_V2021/bin/salome/runSalome.py", line 694, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
  File "/opt/salome_meca/appli_V2021/bin/salome/runSalome.py", line 639, in startSalome
    session=clt.waitNSPID("/Kernel/Session",mySessionServ.PID,SALOME.Session)
  File "/opt/salome_meca/Salome-V2021-s9/modules/KERNEL_V9_7_0/bin/salome/orbmodule.py", line 183, in waitNSPID
    raise RuntimeError("Process %d for %s not found" % (thePID,theName))
RuntimeError: Process 12993 for /Kernel/Session not found


On the hypothesis that the singularity container had a strict x-server requirement, I tested x11-apps.
sudo apt install x11-apps

NOTE: xclock and xcalc display properly and run fine.

vcxsrv on Xlaunch on windows did not change the result.



I appreciate your consideration and suggestions to install the singularity salome-meca either on Ubuntu, or in a workably fast installation following the instructions for the prepared debian distribution.

Kind regards.

#2 Re: Salome-Meca installation » Salome Meca 2021 on WSL2 » 2022-07-20 22:13:47

Following the instructions of post 1 of this thread, I obtained a running version of salome-meca.
It had a few problems:
1. It ran in software GL mode, although my computer has a mobile Nvidia card
2. Perhaps as a consequence, updating the screen was often incomplete, but the screen could be updated by switching between steps in aster-study.
3. Although the interactive performance was adequate for a simple tutorial, running the tutorial consumed very little resource, but consumed about 2 hours of wall-clock time (Divijay Patankar example 2 https: / / youtu.be/qZxoJVP0L98).

In response I have begun to explore WSL2/Ubuntu22.04/Singularity.
Should new installations use Apptainer in lieu of singularity ?
If using the debian package for singularity (https: / / github.com/sylabs/singularity/releases/download/v3.10.1/singularity-ce_3.10.1-jammy_amd64.deb) , is it necessary to also build golang and other pre-requisites of a source installation ?

Thank-you