20030803: Solaris 9 support for Unidata packages (cont.)

>From: Simon Kissler <address@hidden>
>Organization: Valparaiso University
>Keywords: 200306161917.h5GJHQLd025665

Simon, et. al.,

re:
>at this time the server has been upgraded to Solaris 9 and from anything
>we can tell is fully operational. You may start your work whenever it is
>convenient. If you have any problems, please let us know (respond to all)
>and we will be happy to assist in any way possible.

I logged onto aeolus this afternoon and did all but the last step of
the LDM-6.0.14 installation.  As soon as the remaining step is finished
(needs to be done as 'root'), I will cut over to the new LDM and then
upgrade McIDAS to the v2003 release (the McIDAS upgrade will involve
deleting a number of data files since they were likely damaged; see
comments below for comments on /var/data having filled).

Here is what needs to be done as 'root':

cd /home/ldm/ldm-6.0.14/src
/usr/ccs/bin/make install_setuids

While logged on as 'root', please also do the following:

cd /home/ldm
rm -rf ldm-5.1.3

I tried to remove this directory tree as 'ldm', but it is owned by
'root', so I didn't have permission.

A quick comment before I log off for this evening.  When I got on this
afternoon, the /var/data file system was 100% full.  I found that this
was due to the /var/data/ldm/gempak/nport/SOUNDER subdirectories had
not been scoured since last October.  I removed the subdirectories (it
was the quickest way to free up the space) and added a scouring action
to the crontab for 'ldm'.  You now have almost 30 GB of disk free
in /var/data:

/dev/dsk/c0t1d0s0    35009161 3332780 31326290    10%    /var/data

I also modified the pqact.conf entries to set logging to
~ldm/logs/ldm-mcidas.log* for the various ldm-mcidas decoders that are
running and setp rotation of these and the LDM log files.  Along with
this modification, I took the liberty of upgrading your ldm-mcidas
decoders to the latest distribution, ldm-mcidas-2003.  I did this _not_
by installing the new distribution in /usr/local/ldm-mcidas, but,
rather, by unpacking the distribution in ~ldm and then copying the
relevant decoders from ~ldm/ldm-mcidas-2003/bin to ~ldm/decoders and
the ~ldm/ldm-mcidsa-2003/etc files SATANNOT and SATBAND to ~ldm/etc.
This is now the recommended way to use the ldm-mcidas decoders, so your
setup now matches many other users.  I recommend that you remove
the /usr/local/ldm-mcidas directory hierarchy since it is no
longer used.

That's it for this evening.  I will log back on tomorrow to finish
the LDM upgrade (after the above work by 'root') and then tackle
McIDAS.

>Thanks,

No worries.

Tom

From: Unidata Support <support@-u>

Bill,

>Sounds like everything is up to speed then?

More or less.  I just tried to get on aeolus to finalize the McIDAS
installation, but I can't seem to get to it.  Any idea of what may be
up?  A traceroute from UCAR to aeolus shows that the problem is
somewhere at or near Valparaiso:

% traceroute aeolus.valpo.edu
trying to get source for aeolus.valpo.edu
source should be 128.117.140.45
traceroute to aeolus.valpo.edu (152.228.34.180) from 128.117.140.45 
(128.117.140.45), 30 hops max
outgoing MTU = 1500
 1  flra-n140 (128.117.140.252)  2 ms  1 ms  1 ms
 2  gin-n243-80.ucar.edu (128.117.243.81)  1 ms  1 ms  1 ms
 3  64.140.70.213 (64.140.70.213)  3 ms  2 ms  2 ms
 4  170.147.161.94 (170.147.161.94)  3 ms  3 ms  3 ms
 5  199.183.38.121 (199.183.38.121)  28 ms  28 ms  28 ms
 6  peer03.sji-ca.icg.net (170.147.129.5)  29 ms  28 ms  28 ms
 7  114.ATM1-0.BR2.SJC1.ALTER.NET (204.255.174.61)  29 ms  29 ms  29 ms
 8  154.ATM3-0.XR1.SJC1.ALTER.NET (152.63.51.174)  30 ms  30 ms  29 ms
 9  0.so-0-0-0.XL1.SJC1.ALTER.NET (152.63.55.114)  30 ms  30 ms  30 ms
10  0.so-3-0-0.TL1.SAC1.ALTER.NET (152.63.53.250)  33 ms  33 ms  33 ms
11  0.so-6-0-1.TL1.CHI4.ALTER.NET (152.63.1.141)  74 ms  74 ms  74 ms
12  0.so-7-0-0.CL1.IND6.ALTER.NET (152.63.64.66)  83 ms  83 ms  83 ms
13  191.ATM7-0.GW4.IND1.ALTER.NET (152.63.66.65)  83 ms  83 ms  83 ms
14  valpoedu-gw.customer.alter.net (65.195.245.234)  88 ms  87 ms  86 ms
15  * * *
16  * * *
17  * * *
18  * * *
 ...

>Simon has taken care of the root issues with McIDAS.

The 'root' issues I ran into were with 'ldm', not 'mcidas', and Simon
did take care of those.

>I upgraded GEMPAK this afternoon.

Sounds good.

>Anything else to take care of?

Yes.  I need to do a couple of more small things to the McIDAS v2003
installation that I started last night and almost finished this
morning.  I did a number of things during the upgrade like:

- wipe out the 7.8 and 7.8 installations

- change the XCD decoding from /var/data/mcidas (and /var/data/xcd which
  was a link to /var/data/mcidas) to /var/data/ldm/mcidas; this is now
  parallel to the GEMPAK data storage

- update file REDIRECTions to reflect the fact that location of the data
  directory moved

- update ADDE dataset definitions to include new dataset elements introduced
  in v2003

- modified ~ldm/decoders/mcscour.sh to scour new data files produced
  by v2003

- truned back on compositing of GOES-East and GOES-West imagery and
  imagery with topographic images

- installed the BLIZZARD training dataset in ~mcidas/data/tutorial and
  changed the ADDE pointing for the user 'mcidas' to look locally for
  this dataset instead of looking at a remote server not on the
  Valparaiso campus

During the process of updating LDM and McIDAS, I had occasion to wipe
out a lot of very old data files and free up a considerable amount of
disk space.  Before I pronounce my work done, I want to observe things
for a few days to make sure that all of the 'T's have been dotted ;-)

>Thanks,

No worries...

Tom
**************************************************************************** <
Unidata User Support                                    UCAR Unidata Program <
(303)497-8643                                                  P.O. Box 3000 <
address@hidden                                   Boulder, CO 80307 <
---------------------------------------------------------------------------- <
Unidata WWW Service              http://my.unidata.ucar.edu/content/support  <
**************************************************************************** <