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

[McIDAS #GYT-719991]: Interesting batch file errors



Hi Paul,

Thanks for the login credentials.  I successfully SSHed to climate.cod.edu
as 'mcidas', so I know the procedure works.

Question:

- in what account and on what machine are the scripts that are having
  difficulties running?

If all of the McIDAS scripts are running on climate.cod.edu and all
are running from the 'mcidas' account, then I can start poking around
in earnest.

The first thing that I noticed is the existence of at least a couple
of files that should be created/used on a per-session basis in
the $MCDATA directory of 'mcidas':

<as 'mcidas' on climate>

cd $MCDATA

ls 
 AFOS.BAT          GRID0021        NEWBREF.ET       PRINT.GRX          
TESTVIS2.ET
AFOS.CFG           GRID0022        NEWISFC.IDM      PUBLIC.SRV         
TESTVIS.ET
ALLOC.WWW          GRID0023        NEWTERM.IDM      RADAR.GRX          
TESTVIS.ST
AREA4467           GRID0024        NEWVEL.ET        RAOBCON.SITE       
TIRDEC.CFG
AREA4467.bak       GROUPS.DAT      NEWVEL.ET.OLD    RAOB.RAP           uwgrid.sh
AREA4468           H2O2.ET         NEXCOMP.ET       RESOLV.SRV         VAPOR2.ET
AREA4469           HH.ST           NEXRADDE.BAT     ROUTE.SYS          VAPOR3.ET
BANANA.ST          HODO.GRX        NEXRAD.GRX       RTGRIDS.TXT        VAPOR.ET
BASICVV1           HRS.CFG         NEXRCOMP.CFG     RTMODELS.CFG       VAPOR.GRX
BREFTEST.ST        IDS.CFG         NEXRFILE.CFG     RTMODELS.CFG.2006  VAPOR.ST
CIRCUIT.DAT        IMAGE2.ET       NEXRID.CFG       RTMODELS.CFG.2008  VIRT7001
CLEAR.ST           INFRARED.ET     NGMMOS.CFG       S99xcd             VIRT7002
COUNTRY.DAT        IRABDEC.CFG     NNEXRAD.CFG      SAOMETAR.RAP       VIRT7003
DCLSTIDX.PTR       IRTEMP2.ST      NOAAPORT.BAT     SAT.GRX            VIRT7777
DDS.CFG            ISFCDEC.CFG     NOGRIB2.CFG      SERVER.LOG         VIRT7778
DECINFO.DAT        ISHPDEC.CFG     NOGRIB.CFG       SFCCON.SITE        VIRT8888
decodertypes.core  LWPATH.NAM      NOGRIB.CFG.2006  SIGCO.DAT          VIRT8889
DECOSTAT.DAT       MBCOLOR.ET      NOGRIB.CFG.2008  SKEDFILE           VIRT9000
DMMISC.ERR         MB.ET           NOWRAD.CFG       STRTABLE           VIRT9004
DMRAOB.ERR         MB.GRX          NTXT.CFG         SURFACE.GRX        VIRT9005
DMSFC.ERR          MB.ST           OLDISFC.IDM      SYNDEC.CFG         VIRT9007
DMSYN.ERR          MCCMDHIST.TXT   OLDTERM.IDM      SYNOPTIC.RAP       VIRT9300
DREF.ET            MCGUISTART.BAT  PAULBREF.ET      TERMCHAR.001       VIS.ET
fort.18            MDRDEC.CFG      PAULBREF.ST      TERMDEC.CFG        VIS.ST
fort.19            MESO.GRX        PAULBREF.ST.OLD  TERMFCST.RAP       
WBOXDEC.CFG
fosrelay.cfg       MYBREF.ET       PAULDREF.ET      TESBREF.ET         
WNEXRAD.CFG
FRAMENH.001        MYBREF.ST       PAULHC1.ET       TESTBREF2.ST       WW.ET
GFSMOS.CFG         MYBREF.ST.OLD   PAULHCA.ET       TESTBREF.ET        
XCDDEC.BAT
GINI.CFG           MYVIS.ET        PAULPRET.ET      TESTBREF.ST        
XCDDEC.VER
GRAPHICS.KEY       NAMMOS.CFG      PAULVEL.ST       TESTIR.ST          XCD.NAM
GRBFILER.CFG       NAMMOS.RAP      PIRPDEC.CFG      TESTNEX.ST         
ZURBREF.ET
GRIBDEC.CFG        NBIN.CFG        PPS.CFG          TESTVAPOR5.ET      
ZURBREF.ST

The files that jump out at me are:

FRAMENH.001
GRAPHICS.KEY
TERMCHAR.001

These files are supposed to only exist in a session specific subdirectory
of ~mcidas/.mctmp.  For instance:

<as 'mcidas'>

address@hidden:~/workdata$ mcenv

address@hidden:~/workdata$ ls ~/.mctmp/552271900/
BASICVV1  FRAMED       GRAPHICS.KEY  STRTABLE
Frame1.0  FRAMENH.001  mcclean.lock  TERMCHAR.001

The most typical way that these files can end up in the $MCDATA
directory is that environment variables needed for McIDAS sessions
(remember a script will create a McIDAS session) are not
defined and/or not properly defined.

The thing that is needed now is to figure out which script(s) need
to be modified to fully set environment variables needed by McIDAS.

Can you verify if the full set of scripts that need to be looked
at are the ones run from 'cron' in the 'mcidas' account?

If yes, this looks to be:

00 21 * * * /home/ldm/util/mcscour.sh >> /dev/null 2>&1
12 * * * * /home/mcidas/paulsbatches/createmeso.pl >> /dev/null 2>&1
45 07 * * * /home/mcidas/paulsbatches/createmaps.pl >> /dev/null 2>&1
10 1,2,13,14 * * * /home/mcidas/paulsbatches/createhodo.pl >> /dev/null 2>&1
11 1,2,13,14 * * * /home/mcidas/crosskickoff CROSS.BAT >> /dev/null 2>&1
5,20,35,50 * * * * /home/mcidas/paulsbatches/createprofilers.pl >> /dev/null 
2>&1
45 1,13 * * * /home/mcidas/paulsbatches/createcanadahodo.pl >> /dev/null 2>&1

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: GYT-719991
Department: Support McIDAS
Priority: Normal
Status: Open


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.