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

20050221: ipcs and ipcrm problem?



Doug,

The first error message you have:

[GEMPLT -101]  NOPROC - Nonexistent executable

means that either you haven't sourced the $NAWIPS/Gemenviron
variables into your shell script environment, or you have
a file in your working directory with the name of a GEMPAK executable
program such as "gplt" or "ps". It seems that $GEMEXE variable is probably 
not set, which will be set after sucessfully sourcing Gemenviron. When you 
run a script interactively, the script will inherit your environment, but 
when run from a cron or batch mode, you will have to ensure that the shell 
sets its environment since it won't be inheriting your logged in environment.

The error message:
   Error in message send = 22
   itype, ichan, nwords,0,65536,3

signals that you do have a message queue problem, which
is likely due to the program not being able to talk to $GEMEXE/gplt
or $GEMEXE/ps due to the above problem.

To clear this up, exit out of GEMPAK and run "cleanup -c".
This command will remove existing message queues (eg, the "ipcrm" command
is run to remove message queues found with "ipcs"). It will also
look for running "gplt" processes and kill them. 

After running the cleanup command, use the /bin/ps command in linux
to see if you have any gempak device drivers still running (eg xw, gf, ps).
After clearing the environment, make sure your script is sourcing Gemenviron,
and then retry.

Lastly, you can clean up your DEVICE line in you script to
remove the space between the "ps" and "|" characters which 
shouldn't be a problem (unless its some control character I can't
see in the text file dump.

Steve Chiswell
Unidata User Support



>From: dmiller <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200502212225.j1LMPPv2000092

>This is a multi-part message in MIME format.
>--------------090905030201020201040306
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>Content-Transfer-Encoding: 7bit
>
>
>    Steve:
>
>         The attached file (gempak_diag) is the text output for a failed 
>script. I'm not familiar with how I can tell via ipcs if it is a problem 
>with message queues. I'm trying to run the gempak script via RedHat 
>Enterprise on a Dell Linux machine. Thank you for any insights you can give.
>
>    Regards,
>   Doug Miller
>
>
>--------------090905030201020201040306
>Content-Type: text/plain;
> name="gempak_diag"
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline;
> filename="gempak_diag"
>
> [GEMPLT -101]  NOPROC - Nonexistent executable.
> GDFILE    Grid file                         ./2004081312_wrf.gem
> GDATTIM   Grid date/time                    all
> GLEVEL    Grid level                        10
> GVCORD    Grid vertical coordinate          hght
> PANEL     Panel loc/color/dash/width/regn   0
> SKIP      Skip_cntr/skip_plt_x;skip_plt_y   0/4;4
> SCALE     Scalar scale / vector scale        
> GFUNC     Scalar grid                       gwfs(knts((mag(wnd))),3)
> CTYPE     Contour type:  C/F                c/f                         ! c
> CONTUR    Subbox/smooth                     1
> CINT      Contour interval/min/max          5;10;15;20;25;30;35;40;50;60
> LINE      Color/type/width/label/smth/fltr  1/1/5/1
> FINT      Fill interval/min/max             10;15;20;25;30;35;45
> FLINE     Fill colors/fill types            0;20;27;28;29;30;2
> HILO      Color/symbol/rng/rad/cnt/intp      
> HLSYM     HILO txt size/posn/font/wdth/hw   2;1.5//21//hw
> CLRBAR    Color/ornt/anch/x;y/ln;wd/freq|t  1/V/LL/0.87;.47/.30;.01
> GVECT     Vector grid                       obs
> WIND      Wind symbol/siz/wdth/typ/hdsz     bk1/.7/1
> REFVEC    Mag;x;y;txtsiz/font/wdth/HW;labl   
> TITLE     Title color/line/title            2/0/~ WRF 10m Surface Winds (knot
> s)
> TEXT      Size/fnt/wdth/brdr/N-rot/just/hw  1.5
> CLEAR     Clear screen flag                 y
 GAREA     Graphics area                     20.;-90;35.0;-70
> IJSKIP    Iskp;Istrt;Istp/Jskp;Jstrt;Jstp    
> PROJ      Map projection/angles/margins|dr  mer
> MAP       Map color/dash/width/filter flag  2/1/6
> LATLON    Line color/dash/width/freq/inc/l  4/3/1/1;1/2;1.999
> DEVICE    Device|name|x size;y size|color   ps |wrf_sfc_wnd.ps|5;6|C
> STNPLT    Txtc/txt attr|marker attr|stnfil   
> Parameters requested: GDFILE,GDATTIM,GLEVEL,GVCORD,PANEL,SKIP,SCALE,GFUNC,
> CTYPE,CONTUR,CINT,LINE,FINT,FLINE,HILO,HLSYM,CLRBAR,GVECT,WIND,REFVEC,TITLE,
> TEXT,CLEAR,GAREA,IJSKIP,PROJ,MAP,LATLON,DEVICE,STNPLT.
> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GE
> MPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMP
> AK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK
> -GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-G
> DPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDP
> LOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLO
> T> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT> GEMPAK-GDPLOT>
>  GDFILE   = ./2004081312_wrf.gem
> GDATTIM  = all
> GLEVEL   = 10
> GVCORD   = hght
> PANEL    = 0
> SKIP     = 0/4;4
> SCALE    =  
> GFUNC    = gwfs(knts((mag(wnd))),3)
> CTYPE    = c/f                         ! c
> CONTUR   = 1
> CINT     = 5;10;15;20;25;30;35;40;50;60
> LINE     = 1/1/5/1
> FINT     = 10;15;20;25;30;35;45
> FLINE    = 0;20;27;28;29;30;2
> HILO     =  
> HLSYM    = 2;1.5//21//hw
> CLRBAR   = 1/V/LL/0.87;.47/.30;.01
> GVECT    = obs
> WIND     = bk1/.7/1
> REFVEC   =  
> TITLE    = 2/0/~ WRF 10m Surface Winds (knots)
> TEXT     = 1.5
> CLEAR    = y
> GAREA    = 20.;-90;35.0;-70
> IJSKIP   =  
> PROJ     = mer
> MAP      = 2/1/6
> LATLON   = 4/3/1/1;1/2;1.999
> DEVICE   = ps |wrf_sfc_wnd.ps|5;6|C
> STNPLT   =  
> GEMPAK-GDPLOT>Error in message send = 22
>itype, ichan, nwords,0,65536,3
>
>--------------090905030201020201040306--
>
--
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.


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.