Salome_Meca 2024 on WSL2 - C_A missing

k_zurawski

Hello,
I have just installed Ununtu 22.04 under WSL2 and Apptainer. I'm getting the same error as in case of Debian 12.

No version of C_A is available through GUI.

Terminal returns this information:
`u22@W2:~$ apptainer run salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif

running salome_meca in software rendering mode
++ using container salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
++ using software rendering mode (should use mesa_salome starter)
AsterStudy: ven.-10-15:46:47.479 AsterStudy is activating...
AsterStudy: ven.-10-15:46:47.479 Creating workspace...
AsterStudy: ven.-10-15:46:47.497 Refreshing configuration on localhost...
AsterStudy: ven.-10-15:46:57.730 workspace is ready.
AsterStudy: ven.-10-15:46:59.758 AsterStudy activated
AsterStudy: ven.-10-15:47:01.639 Refreshing configuration on localhost...
double free or corruption (out)
[W2:93043] *** Process received signal ***
[W2:93043] Signal: Abandon (6)
[W2:93043] Signal code: (-6)
[W2:93043] [ 0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140)[0x7fb3ef9f3140]
[W2:93043] [ 1] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7fb3ecdeed51]
[W2:93043] [ 2] /lib/x86_64-linux-gnu/libc.so.6(abort+0x123)[0x7fb3ecdd8537]
[W2:93043] [ 3] /lib/x86_64-linux-gnu/libc.so.6(+0x7a458)[0x7fb3ece30458]
[W2:93043] [ 4] /lib/x86_64-linux-gnu/libc.so.6(+0x8174a)[0x7fb3ece3774a]
[W2:93043] [ 5] /lib/x86_64-linux-gnu/libc.so.6(+0x82d78)[0x7fb3ece38d78]
[W2:93043] [ 6] /usr/lib/python3/dist-packages/PyQt5/QtCore.abi3.so(+0x2137ad)[0x7fb399efc7ad]
[W2:93043] [ 7] /usr/lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x1131a7)[0x7fb3f70271a7]
[W2:93043] [ 8] /usr/lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x2686c7)[0x7fb3f717c6c7]
[W2:93043] [ 9] /usr/lib/x86_64-linux-gnu/libpython3.9.so.1.0(Py_FinalizeEx+0x74)[0x7fb3f70fba84]
[W2:93043] [10] SALOME_Session_Server_No_Server(Z18AbstractGUIAppMainI14GUIAppNewStyleEiiPPc+0x2651)[0x560ddbf75ef1]
[W2:93043] [11] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7fb3ecdd9d7a]
[W2:93043] [12] SALOME_Session_Server_No_Server(start+0x2a)[0x560ddbf7117a]
[W2:93043] *** End of error message ***`

as_run doesn't work as well:

`Singularity> as_run Case02b.export
pas d'acccès en écriture dans /local00/tmp/astk_u22

EXIT_CODE=4
Singularity>`

Could anyone check under WSL if this error occurs?

I had the same situation with Salome_Meca 2023. On the other hand v2022 runs, is unstable sometimes, but runs.

mf

k_zurawski

Hello,

don't know the reason for your problem, but maybe also try Ubuntu 24.04LTS in WSL2. In my case, see other thread, it was nearly flawless (difference: native Ubuntu 24.04LTS, no WSL).

Mario.

hberro

k_zurawski

Try binding /local00 to any local directory on your pc.

mkdir /tmp/local00
./salome-meca... -B /tmp/local00:/local00

Let me know if that helps

k_zurawski

I noticed something, when I'm running SM2022 (which works ok) I'm getting in terminal normal info:

INFO : Running salome_meca in software rendering mode

runSalome running on W2
Searching for a free port for naming service: 2810 - OK
Searching Naming Service + found in 0.1 seconds
Searching /Kernel/Session in Naming Service ++++++++ found in 4.0 seconds
Start SALOME, elapsed time : 4.3 seconds

Warning: module HexoticPLUGIN is improperly configured!
Module HexoticPLUGIN will not be available in GUI mode!

Warning: module GHS3DPLUGIN is improperly configured!
Module GHS3DPLUGIN will not be available in GUI mode!

Warning: module GHS3DPRLPLUGIN is improperly configured!
Module GHS3DPRLPLUGIN will not be available in GUI mode!

Warning: module BLSURFPLUGIN is improperly configured!
Module BLSURFPLUGIN will not be available in GUI mode!

Warning: module NETGENPLUGIN is improperly configured!
Module NETGENPLUGIN will not be available in GUI mode!

Warning: module HYBRIDPLUGIN is improperly configured!
Module HYBRIDPLUGIN will not be available in GUI mode!

Warning: module GMSHPLUGIN is improperly configured!
Module GMSHPLUGIN will not be available in GUI mode!

When I'm running SM2023:

