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

20051209: Public ADDE server stratus.al.noaa.gov (cont.)



>From: Eirh-Yu Hsie <address@hidden>
>Organization: CU/CIRES NOAA/ESRL
>Keywords: 200512091601.jB9G1w7s009532 McIDAS Solaris 10

Hi Hsie,

re:
>You can ssh into cirrus then to hail (temporary 
>name). After I satisfy with the setup, I will switch the name to 
>stratus.  It seems work now, but I am not sure of it. If you can, please 
>take a look.  You can issue:
>
>% svcs
>
>to see the services.  "svc:/network/mcidas", "svc:/network/mcserv", and 
>"svc:/network/mccompress" are all online.

OK.  I was able to logon successfully.

Access to the remote ADDE server does not seem to work. Here is
what I did to ascertain this:

<login as 'mcidas'>
cd solaris/workdata

I found that the 'mcidas' account is looking at the remote adde
server on stratus for most datasets:

dataloc.k LIST
Group Name                    Server IP Address
--------------------         ----------------------------------------
AMRC                         UWAMRC.SSEC.WISC.EDU
BLIZZARD                     STRATUS.AL.NOAA.GOV
CIMSS                        STRATUS.AL.NOAA.GOV
GINICOMP                     STRATUS.AL.NOAA.GOV
GINIEAST                     STRATUS.AL.NOAA.GOV
GINIWEST                     STRATUS.AL.NOAA.GOV
GOESEAST                     STRATUS.AL.NOAA.GOV
ME7                          IO.SCA.UQAM.CA
MYDATA                       <LOCAL-DATA>
NEXRCOMP                     STRATUS.AL.NOAA.GOV
RTGRIDS                      STRATUS.AL.NOAA.GOV
RTIMAGES                     STRATUS.AL.NOAA.GOV
RTNEXRAD                     STRATUS.AL.NOAA.GOV
RTPTSRC                      STRATUS.AL.NOAA.GOV
RTWXTEXT                     STRATUS.AL.NOAA.GOV
TOPO                         STRATUS.AL.NOAA.GOV

<LOCAL-DATA> indicates that data will be accessed from the local data directory.
DATALOC -- done

This works OK showing that the code built under Solaris 10 is working.

I then verified that dataset definitions were setup on hail:

dsserve.k LIST RTIMAGES
Group/Descriptor         Type  Format & Range     RT Comment
------------------------ ----- ------------------ -- --------------------
RTIMAGES/ANTARCTIC       IMAGE AREA                  Antarctic IR Composite
                               
DIRFILE=/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_*
RTIMAGES/EDFLOATER-I     IMAGE AREA                  Educational Floater
                               DIRFILE=/wrk/data/sat/mcidas/GOES-*_fl1/*/*/*
RTIMAGES/EDFLOATER-II    IMAGE AREA                  Educational Floater II
                               DIRFILE=/wrk/data/sat/mcidas/GOES-*_fl2/*/*/*
RTIMAGES/GE-39           IMAGE AREA                  GOES-East Hemispheric Short
                                                      IR
                               
DIRFILE=/wrk/data/sat/mcidas/GOES-12/4km/3.9/3.9_*
RTIMAGES/GE-CO2          IMAGE AREA                  GOES-East Hemispheric CO2
                               
DIRFILE=/wrk/data/sat/mcidas/GOES-12/4km/13.3/13.3_*
RTIMAGES/GE-IR           IMAGE AREA                  GOES-East Hemispheric IR
                               DIRFILE=/wrk/data/sat/mcidas/GOES-12/4km/IR/IR_*
RTIMAGES/GE-IRTOPO       IMAGE AREA 220-229          GOES-East IR/TOPO Composite
RTIMAGES/GE-VIS          IMAGE AREA                  GOES-East Hemispheric VIS
                               
DIRFILE=/wrk/data/sat/mcidas/GOES-12/4km/VIS/VIS_*
 ...

I then verified that the data is in the directories specified in
the definitions above:

ls /wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_*
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051209_0000
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051209_0600
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051209_0900
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051209_1200
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051209_1800
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051209_2100
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051210_0000
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051210_0300
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051210_0600
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051210_0900
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051210_1200
/wrk/data/sat/mcidas/ANTARCTIC/4km/IR/IR_20051210_1500

Then I tried to point at the remote ADDE interface:

dataloc.k ADD RTIMAGES hail.al.noaa.gov

Group Name                    Server IP Address
--------------------         ----------------------------------------
RTIMAGES                     HAIL.AL.NOAA.GOV

<LOCAL-DATA> indicates that data will be accessed from the local data directory.
DATALOC -- done

Everything is good up until this point.  Interrogating the remote
server interface in any way, however, fails:

dsinfo.k IMAGE RTIMAGES
dsinfo.k: cannot run server 'lwprserv': No such file or directory
    No Datasets found of Type: IMAGE in Group: RTIMAGES
DSINFO -- done

imglist.k RTIMAGES/GE-IR
Image file directory listing for:RTIMAGES/GE-IR
imglist.k: cannot run server 'adirserv': No such file or directory
imglist.k: done


It looks like the configuation setup for the remote server access
is not correctly passing a '-H' flag whose value should be the
HOME directory of the mcadde account.  In fact, nothing is being
passed to the initial ADDE executable ~mcidas/solaris/bin/mcservsh.

I have hardwared things to work by modifying ~mcidas/solaris/bin/mcservsh:

TZ=GMT
export TZ

McINST_ROOT='/home/mcidas/solaris'

case $1 in
-H)     HOME="$2"
        shift
        shift

        [ -f "$HOME/.mcenv" ] &&
           . "$HOME/.mcenv"
        ;;

*)      # <<<<< UPC add 20051210 - for Solaris 10 >>>>>
        [ -f "$McINST_ROOT/.mcenv" ] &&
           . "$McINST_ROOT/.mcenv"
        ;;
esac

It would be much better, however, to figure out how the command line
options should be passed to mcservsh using svcs.

How did you setup the services on hail?

Cheers,

Tom
--
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.