[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Staging #BJE-146276]: 20220917: ADDE use at UQAM

Subject: [Staging #BJE-146276]: 20220917: ADDE use at UQAM
Date: Wed, 21 Sep 2022 10:38:52 -0600
Hi Christian,

re:
> I checked my configuration and it is not exactly as you describe.

OK, I am not surprised that my guess was not on target given that
there are several possibilities for what could be causing the issue.

re:
> Here is what I have:
> 
> % echo $MCTABLE_WRITE
> /home/ldm/mcidas/data/MCTABLE.TXT
> 
> % more /home/ldm/mcidas/data/MCTABLE.TXT
> ADDE_ROUTE_NEXRCOMP=AUTAN.SCA.UQAM.CA
> ADDE_ROUTE_RTGRIDS=AUTAN.SCA.UQAM.CA
> HOST_AUTAN.SCA.UQAM.CA=132.208.132.64
> HOST_GOESSOUTH.UNIDATA.UCAR.EDU=128.117.156.12
> HOST_UNIDATA2.SSEC.WISC.EDU=128.104.110.130
> ADDE_ROUTE_RTGRIBS=LOCAL-DATA
> ADDE_ROUTE_RTGRIB2=LOCAL-DATA
> ADDE_ROUTE_RTGOESR=128.117.149.100
> ADDE_ROUTE_BLIZZARD=LOCAL-DATA
> ADDE_ROUTE_RTGOES16=LEAD.UNIDATA.UCAR.EDU
> ADDE_ROUTE_NPGOESR=LEAD.UNIDATA.UCAR.EDU
> HOST_LEAD.UNIDATA.UCAR.EDU=128.117.149.100
> HOST_ADDE.UCAR.EDU=128.117.114.120
> ADDE_ROUTE_RTGOESS=ADDE.UCAR.EDU
> HOST_LOCALHOST=127.0.0.1
> HOST_UWAMRC.SSEC.WISC.EDU=128.104.109.32
> ADDE_ROUTE_AMRC=UWAMRC.SSEC.WISC.EDU
> HOST_GOESEAST.UNIDATA.UCAR.EDU=128.117.12.26
> ADDE_ROUTE_EAST=GOESEAST.UNIDATA.UCAR.EDU
> HOST_ADDE.EUMETSAT.INT=193.17.10.4
> ADDE_ROUTE_EUM_AD=ADDE.EUMETSAT.INT
> HOST_SATEPSANONE.NESDIS.NOAA.GOV=13.225.189.113
> ADDE_ROUTE_PUB=SATEPSANONE.NESDIS.NOAA.GOV
> HOST_GOESWEST.UNIDATA.UCAR.EDU=128.117.156.14
> ADDE_ROUTE_WEST=GOESWEST.UNIDATA.UCAR.EDU
> ADDE_ROUTE_RTWXTEXT=LOCAL-DATA
> ADDE_ROUTE_GINICOMP=LOCAL-DATA
> ADDE_ROUTE_GINIEAST=LOCAL-DATA
> ADDE_ROUTE_GINIWEST=LOCAL-DATA
> ADDE_ROUTE_RTPTSRC=LOCAL-DATA
> ADDE_ROUTE_RTNEXRAD=LOCAL-DATA
> ADDE_ROUTE_CIMSS=LOCAL-DATA
> ADDE_ROUTE_RTIMAGES=LOCAL-DATA
> ADDE_ROUTE_MYDATA=LOCAL-DATA
> ADDE_ROUTE_TOPO=LOCAL-DATA

Hmm...  The pair of entries from this listing that is most interesting 
to me is:

ADDE_ROUTE_EAST=GOESEAST.UNIDATA.UCAR.EDU
HOST_GOESEAST.UNIDATA.UCAR.EDU=128.117.12.26

Why?

- the process(es) being run on autan.sca.uqam.ca are all accessing
  the EAST dataset

- goeseast.unidata.ucar.edu's IP is a virtual one on the same machine
  being pointed to by adde.ucar.edu

  I just made sure  that this statement is accurate by SSHing to
  goeseast.unidata.ucar.edu as 'mcidas' and then running 'hostname';
  doing the same but to adde.ucar.edu; and then pointing at
  goeseast.unidata.ucar.edu for the EAST dataset, doing an IMGLIST
  for EAST/FDC13.ALL, and then checking the ADDE log files on
  the backend machine, and seeing that it was, in fact the machine
  that got the ADDE request from me

So, this must mean that there is another file that has the EAST <-> IP
mapping that is being used in preference to MCTABLE.TXT.

The environment variable MCTABLE_READ can contain a semi-colon list
of files that will be searched for ADDE entries.  I am betting that
MCTABLE_READ in the environment in which your process is being run
will contain a file other than MCTABLE.TXT, and the name<->IP 
mapping for EAST in that file is still pointing at atm.ucar.edu.

re:
> But, looking for ATM.UCAR I get this in the mcidas account:
> 
> % grep ATM.UCAR ~mcidas/data/*
> 
> /home/mcidas/data/ADDEGRID.CORE:REM atm.ucar.edu
> /home/mcidas/data/ADDEGRID.CORE:RTGRIBS SERVERS=ADDE.SSEC.WISC.EDU 
> ATM.UCAR.EDU STRATUS.AL.NOAA.GOV ADDE.CISE-NSF.GOV ADDE.UCAR.EDU LOCAL-DATA
> /home/mcidas/data/ADDEGRID.CORE:RTGRIB2 SERVERS=ADDE.UCAR.EDU 
> ADDE.SSEC.WISC.EDU ATM.UCAR.EDU LOCAL-DATA
> /home/mcidas/data/ADDEGRID.CORE:RTGRIDS SERVERS=STRATUS.AL.NOAA.GOV 
> ADDE.SSEC.WISC.EDU ATM.UCAR.EDU ADDE.UCAR.EDU LOCAL-DATA

> /home/mcidas/data/ADDEIMAGE.CORE:CIMSS SERVERS=ATM.UCAR.EDU 
> ADDE.SSEC.WISC.EDU WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU 
> LEAD.UNIDATA.UCAR.EDU LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:GINICOMP SERVERS=ADDE.SSEC.WISC.EDU 
> ATM.UCAR.EDU WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU LEAD.UNIDATA.UCAR.EDU 
> LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:GINIEAST SERVERS=ADDE.SSEC.WISC.EDU 
> ATM.UCAR.EDU WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU LEAD.UNIDATA.UCAR.EDU 
> LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:GINIWEST SERVERS=ADDE.SSEC.WISC.EDU 
> ATM.UCAR.EDU WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU LEAD.UNIDATA.UCAR.EDU 
> LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:NEXRCOMP SERVERS=ADDE.SSEC.WISC.EDU 
> ATM.UCAR.EDU WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU LEAD.UNIDATA.UCAR.EDU 
> LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:RTIMAGES SERVERS=ADDE.SSEC.WISC.EDU 
> ATM.UCAR.EDU WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU LEAD.UNIDATA.UCAR.EDU 
> LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:TOPO SERVERS=ADDE.SSEC.WISC.EDU 
> WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU ATM.UCAR.EDU LEAD.UNIDATA.UCAR.EDU 
> LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:RTNEXRAD SERVERS=ATM.UCAR.EDU 
> ADDE.SSEC.WISC.EDU WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU 
> LEAD.UNIDATA.UCAR.EDU LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:RTTDWR SERVERS=ATM.UCAR.EDU 
> ADDE.SSEC.WISC.EDU WEATHER.RSMAS.MIAMI.EDU ADDE.UCAR.EDU 
> LEAD.UNIDATA.UCAR.EDU LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:GLOBAL SERVERS=ADDE.SSEC.WISC.EDU 
> ADDE.UCAR.EDU ATM.UCAR.EDU LEAD.UNIDATA.UCAR.EDU LOCAL-DATA
> /home/mcidas/data/ADDEIMAGE.CORE:RTGOESR SERVERS=ATM.UCAR.EDU 
> LEAD.UNIDATA.UCAR.EDU ADDE.UCAR.EDU
> /home/mcidas/data/ADDEIMAGE.CORE:NPGOESR SERVERS=ATM.UCAR.EDU 
> LEAD.UNIDATA.UCAR.EDU ADDE.UCAR.EDU

> /home/mcidas/data/ADDEPOINT.CORE:REM atm.ucar.edu
> /home/mcidas/data/ADDEPOINT.CORE:RTPTSRC SERVERS=ATM.UCAR.EDU 
> WEATHER.RSMAS.MIAMI.EDU STRATUS.AL.NOAA.GOV ADDE.UCAR.EDU LOCAL-DATA

> /home/mcidas/data/ADDETEXT.CORE:REM atm.ucar.edu
> /home/mcidas/data/ADDETEXT.CORE:RTWXTEXT SERVERS=WEATHER.RSMAS.MIAMI.EDU 
> ATM.UCAR.EDU ADDE.SSEC.WISC.EDU STRATUS.AL.NOAA.GOV ADDE.UCAR.EDU LOCAL-DATA

Assuming that the process that is still using atm.ucar.edu is not being run
from an interactive session (or is it?), I can say that the settings in
/home/mcida/data/ADDEIMAGE.CORE should not be used as they were designed
to be used during interactive McIDAS sessions.

re:
> Any advice on what to modify?

First, please give me a short description of how the process that is still
requesting data from atm.ucar.edu is running.  What I mean is:

- is it being run from an interactive session?

- is it being run from a script?

  If yes, how is the script being run (e.g., cron or the McIDAS scheduler)?

  If yes, can I take a look at the script?

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: BJE-146276
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.
Prev by Date: [McIDAS #CXH-788694]: Password for download McIDAS software no working
Next by Date: [McIDAS #CXH-788694]: Password for download McIDAS software no working
Previous by thread: [Staging #BJE-146276]: 20220917: ADDE use at UQAM
Next by thread: [Staging #BJE-146276]: 20220917: ADDE use at UQAM
Index(es):
- Date
- Thread