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

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

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 #ROJ-852250]: Cron job can't reset LDM registry?
  • Date: Tue, 04 Apr 2017 13:44:02 -0600
Chris,

Odd.

There must be something in the difference between your crond(8) environment
and your user-shell environment that's causing the problem.

Try replacing the relevant LDM user's crontab(1) entries with these:

0 0 * * * bash -l -c 'ldmadmin newlog'
0 1 * * * bash -l -c 'ldmadmin scour' >/dev/null
0 2 * * * bash -l -c 'ldmadmin check' >/dev/null

The modifications should ensure that the environments are the same.

> There are no mentions of "regutil" in the log files.  I verified that it is
> still happening by running a cron job just now.

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.