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.
Hi Christian, re: > Sorry for my very long delay to reply... I have to apologize for not being able to respond to your email before now... yesterday was a very busy day for me... re: MCTABLE_READ and MCTABLE_WRITE > Yes, I have this: > MCTABLE_WRITE=/home/ldm/mcidas/data/MCTABLE.TXT > MCTABLE_READ=/home/ldm/mcidas/data/MCTABLE.TXT;/home/mcidas/data/ADDESITE.TXT > > and looking at ADDESITE.TXT: > more /home/mcidas/data/ADDESITE.TXT > ADDE_ROUTE_RTTDWR=LOCAL-DATA > HOST_SIROCCO=132.208.132.175 > ADDE_ROUTE_CIMSS=LOCALHOST > ADDE_ROUTE_GINICOMP=LOCALHOST > ADDE_ROUTE_GINIEAST=LOCALHOST > ADDE_ROUTE_GINIWEST=LOCALHOST > ADDE_ROUTE_NEXRCOMP=LOCALHOST > ADDE_ROUTE_RTIMAGES=LOCALHOST > ADDE_ROUTE_RTNEXRAD=LOCALHOST > ADDE_ROUTE_RTPTSRC=LOCALHOST > ADDE_ROUTE_RTWXTEXT=LOCALHOST > HOST_LOCALHOST=127.0.0.1 > ADDE_ROUTE_TOPO=LOCALHOST > 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.198.99 > 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_MYDATA=LOCAL-DATA > > I checked the IP and they all seem to point at the correct machine, but > maybe I am mistaken. I see the entries for GOESEAST: ADDE_ROUTE_EAST=GOESEAST.UNIDATA.UCAR.EDU HOST_GOESEAST.UNIDATA.UCAR.EDU=128.117.12.26 I just did an 'nslookup goeseast.unidata.ucar.edu' and the output was: % nslookup goeseast Server: 128.117.64.44 Address: 128.117.64.44#53 Non-authoritative answer: Name: goeseast.unidata.ucar.edu Address: 128.117.135.119 Given this, HOST_GOESEAST.UNIDATA.UCAR.EDU's value needs to be changed to: HOST_GOESWEST.UNIDATA.UCAR.EDU=128.117.135.119 In a previous email, you listed the contents of your MCTABLE.TXT file, and a lookup on the name seemed matched the entry in the file. If this is correct, it should mean that DNS for the name has been changed or updated to have the current value from 'nslookup'. I tested the current name lookup by SSHing to goeseast.unidata.ucar.edu and then running 'hostname', and using both the name and IP address worked. Given this, I think that the HOST_GOESWEST.UNIDATA.UCAR.EDU entry in both MCTABLE.TXT and ADDESITE.TXT need to be updated. re: how is your process being run > It is run by cron... so not interactive. OK. That's what I thought would be the case. > It is run by cron: > 01,11,21,31,41,51 * * * * sc/do_g16 > logs/do_g16.out 2> logs/do_g16.err > 03,13,23,33,43,53 * * * * sc/do_g17 > logs/do_g17.out 2> logs/do_g17.err Hmm... is the cron-run script being run as 'mcidas' or some other user. I just want to make sure that the appropriate MCTABLE_READ files are being checked. re: > I have them in attachment! Thanks. According to do_g16, the script that does the McIDAS stuff is 'make_g16'. you attached 'do_g16' and 'do_g17': DATADIR=/home/httpd/html/satellite MCIDASDIR=$HOME/mcidas/data WORK=$HOME/mcidas/work_$$ mkdir $WORK cd $WORK $HOME/sc/make_g16 Could you send the 'make_g16' 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.