running salome_meca in software rendering mode
++ using container salome_meca-lgpl-2023.1.0-4-20240327-scibian-10.sif
++ using software rendering mode (should use mesa_salome starter)

and it doesn't work.

When I'm running 2024 I'm getting the same output:

running salome_meca in software rendering mode
++ using container salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
++ using software rendering mode (should use mesa_salome starter)

SM 22 is looking for empty port. SM 23 and 24 not. Maybe it should? Or maybe it's blocked somehow? Could you post here what's the output on your terminal after starting SM 24?

mf

k_zurawski
Good morning,

when I launch the new container, I get the following in the terminal:

(base) mario@HP-Z8-G4-Workstation:~$ ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11
/home/mario/./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11:433: SyntaxWarning: invalid escape sequence '.'
regexp = re.compile("hwloc_(.).so")
'+ running salome_meca in GPU mode
++ using container salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
++ prepend system 'libGL' libs

** (SALOME_Session_Server_No_Server:5569): WARNING **: 07:41:01.894: atk-bridge: get_device_events_reply: unknown signature

(I changed the formatting a bit, the + messes with it)

The warnings seen in the 2022 version are long gone, because they were kind of useless. The invalid escape sequence, I don't know about, but it also doesn't seem to cause anything,

Mario.

k_zurawski

mf Thank you

How come are you starting container by ./ not using "singularity run..."?

mf

k_zurawski

It's in the .sh script in the top line of the terminal,

Mario.

k_zurawski

mf OK, don't bother. I give up.

k_zurawski

So it's not exactly what should be done, which might give different results... Could you try by just singularity run salome... ?

mf

k_zurawski
It's would be the same.

Mario.

k_zurawski

mf Thank you for your help.

k_zurawski

hberro
Hello,
Singularity> ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif -B /tmp/local00:/local00
bash: ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif: Permission non accordée

w2@W2:~$ ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif -B /tmp/local00:/local00
-bash: ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif: Permission denied

what else should I do?

k_zurawski

Yesterday I installed Ubuntu 22.04 under Hyper-V, updated OS and installed Apptainer 1.3.4. The result is the same as in Debian under WSL. I had a gut feeling that there's a communication error between preprocessor and solver. I haven't seen it in WSL, but below screenshot might indicate that. Could anyone comment on this?

When I try to run as_run in shell I'm getting result as below. I'm really illiterate when it comes to dealing with Linux and these kinds of problems.

nicolas_p

You have a problem with as_run since you have no access to /local00/tmp

Try to see if it exists in your system and copy a file.

k_zurawski

nicolas_p
where should it be created? In / or in /home/u22/ ?

nicolas_p

yes directly in /.

k_zurawski

what can I do about it?

nicolas_p

here, this is not a problem with smeca but basic linux problem.

k_zurawski

nicolas_p
ok, so how to deal with it? I'd really appreciate if you could guide me through the whole process. I only know basic Linux commands and I'm far from being "proficient" with it. Please don't look at it as sort of ignorance. I really don't have much time. I'd rather spend it on Code_Aster, not on Linux itself.

jeanpierreaubry

nicolas_p

here, this is not a problem with smeca but basic linux problem.

is this good enough a reason not to help ?

StanislavPavlica

Hello Krzysztof,

try following steps:

I believe you should use singularity not apptainer to run salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif.
I'm not using Windows so I'm not sure of this:

To quickly install the 4.0.0 package singularity use the following commands inside the WSL2 Ubuntu 22.04 window:

wget https://github.com/sylabs/singularity/releases/download/v4.0.0/singularity-ce_4.0.0-jammy_amd64.deb
sudo apt install ./singularity-ce_4.0.0-jammy_amd64.deb

File salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif put in your home directory:
/home/u22/
Or you can make a link in your home directory.
Then run inside the WSL2 Ubuntu 22.04 window this command to install salome_meca (in /home/u22/ directory):
singularity run --app install salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
This command generate in your home directory a script with same name as a container but without extension .sif:
salome_meca-lgpl-2024.1.0-1-20240327-scibian-11
Then run this script to start salome_meca:
./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11
Script prepare environment to properly run container including access to /local00/tmp

If you start container with command
singularity run salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
this environment is missing and salome _meca is not running properly.

Stano

k_zurawski

StanislavPavlica
I have Apptainer in virtual machine and Singularity 4.2.0 in Debian 12 on WSL. Both don't work. The last one screenshot is from Singularity and Debian.

k_zurawski

StanislavPavlica
I followed your step-by-step guide and AsterStudy sees Code_Aster on my VM. as_run also starts, but I haven't run any simulations yet.
BIG THANKS!!!

I need to replicate the same on WSL and Debian and see if this also solves the issue. If not, I'll try WSL with Ubuntu 22.04 as in case above. Pity I can't have 2 separate workstations, one with Windows and one with Ubuntu.