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.
Hi Tim, re: 'root' ownership of directory where LDM is to make its queue > Okay thanks! No worries. re: > However, now that I ran ldmadmin start then ldmadmin watch I get the > following and it doesn't change: > > (Type ^D when finished) This shows that you are not receiving data. The place to look for clues as to what is going on is the LDM log file, ~ldm/logs/ldmd.log. If this file does not exist or is zero length, it means that logging is not setup properly. re: > Also, when running ldmadmin check, I get the following: > > Checking for a running LDM system... > Checking the system clock... > > The system clock is more than 10 seconds off, which is specified by > registry parameter "/check-time/limit". > > You should either fix the problem (recommended) or disable time-checking > by executing the command "regutil -u 0 /check-time/enabled" (not > recommended). > > Is this a separate topic from the queue? Yes. The system clock on machines running LDMs should be kept accurate, and this is typically done by use of the 'ntpd' daemon. The LDM checks to see if your clock is within 10 seconds (by default) of being correct (as determined by 'ntpdate'), and if it is outside of this bound, you get informed. re: > Are these two problems related? No, not at all. 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: LRB-829354 Department: Support IDD Priority: Normal Status: Closed