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

chris,

What's the user-shell of your LDM user? bash(1)? tcsh(1)?

What's the output of the command "regutil | egrep 'data|scour'"?

> Our recent change to forcing the cron to call ldmadmin commands using bash
> has caused something else weird to happen.  The scour routine is not able
> to find any of our data directories.  I asked my system administrator
> (cc'd) about it and I've copied below what he tried.  Any ideas?
> 
> Thanks,
> Chris
> 
> ---------------------------------------------------------------
> One thing I did was to change the commands to use the full path to the
> binary ldmadmin, e.g. I changed:
> 
> 0 1 * * * bash -l -c 'ldmadmin scour' >/dev/null
> 
> to be:
> 
> 0 1 * * * bash -l -c '/local/ldm/bin/ldmadmin scour' >/dev/null
> 
> Don't know if that will correct the problem, but it's always good to
> specify a full path.
> 
> I tried running this from LDM's console:
> 
> (blizzard) /local/ldm > /bin/bash -l -c '/local/ldm/bin/ldmadmin watch'
> 
> And it seemed to work.
> 
> But when I tried to run the scour I saw the same errors you did:
> 
> (blizzard) /local/ldm > /bin/bash -l -c '/local/ldm/bin/ldmadmin scour'
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/acft: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/acft does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/airm: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/airm does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/csig: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/csig does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/drops: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/drops does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/idft: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/idft does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/images: No such file
> or directory
> 
> scour: directory ~ldm/data/gempak/images does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/isig: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/isig does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/jason: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/jason does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/model: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/model does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/mos: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/mos does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/nldn: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/nldn does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/nwx: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/nwx does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/rdf: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/rdf does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/scd: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/scd does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/ship: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/ship does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/ship6hr: No such file
> or directory
> 
> scour: directory ~ldm/data/gempak/ship6hr does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/storm: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/storm does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/surface: No such file
> or directory
> 
> scour: directory ~ldm/data/gempak/surface does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/syn: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/syn does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/taf: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/taf does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: *~ldm/data/gempak/upperair*: No such
> file or directory
> 
> scour: directory ~ldm/data/gempak/upperair does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/logs: No such file or directory
> 
> scour: directory ~ldm/logs does not exist, skipping
> 
> /local/ldm/bin/scour: line 119: cd: ~ldm/data/gempak/logs: No such file or
> directory
> 
> scour: directory ~ldm/data/gempak/logs does not exist, skipping
> 
> But when I switched to a bash shell, and did a cd into one of the
> directories, I did NOT get an error:
> 
> (blizzard) /local/ldm > bash
> 
> [ldm@blizzard ~]$ pwd
> 
> /local/ldm
> 
> [ldm@blizzard ~]$ cd *~ldm/data/gempak/upperair*
> 
> [ldm@blizzard upperair]$ pwd
> 
> /local/ldm/data/gempak/upperair
> 
> [ldm@blizzard upperair]$

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ROJ-852250
Department: Support LDM
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.