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

You are not logged in.

#1 2020-09-15 20:07:46

chenghui62000
Member
From: Norway
Registered: 2018-06-19
Posts: 99

Run same case on two computers, but one raises EXIT_CODE = 139

Hi experts,

I have a problem with my simulation (The simulation is a little complex). First, I set up the simulation case on my laptop computer. The case passed a test simulation on my laptop computer, but when I move the simulation to my desktop computer, the case is crashed.


The software environment on my laptop is Code_Aster14.4 in Windows Subsystem Linux (WSL). CPU: i7-8750H; Memory: 16GB
The desktop computer is Linux Mint 19.3, CPU: Intel Xeon E5-2620 v4;  Memory: 32GB

I attached the mess files for the simulations on the two computers, I really wish some can help me with that.

Best regards,
Hui Cheng

Last edited by chenghui62000 (2020-09-15 20:12:34)


Attachments:
mess_laptop.log, Size: 1.71 MiB, Downloads: 12

Offline

#2 2020-09-15 20:08:54

chenghui62000
Member
From: Norway
Registered: 2018-06-19
Posts: 99

Re: Run same case on two computers, but one raises EXIT_CODE = 139

Here is the mess file from my desktop computer.

Following information is not recorded in the mess file:

#3      Dechargement de la memoire sur disque             CPU (USER+SYST/SYST/ELAPS):      0.04      0.03      0.04
#3      Dechargement de la memoire sur disque             CPU (USER+SYST/SYST/ELAPS):      0.01      0.01      0.01
#3      Dechargement de la memoire sur disque             CPU (USER+SYST/SYST/ELAPS):      0.02      0.01      0.02
#3      Dechargement de la memoire sur disque             CPU (USER+SYST/SYST/ELAPS):      0.00      0.00      0.00
#3      Dechargement de la memoire sur disque             CPU (USER+SYST/SYST/ELAPS):      0.04      0.02      0.03
#3      Dechargement de la memoire sur disque             CPU (USER+SYST/SYST/ELAPS):      0.01      0.01      0.01
Segmentation fault (core dumped)
EXECUTION_CODE_ASTER_EXIT_2659=139
<INFO> Code_Aster run ended, diagnostic : <F>_ABNORMAL_ABORT

--------------------------------------------------------------------------------
 Content of /tmp/hui-UiS-interactif_197966 after execution

.:
total 165504
drwx------  3 hui  hui       4096 Sep 15 21:25 .
drwxrwxrwt 34 root root     12288 Sep 15 21:25 ..
-rw-rw-r--  1 hui  hui       1420 Sep 15 21:25 2659.export
-rw-rw-r--  1 hui  hui       2881 Sep 15 21:25 config.txt
-rw-rw-r--  1 hui  hui      11262 Sep 15 21:25 fort.1
-rw-rw-r--  1 hui  hui      11262 Sep 15 21:25 fort.1.1
-rw-rw-r--  1 hui  hui          0 Sep 15 21:25 fort.15
-rw-rw-r--  1 hui  hui    1324454 Sep 15 21:25 fort.20
-rw-rw-r--  1 hui  hui     141269 Sep 15 21:25 fort.6
-rw-rw-r--  1 hui  hui          0 Sep 15 21:25 fort.8
-rw-rw-r--  1 hui  hui          0 Sep 15 21:25 fort.9
-rw-rw-r--  1 hui  hui       7073 Sep 15 21:25 fort.91
-rw-rw-r--  1 hui  hui  140902408 Sep 15 21:25 glob.1
drwxr-xr-x  2 hui  hui       4096 Sep 15 21:25 REPE_OUT
-rw-rw-r--  1 hui  hui   27033608 Sep 15 21:25 vola.1

REPE_OUT:
total 8
drwxr-xr-x 2 hui hui 4096 Sep 15 21:25 .
drwx------ 3 hui hui 4096 Sep 15 21:25 ..


--------------------------------------------------------------------------------
 Size of bases

<INFO> size of vola.1 :     27033608 bytes
<INFO> size of glob.1 :    140902408 bytes

