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

Re: Perl library error msg...

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: Re: Perl library error msg...
  • Date: Wed, 12 Jul 2000 10:13:07 -0600
"Patrick S. Market" wrote:

  Anne:

  There seems to be a problem with the ldm being able to find the
  appropriate libraries to run perl.  When I am logged on, I can run
dostats,
  scour, etc., but when the ldm is left on its own, the following
  error occurs; this is what was mailed to the ldm.  This happens
  every time one of the processes in the crontab runs.  The file I
  submit to the crontab is /usr/local/ldm/ldmcronjobs.

  Hope you had a good weekend.

  Pat

  Forwarded message:
  > From ldm Sat Jul  8 18:36:11 2000
  > Date: Sat, 8 Jul 2000 18:35:01 -0500 (CDT)
  > From: Local Data Manager <ldm>
  > Message-Id: <address@hidden>
  > To: ldm
  > Subject: Output from "cron" command
  > Content-Type: text
  > Sender: ldm
  > Content-Length: 213
  >
  > Your "cron" job on bergeron.snr.missouri.edu
  > /usr/local/ldm/bin/ldmadmin dostats
  >
  > produced the following output:
  >
  > ld.so.1: /usr/local/bin/perl: fatal: libgdbm.so.2: open failed: No such
file or directory
  > Killed
  >
  >
  >

"Patrick S. Market" wrote:

> Anne:
>
> In reference to my last mail, could it be that the
>
>    $ENV{'PATH'} =
>
> line in bin/ldmadmin  needs to be edited to include /usr/local/lib   ?
>
> That path is where the libgdbm.so.2 library resides.
>
> Thanks again.
>
> Pat
>
> --
> ========================================================================
> Dr. Patrick S. Market
> Dept. of Soil & Atmospheric Sciences
> University of Missouri-Columbia                 Phone:  (573) 882 - 1496
> 203 Gentry Hall                                 Fax:    (573) 884 - 5133
> Columbia, MO 65211 USA          E-mail: address@hidden
> ========================================================================

Hi Pat,

I had a great weekend - thanks!

No, setting the path for ldmadmin won't help.  It is perl that needs to
know where to find the library.

The environment variable LD_LIBRARY_PATH needs to be set correctly for perl
within the context of cron.  Unless you tell it otherwise, cron will use
some system path. You can tell it otherwise by setting the value within
your cron entry.   I.e, in your dostats cron entry, you can insert a
string, separated by a space, in front of the command field to set the
variable.  It might end up looking like this:

    # mail ldmstats and current data routings to UPC
    35 * * * * LD_LIBRARY_PATH=/usr/local/lib bin/ldmadmin dostats

Or, if necessary, you can append a path to the value of your current
LD_LIBRARY_PATH:

    # mail ldmstats and current data routings to UPC
    35 * * * * LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib bin/ldmadmin
dostats


Anne

--
***************************************************
Anne Wilson                     UCAR Unidata Program
address@hidden                  P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************