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.
andrew farnsworth wrote: > > Hi Anne > I am trying your suggestions now. To answer your questions, we are only > receiving hourly products - I can confirm this from our recent CD burns and > from the drive directory structure. Second, I cannot ~ldm/logs without > receiving the message "permission denied" or no such file or directory. > Third, I am going to try your suggestions as far as winnowing the pqact to > see whether or not everything is working correctly in terms of the feed > (which seems to be okay as far as I can tell from what scrolls on the > screen). > > Also, when I tried to change the pqact and did the pqactHUP, that worked > fine. But ldmadmin tail returned the message "cannot open input." What is > that about? > > Thanks! > Andrew > Good Morning, Andrew! It sounds like you don't have a log file. See http://www.unidata.ucar.edu/packages/ldm/ldmPreInstallList.html#s14. This section shows you the directory structure we recommend. Under ~ldm there should be a directory called logs. (Maybe yours was set up in a different place??) In there, the log that the ldm writes to is 'ldmd.log'. Usually logs are rotated via a cron job that invokes 'ldmadmin newlog'. (See http://www.unidata.ucar.edu/packages/ldm/ldmConfigInstallList.html#s8 for how to set this up.) By default the last four logs are kept in addition to ldmd.log. Logging is essential - it's the best way to know what the ldm is doing, and it's the only way for it to tell you if there's a problem. Be sure that your logging is working. See http://www.unidata.ucar.edu/packages/ldm/ldmPreInstallList.html#s8, especially the section on what to add to /etc/syslog.conf for instructions on how to get the syslog daemon to log ldm messages to ldmd.log. You can tell if logging is working when 'ldmadmin log' or 'ldmadmin tail' shows you the contents of the log. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************