Parallelization issue - forrtl: severe (43) error

[rgawde]

Hello everyone,

We have been trying to start the biogeochemical module of ROMS. I was also able to get the model to compile and create the executable, oceanM.
However, when I try to set up a run using the forcing conditions for 2010, using the following command line:

mpirun -np 56 ./oceanM choproms.in 2>&1 >myrun.log &

I get the following error:

[1] 20597
$ forrtl: severe (43): file name specification error, unit 15, file "Unknown"
Image PC Routine Line Source
oceanM 00000000006D9D39 Unknown Unknown Unknown
oceanM 00000000006ED562 Unknown Unknown Unknown
oceanM 00000000004109B1 Unknown Unknown Unknown
oceanM 000000000040B062 Unknown Unknown Unknown
oceanM 000000000040AA7A Unknown Unknown Unknown
oceanM 000000000040A9DE Unknown Unknown Unknown
libc.so.6 00002AE1E1498B15 Unknown Unknown Unknown
oceanM 000000000040A8E9 Unknown Unknown Unknown

I tried running the debug option in serial mode and it runs fine. Then I added the explicit path for libc.so.6 to my .bashrc file and tried re-running it in parallel. But now the only output I get is (repeatedly):

Model Input Parameters: ROMS/TOMS version 3.5
Thursday - March 23, 2017 - 2:47:51 PM
-----------------------------------------------------------------------------

Do you have anything that jumps out at you?

Thanks,
Rasika

[kate]

What exactly are you running? Did you compile for serial execution or parallel, then run on just one core? You'd have an oceanG either way if you compiled for USE_DEBUG.

[rgawde]

Hi Kate,

I should have been clearer. I first compile in serial mode using the USE_DEBUG option. I got the oceanG executable and ran it as a serial run and it worked.

Then I switched to compiling for oceanM still in serial mode with the USE_DEBUG option turned off. The run was successful.

After that I switched to compiling using oceanG and oceanM for parallel mode. Both of them gave me the same error. I have also used -g -traceback option for the debugging mode but I don't get any specific details on the error.

[kate]

In my experience, running in USE_DEBUG=on mode gives me filenames and line numbers. I don't know why you wouldn't. Perhaps this gives more of a clue?

file name specification error, unit 15, file "Unknown"

Not that I know what unit 15 would be.