--------------------------------------------------------------------------------
 Copying results


<A>_COPYFILE       no such file or directory: fort.80

copying .../fort.8...                                                   [  OK  ]
copying .../fort.6...                                                   [  OK  ]

<F>_ABNORMAL_ABORT Code_Aster run ended


 
 ---------------------------------------------------------------------------------
                                            cpu     system    cpu+sys    elapsed
 ---------------------------------------------------------------------------------
   Preparation of environment              0.01       0.00       0.01       0.00
   Copying datas                           0.06       0.02       0.08       0.09
   Code_Aster run                         13.83       3.70      17.53      13.49
   Copying results                         0.01       0.02       0.03       0.02
 ---------------------------------------------------------------------------------
   Total                                  14.03       3.81      17.84      13.80
 ---------------------------------------------------------------------------------

as_run 2019.0

------------------------------------------------------------
--- DIAGNOSTIC JOB : <F>_ABNORMAL_ABORT
------------------------------------------------------------


EXIT_CODE=4

Last edited by chenghui62000 (2020-09-15 20:25:04)


Attachments:
mess_desktop.log, Size: 137.96 KiB, Downloads: 13

Offline

#3 2020-09-22 17:41:47

dbpatankar
Member
From: Roorkee, Uttarakhand, India
Registered: 2010-05-22
Posts: 196

Re: Run same case on two computers, but one raises EXIT_CODE = 139

Did you check stderr log?

Offline

#4 2020-09-25 11:46:23

chenghui62000
Member
From: Norway
Registered: 2018-06-19
Posts: 99

Re: Run same case on two computers, but one raises EXIT_CODE = 139

Hi Digvijay Patankar,
How to check Stderr log?

Offline

#5 2020-09-25 21:34:06

dbpatankar
Member
From: Roorkee, Uttarakhand, India
Registered: 2010-05-22
Posts: 196

Re: Run same case on two computers, but one raises EXIT_CODE = 139

chenghui62000 wrote:

Hi Digvijay Patankar,
How to check Stderr log?

If you are using CA from Salome_Meca then the error log will be in

<filename>_Files/RunCase_X/Result-Stage_Y/logs

If you are using CA from command line then the log files will be in

flasheur 

directory.

For each execution, CA creates 3 log files, 1) output log 2) exit log 3) error log.

Offline

#6 Yesterday 14:08:09

chenghui62000
Member
From: Norway
Registered: 2018-06-19
Posts: 99

Re: Run same case on two computers, but one raises EXIT_CODE = 139

Hi Digvijay Patankar,
I use using CA from command, as follows:

/opt/aster144/bin/as_run asterinput/ASTERRUN.EXPORT

but there is nothing in the "flasheur" folder.

Offline

#7 Yesterday 17:06:17

mf
Member
Registered: 2019-06-18
Posts: 97

Re: Run same case on two computers, but one raises EXIT_CODE = 139

Hello,

the manual method in Linux should work too: when you launch your calculation you append '2> ~/error.log' to your as_run command. So it will look like this:

/opt/aster144/bin/as_run asterinput/ASTERRUN.EXPORT 2> ~/error.log

It reroutes the output of stderr into a file 'error.log' in your home directory.

This should work, of course you can write the file in whatever directory you want, it is not restricted to your home directory.

You can test this with whatever command will produce an error, for example a 'file not found' error:

ls xyz* 2> ~/error.log

then take a look at the file with

cat ~/error.log

Voila, the error is written to this file

Mario.

Last edited by mf (Yesterday 21:49:36)

Offline

#8 Yesterday 17:18:03

dbpatankar
Member
From: Roorkee, Uttarakhand, India
Registered: 2010-05-22
Posts: 196

Re: Run same case on two computers, but one raises EXIT_CODE = 139

chenghui62000 wrote:

Hi Digvijay Patankar,
I use using CA from command, as follows:

/opt/aster144/bin/as_run asterinput/ASTERRUN.EXPORT

but there is nothing in the "flasheur" folder.

the folder is usually located in your home directory.

Offline