[LDM #ROJ-852250]: Cron job can't reset LDM registry?

Hi Chris,

re:
> After the changes and a couple of days of quiet, we changed to crontab to
> send the output of the "ldmadmin scour" job to our email and discovered
> that the same issue persists:
> 
> ---------- Forwarded message ----------
> From: LDM User <address@hidden>
> Date: Sun, Apr 16, 2017 at 9:00 PM
> Subject: LDM scour output
> To: address@hidden, address@hidden
> 
> 
> scour: directory ~ldm/data/gempak/acft does not exist, skipping
> scour: directory ~ldm/data/gempak/airm does not exist, skipping
> scour: directory ~ldm/data/gempak/csig does not exist, skipping
> scour: directory ~ldm/data/gempak/drops does not exist, skipping
> scour: directory ~ldm/data/gempak/idft does not exist, skipping
> scour: directory ~ldm/data/gempak/images does not exist, skipping
> scour: directory ~ldm/data/gempak/isig does not exist, skipping
> scour: directory ~ldm/data/gempak/jason does not exist, skipping
> scour: directory ~ldm/data/gempak/model does not exist, skipping
> scour: directory ~ldm/data/gempak/mos does not exist, skipping
> scour: directory ~ldm/data/gempak/nldn does not exist, skipping
> scour: directory ~ldm/data/gempak/nwx does not exist, skipping
> scour: directory ~ldm/data/gempak/rdf does not exist, skipping
> scour: directory ~ldm/data/gempak/scd does not exist, skipping
> scour: directory ~ldm/data/gempak/ship does not exist, skipping
> scour: directory ~ldm/data/gempak/ship6hr does not exist, skipping
> scour: directory ~ldm/data/gempak/storm does not exist, skipping
> scour: directory ~ldm/data/gempak/surface does not exist, skipping
> scour: directory ~ldm/data/gempak/syn does not exist, skipping
> scour: directory ~ldm/data/gempak/taf does not exist, skipping
> scour: directory ~ldm/data/gempak/upperair does not exist, skipping
> scour: directory ~ldm/logs does not exist, skipping
> scour: directory ~ldm/data/gempak/logs does not exist, skipping
> 
> 
> The if statement beginning at line 119 in scour is returning false:
> 
> if edir=`cd "$dir" && /bin/pwd`; then
> : true
> else
> $LOGGER "directory $dir does not exist, skipping"
> continue
> 
> I've verified that the directories ($dir) exist so why would '/bin/pwd'
> cause the statement to be false?

I really don't know, sorry.

To see if the problem was in how the directory was specified in the
'scour' configuration file, ~ldm/etc/scour.conf, I replicated all
of the active entries (those that did not have a beginning '#'
character), and changed them to use absolute directory locations.

For example:

change:

~ldm/data/gempak/acft

to:

/data/local/ldm/gempak/acft

I also got rid of the Optional-filename-pattern setting on all entries
except that for the /data/local/ldm/logs entry.

Let's see if this has any effect.

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: ROJ-852250
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.