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

[LDM #LTH-656578]: decoders

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #LTH-656578]: decoders
  • Date: Tue, 21 Feb 2012 08:05:57 -0700
Hi Marty,

re: directory containing binaries are in PATH?

> Yes.

OK, I had to ask :-)

re: verify that they can run on the new machine?

> ldd ~ldm/decoders/dcgrib2
> 
> linux-vdso.so.1 =>  (0x00007fffebbff000)
> libgfortran.so.1 => not found
> libm.so.6 => /lib64/libm.so.6 (0x00000030c4800000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000030cf000000)
> libc.so.6 => /lib64/libc.so.6 (0x00000030c3c00000)
> /lib64/ld-linux-x86-64.so.2 (0x00000030c3800000)
> 
> I noticed the fortran library missing, so I grabbed the dcgrib2 and other
> dc* binaries from the gempak install with the following result.

Was the "gempak install" made on the target machine?  This would be my
recommendation in any case as it would eliminate questions about shared
library availability/mismatch.

re:
> I believe
> that it is a step in the right direction, but it has not resolved the issue.

It is definitely a step in the right direction.

re: version of the LDM running on your "old" machine?

> 6.1.01

I assume you mean 6.10.1.

re: What does the following look like: ls -alt ~ldm/var

> ls -alt ~ldm/var
>
> total 8
>
> drwxr-xr-x. 15 ldm ldm 4096 Feb 21 02:36 ..
> drwxrwxr-x.  2 ldm ldm 4096 Feb 20 17:10 .
> lrwxrwxrwx.  1 ldm ldm   19 Feb 20 17:10 logs -> /usr/local/ldm/logs
> lrwxrwxrwx.  1 ldm ldm   19 Feb 20 17:10 queues -> /usr/local/ldm/data
> lrwxrwxrwx.  1 ldm ldm   19 Feb 20 17:10 data -> /usr/local/ldm/data

OK, this is what is expected when:

- the HOME directory for the user 'ldm' is /usr/local/ldm
- one has done an upgrade of a pre-LDM 6.9.x+ to a post
  LDM-6.9.x+ installation

Given this, what is the output from:

ls -alt /usr/local/ldm/data

Also, what does the dcgrib2 log file indicate?

This should be located in the data/gempak/logs directory.  The
question remains as to where this directory really is... I suspect
that it may be /usr/local/ldm/data/data/gempak/logs, but this is
just a guess.

Last question for now:

- what was the setting of the environment variable LDMHOME when
  LDM-6.10.1 was built?

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: LTH-656578
Department: Support LDM
Priority: Normal
Status: Closed