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.
Gerry, This means that your gplt process is no longer talking to the tty. There is a script that will cleanup most of this, run: "cleanup -c" It will look for the gplt processes and kill them, followed by removing the message queues (with ipcrm). After running the script, check for remaining message queues with "ipcs" as well as any hung "gplt" processes and device drivers "xw", "gf", etc. Steve Chiswell On Tue, 26 Aug 2003, Gerry Creager N5JXS wrote: > Timing is, of course, everything. > > I've got a big demo and these stopped working. Can you help with the > interpretation? > > GEMPAK-GDPLOT>Error in message send = 22 > itype, ichan, nwords,1,-1,3 > Error in message send = 22 > itype, ichan, nwords,1,-1,2 > Creating process: gplt for queue -1 > Error in message send = 22 > itype, ichan, nwords,1,-1,2 > Error in message send = 22 > itype, ichan, nwords,1,-1,3 > [GEMPLT -1] NMBRER - Mailbox read. > [GPEND -3] Fatal error initializing GEMPLT. > > Thanks! > gerry > -- > Gerry Creager -- address@hidden > Texas Mesonet -- AATLT, Texas A&M University > Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.847.8578 > Page: 979.228.0173 > Office: 903A Eller Bldg, TAMU, College Station, TX 77843 >