[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GEMPAK #MEU-566855]: nagrib2 segmentation fault error
This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
- Subject: [GEMPAK #MEU-566855]: nagrib2 segmentation fault error
- Date: Wed, 12 Dec 2007 15:01:43 -0700
> <FONT face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" > size=2><DIV>Hi Steve..</DIV><DIV> </DIV><DIV>Thanks for the response and > for the setflag clarification.</DIV><DIV> </DIV><DIV>Nagrib2 or > nagrib1 literally crashes with a "segmentation fault error" as it > is running - there is no other error message produced and at times doenst > even leave a gplt job running in the > background.</DIV><DIV> </DIV><DIV>The crash does not occur consistently > either - in otherwords - nagribing the same grib file sometimes works (no > crash) and sometimes does not. I've seen this happen when > multiple gempak progs are running from the same directory (and overwriting > the .nts files) but I made sure this wasnt happening (by having this be the > only program running).</DIV><DIV> </DIV><DIV>Also Ive seen this happen > when I have not set my env var DISPLAY to :0.0 in scripts launching gempak > programs invoking gplt processes. However - this wa s happening to me running nagrib from the command line interface as well as running it from a script.</DIV><DIV> </DIV><DIV>PErhaps unrelated or maybe not - I noticed the same happens with gpmap - however in this case - when I delete the .nts file prior to launching gpmap I get no problems. But once that .nts file is written it loses its mind with a "segmentation fault error".</DIV><DIV> </DIV><DIV>Pete<BR></DIV><FONT color=#990099>-----"Unidata GEMPAK Support" <address@hidden> wrote: -----<BR><BR></FONT>>To: address@hidden<BR>>From: "Unidata GEMPAK Support" <address@hidden><BR>>Date: 12/10/2007 05:05PM<BR>>cc: address@hidden<BR>>Subject: [GEMPAK #MEU-566855]: nagrib2 segmentation fault error<BR>><BR>><BR>>Pete,<BR>><BR>>The USE_GFORTRAN=1 flag is only set for compiling the package by <BR>>telling<BR>>which Makinc.linux64_xxxxxx file to use.<BR>><BR>>This flag has no effect for the runtime environment.<BR>><BR>>The na programs can be linked directly to the gplt, but it does<BR>>produce<BR>>a much larger executable, so I don't do it, but it is possible.<BR>><BR>>It would help to know at what point you see a segmentation fault, eg<BR>>in launching, or<BR>>somewhere within running the program, and what your input source is.<BR>>The problem<BR>>you are describing could be a Tab" character within a FORMAT<BR>>statement within the<BR>>code that gfortran doesn't handle and I didn't catch in the<BR>>distribution.<BR>>Can you provide the text output of your session and show me the<BR>>error?<BR>><BR>>Thanks,<BR>><BR>>Steve Chiswell<BR>>Unidata&nb sp;User Support<BR>><BR>><BR>>> Hi..<BR>>> <BR>>> I upgraded directly from GEMPAK 5.10.2 to GEMPAK 5.10.4 (using<BR>>RHEL5) and<BR>>> am noticing many Segmentation Fault messages when I use nagrib2 and<BR>>nagrib<BR>>> - didnt see any threads or messages regarding this on the gembud<BR>>email<BR>>> archive.<BR>>> <BR>>> I downloaded/installed gempak_upc5.10.4_linux64.tar.gz<BR>>> I am sourcing the 5.10.4 Gemenviron (which was modified for system<BR>>> specific data locations)<BR>>> To invoke the new version of GEMPAK.. I killed all cron jobs then<BR>>logged<BR>>> out/in<BR>>> I noted nagrib and nagrib2 still require gpend to function in both<BR>>5.10.2<BR>>> and 5.10.4<BR>>> After the errors - for fun I rolled back GEMPAK to ver 5.10.2 an d<BR>>noted<BR>>> nagrib2 and nagrib work just fine (I am still running 5.10.2)<BR>>> <BR>>> Any advice.. does it have to do something with how the "set<BR>>> USE_GFORTRAN=1" is uncommented in the Gemenviron file (my system is<BR>>a<BR>>> xw8400 Linux workstation (HP) running RHEL5 x86_64)??<BR>>> <BR>>> Pete<BR>>> <BR>>> <BR>>> -----------------------------------------<BR>>> The information contained in this message is intended only for the<BR>>> personal and confidential use of the recipient(s) named above. If<BR>>> the reader of this message is not the intende d recipient or an<BR>>> agent responsible for delivering it to the intended recipient, you<BR>>> are hereby notified that you have received this document in error<BR>>> and that any review, dissemination, distribution, or copying of<BR>>> this message is strictly prohibited. If you have received this<BR>>> communication in error, please notify us immediately, and delete<BR>>> the original message.<BR>>> <BR>><BR>><BR>>Ticket Details<BR>>===================<BR>>Ticket ID: MEU-566855<BR>>Department: Support GEMPAK<BR>>Priority: Normal<BR>>Status: Closed</FONT> > Pete, I have a nagrib2 process here running every 5 minutes for the FNEXRAD nathr composites I create and haven't see this problem, but will pick through and see if there is a nts problem. The think you can check on your end is do a "wc -l gemglb.nts" and make sure there are less than 300 entries. Also make sure your disk space didn't fill up and corrupt the file (not likely given it occurs represtedly). Steve Chiswell Unidata User Support Ticket Details =================== Ticket ID: MEU-566855 Department: Support GEMPAK Priority: Normal Status: Closed
- Prev by Date: [GEMPAK #UER-356689]: NAGRIB not decoding AMPS WRF grids
- Next by Date: [GEMPAK #XVF-230778]: HRIT format MTSAT data in GEMPAK
- Previous by thread: [GEMPAK #MEU-566855]: nagrib2 segmentation fault error
- Next by thread: [GEMPAK #UER-356689]: NAGRIB not decoding AMPS WRF grids
- Index(es):