Re: 20040516: Error in using interactive gempak programs

Thanks... I did it the hard way but I'll try to remember the easy way 
next time!

gerry

Steve Chiswell wrote:
> Gerry,
>
> When you recieve errors with message queue, its likely t hat you have
> gplt and device drivers that weren't shut down with gpend (either
> interactively, or in one of your crons).
>
> The command "cleanup -c" runs a script in $NAWIPS/bin/scripts to automate
> the process, but you can accomplish  the same with finding the process IDs
> of gplt, xw, gf etc using "/bin/ps -eaf" and killing those,
> and then using the "ipcs" cammand to list open
> message queues and remove them with the "ipcrm" command.
>
> The cleanup script mentioned above tries to automate the process,
> but since the /bin/ps output format varies so much between different
> systems, you may have to do it manually as above.
>
> Steve CHiswell
> Unidata User Support
>
> On Sun, 16 May 2004, Gerry Creager N5JXS wrote:
>
>
> > No, That was the first, and obvious thought.  Declan and Daryl both came
> > up with a plausible starting point.  In looking at IPC resources, I had
> > problems.  A number of the processes were failing and leaving resources
> > hanging.
> >
> > df -h
> > Filesystem            Size  Used Avail Use% Mounted on
> > /dev/hda2              36G  5.4G   29G  16% /
> > /dev/hda1              99M  6.3M   88M   7% /boot
> > none                  248M     0  248M   0% /dev/shm
> > bigfoot.xxxx.xxxx:/data/gempak/nexrad/craft
> >                       935G  467G  469G  50% /data/craft
> > xx.xx.xx.xx:/data       151G   63G   80G  44% /data/ldm
> >
> > There was a reference Chiz had penned in 2000, recommending killing,
> > explicitly, running Gempak programs accessing gplt, based on an
> > examination using 'ps -efw' and then manually deleting the hanging IPC
> > message queues ('ipcs') using 'ipcrm' which cleared the issue.
> >
> > I had attempted to duplicate a machine for gempak processing and had
> > failed to get some of the target/output subdirectories right. As the
> > scripts using those target directories couldn't write to 'em, the
> > scripts failed improperly, rather than gracefully.
> >
> > So, rather than an easy-to-identify hard-disk error, it was a little,
> > but not much, more esoteric failure caused, as most of these things are,
> > by operator error.
> >
> > Thanks for the suggestion, though.  Good thought.
> >
> > Regards,
> > Gerry
> >
> > Michael W Dross wrote:
> >
> > > Not to state the obvious but are any of your filesystems full?
> > >
> > > Mike
> > > ________________________________________________________
> > > Michael Dross                             address@hidden
> > > Duke Power Company                  Meteorologist/Scientist
> > > 9700 David Taylor Dr.               Voice: 704-594-0341
> > > Charlotte, NC 28269                       Mobile: 980-722-0756
> > >
> > >
> > > |---------+----------------------------->
> > > |         |           Gerry Creager     |
> > > |         |           N5JXS             |
> > > |         |           <gerry.creager@tam|
> > > |         |           u.edu>            |
> > > |         |           Sent by:          |
> > > |         |           owner-gembud@unida|
> > > |         |           ta.ucar.edu       |
> > > |         |                             |
> > > |         |                             |
> > > |         |           05/15/2004 05:37  |
> > > |         |           PM                |
> > > |         |                             |
> > > |---------+----------------------------->
> > >  
> > > >-------------------------------------------------------------------------------------------------------------------------------|
> > >  |                                                                              
> > >                                                  |
> > >  |       To:       "'address@hidden'" <address@hidden>                          
> > >                                |
> > >  |       cc:                                                                    
> > >                                                  |
> > >  |       Subject:  Error in using interactive gempak programs                   
> > >                                                  |
> > >  
> > > >-------------------------------------------------------------------------------------------------------------------------------|
> > >
> > >
> > >
> > >
> > > Can anyone shed some light on the following error message?
> > >
> > > [gerry@gemdata2 ~]$ gpnexr2
> > > msgget: No space left on device
> > > Error in message send = 22
> > > itype, ichan, nwords,1,-1,2
> > > msgget: No space left on device
> > > Creating process: gplt for queue -1
> > > msgget: No space left on device
> > > msgget: No space left on device
> > > 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.
> > >  [GPNEXR2 -3]  Fatal error initializing GEMPLT.
> > >
> > >
> > > TIA, 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
> >
> > --
> > 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

--
Gerry Creager -- address@hidden
Network Engineering -- 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