[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20010606: NMAP2 problem

Kevin,

If you have a datatype.tbl file that is 0 bytes, then this is something outside
of GEMPAK since no GEMPAK program ever tries to modify any table.
In fact, if you are running as a different user than your GEMPAK account 
is installed under, then that should be impossible.

Some reasons you could get a 0 length file are if you try to open the file
in your editor, and your disk space is full. Anything like that would
crater NMAP2. Of course, Garp has its own files, and never looks at
datatype.tbl. NMAP relies more on the GEMTBL/nmap/.... tables.

I would suggest checking your system logs to see if there are disk full
messages. 

I haven't had problems with NMAP2 running all night. Presumably you
are running 5.6.C.1 and still at RH Linux 6.x? I am running here with RH 7.0 &
7.1
 
Steve Chiswell
Unidata User SUpport

On Wed, 6 Jun 2001, Kevin Polston wrote:

> Hey Steve,
> 
> I have run into a problem that I don't know how to fix. I had several
> image loops running in NMAP2 last night (I left them run overnight).
> When I checked this morning I had a message that said "too many file
> systems open". I had seen this before......so I cleared everything and
> restarted NTL and opened NMAP2. Well, when I right-clicked to bring up
> the menus (image, obs, grids, etc).....there was nothing there. I have
> had this happen to. The datatype.tbl file was empty (ie it had 0
> bytes....nothing in it). I had a backup datatype.tbl file that I copied
> into the proper directory. Well, it looked like everything was fine. I
> clicked to bring up an image....and all the subdirectories were there.
> However, when I clicked on the last submenu (the one which will show the
> data links in the white window) nothing came up. This was for both
> satellite and radar. However....the other data sources were working fine
> (upper air, profiler, surface obs, gridded data). What's more...I was
> able to call up the imagery in NMAP and NSAT and GARP. I looked through
> the datatype.tbl file and I couldn't see anything that was wrong. What
> would you suggest to fix the problem.
> 
> KP 
> 
>