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

20010323: Unidata application installation at Valparaiso (cont.)

>From: Simon Kissler <address@hidden>
>Organization: Valparaiso
>Keywords: 200103231414.f2NEEhL25449 McIDAS-X ADDE

Simon,

>thanks for your quick response. To give you a quick run of where I am at:
>
>I have the ldm installed and it is apparently ingesting data as well as
>decoding data. I have installed the LDM-MCIDAS package.

Excellent.  I didn't quite know where things stood.

>I have also done the MCIDAS ADDE install. I seem to remember my
>LOCDATA.BAT file looking slightly different.

OK.  This may be due to a difference in the DATALOC.BAT file in the
distribution and the one that I am going to release in the next addendum.
We can deal with this later.

>To maybe give you a better idea of where this is at since I'm at least
>slightly confused on where I'm supposed to be picking up the ball at this
>point in time,

OK.

>I've set you up with an account on aeolus to help look around. 

Thanks.

>I would appreciate if you'd change the password upon login using the
>passwd command. Access via telnet and SSH2 is enabled thru our firewall.

Done.

Here is one thing that I ran into quickly.  I setup the login account
you gave me to run McIDAS.  When I try to run a McIDAS command, however,
I get an error:

[ 49 ] > dmap.k LOCDATA.BAT
ld.so.1: dmap.k: fatal: /opt/SUNWspro/lib/libF77.so.4: Permission denied
Killed

I traced this down to incorrect permissions on the /opt/SUNWspro/SC5.0/lib
directory:

ls -alt /opt/SUNWspro/SC5.0
total 24
drwxr-xr-x   3 bin      compilers    1024 Aug 17  2000 bin
drwxrwx---  16 bin      compilers    2560 Aug 17  2000 lib
drwxr-xr-x  21 bin      compilers     512 Jul 14  1999 ..
drwxrwx---   9 bin      compilers     512 Jun 29  1999 man
drwxr-xr-x  10 bin      compilers     512 Jun 29  1999 .
drwxr-xr-x   3 bin      compilers     512 Jun 29  1999 htmldocs
drwxrwx---   9 bin      compilers     512 Jun 29  1999 include
drwxr-xr-x   3 bin      compilers     512 Jun 29  1999 src
drwxrwx---   2 bin      compilers     512 Jun 29  1999 READMEs
drwxr-xr-x   3 bin      compilers     512 Jun 29  1999 examples

You can see from this list that the lib, man, include, and READMEs
directories do not allow global read access.  This means that the
average user (one not in the 'compilers' group) can not run programs
that need the shared libraries in /opt/SUNWspro/SC5.0/lib.

Aside from this, I took a cursory look at the McIDAS
ingestion/decoding, and it appears to be running correctly.  I am was
suprised by this given the read permissions on /opt/SUNWspro/SC5.0/lib
until I saw that both 'mcidas' and 'ldm' are in the same group as the
owner of the directories above.  Is there a reason that the permissions
on /opt/SUNWspro/SC5.0/lib are set they way that they are?

>Thank you very much for your help.

Are ports 500 and 503 enabled through your firewall?  If so, I will be
able to test remote ADDE services from Unidata (and my home account).
If not, I will need to get McIDAS to run from the login account you
gave me.  Better yet, it would be very helpful if I could get the
password for the 'mcidas' account so I can correct anything that is
amiss (if I find such instances).

One last comment on your current setup.  You can put both ldm-mcidas
and XCD decoded data files in the same directory.  This would make your
file REDIRECTions more simple, and make your directory structure
cleaner.  I.e., you could put everything into /var/data/mcidas.  Now is
the time to change the setup since no users are yet depending on it.

If you decide to do this, however, more is needed than just moving
files.  What you would have to do is:

o stop the LDM
o move all files from /var/data/xcd to /var/data/mcidas
o change ~mcidas/data/LOCAL.NAM entries from /var/data/xcd to /var/data/mcidas
o reset your file REDIRECTions in a McIDAS session as 'mcidas':

  REDIRECT REST LOCAL.NAM

o redefine the string XCDDATA in a McIDAS session as 'mcidas'
o reset LSSERVE.BAT defines from that same McIDAS session:

  BATCH LSSERVE.BAT

o restart the LDM

Tom