[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20031111: ADDE on new server (cont.)
- Subject: 20031111: ADDE on new server (cont.)
- Date: Tue, 11 Nov 2003 13:02:57 -0700
>From: "Thomas L. Mote" <address@hidden>
>Organization: University of Georgia
>Keywords: 200311110119.hAB1JnOb008399 McIDAS ADDE Linux compess
Hi Tom,
>I copied and pasted the .mcenv from your message.
OK. I am now able to interrogate the ADDE remote server on cacimbo
using port 503 (compress transfers):
DSINFO P RTPTSRC
Dataset Names of Type: POINT in Group: RTPTSRC
Name NumPos Content
------------ ------ --------------------------------------
AIRCRAFT 10 Real-Time Aircraft data
ETAMOS 10 Real-Time ETA Model Output Statistics
FOUS14 10 Real-Time FOUS14 data
GFSMOS 10 Real-Time ETA Model Output Statistics
LIGHTNING 10 Real-Time Lightning data
PROF6MIN 10 Real-Time 6-Minute Profiler data
PROFHOURLY 10 Real-Time Hourly Profiler data
PTSRCS 120 All point data in MDXX files
SFCHOURLY 10 Real-Time SFC Hourly
SHIPBUOY 10 Real-Time Ship and Buoy data
SYNOPTIC 10 Real-Time SYNOPTIC data
UPPERMAND 10 Real-Time Upper Air (Mandatory)
UPPERSIG 10 Real-Time Upper Air (Significant)
DSINFO -- done
Furthermore, I did a plot of surface temperatures and it worked fine:
SF 12
BATCH MN 12 LALO X CONF X NO "BKGMAP.BAT
SFCPLOT T OLAY LATEST 2003310 GRA=12 BLANK=NO LSIZE=6 DAT=RTPTSRC/SFCHOURLY
SF=YES
Feeling bold, I pointed my McIDAS session at cacimbo for virtually all of
its data. Here are the results
CIMSS - did not work
GINICOMP - did not work (UGAGINI.BAT still to be modified and run)
GINIEAST - did not work (UGAGINI.BAT still to be modified and run)
GINIWEST - did not work (UGAGINI.BAT still to be modified and run)
NEXRCOMP - worked
RTGRIDS - worked
RTIMAGES - did not work
RTNEXRAD - worked
RTWXTEXT - worked
TOPO - worked
The failure of CIMSS and RTIMAGES is likely to be caused by the same
thing. The failure for GINIxxxx is due to the changes needed in
UGAGINI.BAT.
>I am also
>asking again about the firewall and port 500. I was told that it
>was opened, along with 112, 503 and 388.
Well, access through port 503 is working, and that is the most commonly
used interface (compress transfers, that is). Why port 500 access is not
working is a mystery to mee at the moment.
Has /etc/hosts.allow and/or /etc/hosts.deny been setup to deny access?
Have TCP wrappers been setup/partially setup?
Tom