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

20050305: GARP Segmentation Fault

Robert,

When programs that previously worked suddenly stop working
with:
   "absolutely no changes, so it appears as if it
   stopped working for no apparent reason"

Aside from the evident data stream problems that NWS had the past day or so,
You might check the following:

   Are you using the $MODEL/model_name/YYYYMMDDHH_..... naming
   convention that I provide?

   Zero length decoded files (eg disk full at some point)
   Have you tried the GD programs from the command line (or NMAP2) as
   an independent confirmation that it is GARP's problem and not a
   data file or system library problem? If you had some RPMs installed, 
   that could affect your sharable libraries on your system. 

   How about your ~ldm/data directory tree. Is this a symbolic link?
   Are your permissions correct. Do you have grid files in your
   current working directory?

   Are you running as root (looks like that from below). Do you normally
   run as that user? 

   Is you LDM correctly set up using the pqact entries and tables for 5.7.4?
   If your decoders are using old tables (or not finding grid
   tables for the correct version, then that could create bad decoded
   file entries). Old grid tables would not have all the levels/parameters
   that are in the current data stream and would lead to garbage in
   the data files.

   Do you have too many decoded files in the directories that Garp is looking
   at? Scouring a problem? 

Steve Chiswell
Unidata User SUpport




>From: Robert Dewey <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200503060022.j260MSv2009578

>Hello,
>
>I have seem to run into a problem with GARP. I am
>using GEMPAK 5.7.4, and everything was running smooth.
>Then, I went to look at some model data in GARP today,
>and I get a segmentation fault as soon as I click the
>"model" widget. This is the output that I get in the
>x-terminal:
>
>[root@LDM eta]# garp
>GEMPAK: [FL -4]  Cannot read file ....
>GEMPAK: [DM -7]  Read error.
>GEMPAK: [GD -2]  File
>/usr/local/ldm/data/gempak/model/eta cannot be opened.
>GEMPAK: [FL -4]  Cannot read file ....
>GEMPAK: [DM -7]  Read error.
>GEMPAK: [GD -2]  File
>/usr/local/ldm/data/gempak/model/eta cannot be opened.
>Segmentation fault
>[root@LDM eta]#
>
>I have tried swapping the Garp_defaults file with a
>fresh one, tried swapping datatype.tbl with a fresh
>one, and there is no difference. I then tried moving
>the eta directory to a different location, to hide it
>from GARP, but then I just get a standard seg fault,
>without any read errors. Re-installing wouldn't be too
>big of a deal, but I was wondering if there is another
>solution, or if anyone else has experienced this. What
>really gets me, is that everything was running fine -
>I made absolutely no changes, so it appears as if it
>stopped working for no apparent reason.
>
>
>       
>               
>__________________________________ 
>Celebrate Yahoo!'s 10th Birthday! 
>Yahoo! Netrospective: 100 Moments of the Web 
>http://birthday.yahoo.com/netrospective/
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.