[Solved] Salome Meca 2021 on OpenSuSE

edoulin · 2022-01-25 08:14:04

I've been using Code_Aster and SalomeMeca for years (with both compiled and univeral binaries installed) But for now, I get troubles with the new installation procedure.
I had a look in the other posts but didn't find what's wrong. It occurs when I want to prepare the container’s environment and generate the laucher:

singularity run --app install salome_meca-lgpl-2021.0.0-1-20210811-scibian-9.sif

Provide:

The starter script must be installed in /opt/Salome_Meca.
ERROR: no write access to /opt/Salome_Meca.

I already checked the "write access" on all the directories tested (766 mode).
Whatever I try:
1) use of the native OS singularity installed version (3.8.5)
2) use of a compiled singularity version (3.7.0) as described in the installation procedure
3) change for a new directory and it's permissions
4) switch for a other user.

..nothing change!

However, the universal binaries Salome 9.7.0 downloaded from the salome platform works fine
OS : OpenSuSE Leap 15.3
OpenGL: nVidia native card
Linux 64 bits

Has someone an idea to solve this problem?
Thanks for your answers

Best regards

Erwann

Last edited by edoulin (2022-01-31 21:15:14)

hberro · 2022-01-26 22:19:34

Can you please avoid /opt/salome_meca ?

Within the container this is where salome meca is installed and a conflict might be occurring.

I would first try to move the sif to the user's home folder, say

$HOME/containers/smeca2021

And then run the installation script which you provided.

edoulin · 2022-01-28 08:24:52

Thanks but nothing has changed

ERROR: no write access to /home/containers/smeca2021.

... also with root privileges

Last edited by edoulin (2022-01-28 08:29:09)

hberro · 2022-01-28 08:50:26

This is odd... Can you try running the sif file directly

singularity xxx sif

edoulin · 2022-01-28 12:57:25

Salome Meca runs within the container but I can't interact with my own
system.
I don't understand why it needs to have a write access on the source
directory (/home/containers/smeca2021) rather than the destination
directory (/opt/salome meca)

jeanpierreaubry · 2022-01-28 15:25:10

hello edoulin

maybe some of your question concerning accessing directories outside the container are answered in post id=26122

i have a normally working code_aster from the container without using salome_meca and this on opensuse

but i am not all that convinced this is an improvement (when knows what ones is doing) over the old versions

jean pierre aubry

mecour · 2022-01-29 12:29:31

Hello,

another question from long time user of stand alone version who is now forced to use some container :-). Can you please help me with this issue, on opensuse15.3:

mecour@localhost:~/bin> ./salome_meca-lgpl-2021.0.0-0-20210601-scibian-9
Lmod Warning: The environment MODULEPATH has been changed in unexpected ways.
Lmod is unable to use given MODULEPATH. It is using:
"/usr/share/lmod/modulefiles".
Please use "module use ..." to change MODULEPATH instead.

/usr/bin/nvidia-smi
**************************************
INFO : Running salome_meca in GPU mode
**************************************
runSalome running on localhost.localdomain
Searching for a free port for naming service: 2813 - OK
Searching Naming Service + found in 0.1 seconds
Searching /Kernel/Session in Naming Service +++++++Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyTraceback (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 5067 for /Kernel/Session not found
--- Error during Salome launch ---

Historically I was able to find solution to this problem, see forum id 24470. So now in container I really can't find the solution.

thank you.

mecour

AsterO'dactyle · 2022-01-29 18:14:27

export DISPLAY=:1.0 ?

hberro · 2022-01-31 09:28:20

edoulin wrote:

Salome Meca runs within the container but I can't interact with my own
system.
I don't understand why it needs to have a write access on the source
directory (/home/containers/smeca2021) rather than the destination
directory (/opt/salome meca)

try to bind the directory that you would like to be accessible from within the container using the -B flag, for example :

singularity run -B $HOME/mydata:/mydata xxxxxxx.sif

$HOME/mydata is supposed then to be accessible in /mydata from within the container so you can access the file system.

Side note : Singularity is supposed to mount by default your home directory. This is the common behaviour but I do not know why on your installation this does not seem to be the case...

hberro · 2022-01-31 09:32:08

mecour wrote:

Hello,
another question from long time user of stand alone version who is now forced to use some container :-). Can you please help me with this issue, on opensuse15.3:
Historically I was able to find solution to this problem, see forum id 24470. So now in container I really can't find the solution.
thank you.
mecour

Hello mecour,

try :

unset MODULEPATH_ROOT

just before running the container (there might be a conflict happening there from your opensuse bash settings)

mathieu.courtois · 2022-01-31 15:48:47

/home/containers != $HOME/containers

edoulin · 2022-01-31 21:12:39

Hi,

I can launch SalomeMeca and I now have access to my data.
I put this in the .bashrc

    export SMECA_VERSION=salome_meca-lgpl-2021.0.0-0-20210601-scibian-9.sif
    export SMECA_PATH=/home/containers/smeca
    alias salome2021='singularity run --nv --bind /home:/home $SMECA_PATH/$SMECA_VERSION'

Thanks to all

#1 2022-01-25 08:14:04

[Solved] Salome Meca 2021 on OpenSuSE

#2 2022-01-26 22:19:34

Re: [Solved] Salome Meca 2021 on OpenSuSE

#3 2022-01-28 08:24:52

Re: [Solved] Salome Meca 2021 on OpenSuSE

#4 2022-01-28 08:50:26

Re: [Solved] Salome Meca 2021 on OpenSuSE

#5 2022-01-28 12:57:25

Re: [Solved] Salome Meca 2021 on OpenSuSE

#6 2022-01-28 15:25:10

Re: [Solved] Salome Meca 2021 on OpenSuSE

#7 2022-01-29 12:29:31

Re: [Solved] Salome Meca 2021 on OpenSuSE

#8 2022-01-29 18:14:27

Re: [Solved] Salome Meca 2021 on OpenSuSE

#9 2022-01-31 09:28:20

Re: [Solved] Salome Meca 2021 on OpenSuSE

#10 2022-01-31 09:32:08

Re: [Solved] Salome Meca 2021 on OpenSuSE

#11 2022-01-31 15:48:47

Re: [Solved] Salome Meca 2021 on OpenSuSE

#12 2022-01-31 21:12:39

Re: [Solved] Salome Meca 2021 on OpenSuSE

Board footer