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

20040423: gpmap 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: 20040423: gpmap error
  • Date: Sun, 25 Apr 2004 11:11:29 -0600
David,

At some point, your script has exited without clearing the message
queue, and the script now finds an existing gplt process or message queue but
can't connect.

You should be able to clear up your hung gplt processes and remove
any stray message queues by running the gempak cleanup script as:
cleanup -c

You should also use the "/bin/ps" command to search for any remaining device 
drivers
(xw, gf, gif, ps etc) and gplt processes. Use "ipcs" to list your message queues
and verify that cleanup has removed all old ones that belong to you. The
cleanup script uses the "ipcrm" system command, which you can run manually too.

For more information about "ipcs" and "ipcrm", see the GEMPAK tutorial at
http://my.unidata.ucar.edu/content/software/gempak/tutorial and/or the
GEMPAK mail archives. 

Steve Chiswell


>From: "David C Welsh" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200404231645.i3NGjsCT009347

>I am using gpmap to plot NNEXRAD data. I am running the program in a 
>cron job script using the restore function to read in a"nts" file. I am 
>running on Linux This script and gpmap restore combo worked for over a 
>year. I am getting the follow error messages:
>
>Error in message send = 22
>itype, ichan, nwords,1,-1,2
>Error in message send = 22
>itype, ichan, nwords,1,-1,1
>Error in message send = 22
>itype, ichan, nwords,1,-1,3
> [GEMPLT -1]  NMBRER - Mailbox read.
> [GPMAP -3]  Fatal error initializing GEMPLT.
>
>I ran gpmap interactively and received the same error messages.
>
>What can I do to fix this?  Thanks
>
>David Welsh, NOAA/ETL
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.