NC error

[mashinde]

Hi frds,

I am running ROMS on newly installed SUN cluster with 32 processors.....i am getting following error. I am not geting the message from the error..is it coming from the model or is it coming from the netcdf/hdf lib installed in the cluster.
I know there is something wrong with I/O.
Below Here I am copy/paste last portion of output.log file that gives error meg...


STEP Day HH:MM:SS KINETIC_ENRG POTEN_ENRG TOTAL_ENRG NET_VOLUME

1296000 30 00:00:00 0.000000E+00 1.847497E+04 1.847497E+04 1.348133E+16
DEF_HIS - creating history file: /share/apps/ROMS/Projects/rmed16/his_rmed16_0091.nc
WRT_HIS - wrote history fields (Index=1,1) into time record = 0000001
DEF_AVG - creating average file: /share/apps/ROMS/Projects/rmed16/avg_rmed16_0180.nc
DEF_DIAGS - creating diagnostics file: /share/apps/ROMS/Projects/rmed16/dia_rmed16_0180.nc
oceanG: string.c:177: NC_check_name: Assertion `name != ((void *)0)' failed.
forrtl: error (76): Abort trap signal
Image PC Routine Line Source
libc.so.6 0000003D12830265 Unknown Unknown Unknown
libc.so.6 0000003D12831D10 Unknown Unknown Unknown
libc.so.6 0000003D128296E6 Unknown Unknown Unknown
oceanG 00000000009411A2 Unknown Unknown Unknown
oceanG 0000000000947CA6 Unknown Unknown Unknown
oceanG 00000000008BEF0F Unknown Unknown Unknown
oceanG 0000000000954014 Unknown Unknown Unknown
oceanG 000000000083F25B Unknown Unknown Unknown
oceanG 0000000000621084 def_var_mod_mp_de 118 def_var.f90
oceanG 00000000005EF9BD def_diags_ 232 def_diags.f90
oceanG 00000000004547FF output_ 263 output.f90
oceanG 000000000044D652 main3d_ 169 main3d.f90
oceanG 000000000044A600 ocean_control_mod 159 ocean_control.f90
oceanG 000000000044A029 MAIN__ 109 master.f90
oceanG 0000000000449D9C Unknown Unknown Unknown
libc.so.6 0000003D1281D994 Unknown Unknown Unknown
oceanG 0000000000449CA9 Unknown Unknown Unknown
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 22092 on node compute-0-14.local exited on signal 6 (Aborted).
--------------------------------------------------------------------------

Note: all the pre-compiled test successfully run on the same cluster without any problem.


Any suggestion !



Thanks !

Mahesh

[kate]

A wild guess is that you are asking it to define a diagnostics variable, but it's missing the variable name. Do you have the latest greatest varinfo.dat? Is this with UPWELLING or one of your cases? Have you tried UPWELLING with diagnostics? Do you have a working debugger?

[jcwarner]

This info is trying to tell you something:

oceanG 0000000000621084 def_var_mod_mp_de 118 def_var.f90
oceanG 00000000005EF9BD def_diags_ 232 def_diags.f90
oceanG 00000000004547FF output_ 263 output.f90
oceanG 000000000044D652 main3d_ 169 main3d.f90

what is on/near the lines 118 in def_var.f90, lines 232 in def_diags (probably the call to def_var), etc. as kate said, what var is it getting stuck at?