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

Re: LDM upgrade

Gini,

>Date: Fri, 17 Jun 2005 11:11:36 -0500
>From: Virginia Galvin <address@hidden>
>To: Steve Emmerson <address@hidden>,
>To: Virginia Galvin <address@hidden>
>Subject: Re: LDM upgrade

The above message contained the following:

> Right now we plan to upgrade  Monday after 2pm EDT.
> But if we are delayed, will you still be around Tues and Wed?

I'll be available Monday, Tuesday, and Wednesday, except after 2 PM MDT
on Tuesday.

> Our current Queue is 2GB and pqmon reports:
> 
> nprods 167993
> nfree    4
> nempty  344003

The queue isn't limited by the number of slots.

> nbytes  2097147176

It's limited by the amount of available space in the data portion of the
queue.

> maxprods 252565
> maxfree 14
> minempty 259433

The maximum number of data-products in the queue only fill about half
the available slots.

> maxext 2840
> age 10697

Currently, the oldest product has been in the queue for slightly less
than 3 hours.

> Does that look like its big enuf?

Your queue is definitely big enough.

> I have the ldm 6.0.1 compiled and I think I just need to to do the 
> following?
> 
> su - ldm
> make install

I assume you mean 6.1.0 rather than 6.0.1.

You should be able to execute the above now without affecting a running
LDM -- assuming the directory structure is correct: any running LDM is
executing out of $HOME/runtime/bin and that link points to a non-6.1.0
directory.  See

    
http://my.unidata.ucar.edu/content/software/ldm/ldm-6.1.0/basics/preinstallation.html#subdirs

> su -
> make install_setuids (as root)

If the assumptions in the above paragraph are correct, then you can also
execute this step without affecting a running LDM.

> (Should I modify the startup on boot script? )

Probably.  Compare what you have with the example in the "LDM Basics"
webpages of the version 6.1.0 package:

    
http://my.unidata.ucar.edu/content/software/ldm/ldm-6.1.0/basics/configuring.html#boot

> su - ldm
> configure  ldmadmin  and ldmd.conf  (or can I  use the 6.0.14 versions?)

You should check the ldmadmin(1) script as described in the LDM Basics"
webpage for version 6.1.0.  See

    
http://my.unidata.ucar.edu/content/software/ldm/ldm-6.1.0/basics/vet-ldmadmin.html

You should probably reuse the LDM configuration-file, ldmd.conf.
Assuming that the $HOME/etc directory is an actual directory, this will
happen automatically.

> ldmadmin stop
> ln -s $VERSIONDIR runtime
> pqcheck -F   ( I dont need to recreate it unless there is an error?)

If the "ldmadmin stop" goes OK, then you don't need to execute the
"pqcheck -F" command unless the "ldmadmin start" command indicates a
problem (which is shouldn't).

> ldmadmin start
> ldmadmin watch

Yup.

Regards,
Steve Emmerson